Re: Scanning Outbound emails

2010-05-06 Thread Sanesecurity
http://memberwebs.com/stef/software/clamsmtp/ Hope this helps, Cheers, Steve Sanesecurity -- View this message in context: http://old.nabble.com/Scanning-Outbound-emails-tp28457702p28469965.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.

Scanning Outbound emails

2010-05-05 Thread Alans
Hi all, Can we use spamassasin in ISP environment to scan outbound emails? Regards, Alans

Re: Scanning Outbound emails

2010-05-05 Thread ram
On Wed, 2010-05-05 at 10:44 +0300, Alans wrote: Hi all, Can we use spamassasin in ISP environment to scan outbound emails? Regards, Alans Yes. But separate out your inbound outbound scans. For outbound Disable all IP based rules because they will cause FP's. Also we have often seen

RE: Scanning Outbound emails

2010-05-05 Thread Alans
notification back to sender about his/her activity. Regards, Alans -Original Message- From: ram [mailto:r...@netcore.co.in] Sent: Wednesday, May 05, 2010 3:10 PM To: Alans Cc: users@spamassassin.apache.org Subject: Re: Scanning Outbound emails On Wed, 2010-05-05 at 10:44 +0300, Alans

RE: Scanning Outbound emails

2010-05-05 Thread Bernd Petrovitsch
On Mit, 2010-05-05 at 15:38 +0300, Alans wrote: [...] Actually we are seeking a solution to our problem which is sending spam through our network. We are about to close port 25 and tell customers to switch to our smtp relay and scan it with spamassasin (I still don't know if possible or no!).

Re: Scanning Outbound emails

2010-05-05 Thread Frank Heydlauf
Hi, On Wed, May 05, 2010 at 03:38:01PM +0300, Alans wrote: ... We are about to close port 25 and tell customers to switch to our smtp relay and scan it with spamassasin (I still don't know if possible or no!). As Bernd Petrovitsch already told you: Yes, that's possible. To close port 25 is a

RE: Scanning Outbound emails

2010-05-05 Thread Alans
Frank, Bernd, Thank you all. Regards, Alans -Original Message- From: Frank Heydlauf [mailto:fh-sa2...@lf.net] Sent: Wednesday, May 05, 2010 4:10 PM To: users@spamassassin.apache.org Subject: Re: Scanning Outbound emails Hi, On Wed, May 05, 2010 at 03:38:01PM +0300, Alans wrote

Re: Scanning Outbound emails

2010-05-05 Thread Jari Fredriksson
On 5.5.2010 15:38, Alans wrote: We are about to close port 25 and tell customers to switch to our smtp relay and scan it with spamassasin (I still don't know if possible or no!). We want to reject all spam emails and send notification back to sender about his/her activity. There is one

Re: Scanning Outbound emails

2010-05-05 Thread Kris Deugau
On Wed, 2010-05-05 at 10:44 +0300, Alans wrote: Hi all, Can we use spamassasin in ISP environment to scan outbound emails? ram wrote: Yes. But separate out your inbound outbound scans. FWIW I can say with authority that this is not necessary. It may simplify your mail system depending

Re: Scanning Outbound emails

2010-05-05 Thread Kris Deugau
Jari Fredriksson wrote: On 5.5.2010 15:38, Alans wrote: We are about to close port 25 and tell customers to switch to our smtp relay and scan it with spamassasin (I still don't know if possible or no!). We want to reject all spam emails and send notification back to sender about his/her

Re: Scanning Outbound emails

2010-05-05 Thread Charles Gregory
On Wed, 5 May 2010, Bernd Petrovitsch wrote: Why shouldn't it be possible? SpamAssassin doesn't care where the mail comes from Well, actually, it DOES. The test DOS_DIRECT_TO_MX being an example. Which brings me back to the slightly confused feeling that I still get over

Re: Scanning Outbound emails

2010-05-05 Thread Charles Gregory
On Wed, 5 May 2010, Jari Fredriksson wrote: There is one special group that will suffer from that decision: namely SpamAssassin users within your network. If they do report their spam to SpamCop using SpamAssassin's own report mechanism, they are screwed Why not just add a negative-scoring

Re: Scanning Outbound emails

2010-05-05 Thread Jari Fredriksson
On 5.5.2010 17:39, Kris Deugau wrote: Jari Fredriksson wrote: On 5.5.2010 15:38, Alans wrote: We are about to close port 25 and tell customers to switch to our smtp relay and scan it with spamassasin (I still don't know if possible or no!). We want to reject all spam emails and send

Re: Scanning Outbound emails

2010-05-05 Thread Jari Fredriksson
On 5.5.2010 17:44, Charles Gregory wrote: On Wed, 5 May 2010, Jari Fredriksson wrote: There is one special group that will suffer from that decision: namely SpamAssassin users within your network. If they do report their spam to SpamCop using SpamAssassin's own report mechanism, they are

Re: Scanning Outbound emails

2010-05-05 Thread Kris Deugau
Jari Fredriksson wrote: If my SA sends an email to SpamCop with a spam as an attachment, and that gets rejected by my ISP and a feedback sent to me.. it would be a problem. To me. *headdesk* Ah, right. We're not keen on being a smarthost for customers already running their own mail systems

Re: Scanning Outbound emails

2010-05-05 Thread Marc Perkel
On 5/5/2010 5:38 AM, Alans wrote: Thanks ram, Actually we are seeking a solution to our problem which is sending spam through our network. We are about to close port 25 and tell customers to switch to our smtp relay and scan it with spamassasin (I still don't know if possible or no!). We

Re: Scanning Outbound emails

2010-05-05 Thread Liam R. MacInnes
On 2010-05-05, at 5:09 AM, ram wrote: On Wed, 2010-05-05 at 10:44 +0300, Alans wrote: On my servers I just add the score header and let the mail go but send a copy to a program. If more than 10 occur in 30 minutes from the same customer , the customers account is temporarily blocked and

RE: Scanning Outbound emails

2010-05-05 Thread Giampaolo Tomassoni
... except, after checking their site just now, you now get a personalized reporting address once you've signed up. *sigh* AFAIK, the reporting e-mail addresses are all of the form /^submit.\...@spam\.spamcop\.net$/ .

RE: Scanning Outbound emails

2010-05-05 Thread R-Elists
In particular, I find these two paragraphs from Mail::SpamAssassin::Conf to be contradictory: Trusted relays that accept mail directly from dial-up connections (i.e. are also performing a role of mail submission agents - MSA) should not be listed in