I've narrowed my problems down to three. Two may be related.


1. Virtual alias table lookup failure:


syslog is full of pairs of entries like these:


Oct 23 13:03:06 theglobalvoice postfix/trivial-rewrite[23647]: warning: virtual_alias_domains: proxy:mysql:/etc/postfix/mysql_virtual_alias_maps.cf: table lookup problem Oct 23 13:03:06 theglobalvoice postfix/trivial-rewrite[23647]: warning: virtual_alias_domains lookup failure


Here's mysql_virtual_alias_maps.cf, password redacted:


user = postfix
password = {redacted}
hosts = localhost
dbname = postfix
table = alias
select_field = goto
where_field = address


2. Milter service:


Oct 23 13:08:03 theglobalvoice postfix/pickup[23600]: F41BC605E8: uid=1000 from=<tgvpadmin> Oct 23 13:08:03 theglobalvoice postfix/cleanup[23702]: warning: connect to Milter service inet:localhost:8891: Connection refused Oct 23 13:08:03 theglobalvoice postfix/cleanup[23702]: F41BC605E8: message-id=<20191023130802.f41bc60...@mail.theglobalvoice.info>


I installed opendkim and opendkim-tools. This is one  of probably many holes I have in my knowledge of how mail security works these days, as I remember doing none of this in 2016, or the person who did it for us failed to communicate it when he was done. So much for free consulting.


3. SMTP:


Oct 23 13:18:03 theglobalvoice postfix/smtpd[24095]: lost connection after RCPT from web01.groups.io[66.175.222.12] Oct 23 13:18:03 theglobalvoice postfix/smtpd[24095]: disconnect from web01.groups.io[66.175.222.12] ehlo=2 starttls=1 mail=1 rcpt=0/1 commands=4/5 Oct 23 13:18:03 theglobalvoice postfix/smtpd[24195]: lost connection after RCPT from web01.groups.io[66.175.222.12] Oct 23 13:18:03 theglobalvoice postfix/smtpd[24195]: disconnect from web01.groups.io[66.175.222.12] ehlo=2 starttls=1 mail=1 rcpt=0/1 commands=4/5 Oct 23 13:18:17 theglobalvoice postfix/smtpd[24095]: connect from web01.groups.io[66.175.222.12] Oct 23 13:18:18 theglobalvoice postfix/smtpd[24095]: NOQUEUE: reject: RCPT from web01.groups.io[66.175.222.12]: 451 4.3.0 <bounce+17584+3208+11292+2273...@groups.io>: Temporary lookup failure; from=<bounce+17584+3208+11292+2273574@groups.i > to=<chris...@theglobalvoice.info> proto=ESMTP helo=<web01.groups.io>


I don't know even where to start with this one. Time to go back to school I think.


On 10/22/2019 7:10 PM, Steve Matzura wrote:

Thanks, Noel. Very helpful. MySQL is definitely installed and working, but I don't know about Milter, as it was set up by someone else who didn't quite do well by me in educating me in the find points of Postfix management, which is why I am where I am today. I'll get on that and report back.



On 10/22/2019 3:46 PM, Noel Jones wrote:
On 10/22/2019 1:58 PM, Steve Matzura wrote:
I am running a copy of configurations from a running version 2 installation from Ubuntu 14.04, now alive as version 3 on Ubuntu 18.04.


I thought I'd be slick and port over all the user mailbox directories in /var/mail/vmail, all the customized .cf's, and the MySQL database. Everything ported over nicely, Postfix runs in backward compatibility mode, but for  every mail message, I get this in syslog:


Oct 22 18:51:36 tgvprod postfix/pickup[1114]: 852EB604E4: uid=1000 from=<tgvpadmin> Oct 22 18:51:36 tgvprod postfix/cleanup[2770]: warning: connect to Milter service inet:localhost:8891: Connection refused

This usually means the milter service isn't started, or not installed. Or maybe the firewall preventing connections to the milter.

Did you install the milter from the other machine and copy its config?  Ditto firewall config?

Test until you get the milter working. The default value milter_default_action=tempfail will prevent postfix from receiving mail until this is fixed.


Oct 22 18:51:36 tgvprod postfix/cleanup[2770]: warning: proxy:mysql:/etc/postfix/mysql_virtual_alias_maps.cf lookup error for "tgvpadmin@tgvprod"

maybe your sql service isn't started, or not installed.

Did you install sql and copy the sql config files from the old machine?

Test until you get sql queries working.  Generally it's easier to start with hash: files before adding the complexity of a database.

To prevent losing mail, postfix will tempfail all mail when there's a map lookup error.




  -- Noel Jones

Reply via email to