On Tue, Jul 05, 2005 at 03:35:45PM +0100, David Woodhouse wrote:
That's your definition maybe, but I don't think you'll find any ISP
including "forwarding of users' mail to the ISP's mailhosts from
elsewhere" under what is defined as 'abuse' in their Acceptable Use
Policy.
The sender (the one publishing SPF, the owner of the domain) is
the one setting the policy here. Using his name while forwarding
_is_ abuse. If the final recipient checks SPF then the message
should be rejected, by design.
The user using the forwarder made a poor choice. Don't blame SPF.
Right. And in general it isn't acceptable for any large mail provider to
_not_ support forwarding, and the only feasible way they can support
forwarding it to refrain from checking SPF. That's the approach which is
taken by most so far.
Talking about throwing the baby out... I truly believe you advice
ISPs to stop checking SPF yet that is NOT the solution.
The forwarding ISP should do something here, not the ISP at the end.
Forwarding without rewriting the 2821.MAILFROM also causes problems
with bounces because the sender will receive a bounce from some place
that they never sent email to.
That's not a _problem_ though. That's just normal operation. It's worked
that way for years.
So have open relays and non-authenticated mail submission. Somehow
the past cannot be used to prove a point so please try again.
Alex