Wietse Venema schreef op 7-1-2014 19:42:
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:
I suggest that this is a question for the Dovecot mailing list.
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.
second problem is that on the first server (spamsnake) I get sometimes this
error:
Jan 7 14:56:56 bsd5 postfix/error[7639]: 0BF47A41459:
to=<ca...@somedomain.nl>, relay=none, delay=20, delays=20/0/0/0.01, dsn=4.3.0,
status=deferred (unknown mail transport error)
Look for an error/fatal/panic record BEFORE these.
http://www.postfix.org/DEBUG_README.html#logging
Look for obvious signs of trouble
Postfix logs all failed and successful deliveries to a logfile. The
file is usually called /var/log/maillog or /var/log/mail; the exact
pathname is defined in the /etc/syslog.conf file.
When Postfix does not receive or deliver mail, the first order of
business is to look for errors that prevent Postfix from working
properly:
% egrep '(warning|error|fatal|panic):' /some/log/file | more
Note: the most important message is near the BEGINNING of the output.
Error messages that come later are less useful.
The nature of each problem is indicated as follows:
* "panic" indicates a problem in the software itself that only a
programmer can fix. Postfix cannot proceed until this is fixed.
* "fatal" is the result of missing files, incorrect permissions,
incorrect configuration file settings that you can fix. Postfix
cannot proceed until this is fixed.
* "error" reports an error condition. For safety reasons, a Postfix
process will terminate when more than 13 of these happen.
* "warning" indicates a non-fatal error. These are problems that
you may not be able to fix (such as a broken DNS server elsewhere
on the network) but may also indicate local configuration errors
that could become a problem later.
OK, I found these:
Jan 7 20:42:47 bsd5 postfix/smtpd[32633]: warning: hostname
server.alleactiesophetweb.com does not resolve to address 178.18.86.76:
Name or service not known
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
Jan 7 20:42:50 bsd5 postfix/smtp[718]: fatal: garbage after numerical
service in server description: [217.195.119.6]:25,smtp:[217.195.119.6]:25
Jan 7 20:42:50 bsd5 postfix/smtp[719]: fatal: garbage after numerical
service in server description: [217.195.119.6]:25,smtp:[217.195.119.6]:25
Jan 7 20:42:51 bsd5 postfix/qmgr[19731]: warning: private/smtp socket:
malformed response
Jan 7 20:42:51 bsd5 postfix/qmgr[19731]: warning: transport smtp
failure -- see a previous warning/fatal/panic logfile record for the
problem description
Jan 7 20:42:51 bsd5 postfix/master[19724]: warning: process
/usr/lib/postfix/smtp pid 717 exit status 1
Jan 7 20:42:51 bsd5 postfix/master[19724]: warning:
/usr/lib/postfix/smtp: bad command startup -- throttling
Jan 7 20:42:51 bsd5 postfix/qmgr[19731]: warning: private/smtp socket:
malformed response
Jan 7 20:42:51 bsd5 postfix/qmgr[19731]: warning: transport smtp
failure -- see a previous warning/fatal/panic logfile record for the
problem description
Jan 7 20:42:51 bsd5 postfix/master[19724]: warning: process
/usr/lib/postfix/smtp pid 718 exit status 1
Jan 7 20:42:51 bsd5 postfix/qmgr[19731]: warning: private/smtp socket:
malformed response
Jan 7 20:42:51 bsd5 postfix/qmgr[19731]: warning: transport smtp
failure -- see a previous warning/fatal/panic logfile record for the
problem description
Jan 7 20:42:51 bsd5 postfix/master[19724]: warning: process
/usr/lib/postfix/smtp pid 719 exit status 1
Jan 7 20:44:34 bsd5 postfix/smtpd[31300]: warning: hostname
ktm.magnumhost.net does not resolve to address 69.64.64.71: Name or
service not known
Third problem is that I have reject_unverified_recipient enabled but it
is not working I have one domain which receives about 100 mails an hour
off which 99 are spam. the use only one emailaccount (no catchall) but
the mail is refused at the second server after it has gone through the
spamsnake. This was working ok, but I don't know what I did to break
this ;-)
Unfortunately, there is not enough concrete content that allows
anyone to reproduce this.
Working:
Jan 7 16:19:27 bsd5 postfix/smtpd[13920]: connect from
summer2.hostnet.nl[91.184.19.58]
Jan 7 16:19:27 bsd5 postfix/cleanup[13923]: 1DCA1A412D2:
message-id=<20140107151927.1dca1a41...@bsd5.domain.net>
Jan 7 16:19:27 bsd5 postfix/qmgr[3929]: 1DCA1A412D2:
from=<postmas...@domain.nl>, size=226, nrcpt=1 (queue active)
Jan 7 16:19:27 bsd5 postfix/smtp[14158]: 1DCA1A412D2:
to=<i...@navi-888.com>, relay=31.151.138.50[31.151.138.50]:25,
delay=0.35, delays=0/0/0.26/0.09, dsn=5.1.1, status=undeliverable (host
31.151.138.50[31.151.138.50] said: 550 5.1.1 <i...@navi-888.com>:
Recipient address rejected: User unknown in local recipient table (in
reply to RCPT TO command))
Jan 7 16:19:27 bsd5 postfix/qmgr[3929]: 1DCA1A412D2: removed
Jan 7 16:19:29 bsd5 postfix/smtpd[11781]: disconnect from
mx2.digitalrevolution.nl[193.164.144.11]
Jan 7 16:19:30 bsd5 postfix/postscreen[3930]: PASS NEW
[217.92.229.18]:12733
Jan 7 16:19:30 bsd5 postfix/smtpd[13920]: NOQUEUE: reject: RCPT from
summer2.hostnet.nl[91.184.19.58]: 450 4.1.1 <i...@navi-888.com>:
Recipient address rejected: unverified address: host
31.151.138.50[31.151.138.50] said: 550 5.1.1 <i...@navi-888.com>:
Recipient address rejected: User unknown in local recipient table (in
reply to RCPT TO command); from=<mi...@mediagroupholland.nl>
to=<i...@navi-888.com> proto=ESMTP helo=<summer2.hostnet.nl>
Jan 7 16:19:30 bsd5 postfix/smtpd[13920]: disconnect from
summer2.hostnet.nl[91.184.19.58]
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 <nikola_1...@domain2.com>; Tue, 7 Jan 2014 21:09:28
+0100 from outmail014.prn2.facebook.com[66.220.144.141];
from=<update+zj4o4yjsy...@facebookmail.com> to=<nikola_1...@domain2.com>
proto=ESMTP helo=<mx-out.facebook.com>
Jan 7 21:09:28 bsd5 postfix/cleanup[1318]: 657CDA4128E:
message-id=<493f1c6806a0a3360ea2e930a6c9e...@www.facebook.com>
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=<update+zj4o4yjsy...@facebookmail.com>, size=11166, nrcpt=1 (queue
active)
Jan 7 21:09:33 bsd5 postfix/smtp[2393]: 8F25CA40953:
to=<nikola_1...@domain2.com>, 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?
Thanks so far Wietse.
Wietse
Thanks so far Wietse,
