Your message dated Wed, 16 Jun 2010 14:18:12 +0200
with message-id <[email protected]>
and subject line Re: Masqmail crashes on receiving an specific mail message 
from fetchmail
has caused the Debian Bug report #388102,
regarding Masqmail crashes on receiving an specific mail message from fetchmail.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
388102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388102
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: masqmail
Version: 0.2.20-1

      Masqmail crashed today each time it got fed a specific spam
message by fetchmail, retrieved from one of my POP accounts. This is the
only such incident in several years of use.
      I retrieved the message with "fetchmail --bsmtp /tmp/smtp.log",
which dumps the SMTP data that would normally be sent to masqmail into
the given file, and its contents are attached as "smtp.log".
      I've hidden my e-mail addresses and login names there with
"xxxxxx" and "@example.org", but otherwise the content is untouched.
      The machine is an Apple PowerBook, with MacOS X 10.3.9. I compiled
masqmail from the Debian source package, installed in "/usr/sbin/", and
I'm reporting the bug here because it does not have a web page anymore,
and the Debian package maintainer is also its author (Hi, Oliver!).
      The version of masqmail as reported by "masqmail -bV" is:

masqmail 0.2.20 +resolver +smtp-server +pop3 +auth +ident

      Here is the crash report:

-------------------------------------------------------------------
Host Name:      Silver-Bullet.local
Date/Time:      2006-09-18 17:23:21 +0200
OS Version:     10.3.9 (Build 7W98)
Report Version: 2

Command: masqmail
Path:    /usr/sbin/masqmail
Version: ??? (???)
PID:     25473
Thread:  0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x02008000

Thread 0 Crashed:
0   libSystem.B.dylib           0x90007a60 strcpy + 0x60
1   libglib-1.2.0.dylib         0x000d61a4 g_strdup + 0x34 (gstrfuncs.c:94)
2   masqmail                    0x00002250 accept_message_stream + 0x228 
(accept.c:151)
3   masqmail                    0x00002c80 accept_message + 0x1c (accept.c:473)
4   masqmail                    0x000128fc smtp_in + 0x3e0 (smtp_in.c:254)
5   masqmail                    0x0000b090 accept_connect + 0xec (listen.c:88)
6   masqmail                    0x0000b480 listen_port + 0x390 (listen.c:210)
7   masqmail                    0x0000d198 main + 0xb88 (masqmail.c:716)
8   masqmail                    0x00001c98 _start + 0x188 (crt.c:267)
9   masqmail                    0x00001b0c start + 0x30

PPC Thread State:
  srr0: 0x90007a60 srr1: 0x0000d030                vrsave: 0x00000000
    cr: 0x24004242  xer: 0x00000004   lr: 0x000d61a4  ctr: 0x90007a00
    r0: 0x00000000   r1: 0xbffff380   r2: 0xa0000b8c   r3: 0x01806400
    r4: 0x02007004   r5: 0x00000000   r6: 0xfefefeff   r7: 0x80808080
    r8: 0x61676520   r9: 0x02008000  r10: 0x6066641f  r11: 0x000df6b8
   r12: 0x80808080  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
   r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
   r20: 0x00000000  r21: 0xa00015ac  r22: 0x00000000  r23: 0x0000004b
   r24: 0xa00015ac  r25: 0x00000ac3  r26: 0x00401b30  r27: 0x00000000
   r28: 0x004013b0  r29: 0x01806400  r30: 0x01805400  r31: 0x00002034

Binary Images Description:
    0x1000 -    0x1cfff masqmail        /usr/sbin/masqmail
   0xbe000 -    0xdefff libglib-1.2.0.dylib     /sw/lib/libglib-1.2.0.dylib
0x8fe00000 - 0x8fe4ffff dyld    /usr/lib/dyld
0x90000000 - 0x9014ffff libSystem.B.dylib       /usr/lib/libSystem.B.dylib
0x90c32000 - 0x90c4cfff libresolv.9.dylib       /usr/lib/libresolv.9.dylib
0x939d0000 - 0x939d4fff libmathCommon.A.dylib   
/usr/lib/system/libmathCommon.A.dylib
-------------------------------------------------------------------

      Cheers,
--
        Alberto González Palomo
        Toledo, España / Saarbrücken, Deutschland
        [email protected]

Attachment: smtp.log
Description: Binary data


--- End Message ---
--- Begin Message ---
tag 388102 unreproducible
thanks

I was not able to reproduce a masqmail crash with the supplied
message. I used the following command to insert the mail into
masqmail:

    <smtp.log awk '
        BEGIN{
            print "EHLO";
        }
        {
            sub(/xxx*@(localhost|example.org)/, "mei...@localhost");
            print;
        }
    ' | masqmail -bs


I want to guess about what could have caused the crash:

The version that crashed was linked against glib-1.2, while the
current version is linked against glib-2. The backtrace shows the
crash in:

> 0   libSystem.B.dylib         0x90007a60 strcpy + 0x60
> 1   libglib-1.2.0.dylib       0x000d61a4 g_strdup + 0x34 (gstrfuncs.c:94)
> [...]

Special about the supplied mail is that it contains a line (#99) with
more than 4096 characters. This probably is related to the error.

Masqmail 0.2.21 and newer can handle arbitrary long message data lines
when reading mails. I checked this by examining spooles messages.
Unfortunately, I cannot dig into the development history before
0.2.21. The ChangLog and NEWS files do not mention it.


Be the crash caused by glib-1.2 or masqmail-0.2.20, it is gone with
glib-2 and masqmail-0.2.21 (and greater).

Therefore I close this bug.


meillo


--- End Message ---

Reply via email to