On Wed, 2004-04-21 at 18:52 -0400, Stuart D. Gathman wrote:
I have heard it stated several times on this list that legitimate
forwarding is set up by the receiver - and therefore the receiver should
be able to whitelist the forwarder. I have just run into an SPF false
positive where the sender initiated forwarding.
The sender is a hospital. They have a service where you can email
pictures of your newborn(s) to family and friends from terminals in the
hospital. Or maybe it is just a generic webmail service.
Such things are relatively common in the real world.
Naturally, mail with an SPF enabled from domain gets bounced by an
SPF checking MTA (mine). The bounce has a nice link to the why.html page,
and was properly delivered to the from address, but the user was still
confused.
Especially after they forwarded the bounced message from home several days
later and it arrived with no problems. Naturally they felt jipped.
The sender felt it was the hospitals fault (because it worked from home).
The recipient felt is was the fault of SPF, and got angry when I tried to
explain how it works.
The recipient is right to be angry if legitimate mail is being bounced
by your unilaterally applied policies. I just hope they aren't _paying_
you for this 'service'.
--
dwmw2