From: Thijs <thijs@balpol.tudelft.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.21-ac3
Date: Wed, 25 Jun 2003 22:29:26 +0200 [thread overview]
Message-ID: <3EFA0626.3060104@balpol.tudelft.nl> (raw)
In-Reply-To: <2ltx.Us.17@gated-at.bofh.it>
Hi,
Since 2.4.21-ac2 i'm experiencing problems with Postfix on Debian
Stable. Messages get corrupted while being handled by Postfix.
Vanilla 2.4.21 and 2.4.21-ac1 are fine, but 2.4.21-ac2/3 causes
problems. Going back to ac1 resolves the issue. I tried kernels on
several Debian servers, but all have the same problem. Could be it's
something in postfix that emerges with this specific patch, but it's at
least curious. I'm not too familiar with this matter unfortunately.
The only logentries i see are:
postfix/qmgr[399]: warning: active/0/4/04E5B17E3F: too many length bits,
record type 255
postfix/qmgr[399]: warning: 04E5B17E3F: envelope records out of order
postfix/qmgr[399]: warning: saving corrupt file "04E5B17E3F" from queue
"active" to queue "corrupt"
...or just...
postfix/smtp[536]: warning: corrupted queue file: active/C/7/C7AC317E3F
Tested on: Intel PPro, Intel Celeron, AMD Duron
Tested on: ext2 and ext3
All other programms seem to work fine, no other strange messages
whatsoever...
Regards,
--Thijs Welman
Delft University of Technology, the Netherlands
next parent reply other threads:[~2003-06-25 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ltx.Us.17@gated-at.bofh.it>
2003-06-25 20:29 ` Thijs [this message]
2003-06-25 22:15 ` weird postfix mailspool corruption with 2.4.21-ac2+ (was Re: Linux 2.4.21-ac3) Scott McDermott
2003-06-26 6:30 ` Linux 2.4.21-ac3 Geller Sandor
2003-06-27 19:37 David Mansfield
[not found] <fa.cf4gkbu.1h1o5ik@ifi.uio.no>
[not found] ` <fa.hh6ttrp.1d52bhj@ifi.uio.no>
2003-06-25 20:54 ` Jonathan Hudson
-- strict thread matches above, loose matches on Subject: below --
2003-06-25 16:36 Alan Cox
2003-06-25 22:10 ` Jonathan McDowell
2003-06-27 17:11 ` Mika Liljeberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EFA0626.3060104@balpol.tudelft.nl \
--to=thijs@balpol.tudelft.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).