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-x postfix/master[2468]: terminating on signal 15
Mar 10 18:15:29 ip-x postfix/master[3086]: daemon started -- version
2.7.0, configurat
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 "[...]"
Noel,
Thank you. It confirms the theory that postfix is not aware of the
settings for smtpd_milters
~$ sudo postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
default_transport = aws-email
inet_protoco
On 3/10/2012 9:57 AM, Antony wrote:
> Hi all,
>
> I am currently running into some issues with Postfix on my Amazon
> EC2 instance, not talking to OpenDKIM milter (also running on the
> same box). I believe Postfix isn't following
> smtpd_milters/non_smtpd_milters parameters. The reason is that no
Hi all,
I am currently running into some issues with Postfix on my Amazon EC2
instance, not talking to OpenDKIM milter (also running on the same box).
I believe Postfix isn't following smtpd_milters/non_smtpd_milters
parameters. The reason is that no matter what port number I use (even
non-wo
