An.H.Nguyen | 1 Aug 01:40 2007
Picon

Re: Re: multiplexor error

The bayes tests already showed up this morning.
Now there are some issues after bayes and autowhitelist is up and 
running....
I am able to increase the bayes db to 50mb but the autowhitelist seems to 
have a limit of 1mb...
Is there a way to increase autowhitelist_db size?

There are some autowhitelist errors which still happen a few times a day...
Is there a way to fix these errors?
(Should I disable bayes_auto_expire and manually run it once per day with 
this command? "sa-learn --sync --force-expire")
=====================================================================================
Jul 31 16:22:15 mimedefang-multiplexor[18825]: [ID 980602 mail.info] Slave 0 
stderr: auto-whitelist: open of auto-whitelist file failed: locker: 
safe_lock: cannot create tmp lockfile 
/.spamassassin/auto_whitelist.lock.hestia.sjsu.edu.18825 for 
/.spamassassin/auto_whitelist.lock: Permission denied
Jul 31 16:23:59 mimedefang-multiplexor[24460]: [ID 980602 mail.info] Slave 0 
stderr: locker: safe_lock: unlink of temp lock 
/.spamassassin/auto_whitelist.lock.hestia.sjsu.edu.24460 failed: No such 
file or directory
Jul 31 16:24:00 mimedefang-multiplexor[24460]: [ID 980602 mail.info] Slave 2 
stderr: locker: safe_lock: unlink of temp lock 
/.spamassassin/auto_whitelist.lock.hestia.sjsu.edu.24460 failed: No such 
file or directory
=====================================================================================

Here's my settings in the sa-mimedefang.cf file.
Please give me some thoughts about these settings:
================================
(Continue reading)

An.H.Nguyen | 1 Aug 03:14 2007
Picon

Reinstall needed?

Do we need to reinstall mimedefang after upgrading spamassassin from 3.2.0 
to 3.2.2?
Thanks,
An Nguyen

An.H.Nguyen | 1 Aug 09:21 2007
Picon

SPF integration problem

I have these errors when I tried to implement SPF check.

Jul 31 23:52:02 hestia mimedefang-multiplexor[29566]: [ID 980602 mail.info] 
Slave 0 stderr: no IP address given at /usr/local/
lib/perl5/site_perl/5.8.7/Mail/SPF/Query.pm line 255, <STDIN> line 1.
Jul 31 23:52:02 hestia mimedefang-multiplexor[29566]: [ID 389462 mail.error] 
Slave 0 died prematurely -- check your filter rul
es
Jul 31 23:52:02 hestia mimedefang-multiplexor[29566]: [ID 204284 mail.error] 
Reap: slave 0 (pid 628) exited normally with stat
us 9 (SLAVE DIED UNEXPECTEDLY)
Jul 31 23:52:02 hestia mimedefang[29579]: [ID 847421 mail.error] Error from 
multiplexor: ERR No response from slave

What have I missed?
Can someone please give me an example of the mimedefang-filter code and all 
requirements which can make SPF work?
Thanks,
An Nguyen

Here's my code (after I commented out)
# use Mail::SPF::Query;
#  %PROCEDURE: spf_query
# sub spf_query ($$$$) {
      # my ($ip, $sender, $helo, $guess) =  <at> _;
      # The guess parameter needs to be set to either 0 or 1.
      # if ($guess != 1) {
              # $guess = 0;
      # }
      # Check this sender against any SPF or Caller-ID records
(Continue reading)

Kimmo Jaskari | 1 Aug 13:19 2007
Picon

Re: Exchange2AccessPaged help?

On Tue, 2007-07-31 at 13:27 -0400, Kevin A. McGrail wrote:

> > No in your email.  Here's the MS KB Article:
> > http://support.microsoft.com/kb/823866/en-us I mentioned.  This technote
> > covers Excahnge 2003, but other technotes mentioning Exchange 2000 refer
> > to this one.
> 
> That's the same technote that is mentioned in the link I gave which is just 
> a simplified version of that technote that removes irrelevant stuff.
> 
> http://www.peregrinehw.com/downloads/ldap/NOTE-EXCHANGE2003

I appreciate the input, and I have looked at those scripts. They
essentially do what the Exchange2AccessPaged does (or it does what they
do, not sure which came first), but the latter does it in one script
very neatly. Also, the latter almost works for me...

http://www.mimedefang.org/kwiki/index.cgi?Exchange2AccessPaged

I had issues with getting the scripts at peregrinehw.com to work for me
on Solaris, though; I did check the INSTALL bit and made sure I had the
dependencies installed for Perl but the export script still choked,
either complaining about the username/password combo or apparently
running for a fast second but producing no output whatsoever. Again, the
cut and paste school for Perl programming didn't cover that. ;)

The main thing I was wondering though was if anyone had any ideas about
what could be causing this to happen in the middle of generating the
access file with Exchange2AccessPaged:

(Continue reading)

mike campbell | 1 Aug 15:11 2007
Picon

What is the best/fastest/easiest way to use greylisting?

I've been running mimedefang for a couple of years successfully with it 
interfacing to clamav and spamassassin. I have decided to try and add in 
greylisting as well and upon checking around I see several places that 
document how to do this:

http://www.mimedefang.org/kwiki/index.cgi?Greylisting
http://whatever.frukt.org/mimedefangfilter.text.shtml
http://mark.tranchant.co.uk/notes/greylist
http://www.golden-gryphon.com/software/misc/mimedefang-filter.html

and from the original design for greylisting there is a perl milter at 
http://projects.puremagic.com/greylisting/downloads.html

All of these look very similar but having never tried greylisting before 
was wondering what is the best/fastest/easiest implementation for use 
with MD?

Any hints or tips for implementation would greatly be appreciated.
--

-- 

Mike Campbell | Principal Support Engineer | 407.458.2313
Oracle Support Services
7453 TG Lee Blvd. | Orlando, FL 32822
Richard Whelan | 1 Aug 17:18 2007
Picon
Picon

Re: What is the best/fastest/easiest way to use greylisting?

Hi Mike,

Having just gone through the same exercise over the last couple of
weeks, I ended up using milter-greylist, available from 
http://hcpnet.free.fr/milter-greylist/. It's incredibly simple to setup,
and doesn't seem to impede performance at all, in fact I would that it
has helped in a lot of ways, as it reduced the amount of mail entering
mimedefang/spamassassin.  've got it as the first milter within
Sendmail, with the mimedefang milter straight after. It's spread across
three servers, all of which share their data with each other. This,
together with the addition of the SaneSecurity signatures for ClamAV,
has made a huge difference to the amount of spam now entering our mailboxes.

Cheers,

Richard

-------- Original Message --------
Subject: [Mimedefang] What is the best/fastest/easiest way to use  
 greylisting?
From: mike campbell <mike.campbell <at> oracle.com>
To: mimedefang <at> lists.roaringpenguin.com
Date: 01/08/2007 14:11
> I've been running mimedefang for a couple of years successfully with
> it interfacing to clamav and spamassassin. I have decided to try and
> add in greylisting as well and upon checking around I see several
> places that document how to do this:
>
> http://www.mimedefang.org/kwiki/index.cgi?Greylisting
> http://whatever.frukt.org/mimedefangfilter.text.shtml
(Continue reading)

mike campbell | 1 Aug 17:36 2007
Picon

What is the best/fastest/easiest way to use greylisting?

Would you believe that I actually started looking at milter-greylist 
initially but realized it was another milter in sendmail and thought it 
might be better to combine greylisting into MD since that would only be 
1 milter to be involved. Perhaps I was right on my first approach!!

One thing I don't see to be able to get to work is subnetmatch. I have 
tried to define "subnetmatch /24" but in my greylist.db I see something 
like this:

148.87.xxx.yyy  <mike.campbell <at> domain.com>      
<mikecampbell <at> domain.org>   1185982451 # 2007-08-01 10:34:11

And when I send another email (after the initial delay) then if it comes 
from a different IP address then it too is greylisted. So, does the /24 
change the way that the entries show up in the greylist.db file to 
exclude the last octet?
--

-- 

Mike Campbell | Principal Support Engineer | 407.458.2313
Oracle Support Services
7453 TG Lee Blvd. | Orlando, FL 32822
Kimmo Jaskari | 1 Aug 17:46 2007
Picon

Re: Adding mimedefang to sendmail's startup script

On Tue, 2007-07-31 at 17:43 -0400, Lisa Casey wrote:
> Since installing mimedefang on this FreeBSD box, when I reboot it there's
> something screwy going on when sendmail starts up. It's got something to do
> with startup scripts and either something I've failed to do or something
> I've done incorrectly. Before installing mimedefang, sendmail started fine
> on bootup. Now when I reboot the box I get this in /var/log/maillog:
> 
> Jul 31 17:19:20 mail sm-mta[399]: NOQUEUE: SYSERR(root): opendaemonsocket:
> daemon IPv4: cannot bind: Address al
> ready in use

That does mean that something else is already listening on that port, so
you are probably right that Sendmail is trying to start itself twice.
Most likely you've done something odd. :) FreeBSD apparently (I'm pretty
FreeBSD challenged, I'm mainly a Solaris guy) has a fairly advanced
startup script system that allows services to keep track of dependencies
(though not as cool as Solaris SMF ;) but there does exist
documentation. 

If you look here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-starting-services.html

and here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-rcd.html

the rc.d mechanism is explained pretty well.

Since your rc.conf has sendmail enable set to yes, it does run the
(Continue reading)

Scott Silva | 1 Aug 17:54 2007
Picon

Re: multiplexor error

An.H.Nguyen spake the following on 7/31/2007 4:40 PM:
> The bayes tests already showed up this morning.
> Now there are some issues after bayes and autowhitelist is up and
> running....
> I am able to increase the bayes db to 50mb but the autowhitelist seems
> to have a limit of 1mb...
> Is there a way to increase autowhitelist_db size?
> 
> There are some autowhitelist errors which still happen a few times a day...
> Is there a way to fix these errors?
> (Should I disable bayes_auto_expire and manually run it once per day
> with this command? "sa-learn --sync --force-expire")
Bayes_auto_expire can cause many problems with busy systems. If messages come
in during the auto_expire, you can get spamassassin timeouts.
If you can cron the forced expire at the non-peak time of your system, and
maybe stop your mail system for that minute or two it might take, you might be
much happier. If your system is too busy, consider moving your bayes to sql.
It will expire stuff up to 5 or 10 times faster depending on the size of your
db and the amount of records needing to be expired.

I have had mixed results with the auto_whitelist, so I can't comment on it.

--

-- 

MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!

Kris Deugau | 1 Aug 19:12 2007
Picon

Re: Reusing a mimedefang-filter

Lisa Casey wrote:
> I have been using mimedefang 2.48 (old, I know) on Redhat 7.2. I 
> installed Mimedefang 2.61 from ports on FreeBSD. On the Redhat box, I 
> have made several changes to my mimedefang-filter. Rather than trying to 
> recreate these anew, could I just copy my mimedefang-filter from the 
> redhat box to the FreeBSD box? Can Mimedefang 2.61 use a 
> mimedefang-filter file from mimedefang 2.48?

You could *probably* do this without error - but check through the 
changelog for NOTE INCOMPATIBLE warnings.  IIRC there are a few things 
that changed incompatibly somewhere in that range.

You also tend to miss out on new features in the new default 
mimedefang-filter;  I usually at least scan through quickly side-by-side 
with my existing filter and see what's new, and compare that with what I 
changed myself.

-kgd

Gmane