R. Berger: > -The biggest problem now is that some clients can't get their email > using their exchange 2008 pop connector, because it stop after 5 > messages with corrupt headers. I don't know where this comes from or to > find a solution. This is a sample header:
Wietse: > I suggest that this is a question for the Dovecot mailing list. R. Berger: > I am not sure. Googling shows me several of the problem, all pointing to > postfix and none pointing to dovecot. The problem is the "Return-Path: > <MAILER-DAEMON>" header which is not confirming RFC2821 (I think) and > therefore refused by Exchange when delivered by the popconnector. What concrete evidence do you have that "Return-Path: <MAILER-DAEMON>" trips up exchange? I find this hard to believe. I recall Microsoft having difficulties with null bytes in headers. > Jan 7 20:42:50 bsd5 postfix/smtp[717]: fatal: garbage after numerical > service in server description: [217.195.119.6]:25,smtp:[217.195.119.6]:25 See the Postfix documentation for relayhost syntax. > Not working: > Jan 7 21:09:28 bsd5 postfix/smtpd[32230]: 657CDA4128E: > client=outmail014.prn2.facebook.com[66.220.144.141] > Jan 7 21:09:28 bsd5 postfix/cleanup[1318]: 657CDA4128E: hold: header > Received: from mx-out.facebook.com (outmail014.prn2.facebook.com > [66.220.144.141])??by bsd5.domain.net (Postfix) with ESMTP id > 657CDA4128E??for <[email protected]>; Tue, 7 Jan 2014 21:09:28 > +0100 from outmail014.prn2.facebook.com[66.220.144.141]; > from=<[email protected]> to=<[email protected]> > proto=ESMTP helo=<mx-out.facebook.com> > Jan 7 21:09:28 bsd5 postfix/cleanup[1318]: 657CDA4128E: > message-id=<[email protected]> > Jan 7 21:09:33 bsd5 MailScanner[1590]: Requeue: 657CDA4128E.AFEBB to > 8F25CA40953 > Jan 7 21:09:33 bsd5 MailScanner[1590]: Requeue: 657CDA4128E.AFEBB to > 8F25CA40953 > Jan 7 21:09:33 bsd5 postfix/qmgr[19731]: 8F25CA40953: > from=<[email protected]>, size=11166, nrcpt=1 (queue > active) > Jan 7 21:09:33 bsd5 postfix/smtp[2393]: 8F25CA40953: > to=<[email protected]>, relay=bsd4.domain.net[83.96.158.143]:25, > delay=4.8, delays=4.8/0/0.02/0, dsn=2.0.0, status=sent (250 2.0.0 Ok: > queued as D65871B530AC) > > Can you see anything in this? Your "working" example rejects mail for an unknown LOCAL recipient, whereas the "not working" example accepts and forwards mail for a REMOTE recipient. What is wrong with that? Wietse
