Noel,
Yes, thank you! I shouldn't have used vim to edit the file directly. Had
I used postconf -e, it would have save me the pain.
Mar 10 18:15:29 ip-xxxxx postfix/master[2468]: terminating on signal 15
Mar 10 18:15:29 ip-xxxxx postfix/master[3086]: daemon started -- version
2.7.0, configuration /etc/postfix
Mar 10 18:16:48 ip-xxxxx postfix/smtpd[3093]: connect from
localhost[127.0.0.1]
Mar 10 18:16:48 ip-xxxxx postfix/smtpd[3093]: E9EA1982F0:
client=localhost[127.0.0.1]
Mar 10 18:16:49 ip-xxxxx postfix/cleanup[3098]: E9EA1982F0:
message-id=<1331403408.4f5b9a90949ea@swift.generated>
Mar 10 18:16:49 ip-xxxxx opendkim[1802]: E9EA1982F0 "DKIM-Signature"
header added
Mar 10 18:16:49 ip-xxxxx postfix/qmgr[3089]: E9EA1982F0:
from=<i...@coudora.com>, size=907, nrcpt=1 (queue active)
Mar 10 18:16:49 ip-xxxxx postfix/smtpd[3093]: disconnect from
localhost[127.0.0.1]
Mar 10 18:16:49 ip-xxxxx postfix/pipe[3099]: E9EA1982F0:
to=<sunnydeli...@umich.edu>, relay=aws-email, delay=0.59,
delays=0.13/0.01/0/0.46, dsn=2.0.0, status=sent (delivered via aws-email
service)
Mar 10 18:16:49 ip-xxxxx postfix/qmgr[3089]: E9EA1982F0: removed
On 3/10/12 11:43 AM, Noel Jones wrote:
On 3/10/2012 11:20 AM, Antony wrote:
Noel,
Thank you. It confirms the theory that postfix is not aware of the
settings for smtpd_milters
~$ sudo postconf -n
relayhost = email-smtp.us-east-1.amazonaws.com
Typically (but not always) the relayhost should be enclosed in
brackets "[...]" to disable MX lookups.
But I still don't know why it doesn't read the setting. I am going
to try to re-arrange the config order..maybe something overrides the
setting :/
Antony
The order doesn't matter unless you've added a parameter twice (not
the case this time since it would still show up).
Probably a typo in main.cf, possibly unprintable characters in the
parameter name. Make sure to use a plain-text only editor such as
vi, or edit main.cf automatically with postconf using a command like
postconf -e 'smtpd_milters=inet:inet:127.0.0.1:1234'
man postconf for details.
-- Noel Jones
