headers
Mack | 2 Oct 2007 00:55

Upgrading..... 2.52 -> current

I'm about to build a new machine, based on ubuntu (server) this time instead
of RHEL and hopefully will move MD forward to the latest build (using 2.52
atm due to being lazy about upgrading and patching md.pl with some stuff),
without me being overly lazy reading the patch notes for each version going
forward, ./......
Anybody know of anything that may bite me on the ass with the filter code ?

TIA

Mack
Permalink | Reply | 0 comments |
headers
Dale Moore | 4 Oct 2007 20:09
Picon
Favicon

Mimedefang 2.64-Beta-1 build Notes

I built mimedefang for first time.
I am building it for Solaris 9, Solaris 10, Redhat Fedora Core 5 (32 and 64),
and Fedora 7 (32 and 64).
I am testing to see how it might fit into our email environment.
Here are some notes about this novice build/install procedure.

Solaris 9 problem with mimedefang.c and AF_LOCAL .
I see that this has been covered earlier on this mailing list.
No further comment necessary.

We try to keep our source area and build area or object area
separate. To do this we use Make's VPATH features.  I relealize that
on some remote system there is a make that doesn’t do VPATH,
so you might be reluctant to take advantage of this configuration.
We find it tremendously useful.  Sure would be nice if your
Makefile.in accomodated $(srcdir) and perhaps $(top_srcdir)
variables in addition to setting VPATH.  Many of the other
autoconf'd and automake'd applications seem to do this quite well.

In configure.in there exists a macro for determining whether
libmilter needs libsm.  This macro appears to be correct.
But this macro, MD_MILTER_SM, is never called.  Instead
an approach that doesn’t work quite as well is used.
This works for me is in the macro MD_MILTER_SM
   AC_MSG_CHECKING(whether libmilter must be linked with libsm)
   RESULT=`$NM $LIBMILTER | fgrep sm_strlcpy`
   if test -z "$RESULT" ; then
      AC_MSG_RESULT(no)
   else
      AC_MSG_RESULT(yes)
(Continue reading)

Permalink | Reply | 0 comments |
headers
David F. Skoll | 4 Oct 2007 20:29
Favicon

Re: Mimedefang 2.64-Beta-1 build Notes

Hi, Dale,

> We try to keep our source area and build area or object area
> separate. To do this we use Make's VPATH features.  I relealize that
> on some remote system there is a make that doesn’t do VPATH,
> so you might be reluctant to take advantage of this configuration.
> We find it tremendously useful.  Sure would be nice if your
> Makefile.in accomodated $(srcdir) and perhaps $(top_srcdir)
> variables in addition to setting VPATH.  Many of the other
> autoconf'd and automake'd applications seem to do this quite well.

OK... I'm not familiar with this.  Could you send me (off-list) an
example (or even better a patch? :-))

> In configure.in there exists a macro for determining whether
> libmilter needs libsm.  This macro appears to be correct.
> But this macro, MD_MILTER_SM, is never called.  Instead
> an approach that doesn’t work quite as well is used.

Actually, I'm thinking of removing all that cruft.  Modern libmilters
do not need libsm and I don't know if it's worth supporting ancient ones.

> Also in configure.in there exists a macro for determining
> whether libsm needs libldap.  This macro is named MD_SM_LDAP.
> It is called only from MD_MILTER_SM .  But because
> MD_MILTER_SM is never called, MD_SM_LDAP is never called.

I'll look into fixing it.  To be honest, configure.in more-or-less
accreted features until it "worked for me".  It probably needs
an overhaul.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Steffen Kaiser | 5 Oct 2007 10:31
Picon

Re: accept, then scan?


On Fri, 21 Sep 2007, Andy Lyttle wrote:

> I'll be upgrading from Slackware 9.0 to Slackware 12.0, which will take perl 
> from 5.8.0 to 5.8.8.  Or, I could scrap that and build my own perl, but I'd

On Debian woody I ran with my "alternative" perl installation in 
/usr/local. That has the disadvantage that you need to watch out for 
security updates yourself, but the advantage that the version of perl 
_and_ the modules are the version you choose. Woody's versions of modules 
were far too old for MIMEDefang. It was easy going.

Bye,

--

-- 
Steffen Kaiser
Permalink | Reply | 0 comments |
headers
Kevin A. McGrail | 10 Oct 2007 21:31
Favicon
Gravatar

OT: Symantec AntiVirus for Linux

Has anyone used the new Symantec Endpoint Protection (aka SAV 11) that just 
came out that includes Symantec AntiVirus(TM) for Linux?  Obviously, my 
thoughts are to then see about tying this into MD.

Regards,
KAM
Permalink | Reply | 0 comments |
headers
nus4u | 12 Oct 2007 09:45
Picon

Error: Check you filter rules....

Hi,

I ve got some error Msgs where i don t have any solution to
fix them:

#################
Oct  8 15:20:39 asgw01 sendmail[6355]: l98DKbTb006355: Milter: from=<pha <at> medsino.com>, reject=451
4.3.2 Please try again later
Oct  8 15:20:39 asgw01 mimedefang-multiplexor[1454]: Slave 2 stderr: MIME::Parser: can't close: No
space left on device at /usr/lib/perl5/site_perl/5.8.5/MIME
/Parser.pm line 874.
Oct  8 15:20:39 asgw01 mimedefang-multiplexor[1454]: Slave 2 died prematurely -- check your filter rules
Oct  8 15:20:39 asgw01 mimedefang-multiplexor[1454]: Reap: slave 2 (pid 5145) exited normally with
status 28 (SLAVE DIED UNEXPECTEDLY)
Oct  8 15:20:39 asgw01 mimedefang-multiplexor[1454]: Slave 2 resource usage: req=28, scans=28,
user=2.841, sys=0.331, nswap=0, majflt=0, minflt=5702, maxrss=0
, bi=0, bo=0
Oct  8 15:20:39 asgw01 mimedefang[1469]: Error from multiplexor: ERR No response from slave
###############

In Mimedefang i use only the funcion filter_recipient for grey- and whitelisting.
/var/spool/MIMEDefang is on a tmpfs Filesystem with 50 MB
( which seems to be enough because not the whole msg is written there!)
When i look with "df" max 1-2% are used.

System is a RHEL 4 , Sendmail 14.1 and Mimedefang 2.63 

Thanks for any Hints...

Regards
(Continue reading)

Permalink | Reply | 1 comment |
headers
John Nemeth | 12 Oct 2007 10:16
Picon
Favicon

Re: Error: Check you filter rules....

On Mar 4,  4:21am, nus4u <at> gmx.net wrote:
} 
} I ve got some error Msgs where i don t have any solution to
} fix them:
} 
} #################
} Oct  8 15:20:39 asgw01 mimedefang-multiplexor[1454]: Slave 2 stderr: MIME::Parser: can't close: No
space left on device at /usr/lib/perl5/site_perl/5.8.5/MIME/Parser.pm line 874.
} ###############
} 
} In Mimedefang i use only the funcion filter_recipient for grey- and
} whitelisting.  /var/spool/MIMEDefang is on a tmpfs Filesystem with 50
} MB ( which seems to be enough because not the whole msg is written
} there!) When i look with "df" max 1-2% are used.

     Actually, multiple copies of the whole message is written there
(along with any other messages being processed at the same time).  50
MB isn't nearly enough.  You should have maxmsgsize * maxnumber of msgs
* 3.  I trimmed out the irrelevant error messages.  The one left is
quite explicit.

}-- End of excerpt from nus4u <at> gmx.net
Permalink | Reply | 501 comments |
headers
David F. Skoll | 12 Oct 2007 11:32
Favicon

Re: Error: Check you filter rules....

nus4u <at> gmx.net wrote:

> Oct 8 15:20:39 asgw01 mimedefang-multiplexor[1454]: Slave 2 stderr:
> MIME::Parser: can't close: No space left on device at
> /usr/lib/perl5/site_perl/5.8.5/MIME/Parser.pm line 874.

Check all your partitions.  I bet /tmp is full.  (MIME::tools likes
to write in /tmp, unfortunately.)

Regards,

David.
Permalink | Reply | 0 comments |
headers
nus4u | 12 Oct 2007 13:11
Picon

Re: Error: Check you filter rules....

"Check your filter rules"....

I had to read a little bit better....

My /var/spool/MIMEDefang was so small because i return a
"ACCEPT_AND_NO_MORE_FILTERING", so not the whole Message
is copied there multiple times.
BUT :
In one Routine i return a "CONTINUE" so this Routine perhaps
with a bigger Msg results in the error entries...

I changed that and check tomorrow if this happens again....

Thanks for help

Regards
Christoph
--

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger
Permalink | Reply | 501 comments |
headers
G.W. Haywood | 12 Oct 2007 19:14
Picon
Favicon

Documentation errata

Hi there,

http://www.mimedefang.org/node.php?id=1

Says

MIME::tools which should read MIME::Tools

and

IO::stringy  which should read IO::Stringy

and it talks about

Mail::Tools

which CPAN has never heard of.

--

73,
Ged.
Permalink | Reply | 0 comments |

Gmane