Re: [fetchmail-users] fetchmail on server unable to connect to postfix

[Rob M. <rob...@gm...>]

On 8/16/07, M. Fioretti <mfi...@ne...> wrote:
>
> The one I reported is the default one in Centos 4.4, I'll try to
> have it upgraded asap, thanks. Not that it would make any difference wrt
> this problem, would it? Now:

It probably wouldn't, but I don't know all the changes that have gone
into fetchmail in the interim.

> I take this to mean that setting smtpaddress as above isn't enough to
> not make fetchmail send an helo different than localhost. Is this correct,
> and if yes, isn't there any other way to make fetchmail helo something
> else?

Right, having taken a moment to dive into the code, the value of the
HELO/ELHO string that is presented is the value of smtphost.  This
defaults to localhost - change this to the fully qualified name of the
host and ensure that it is configured to NOT reject connections that
provide it's own name as the HELO value.

Note that rejecting unqualified HELO values while being fully RFC
compliant will trip up a large number of MUAs (particularly those from
Microsoft).  If you don't expect any mail clients to ever connect
directly you'll probably be ok.

> Generally, I have no problem at all to study man pages. The specific
> problem I have with email related docs is that it's really hard to
> figure out, unless one already knows the whole terminology and protocols
> in advance, to know what to search for.
>
> Even placing the whole error message in google, as I usually do, doesn't
> yeld much when email is concerned. I know this for a fact, that's why I
> also need a bit of pointers from mailing lists.

Which is why I went directly to the postfix site for that snippet, and
I don't even use postfix :)

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche