Sam Varshavchik wrote: > Mail forwarding is not a random event. Mail forwarding occurs, > presumably, at the ultimate recipient's request. It is the ultimate > recipient that places the forwarding in place, so that the recipient's > mail gets forwarded to a different destination.
That forwarding recipe includes an email address, which is personally identifiable data and should be under the direct control of its owner. Thus, it makes sense to require some compliance on the sender's side. > As such, since the whole process is under the complete control of the > recipient, the recipient must then recognize that SPF will not be > functional on forwarded mail. The recipient must concede to disabling > SPF as the cost of having the recipient's mail forwarded. SPF can still > be checked, of course, by the forwarder. Currently, the only way that one can concede forwarding is by IP address. This may make sense for a fully controlled backup MX. In general, the same IP address can be used to forward a message as well as to submit a new one. The forwarded-to recipient has no way to distinguish between those two cases. Furthermore, having to concede full relay privileges to that IP is certainly overkill. Rewriting the sender's address currently works, but is wrong for backup MXes. Isn't there room for designing a better solution? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
