I keep staring at this
Apr 19 14:48:31 mail01 postfix/vpn/smtp[21044]: connect to
back.mail01.example.com[10.1.1.16]:25: Connection refused
Apr 19 14:48:31 mail01 postfix/vpn/smtp[21044]: 3qqJYC3wYbz31Vm:
to=<[email protected]>, relay=none, delay=0.1, delays=0/0.01/0.09/0,
dsn=4.4.1, status=undeliverable (connect to
back.mail01.example.com[10.1.1.16]:25: Connection refused)
That says to me
postfix smtp instance 'vpn' is trying to connect (for some reason) to
back.mail01.example.com[10.1.1.16]:25
port. 25.
The 'vpn' mail transport does not go to port 25. It's set up to send mail to
port 15003.
That port 25 connection has got to be an address-verify attempt, no?
If yes, then WHY is it trying?
Is it picking up the default =static: transport map from main.cf?
I'm back to, or stuck at, scratching my head over how/where to limit address
verification to only one time on the frontend
Something in main.cf like
- address_verify_transport_maps = static:vpn:[back.mail01.example.com]:25
+ address_verify_transport_maps =
lmdb:/etc/postfix/address_verify_transports
/etc/postfix/address_verify_transports
<what do I put here?> vpn:[back.mail01.example.com]:25
* :
? Or do I need to use
-o address_verify_transport_maps=...
in master.cf, per instance?
Jason
