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_protocols = all
mailbox_size_limit = 0
mydestination = e.coudora.com, coudora.com, localhost.ec2.internal,
localhost
myhostname = coudora.com
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
myorigin = /etc/mailname
readme_directory = no
recipient_delimiter = +
relayhost = email-smtp.us-east-1.amazonaws.com
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtpd_use_tls = yes
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
On 3/10/12 10:39 AM, Noel Jones wrote:
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
matter what port number I use (even non-working/non-listening port),
Postfix doesn't complain in the mail.log. It simply picks up the
mail and delivers without contacting milters. Here is the sample
request in the log
Show "postconf -n" output.
