On 2/26/09, Victor Duchovni <victor.ducho...@morganstanley.com> wrote: > On Thu, Feb 26, 2009 at 05:05:26PM +0100, Magnus B?ck wrote: > > > > Is there a way to solve this on server1? I mean adding recipients > > > somewhere to the mail header so server2 knows where to deliver? I > > > already tried to set "enable_original_recipient" to "yes" - in that > > > case a "X-Original-To:" is added but one copy of the mail is delivered > > > for each recipient on server1. Or would adding other header > > > information solve this (e.g. "X-Envelope-To")? > > > > Is it a problem that you get one message per recipient? More data, yes, > > but on the other hand you get correct deliveries. > > > Note, this notion of "correctness" is not one of those pedantic types > of "correctness" that is "optional". Systems that forward mail to > all header recipients are severely broken, and will cause mail loops, > blacklisting by annoyed incorrect recipients, abuse by spammers, ... > > So in short, forwarding systems must PRESERVE the original message > envelope and must not re-create fresh envelopes from message To/Cc > headers. Preserving an original envelope is relevant only for SMTP communication. So the idea of fetching mail by POP3 and then forward it to mail recipients parsed from fetched email header is generally a bad idea? But if I am not wrong that's exactly what fetchmail and POP3 mail proxies do - so all these systems are not correct and not recommended to use? I usually use transport mechanism of postfix to forward a SMTP communication to other mail server. Use of fetchmail is a server2-user requirement.
Thanx, Zoltan
