Well, you'd of course replace the 1234 with the actual LMTP port that the backend is listening on. There is no default port assigned for LMTP, so I don't know what you've used. Or have you added any inet_listener to LMTP at all?
wasnt using inet_listener since I was using UNIX sockets
Switching to inet_listener and changing port to 24 on the proxy
10-master.conf
service lmtp { #unix_listener /var/spool/postfix/private/dovecot-lmtp { #group = postfix #mode = 0666 #user = postfix #}
# Create inet listener only if you can't use the above UNIX socket inet_listener lmtp { port = 24 } }
postfix/main.cf virtual_transport = lmtp:om005pp1:24 #lmtp:hostname:port - om005pp1 is the proxy itself mailbox_transport = lmtp:om005pp1:24
Postfix shows
postfix/lmtp[21872]: C23824502C4: to=<user@dev.domain.com>, relay=om005pp1[192.168.12.204]:24, delay=0.06, delays=0.02/0.01/0.01/0.03, dsn=4.5.2, status=deferred (host om005pp1[192.168.12.204] said: 402 4.5.2 Error: command not recognized (in reply to end of DATA command))
postfix/master.cf on the backend dovecot is 24 inet n - n - - smtpd
when postfix/master.cf on the backend dovecot is 24 inet n - n - - lmtp
proxy postfix shows
postfix/lmtp[21971]: 86CD04502C4: to=<user@dev.domain.com>, relay=om005pp1[192.168.12.204]:24, delay=30, delays=0.02/0.01/0.01/30, dsn=4.4.0, status=deferred (host om005pp1[192.168.12.204] said: 451 4.4.0 Remote server not answering (DATA output timeout) (in reply to end of DATA command))