> On Thu, Jan 06, 2011 at 11:41:28AM -0800, Steve Cooper wrote: > > > Here's the line from our trans.exp file: > > > > /^om_.*/ lmtp:inet:opus.allegro.com:24 > > > > And, the corresponding line in main.cf: > > > > transport_maps = regexp:/etc/postfix/trans.exp > > > > This all worked fine with the old version. > > > > Now, mail destined for om_* addresses get delivered to > Samsung Contact, but > > they hang around in the mail queue most of the time. mailq > shows entries like: > > > > 8A30B524652 35124 Thu Jan 6 11:08:31 g...@wti.com > > (conversation with opus.allegro.com[10.84.2.10] timed out > while sending end of data -- message may be sent more than > > once) > > o...@allegro.com > > o...@allegro.com > > o...@allegro.com > > o...@allegro.com > > om...@allegro.com > > And, eventually, the message is sent more than once. It > appears that each time it is sent, one more recipient > > disappears off the list. But the entire remaining list > gets the message again when postfix reprocesses > > the message. > > Their LMTP service is broken, and does not provide multiple replies > when multiple LMTP recipients are in the same envelope. You need to > set "lmtp_destination_recipient_limit = 1". You could create a clone > > lmtpdumb unix - - n - - lmtp > > transport and set: > > main.cf: > lmtpdumb_destination_recipient_limit = 1 > > transport.exp: > /^om_.*/ lmtpdumb:inet:opus.allegro.com:24 > > LMTP servers are supposed to support multiple recipients and emit > multiple 250 replies at the end of the transaction, one for each > recipient. This LMTP server appears broken. If the same service is > available over SMTP use that instead. > > -- > Viktor. >
Brilliant! That works perfectly. Thank you very much, Viktor. Sincerely, Steve
