On 05/Feb/11 07:51, Mark Constable wrote: > On 05/02/11, Mark Constable wrote: >> > The only thing they can do is set the envelope sender on forwarded mail >> > to point to their own domain, with its own SPF record. >> >> perhaps a hint as to which one would suit rewritting the envelope From >> via a .courier file? > > To answer my own question, this seems to work (Debian)... > > ~ cat .courier-markc2 > |/usr/sbin/sendmail -verp [email protected]
Of course, if you send directly to xxxx.com.au, you don't suffer of forwarding being break. > However, another question, the Return-Path seems to differ from the > sender= so which one is the real envelope From as seen by xxxx.com.au? A forwarder should replace the envelope from. Folks at zzzzz.com should configure postfix to either set an empty envelope from, in case nobody cares about delivery failures, or set it to the address of the one who cares (he or she will have to remove the forwarding rule when xxxx.com.au removes the "tech" user, or similar cases.) However, if xxxx.com.au have BOFHSPFFROM improperly set, and if zzzzz.com don't get a "pass" for their replaced envelope from, then the message may still be rejected. > Delivered-To: [email protected] > Return-Path: <[email protected]> That is a verped return path. Using -f also works. ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
