Hi, I managed to do some test but with no luck.
As suggested I specified two parameters in main.cf that where not
present before:
disable_dns_lookups = no
smtp_host_lookup = dns
Sure mastervoice.it has an A record that point to 2.229.104.67 (web
server) while the mail server is at 2.229.104.69.
I checked also the the transport table that is:
.fax smtp:[192.168.1.211]
autoreply.mastertraining.it gnarwl:
Ans here the actual postconf -n output:
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
anvil_rate_time_unit = 5
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
disable_dns_lookups = no
home_mailbox = Maildir/
html_directory = /usr/share/doc/postfix/html
inet_interfaces = all
local_transport = virtual
mailbox_size_limit = 0
message_size_limit = 51200000
mydestination = mail2.mastercom, localhost.mastercom, localhost,
mastertraining.it, registroelettronico.com, masterscuola.it, mastercom
myhostname = mail.mastertraining.it
mynetworks = 127.0.0.0/8, 192.168.1.0/24, 192.168.2.0/24, 10.10.0.0/24,
10.8.0.0/24, 10.9.0.0/24
myorigin = /etc/mailname
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relay_domains = $mydestination
relayhost =
smtp_host_lookup = dns
smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
smtpd_sender_restrictions = reject_non_fqdn_sender
reject_unknown_sender_domain
smtpd_tls_cert_file = /etc/courier/imapd.pem
smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache
smtpd_use_tls = yes
transport_maps = hash:/etc/postfix/transport
virtual_alias_domains =
virtual_gid_maps = static:5000
virtual_mailbox_base = /home
virtual_mailbox_limit = 0
virtual_mailbox_maps = ldap:mastermail
virtual_uid_maps = static:5000
With this config I keep having the bounce:
Dec 5 12:06:10 mail2 postfix/smtpd[20844]: 7FDFDA711C:
client=unknown[192.168.1.14]
Dec 5 12:06:10 mail2 postfix/cleanup[20848]: 7FDFDA711C:
message-id=<50bf2aa1.6050...@mastertraining.it>
Dec 5 12:06:10 mail2 postfix/qmgr[20841]: 7FDFDA711C:
from=<d.davo...@mastertraining.it>, size=1985, nrcpt=1 (queue active)
Dec 5 12:06:10 mail2 postfix/smtp[20849]: 7FDFDA711C:
to=<d.davo...@mastervoice.it>, relay=none, delay=0.01,
delays=0.01/0/0/0, dsn=5.4.6, status=bounced (mail for mastervoice.it
loops back to myself)
Dec 5 12:06:10 mail2 postfix/bounce[20850]: 7FDFDA711C: sender
non-delivery notification: 8438FA734A
Dec 5 12:06:10 mail2 postfix/qmgr[20841]: 7FDFDA711C: removed
I share this because it's odd enough in my eyes. I bet is some DNS
Anyway, I had to modify the transport table as workaround to deliver the
email for mastervoice.it domain. Like this:
.fax smtp:[192.168.1.211]
mastervoice.it smtp:[ASPMX.L.GOOGLE.COM]
autoreply.mastertraining.it gnarwl:
Please don't insult me, I see that it not the best configuration but
right now is keeping users from biting me.
If I'll solve this strange problem I'll share.
Thanks everybody!
Davo
On 12/04/2012 11:21 PM, Viktor Dukhovni wrote:
On Tue, Dec 04, 2012 at 08:48:47PM +0100, Daniele Davolio wrote:
Here the requested output:
mail2:~# host -t mx mastervoice.it
mastervoice.it MX 10 ASPMX.L.GOOGLE.COM
mastervoice.it MX 20 ALT1.ASPMX.L.GOOGLE.COM
mastervoice.it MX 20 ALT2.ASPMX.L.GOOGLE.COM
mastervoice.it MX 30 ASPMX2.GOOGLEMAIL.COM
mastervoice.it MX 30 ASPMX3.GOOGLEMAIL.COM
I'm at home now, I'll look first for your hints tomorrow morning in
office!
I'll let you know what I'll discover.
Thanks for your always needed help, and patience.
Davo
On Tue, 4 Dec 2012 13:16:45 -0500 (EST), Wietse Venema
<wie...@porcupine.org> wrote:
Ralf Hildebrandt:
* d.davo...@mastertraining.it <d.davo...@mastertraining.it>:
Dec 4 15:13:41 mail2 postfix/smtp[26167]: 4E21EA735A:
to=<e.bos...@mastervoice.it>, relay=none, delay=0.1,
delays=0.1/0/0/0, dsn=5.4.6, status=bounced (mail for mastervoice.it
loops back to myself)
What is the result of
% host -t mx mastervoice.it
on that machine?
There's also an A record. Postfix will deliver mail there if
"disable_dns_lookups=yes" or smtp_host_lookup does not contain
Naturally, loops can also happen when routing is forced via transport
table entries, content filters, ...
So the MX records may be fine, but the OP's configuration may
specify an explicit relayhost, default_transport with a nexthop,
relay_transport with a nexthop, a transport table entry, ...
