-Original Message-
>2.6.6, though many years past EOL, is indeed later than 2.6, so WHEN [the
>listed headers are] NOT >PRESENT they are added ONLY WHEN CLIENTS MATCH THE
>local_header_rewrite_clients >PARAMETER SETTING. That's the default setting
>of "no" for always_add_missing_head
al_header_rewrite_clients
parameter?
Thank you for your time,
Aaron
---
Aaron Bennett
Manager of Systems Administration
Clark University ITS
> -Original Message-
> From: owner-postfix-us...@postfix.org [mailto:owner-postfix-
> us...@postfix.org] On Behalf Of Wietse Venema
> Sent: Wednesday, January 8, 2014 4:13 PM
> To: Postfix users
> Subject: Re: transport rule question
> Postfix would defer when it receives no DNS reply.
>
prefer it to defer. I'm not sure why it's not deferring - is it the relay:
line, or the [] enclosure, or something else?
Thanks for your time,
Aaron
---
Aaron Bennett
Manager of Systems Administration
Clark University ITS
W:508.793.7315
B may be the cause. I'm going to disable window
scaling on one of our three relays and see if it crops up again on the other
two.
Thanks,
Aaron
---
Aaron Bennett
Manager of Systems Administration
Clark University ITS
hough this
isn't verification related.
Anyone hear of this before? It's probably Exchange's fault not postfix. It
doesn't happen enough to be a huge problem but it's maddening all the same.
Thanks,
Aaron
---
Aaron Bennett
Manager of Systems Administration
Clark University ITS
Look at rsyslog -- it's a syslog daemon (that you might use and not know, it's
the native one in a lot of distros). It can log directly to MySQL..
http://www.techrepublic.com/blog/opensource/set-up-rsyslog-to-store-syslog-messages-in-mysql/1174
---
Aaron Bennett
Manager
will
still try to send mails to it as they are DNS RR'ed, but would get no response
ofcause if they hit the dead one.
(How) Do I handle this ? or will I just have to live with the time-loss,
clients connecting to dead postfix server, gives me when it has to retry ?
----
[Aaron Bennett]
Or
/postfix start
{ watch /var/spool/maildrop until it empties out }
$ setenforce enforcing
( the postfix restart is not needed; I just wanted to make sure I triggered a
maildrop run as quickly as possible so I could spend the least amount of time
in SELinux permissive mode. )
Best,
Aaron
---
Aaron Bennett
Manager of Systems Administration
Clark University ITS
oft_bounce = no
strict_rfc821_envelopes = yes
transport_maps = hash:/etc/postfix/transport,
proxy:ldap:/etc/postfix/ldap-transport.cf
undisclosed_recipients_header = To: "Undisclosed Recipients"
virtual_alias_maps = proxy:ldap:/etc/postfix/ldap-alias.cf
---
Aaron Bennett
Manager of Systems Administration
Clark University ITS
Ralf Hildebrandt wrote:
default_rbl_reply = $rbl_code Service unavailable; $rbl_class
[$rbl_what] blocked using $rbl_domain${rbl_reason?; $rbl_reason} --
Contact [EMAIL PROTECTED] for whitelisting
and rbl_code is what you're looking for
OTOH:
# postconf rbl_code
postconf: warning: rbl_code: un
"reject... 554 5.7.1" in
the logs and clients are still getting bounce'd instead of retry'd.
I'm sure I'm doing something stupid. At least one thing... maybe more!
Thanks for your time,
Aaron Bennett
Clark University ITS
Wietse Venema wrote:
To apply smtpd_recipient_restrictions when mail arrives via the
/usr/bin/sendmail command, this solution was posted a few days ago:
To force sendmail command-line submissions through the SMTP server,
use this:
Thank you.
Ralf Hildebrandt wrote:
sendmail != smtpd
thus smtpd_recipient_restrictions don't apply
understood. Nonetheless, do you know of a way to prevent users from
using sendmail to send to a particular recipient, besides an ugly hack
like aliasing the recipient to /dev/null or something?
ers
sits in the incoming queue for quite a while and then in the active
queue for quite a while as well.
Any tips? The hardware is sufficient to run almost any number of smtp
or local processes if that is what's required.
thanks,
Aaron Bennett
# postconf -n
alias_database = hash:/etc/
Magnus Bäck wrote:
Does that go in $alias_maps or $virtual_alias_maps?
This particular example is meant for virtual aliases, but if you adjust
it so that it expects the lookup key to be the bare username it'll work
with local aliases as well.
Thank you, that works.
Magnus Bäck wrote:
Set up an alias on the following form:
[EMAIL PROTECTED][EMAIL PROTECTED],[EMAIL PROTECTED]
In your LDAP map configuration this could translate to something like:
query_filter = mail=%s
result_attribute = mail, mailForwardingAddress
Does that go in $al
ap.
I know I'm missing out on some easy way to do this.
Thanks,
Aaron Bennett
18 matches
Mail list logo