Re: [fetchmail-devel] RFC: support --smtphost for bounces

[Sunil S. <sh...@bo...>]

Quoting from Matthias Andree's mail on Mon, Feb 19, 2007:
> how about the attached patch to fix the "bounces are always
> SMTP-injected to localhost without regard to the --smtphost"?
> <http://bugs.debian.org/150137>
> 
> It's not perfect, and I don't know how to handle cases where --smtphost
> contains LMTP hosts exclusively or is switched to LMTP by --lmtp -
> suggestions?

A lot more work will be required for this.

Here I am assuming that smtphost is not localhost and requires
authentication for relaying the bounce message. The code currently
does not do that because localhost (by default) allows relaying of the
bounce message without authentication.

For using smtphost as a relay server for the bounce message, fetchmail
will have to authenticate using esmtpname. For that, fetchmail will
have to send EHLO, save the response, and parse it. For that, separate
structure will have to be maintained per smtp connection. All the smtp
variables which are currently global/static will have to be part of
that structure.

There will also be a compatibility problem if the user has not
specified any esmtpname. This is not a problem for the incoming mail
as the mail is (presumably) being delivered locally on the smtphost.
However, for the bounce message, authentication is a must as the
smtphost is now going to act as a relay server. So, smtphost should be
automatically used only if the user has specified an esmtpname.

-- 
Sunil Shetye.