Bug 65208

Summary:	maildrop crashed with code 0x06 (io error?)
Product:	Gentoo Linux	Reporter:	Moxum <moxum>
Component:	Current packages	Assignee:	Net-Mail Packages <net-mail+disabled>
Status:	RESOLVED NEEDINFO
Severity:	critical	CC:	veldy
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Moxum 2004-09-24 07:39:46 UTC

when ever maildrop starts processing my .mailfilter it crashes with a 0x06 error code. 

-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
1813A5782F     6662 Fri Sep 24 16:31:14  xxxxx@xxxxxx.com
                    (temporary failure. Command output: maildrop: signal 0x06)
                                         moxum@localhost.xxxxx.xxxxx.xxxxxx

-- 6 Kbytes in 1 Request.


Reproducible: Always
Steps to Reproduce:
1.
2.
3.




I have tried to compile maildrop without the -O2 flags, that changed the error
code to 0xB (segfault?)

For now I just keep my .mailfilter emtpy, that way maildrop delivers perfectly.

Comment 1 Moxum 2004-09-28 04:17:17 UTC

I resolved the issue by editting the ebuild definition. I disabled mysql and ldap recompiled it and it works for me now.

Comment 2 Andrej Kacian (RETIRED) gentoo-dev

2004-10-01 15:20:40 UTC

What version of maildrop, and what did you do to the ebuild?

Comment 3 Thomas T. Veldhouse 2004-10-30 08:01:39 UTC

I also see maildrop 0x0B (Signal 11) errors when maildrop is compiled with -Os.  This is ONLY a problem when it attempts to filter an email [it processes fine, but if a filter match occurs, so does a 0x0B].

Comment 4 Fernando J. Pereda (RETIRED) gentoo-dev

2005-02-10 05:44:51 UTC

maildrop-1.8.0 is in portage right now. Still fails for you ? If it is fixed maybe is time to stabilize it.

Cheers,
Ferdy

Comment 5 Fernando J. Pereda (RETIRED) gentoo-dev

2005-02-13 05:23:04 UTC

maildrop-1.8.0-r1 is on CVS.

Need to know if still fails for you.

Cheers,
Ferdy

Comment 6 Qubax 2005-05-16 04:09:55 UTC

just wanted to add, that i have got the same problem. couldn't find a solution for that.

as mentioned above, an error only occurs if maildrop starts to filter something. without any rules in ~/.mailfilter, it delivers into DEFAULT without problems.

Comment 7 Thomas T. Veldhouse 2005-05-16 06:05:22 UTC

I do not use Gentoo at the moment, so my ability to verify is non-existant.  However, it seems it has been seen by somebody else.  I do recall the issue being partly based upon optimization level and only -O will work.  Any greater optimization (such as -O2, -O3 or -Os) causes this failure.  I think there is a memory bug in the software that is triggered by the optimization level, but has nothing to do with the optimization level in and of itself.