Re: [fetchmail-users] change helo/ehlo

[Florian <ts...@ag...>]

Rob MacGregor schrieb:
> On 6/7/07, Florian <ts...@ag...> wrote:
>   
>> Hello List,
>>
>> i installed fetchmail 6.3.8+SSL on Trustix.
>> Fetching of Mails works, but delivering the mails crashes:
>>     
>
> Contents of .fetchmailrc?
>
> In my case, presumably because I've used "set invisible" I see "EHLO
> <remote server>".  If I don't set that then I see "EHLO <hostname>".
>   
poll pop.gmx.net proto pop3 user "myf...@gm..." password
"password" is "my...@my..."
fetchall

fetchmail ist called for testing just with : "fetchmail -v"

I'll try the "set invisible"
>> How can the HELO/EHLO string be changed?
>>     
>
> Change the system's hostname, ie so that "hostname" provides
> "myhostname.mydomain.de" rather than just "myhostname".
>   
The system has several ip-addresses. Every ip-address corresponds to an
valid name in the DNS (forward and reverse). I'd like to use one of
these names for fetchmail-EHLO.
Is there a onfig-value for customizing the EHLO-String?
Can fetchmail be bound to a certail outgoing interface (like e.g.
postfix : smtp_bind_address)?
How is the EHLO-String determined?
>> According to rfc 2821 i'd like use the fqdn "myhostname.mydomain.de" as
>> EHLO-String.
>>
>> "4.1.1.1  Extended HELLO (EHLO) or HELLO (HELO)
>> [...] The argument field contains the fully-qualified domain name
>> of the SMTP client if one is available."
>>     
>
> Given how few clients actually obey that, if you expect any clients to
> connect to that server it's probably best to relax that check.
>   
I use this check for Spam protection and it works very well! You are
right, that this is a source for false-positives ;-(
I'd like to form my own outgoing traffic in an rfc-conform manner.

Florian