From: Frederic M. <fre...@wo...> - 2007-08-16 16:20:41
|
M. Fioretti a écrit : >>> Helo command rejected: need fully-qualified hostname >>> >> So, fix your postfix configuration >> > > As I mentioned in the original message, I cannot easily change (for > reasons which are everything but technical...) the postfix configuration. > Unless I *am* sure that it is really the only possible way to fix this, that > is. Otherwise I would have posted straight to the postfix list. > > For the record, here is the complete excerpt of the postfix refusal I get > _WITH_: > > poll pop3.myprovider.com with proto POP3 tracepolls > user myaccount there with pass "the password" is root here keep > smtpaddress exact_output_of_hostname_command_here > > Aug 16 14:41:55 machinename postfix/smtpd[5641]: NOQUEUE: reject: RCPT > from localhost[127.0.0.1]: 504 5.5.2 <localhost>: Helo command rejected: > need fully-qualified hostname; from=<testaddress> > to=<root@exact_output_of_hostname_command_here> proto=ESMTP > helo=<localhost> > > 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? > According to fetchmail's man page smtpaddress adds the domain to the rcpt to, not to the helo of the envelope. Have a look at your /etc/hosts. Does the address 127.0.0.1 resolves first to the name of the machine or to localhost as is usually the case by default ? If localhost is the first name, could you rewrite /etc/hosts to put the machine name (what you want to see in the helo) as the first name matching 127.0.0.1 ? Something like: 127.0.0.1 machinename.domain.dom machinename localhost.localdomain localhost My guess is that localhost may be the first name matching 127.0.0.1 and fetchmail uses it in the helo. Frederic |