On 09/09/2016 07:33 AM, Steve Wehr wrote: > Thanks Mark, Here are the results of the tests you suggested. Both attempts > at telnet failed. > > Tried your experiment: > > /etc/postfix>telnet localhost 25 > Trying ::1... > telnet: connect to address ::1: Connection refused > Trying 127.0.0.1... > Connected to localhost.
Interesting. I suggest you put SMTPHOST = '127.0.0.1' in mm_cfg.py since 'localhost' seems to resolve at least first to an IPv6 address on which Postfix isn't listening. I don't see exactly how this will help, but it might. Now, given that Postfix doesn't like st...@tunedinweb.com, the question is what are the PHP scripts that mail to this address doing. Are they connecting to this Postfix differently or even at all (maybe they connect to mx.emailsrvr.com). > /etc/postfix/transport: > st...@tunedinweb.com smtp:mx.emailsrvr.com > ste...@tunedinweb.com smtp:mx.emailsrvr.com > ste...@tunedinweb.com smtp:mx.emailsrvr.com > w...@tunedinweb.com smtp:mx.emailsrvr.com > sti...@tunedinweb.com smtp:mx.emailsrvr.com > ad...@tunedinweb.com smtp:mx.emailsrvr.com > err...@tunedinweb.com smtp:mx.emailsrvr.com > eve...@tunedinweb.com smtp:mx.emailsrvr.com > feedb...@tunedinweb.com smtp:mx.emailsrvr.com > em...@tunedinweb.com smtp:mx.emailsrvr.com > ideachamp_or...@tunedinweb.com smtp:mx.emailsrvr.com > inqu...@tunedinweb.com smtp:mx.emailsrvr.com > mail...@tunedinweb.com smtp:mx.emailsrvr.com > mailman_ad...@tunedinweb.com smtp:mx.emailsrvr.com > mailman-ow...@tunedinweb.com smtp:mx.emailsrvr.com > ord...@tunedinweb.com smtp:mx.emailsrvr.com > payme...@tunedinweb.com smtp:mx.emailsrvr.com > r...@tunedinweb.com smtp:mx.emailsrvr.com > secur...@tunedinweb.com smtp:mx.emailsrvr.com > tune...@tunedinweb.com smtp:mx.emailsrvr.com > ver...@tunedinweb.com smtp:mx.emailsrvr.com > ab...@tunedinweb.com smtp:mx.emailsrvr.com > postmas...@tunedinweb.com smtp:mx.emailsrvr.com If you add local_recipient_maps = proxy:unix:passwd.byname $alias_maps $transport_maps to Postfix main.cf, I think that will work. This is actually only adding $transport_maps as proxy:unix:passwd.byname and $alias_maps are the defaults. This will ensure that none of the addresses in transport_maps (/etc/postfix/transport) is rejected as an unknown local recipient. It appears that Postfix is doing the local recipient check before consulting transport_maps for a transport. I'm not that knowledgeable about the details of Postfix to fully understand this, but I think adding $transport_maps to local_recipient_maps in this case will solve your issue without causing other problems, but I suggest you test and be prepared to reverse when you do this. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
