On Fri, 09-Jan-2004 at 11:44:57 -0800, Justin Mason wrote:
> >Now user1 at sender.com sends an email to user at example.com, which is accepted
> >by the server for example.com (say, mail.example.com). Now
> >mail.example.com forwards the mail on to the foo.com server for
> >user at foo.com. But the foo.com server does an SPF check for sender.com, and
> >sees that mail.example.com isn't permitted, and rejects the message. Oops?
>> .forward on mail.example.com:
>> "| /usr/sbin/sendmail -oi user at foo.com"
>> Problem solved.
And new problems created. First of all, if something goes wrong with the
delivery to user at foo.com, the original sender doesn't find out about it.
Secondly, it could even create a bounce loop, couldn't it? After all, the
envelope sender on the forwarded message will be user at example.com, so if
the user at foo.com address bounces, the bounce goes to user at example.com,
which forwards it to user at foo.com, which bounces, sending a bounce
user at example.com, which forwards it to... and so on.
... ... <Tagline with a cloaking device>
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!