From: M. F. <mfi...@ne...> - 2007-08-16 16:30:11
|
Rob wrote: > Marco wrote: > > I take this to mean that setting smtpaddress as above isn't > > enough to not make fetchmail send an helo different than localhost.... > > 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 Unfortunately this doesn't seem enough. Doing a poll pop3.myisp.com with proto POP3 tracepolls user myaccount there with pass "thepassword" is mfi...@ne... here keep smtphost the.full.machine.name still yelds (may this depend on the fetchmail version???): fetchmail: About to rewrite To: mya...@my... Rewritten version is To: mya...@my... fetchmail: SMTP< 220 the.full.machine.name ESMTP Postfix fetchmail: SMTP> EHLO localhost fetchmail: SMTP< 250-the.full.machine.name fetchmail: SMTP< 250-PIPELINING fetchmail: SMTP< 250-SIZE 10240000 fetchmail: SMTP< 250-ETRN fetchmail: SMTP< 250-STARTTLS fetchmail: SMTP< 250-ENHANCEDSTATUSCODES fetchmail: SMTP< 250-8BITMIME fetchmail: SMTP< 250 DSN fetchmail: forwarding to the.full.machine.name fetchmail: SMTP> MAIL FROM:<a_test_address> SIZE=1192 fetchmail: SMTP< 250 2.1.0 Ok fetchmail: SMTP> RCPT TO:<mfi...@ne...> fetchmail: SMTP< 504 5.5.2 <localhost>: Helo command rejected: need fully-qualified hostname fetchmail: SMTP error: 504 5.5.2 <localhost>: Helo command rejected: need fully-qualified hostname fetchmail: SMTP listener doesn't like recipient address `mfi...@ne...' > Note that rejecting unqualified HELO values while being fully > RFC compliant... Yes, we're aware of this and in _our_ particular case we should be fine. For now, at least. > Which is why I went directly to the postfix site for that snippet, > and I don't even use postfix :) exactly my point. When the underlying terminology and standards are, shall we say, so peculiar, it doesn't matter much which server one uses, does it? Whereas having _already_ acquired_ over time an in-depth knowledge and understanding of the lingo helps a lot. This is where I hope to arrive, of course. Thanks for any further help! As a side note, I hope this thread continues until the problem is solved via fetchmail also because... I'm learning more about fetchmail this afternoon, thanks to this thread, than by reading the docs again and again... Marco |