TR: [Mailman-Users] File attachement problems after install Mailman

Mailing Caranta mailing at caranta.com
Wed Aug 18 01:35:16 CEST 2004


 oups, sorry for previous post, file got attached, as it shouldn't have been
:(


> -----Message d'origine-----
> De : Mailing Caranta [mailto:mailing at caranta.com] 
> Envoyé : mercredi 18 août 2004 01:24
> À : 'mailman-users at python.org'
> Objet : RE: [Mailman-Users] File attachement problems after 
> install Mailman
> 
> Oki, you're right, I changed a few things, and, even though I 
> don't get why it didn't work, I can send mail to my users normally ...
> 
> Except when it come to be sent to a mailman list address :(
> 
> When I do this, I get once again the uuencoded attachement as 
> raw text in the body.
> 
> I noticed this, in the cource of the sent mail :
> **************************************************************
> ***************************************
> Return-Path: <lechat-bounces at caranta.com>
> Received: from minixer.caranta.com (localhost.localdomain [127.0.0.1])
> 	by caranta.com (8.12.8/8.11.6) with ESMTP id i7HNFcqP003544;
> 	Wed, 18 Aug 2004 01:15:38 +0200
> Received: from caranta.com (minixer.lan.local [192.168.10.1])
> 	by caranta.com (8.12.8/8.11.6) with ESMTP id i7HNF9qP003510
> 	for <lechat at caranta.com>; Wed, 18 Aug 2004 01:15:09 +0200
> Received: (from arthur at localhost)
> 	by caranta.com (8.12.8/8.12.5/Submit) id i7HNF8g9003508
> 	for lechat at caranta.com; Wed, 18 Aug 2004 01:15:08 +0200
> Date: Wed, 18 Aug 2004 01:15:08 +0200
> From: Arthur CARANTA <arthur at caranta.com>
> Message-Id: <200408172315.i7HNF8g9003508 at caranta.com>
> To: lechat at caranta.com
> X-caranta.com-MailScanner: Found to be clean, Found to be clean
> X-caranta.com-MailScanner-SpamCheck: not spam (whitelisted),
> 	SpamAssassin (score=-3.234, required 5, autolearn=not 
> spam, AWL 1.67,
> 	BAYES_00 -4.90), not spam (whitelisted),
> 	SpamAssassin (score=2.923, required 5, AWL -4.91,
> 	MIME_HEADER_CTYPE_ONLY 2.23, UNWANTED_LANGUAGE_BODY 2.80,
> 	UPPERCASE_50_75 0.00, V_NO_VOWEL_7 0.70, V_NO_VOWEL_8 1.10,
> 	V_NO_VOWEL_9 0.50, V_VERY_LONG_WORD_2 0.50)
> Cc: 
> Subject: [Lechat] [2004-08-18] Le chat du jour
> X-BeenThere: lechat at www.caranta.com
> X-Mailman-Version: 2.1.5
> Precedence: list
> Reply-To: lechat at caranta.com
> List-Id: lechat.www.caranta.com
> List-Unsubscribe: 
> <http://minixer.caranta.com/mailman/listinfo/lechat>,
> 	<mailto:lechat-request at www.caranta.com?subject=unsubscribe>
> List-Post: <mailto:lechat at www.caranta.com>
> List-Help: <mailto:lechat-request at www.caranta.com?subject=help>
> List-Subscribe: <http://minixer.caranta.com/mailman/listinfo/lechat>,
> 	<mailto:lechat-request at www.caranta.com?subject=subscribe>
> Content-Type: multipart/mixed; boundary="===============1423464382=="
> Sender: lechat-bounces at caranta.com
> Errors-To: lechat-bounces at caranta.com
> X-caranta.com-MailScanner-Information: Please contact the ISP 
> for more information
> X-MailScanner-From: lechat-bounces at www.caranta.com
> Status:   
> 
> --===============1423464382==
> 
> Voici le chat du 2004-08-18
> b(e)gin 664 2004-08-18- Le chat.jpg (<< the b(e)gin is no mistake ;) )
> M_]C_X``02D9)1@`!`0```0`!``#_VP!#``@&!@<&!0@'!P<)"0@*#!0-#`L+
> M#!D2$P\4'1H?'AT:'!P@)"XG("(L(QP<*#<I+#`Q-#0T'R<Y/3 at R/"XS-#+_
> (...cut here...)
> MX]:T]EZ9%RG^-,F\*>'KC;YVA::^T87-JG`_*H&\$^%G;<?#VF9P1_Q[)T/X
> $4`?_V0``
> `
> end
> 
> --===============1423464382==
> Content-Type: text/plain; charset="iso-8859-1"
> MIME-Version: 1.0
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
> 
> _______________________________________________
> Lechat mailing list
> Lechat at www.caranta.com
> http://minixer.caranta.com/mailman/listinfo/lechat
> 
> --===============1423464382==--
> **************************************************************
> ***************************************
> 
> The mailing list bottom lines are seen as attahced files, 
> whereas the pic itself doesn't ...
> I have never ever tryied this before, but is it possible that 
> MIME and uuencode attachements are in the very same email ?
> 
> 
> Best Regards,
> ------------------------------
> Arthur CARANTA
> mailing at caranta.com
> http://www.caranta.com
> ------------------------------ 
> 
> > -----Message d'origine-----
> > De : Mark Sapiro [mailto:msapiro at value.net] 
> > Envoyé : mardi 17 août 2004 18:21
> > À : Mailing Caranta; mailman-users at python.org
> > Objet : Re: [Mailman-Users] File attachement problems after 
> > install Mailman
> > 
> > Mailing Caranta wrote:
> > >
> > >I have a problem that appeared just after installing Mailman.
> > >
> > >I have a cron job that sends a picture every day to some 
> of my users.
> > >To do this I use :
> > >
> > >cat picture.jpg |uuencode picture.jpg|mail user at domain.com
> > 
> > Piping the file into uuencode with cat is an unnecessary step; you
> > could just do
> > 
> >  uuencode picture.jpg picture.jpg|mail user at domain.com
> > 
> > but this has nothing to do with your problem.
> > 
> > >
> > >I used to work perfectly, but now, the received mail 
> hasn't the image
> > >attached to it.
> > >Instead of this, the mail has in plain text (as body) the 
> > Uuencoded file
> > >(Begin ----, etc, etc)
> > 
> > It is highly unlikely that this has anything to do with Mailman.
> > 
> > The received mail you describe is exactly what a mail message
> > containing a uuencoded file normally looks like. Whether you see the
> > uuencoded file as "raw text" or as an attachment depends on the MUA
> > that you use to view the mail.
> > 
> > --
> > Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
> > San Francisco Bay Area, California    better use your sense 
> - B. Dylan
> > 




More information about the Mailman-Users mailing list