Your message dated Sat, 23 Jul 2005 21:28:42 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#224564: fetchmail: passes from address with spaces to MTA
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 20 Dec 2003 08:11:18 +0000
>From [EMAIL PROTECTED] Sat Dec 20 02:11:17 2003
Return-path: <[EMAIL PROTECTED]>
Received: from moutng.kundenserver.de [212.227.126.184] 
        by master.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1AXblk-0004dY-00; Sat, 20 Dec 2003 01:43:24 -0600
Received: from [212.227.126.208] (helo=mrelayng.kundenserver.de)
        by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
        id 1AXblk-0000yR-00
        for [EMAIL PROTECTED]; Sat, 20 Dec 2003 08:43:24 +0100
Received: from [212.202.52.39] (helo=gw.coffee.homeunix.org)
        by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1)
        id 1AXblj-0000cC-00; Sat, 20 Dec 2003 08:43:23 +0100
Received: from coffee by gw.coffee.homeunix.org with local (Exim 3.36 #1 
(Debian))
        id 1AXbli-0006iF-00; Sat, 20 Dec 2003 08:43:22 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: jochen <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: fetchmail: passes from address with spaces to MTA
X-Mailer: reportbug 2.37
Date: Sat, 20 Dec 2003 08:43:22 +0100
Message-Id: <[EMAIL PROTECTED]>
Sender: jochen <[EMAIL PROTECTED]>
X-Provags-ID: kundenserver.de [EMAIL PROTECTED] 
auth:a0968221de07d5fd7961a47174745c92
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 
        2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_12_15 
        (1.212-2003-09-23-exp) on master.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no 
        version=2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_12_15
X-Spam-Level: 

Package: fetchmail
Severity: normal


I'm using option

mda "/usr/sbin/exim -oi -oee -oMr fetchmail -f '<%F>' '<%T>'"

now this executes (for example)

/usr/sbin/exim -oi -oee -oMr fetchmail -f <_Alejandro [EMAIL PROTECTED]> 
<coffee>

which results in

SIGPIPE thrown from an MDA or a stream socket error
socket error while delivering to SMTP host pop.gmx.net
Query status=2 (SOCKET)

First of all this message is rather strange (it fetches from pop.gmx.net
and doesn't deliver to it...) and then the email address <_Alejandro
[EMAIL PROTECTED]> is just not valid.

No, I cannot contact the sender and tell him to fix his MUA, since it is
spam.

fetchmail should not pass such addresses to the MDA.

PS: if you think this is not a fetchmail bug, file it to exim :)


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux gw.coffee.homeunix.org 2.4.21-rsbac #3 Fri Jun 20 00:05:43 CEST 
2003 i586
Locale: LANG=C, [EMAIL PROTECTED]


---------------------------------------
Received: (at 224564-done) by bugs.debian.org; 23 Jul 2005 19:28:51 +0000
>From [EMAIL PROTECTED] Sat Jul 23 12:28:51 2005
Return-path: <[EMAIL PROTECTED]>
Received: from krusty.dt.e-technik.uni-dortmund.de 
(mail.dt.e-technik.uni-dortmund.de) [129.217.163.1] (postfix)
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1DwPg3-0002eX-00; Sat, 23 Jul 2005 12:28:51 -0700
Received: from localhost (localhost [127.0.0.1])
        by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id EED2744016;
        Sat, 23 Jul 2005 21:28:47 +0200 (CEST)
Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1])
 by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 27078-01; Sat, 23 Jul 2005 21:28:46 +0200 (CEST)
Received: from m2a2.dyndns.org (p50914DF1.dip.t-dialin.net [80.145.77.241])
        by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 51BDE44001;
        Sat, 23 Jul 2005 21:28:46 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
        by merlin.emma.line.org (Postfix) with ESMTP id 77FD0798A1;
        Sat, 23 Jul 2005 21:28:45 +0200 (CEST)
Received: from m2a2.dyndns.org ([127.0.0.1])
 by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 21805-14; Sat, 23 Jul 2005 21:28:43 +0200 (CEST)
Received: by merlin.emma.line.org (Postfix, from userid 500)
        id 4CA7E798B0; Sat, 23 Jul 2005 21:28:43 +0200 (CEST)
Date: Sat, 23 Jul 2005 21:28:42 +0200
From: Matthias Andree <[EMAIL PROTECTED]>
To: jochen <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#224564: fetchmail: passes from address with spaces to MTA
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: amavisd-new at dt.e-technik.uni-dortmund.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Jochen,

your MDA option is broken. You MUST NOT enclose the %T or %F in single
quotes, fetchmail does that for you.

So what you've really got was not what you assumed, but instead:

/usr/sbin/exim -oi -oee -oMr fetchmail -f '<'_Alejandro [EMAIL PROTECTED]'>' 
'<'coffee'>'

which is the same as:

/usr/sbin/exim -oi -oee -oMr fetchmail -f '<_Alejandro' '[EMAIL PROTECTED]>' 
'<coffee>'

Use this instead:

mda "/usr/sbin/exim -oi -oee -oMr fetchmail -f %F %T"

-- 
Matthias Andree


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to