On Fri, Feb 17, 2006, Matthias Andree wrote:
Could you manually log into the server with telnet or netcat or perhaps
openssl and see if the BODY.PEEK[HEADER] works?
A3 FETCH 1 BODY.PEEK[HEADER]
Ah- there is NO encoding header in the response.
Subject: TEST
To: anthony(_dot_)kim(_at_)walgreens(_dot_)com
Content-Type: text/plain; charset=iso-8859-1
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.com;
h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
b=Mz0dPtOFdYiXGOSw5t0QPhMcDqPShxmylT2+XolvVNXROtr0H7O4Otiy4wab/n4RKaE87pj6MPoWEl16/QxPfw6kLfy6DUHTw7GZrGhNudXgeBeYnu9Sdg95QBF4s3NCV+5Q74aPWi9FW7j6QyJnC4ikER+WAT9BR2H/7ktz7Bs=
;
MIME-Version: 1.0
X-PMX-Version: 5.1.2.240295, Antispam-Engine: 2.3.0.0, Antispam-Data:
2006.02.17.052605
X-MIMETrack: Itemize by SMTP Server on DomSMTP2/Walgreens(Release
6.5.5|November 30, 2005) at
02/17/2006 07:53:36,Serialize by Router on DomSMTP2/Walgreens(Release
6.5.5|November 30, 2005) at
02/17/2006 07:53:37,Itemize by SMTP Server on NotesMail7/Walgreens(Release
6.5.4FP1 | June 19, 2005) at
02/17/2006 07:53:37,Serialize by Router on NotesMail7/Walgreens(Release
6.5.4FP1 | June 19, 2005) at
02/17/2006 07:53:38,Serialize complete at 02/17/2006 07:53:38
But there is for FETCH 1 BODY[]
Subject: TEST
To: anthony(_dot_)kim(_at_)walgreens(_dot_)com
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.com;
h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
b=Mz0dPtOFdYiXGOSw5t0QPhMcDqPShxmylT2+XolvVNXROtr0H7O4Otiy4wab/n4RKaE87pj6MPoWEl16/QxPfw6kLfy6DUHTw7GZrGhNudXgeBeYnu9Sdg95QBF4s3NCV+5Q74aPWi9FW7j6QyJnC4ikER+WAT9BR2H/7ktz7Bs=
;
MIME-Version: 1.0
X-PMX-Version: 5.1.2.240295, Antispam-Engine: 2.3.0.0, Antispam-Data:
2006.02.17.052605
X-MIMETrack: Itemize by SMTP Server on DomSMTP2/Walgreens(Release
6.5.5|November 30, 2005) at
02/17/2006 07:53:36,Serialize by Router on DomSMTP2/Walgreens(Release
6.5.5|November 30, 2005) at
02/17/2006 07:53:37,Itemize by SMTP Server on NotesMail7/Walgreens(Release
6.5.4FP1 | June 19, 2005) at
02/17/2006 07:53:37,Serialize by Router on NotesMail7/Walgreens(Release
6.5.4FP1 | June 19, 2005) at
02/17/2006 07:53:38,Serialize complete at 02/17/2006 07:53:38
Check if the response to the A3 FETCH command includes the CTE header.
If it does, using this command and making fetchmail parse the different
response format would be the cheapest workaround I could think of, and,
unless someone else has a good idea, the only that might get implemented
in 6.3.X.
Unfortunately, not.
In 6.4.X, we might implement an option so that fetchmail does not split
header/body fetch but get the whole message including header in one huge
piece as POP3 does which makes undeliverable mail more expensive though.
I wanted to try POP3 as a test but our server does not have that
enabled. Sign me up for the beta if this happens. :)
Is there any harm in a procmail recipe that adds CTE:
quoted-printable to my mails?
Well, aside from the general dangers of procmail integration, no (its
error fallthrough behavior is the main problem).
Yes, it would be a shame to have to do this, although for now I
have it as an ugly hack.
Thanks again,
Anthony
_______________________________________________
Fetchmail-friends mailing list
Fetchmail-friends(_at_)lists(_dot_)ccil(_dot_)org
http://lists.ccil.org/cgi-bin/mailman/listinfo/fetchmail-friends