Re: 517 Syntax error ??
mario chiari <[email protected]>
| Newsgroups | gmane.mail.fetchmail.user |
|---|---|
| Message-ID | <[email protected]> |
Hi ok, I'll report on the courier ml and update thanks for your help mario On Sat, 2019-03-02 at 11:04 +0000, Ralph Corderoy wrote: > Hi mario, > > > reading message [email protected]@pop3.mydomain.net:1 of 1 (3054 octets) > > About to rewrite Return-Path: <>... > > ...rewritten version is Return-Path: <>. > > About to rewrite From: <[email protected]>... > > ...rewritten version is From: <[email protected]>. > > About to rewrite To: <[email protected]>... > > ...rewritten version is To: <[email protected]>. > > fetchmail: about to deliver with: /usr/lib/courier/bin/sendmail -i -f > > '<>' -- '[email protected]' > > #****************************517 Syntax error. > > ***********.*********************** > > fetchmail: Error writing to MDA: Broken pipe not flushed > > fetchmail: POP3> QUIT > > fetchmail: POP3< +OK Logging out. > > So it's Courier's sendmail that's giving the `517 Syntax error'. > Google suggests this is quite common. > https://www.courier-mta.org/FAQ.html#esmtperr explicitly mentions 517. > http://courier-mail-server.10983.n7.nabble.com/More-information-re-517-syntax-error-td3484.html > suggests local configuration can play a part if Courier has to make up > an email address. > > The typical cause seems to be an email address with just a hostname, > i.e. not `.' after the `@'. If Courier's logs don't help pin-point the > problem then you may have to > > strace -ffe %desc -s 4096 -o st fetchmail ...your-normal-arguments > > and then look at st.* afterwards. Search for `517' and you'll find the > error message from Courier as it's read by fetchmail. See what was > being given to Courier in the run up to that. >