Fwd: Re: [imp] uuencode

[Richard Heggs]

----- Forwarded message from Richard Heggs 
<Richard.Heggs at nottinghamcity.gov.uk> -----
    Date: Thu, 23 Jan 2003 09:09:14 +0000
    From: Richard Heggs <Richard.Heggs at nottinghamcity.gov.uk>
Reply-To: Richard Heggs <Richard.Heggs at nottinghamcity.gov.uk>
 Subject: Re: [imp] uuencode
      To: Michael M Slusarz <slusarz at bigworm.colorado.edu>

Quoting Michael M Slusarz <slusarz at bigworm.colorado.edu>:

> Quoting Richard Heggs <richard.heggs at nottinghamcity.gov.uk>:
> 
> | Hi list,
> | 
> | I see from a post last July that Michael M Slusarz has added support for
> | uuencoded messages.  This is a huge sticking point for our adoption of
> | Imp (in fact I think it's the only one left).  Will this be going into 
> | Imp 3.2? 
> | I've just configured yesterdays RELENG snapshop, and it doesn't appear to 
> | be there yet......
> 
> I did.  See:
> http://cvs.horde.org/diff.php/horde/lib/MIME/Part.php?r1=1.54&r2=1.55&ty=h
> This change wass only good for HEAD though.

Well, at least it's ready for 4.0, which is good news... when do you expect to 
be releasing beta versions of that?

> Some comments:
> 1. What mail composers are sending messages that are uuencoded?  Those mail 
> composers are absolute crap.  Honestly, any recent mailer won't send via 
> uuencode, especially since MIME was implemented over 10 years ago - and 
> MIME has no support for uuencoding _at all_.  Thus, my solution is hackish 
> as is since there is no RFC to rely on.

Two Words: Local Government.  We currently have nearly 200 users using Horde & 
Imp (out of a potential 2500), and as users have been migrated away from the 
old (and dreadful, but at least is understands uuencode) web based email 
system, the number of complaints about people receiving gibberish instead of 
attachments has risen.  There are some departments and councils who are still 
using ancient versions of Eudora, Outlook, etc.  In addition, Outlook 97 at 
least has the option to choose uuencoded attachments over MIME.  We can educate 
our users about this, but we can't dictate to the n people outside the 
authority who have their clients set wrongly (or are using ancient clients) and 
send email to us on a regular basis.  It's frustrating, but that's the joy of 
supporting users I suppose. :P

> 2. This code can't be backported to IMP 3.x since the MIME framework has 
> been completely reworked in IMP 4.0.  If you compare HEAD and RELENG, you 
> will notice that MIME_Part:: doesn't even have a decode() function in 
> RELENG.
> 
> Feel free to adapt it to your setup.  But in light of #1, and the fact that 
> I personally haven't seen a single uuencoded message, I see no reason to 
> make an effort to potentially cause other problems in the stable 3.x 
> codebase in an effort to backport it.

I can send you hundreds :/

-- 
Richard Heggs
Systems Analyst
City of Nottingham Council

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

----- End forwarded message -----


-- 
Richard Heggs
Systems Analyst
City of Nottingham Council

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/


***************************************************************************
This e-mail (and any attachments) is confidential and may contain personal
views which are not the views of Nottingham City Council unless specifically
stated. If you have received it in error, please delete it from your system,
do not use, copy or disclose the information in any way nor act in reliance
on it and notify the sender immediately. Please note that Nottingham City
Council monitors e-mails sent or received. Further communication will
signify your consent to this.
***************************************************************************