MailTools and MailScanner...

[Michael Mansour]

Hi Scott,

--- Scott Silva <ssilva at sgvwater.com> wrote:

> on 12/4/2007 1:58 PM Philip Zeigler spake the
> following:
> > Scott Silva wrote:
> >> on 12/4/2007 12:06 PM Philip Zeigler spake the
> following:
> >>> ajos1 at onion.demon.co.uk wrote:
> >>>> -
> >>>>
> >>>> The reply back is:
> >>>>
> >>>> ============================
> >>>>
> >>>>  From: mark at zzzzzzzz    to    ajos1 at zzzzzzzz   
>     Date:  Sun, 2 
> >>>> Dec 2007 22:35:59 +0100        Subject:  ajos1
> - Re: MailTools and 
> >>>> MailScanner...        CC/Multi-To:  (none)     
>   Attachments:   
> >>>> (none)      * ajos1 at zzzzzzzz (ajos1 at zzzzzzzz)
> [071202 21:07]:
> >>>>  
> >>>>> Not sure if you use MailScanner or not...
> >>>>>     
> >>>>
> >>>> No, never heard of it.  Don't know where it is
> kept (not on CPAN).
> >>>>
> >>>>  
> >>>>> Since MailTools 2.01 - We have an error... and
> we are not sure if it
> >>>>> is a MailTools problem or a MailScanner
> problem... See the message at
> >>>>> the end...
> >>>>>     
> >>>>
> >>>> The MailTools 2.xx code is a massive clean-up. 
> One of the things which
> >>>> changed, is a stricter use of clean coding
> techniques.
> >>>>
> >>>>  
> >>>>> [root at onion perl_ext]# MailScanner -v | head
> -20
> >>>>> Variable "$FIELD_NAME" is not imported at
> >>>>>    /usr/lib/MailScanner/MailScanner/Message.pm
> line 6907.
> >>>>>     
> >>>>
> >>>> Understandable.  Yes an effect of my cleanups.
> >>>>
> >>>>  
> >>>>> package Mail::Header;
> >>>>>                      $arr->[1] =~
> /\A$FIELD_NAME/o;
> >>>>>     
> >>>>
> >>>> Something very bad is happening here: code is
> added to an existing
> >>>> module.  This code should either be added in
> the core Mail::Header
> >>>> package OR should be added using the OO
> extension mechanism.
> >>>>
> >>>> The author of the mailscanner has to clean-up
> his code, IMO.  I could
> >>>> export the $FIELD_NAME, but preferrably not.
> >>>>   
> >>> Just did a yum update on my Centos 5 system and
> it installed 
> >>> MailTools-2.02.  Is there a fix planned for this
> any time soon or 
> >>> should I downgrade to 1.7.7 and exclude the
> update?
> >>>
> >>> Philip
> >> Which repo did you get this from? I only see it
> in Fedora.
> >>
> > It updated today from the rpmforge repo.
> > 
> > Philip
> Now I see it. My mirror must have been a little
> slow.
> The only fix so far is to downgrade to 1.7x
> MailTools.
> Who knows if or when Julian might work on this. Just
> because the MailTools 
> coder says he is using clean coding techniques
> doesn't mean it is 100% proper 
> coding. We will have to see what else breaks.

Have you noticed anything else break with the latest
RPMforge perl-MailTools and the latest MailScanner
4.66 beta?

Michael.


      Make the switch to the world's best email. Get the new Yahoo!7 Mail now. www.yahoo7.com.au/worldsbestemail