|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: 451 Error: queue file write error
From: Jesper Skriver (jesper
skriver.dk)Date: Thu Jun 29 2000 - 11:10:31 CDT
- Next message: Philip D. Jenkins: "Canonical Maps translating Sender: but not X-Sender:"
- Previous message: John Kerbawy: "test."
- Next in thread: Wietse Venema: "Re: 451 Error: queue file write error"
- Reply: Wietse Venema: "Re: 451 Error: queue file write error"
- Reply: Rask Ingemann Lambertsen: "Re: 451 Error: queue file write error"
- Reply: Franck Martin: "RE: 451 Error: queue file write error"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
We have a client (changed to x.x.x.x to protect the innocent), they
connect about once a minute, and the below is what happends - can anyone
see what goes wrong ?
Jun 29 17:57:30 pasmtp postfix/smtpd[3523]: > unknown[x.x.x.x]: 250 Ok
Jun 29 17:57:30 pasmtp postfix/smtpd[3523]: < unknown[x.x.x.x]: DATA
Jun 29 17:57:30 pasmtp postfix/smtpd[3523]: > unknown[x.x.x.x]: 354 End data with <CR><LF>.<CR><LF>
Jun 29 17:57:30 pasmtp postfix/cleanup[3520]: E797313FB6: message-id=<DF130C297F01D41188F4002035F07715CB4BFE
VORES>
Jun 29 17:57:52 pasmtp postfix/smtpd[3523]: warning: mail_scan_any: got EOF; expected: integer
Jun 29 17:57:52 pasmtp postfix/master[3463]: warning: process /usr/libexec/postfix/cleanup pid 3520 killed by signal 4
Jun 29 17:57:52 pasmtp postfix/smtpd[3523]: > unknown[x.x.x.x]: 451 Error: queue file write error
Jun 29 17:57:57 pasmtp postfix/smtpd[3523]: < unknown[x.x.x.x]: QUIT
Jun 29 17:57:57 pasmtp postfix/smtpd[3523]: > unknown[x.x.x.x]: 221 Bye
Jun 29 17:57:57 pasmtp postfix/smtpd[3523]: smtpd_chat_notify: notify postmaster
Jun 29 17:57:57 pasmtp postfix/smtpd[3523]: connect to subsystem private/cleanup
Jun 29 17:57:58 pasmtp postfix/smtpd[3523]: mail_scan_any: read string: EAECB13FB3
Jun 29 17:57:58 pasmtp postfix/smtpd[3523]: print int: 0
Jun 29 17:57:58 pasmtp postfix/cleanup[3528]: EAECB13FB3: message-id=<20000629155757.EAECB13FB3
pasmtp.tele.dk>
Jun 29 17:57:58 pasmtp postfix/smtpd[3523]: mail_scan_any: read integer: 0
Jun 29 17:57:58 pasmtp postfix/smtpd[3523]: disconnect from unknown[x.x.x.x]
Jun 29 17:57:58 pasmtp postfix/qmgr[3515]: EAECB13FB3: from=<double-bounce
pasmtp.tele.dk>, size=932 (queue active)
Jun 29 17:57:58 pasmtp postfix/cleanup[3528]: C16F113FB4: message-id=<20000629155757.EAECB13FB3
pasmtp.tele.dk>
Jun 29 17:57:58 pasmtp postfix/local[3529]: EAECB13FB3: to=<postmaster
pasmtp.tele.dk>, relay=local, delay=1, status=sent (forwarded as C16F113FB4)
Jun 29 17:57:59 pasmtp postfix/qmgr[3515]: C16F113FB4: from=<double-bounce
pasmtp.tele.dk>, size=1063 (queue active)
Jun 29 17:57:59 pasmtp postfix/smtp[3525]: C16F113FB4: to=<admin
ip.tele.dk>, relay=tifu.tele.dk[193.162.159.199], delay=1, status=sent (250 ok 962294279 qp 3779)
If I set debug level 3, I can see that it dies within a MIME attachement
which is another email, with a VERY long To: line - can this be the
cause ?
If so, how can I permantly reject this one ?
Running postfix-19991231-pl08
/Jesper
-- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network managerAS3292 (Tele Danmark DataNetworks) Private: Geek
AS2109 (A much smaller network ;-)
One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
- Next message: Philip D. Jenkins: "Canonical Maps translating Sender: but not X-Sender:"
- Previous message: John Kerbawy: "test."
- Next in thread: Wietse Venema: "Re: 451 Error: queue file write error"
- Reply: Wietse Venema: "Re: 451 Error: queue file write error"
- Reply: Rask Ingemann Lambertsen: "Re: 451 Error: queue file write error"
- Reply: Franck Martin: "RE: 451 Error: queue file write error"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]