[Workaround.org] Client host rejected problem
Dominique Lauer
dlauer at uni-potsdam.de
Mon Mar 15 16:37:02 CET 2010
Hey guys!
I have a problem with my mailserver.
I set up a mailserver using the ISPmail tutorial for Debian Lenny.
Until I reached the page with the amavis configuration, everything
worked fine for me.
After that, the testmail couldn't be delivered anymore and the
mail.log read like this:
postfix/smtpd[3515]: connect from vs5513.xxx.de[xx.xx.xx.xx]
postfix/smtpd[3515]: NOQUEUE: reject: CONNECT from
vs5513.xxx.de[xx.xx.xx.xx]: 554 5.7.1 <vs5513.xxx.de[xx.xx.xx.xx]>:
Client host rejected: Access denied; proto=SMTP
amavis[2132]: (02132-04) (!)FWD via SMTP: <john at example.com> ->
<test at yyy.de>, 451 4.5.0 From MTA([127.0.0.1]:10025) during
fwd-connect (Negative greeting: 554 5.7.1
<vs5513.xxx.de[xx.xx.xx.xx]>: Client host rejected: Access denied at
(eval 84) line 555, <GEN27> line 135.): id=02132-04
amavis[2132]: (02132-04) Blocked MTA-BLOCKED, [xx.xx.xx.xx]
[77.37.17.46] <john at example.com> -> <test at yyy.de>, Message-ID:
<20100315145205.365CF7E5D at vs5513.xxx.de>, mail_id: Z+IC0ak3VSBE, Hits:
8.311, size: 372, 168 ms
postfix/smtpd[3515]: disconnect from vs5513.xxx.de[xx.xx.xx.xx]
postfix/smtp[3409]: 365CF7E5D: to=<test at yyy.de>,
relay=127.0.0.1[127.0.0.1]:10024, delay=13, delays=13/0/0/0.17,
dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0
From MTA([127.0.0.1]:10025) during fwd-connect (Negative greeting:
554 5.7.1 <vs5513.xxx.de[xx.xx.xx.xx]>: Client host rejected: Access
denied at (eval 84) line 555, <GEN27> line 135.): id=02132-04 (in
reply to end of DATA command))
postfix/smtpd[3460]: disconnect from vs5513.xxx.de[xx.xx.xx.xx]
(Where xx.xx.xx.xx is my server's external IP)
Without amavis running the same problem occured.
So I tried whitelisting my server IP with 'check_client_access' but
that didn't work either.
Also commenting out smtpd_recipient_restrictions was not helping.
When I delete the lines which were added for amavis to work everthing
works fine again, so it has to have something to do with that
connection.
First amavisd also rejected a connection from my external IP, but with
adding @inet_acl to the configuration the problem was solved.
I think what may be messing up all this is that I have a vServer
running and I can't change the /etc/hosts to a different hostname.
So the fqdn is always vs5513.xxx.de even if I add my domain to my
localhost IP.
But still, it's a fqdn and it's the hostname of my server, so there
has to be a way to make that work (and without amavis it works fine!)
So, heres my postconf -n (working):
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
inet_interfaces = all
mailbox_size_limit = 0
mydestination = vs5513.xxx.de, localhost.vserver4free.de, , localhost
myhostname = vs5513.xxx.de
mynetworks = xx.xx.xx.xx
myorigin = /etc/mailname
readme_directory = no
recipient_delimiter = +
relayhost =
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
smtpd_recipient_restrictions =
permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_sasl_path = private/auth
smtpd_sasl_type = dovecot
smtpd_tls_auth_only = no
smtpd_tls_cert_file = /etc/ssl/certs/postfix.pem
smtpd_tls_key_file = /etc/ssl/private/postfix.pem
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtpd_use_tls = yes
virtual_alias_maps =
mysql:/etc/postfix/mysql-virtual-alias-maps.cf,mysql:/etc/postfix/mysql-email2email.cf
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_transport = dovecot
The non working one looks the same but has the last two lines added:
content_filter = smtp-amavis:[127.0.0.1]:10024
receive_override_options = no_address_mappings
Would be great if you knew a way to solve this.
If you need more input, just tell me!
Thank you!
Regards,
Nick
More information about the Workaround-chitchat
mailing list