On 10-11-11 15:39, SourceForge.net wrote: >> Comment By: Stevan Bajic (sbajic) > Date: 2011-11-10 06:39 > > Message: > I don't understand what you mean? You want to make the source IP available > to the DeliveryHost. Is it that? Might I ask what the use case is for that? > Can you name me a real world example where you could/would use the source > IP on the DeliveryHost? >
A ticket is not a mailing-list, taking the discussion here. I'm not sure where you should use this for, but passing on the original sender ip address is the primary use case for XFORWARD. The sole fact that most mail handlers have this standard implemented, does say something about its popularity. Why would you use XFORWARD when passing a message from MTA to amavis? If someone wants to put dspam in the delivery chain between MTA and amavis, this feature is lost. Apart from that, DSPAM could benefit from this data itself too, since it is currently extracting sender ip from the message headers when needed. Message headers is second-hand information at best, and does not work in all cases (f.i. messages injected from localhost). Receiving the sender ip from the MTA in an standardized way would be a nice improvement. Anyway, I was merely adding my musings to the ticket, for future reference. What I forgot to mention was I don't see a real use case for XCLIENT though (after skimming the postfix documentation). -- Tom ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
