[AMaViS-user] help on notify_method please

2008-02-19 Thread web master

I read the sample config file and various docs but this notify_method  
parameter in the config file is still a mystery to me.  Can someone kindly help 
me understand ?
What exactly does it do ?
Do I need to use it ?
What is the fundamental difference between notify_method  and forward_method ?


If I  have  MTA X  (192.168.0.1)  sending to  Amvavisd-new (192.168.0.2) and 
the resulting messages are to be forwarded to yet a 3rd server: 192.168.0.3,  
what should my notify_method and forward_method  be like ?

Many thanks again in advance for any help.

Cauba




  Looking for the perfect gift? Give the gift of Flickr! 

http://www.flickr.com/gift/



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/


[AMaViS-user] exempting mail outs from self rejection

2008-02-19 Thread Voytek Eymont

what the best way to exempt legit mail outs from 'self rejection' ?

one of my users is preparing template for b/cast emails and, sample
template gets rejected:

---
A message from  to:
- 

was considered unsolicited bulk e-mail (UBE).

Our internal reference code for your message is 01613-17/PUvpUT3qkddF

---


-- 
Voytek


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/


Re: [AMaViS-user] Forged 'X-Virus-Scanned' header bypasses Amavis-new scanning

2008-02-19 Thread Christopher J Shaker
It appears the cuprit is the auto whitelist (AWL):


Feb 19 01:37:04 linux postfix/smtpd[567]: connect from 
anna.int.kiev.ua[194.242.60.75]
Feb 19 01:37:05 linux postfix/smtpd[567]: 516D1404B4: 
client=anna.int.kiev.ua[194.242.60.75]
Feb 19 01:37:06 linux postfix/cleanup[667]: 516D1404B4: 
message-id=[EMAIL PROTECTED]
Feb 19 01:37:06 linux postfix/qmgr[32311]: 516D1404B4: 
from=[EMAIL PROTECTED], size=6724, nrcpt=1 (queue active)
Feb 19 01:37:06 linux amavis[32325]: (32325-08) process_request: fileno 
sock=12, STDIN=0, STDOUT=1
Feb 19 01:37:06 linux amavis[32325]: (32325-09) ESMTP::10024 
/var/spool/amavis/tmp/amavis-20080219T010829-32325: 
[EMAIL PROTECTED] - [EMAIL PROTECTED] SIZE=6724 Received: 
from linux.shaker-net.com ([127.0.0.1]) by localhost 
(linux.shaker-net.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP 
for [EMAIL PROTECTED]; Tue, 19 Feb 2008 01:37:06 -0800 (PST)
Feb 19 01:37:06 linux amavis[32325]: (32325-09) body hash: 
521b19d4698d37a4f109534fb83cbcf3
Feb 19 01:37:06 linux amavis[32325]: (32325-09) Checking: nHrkh2qSatmQ 
[EMAIL PROTECTED] - [EMAIL PROTECTED]
Feb 19 01:37:06 linux amavis[32325]: (32325-09) 2822.From: 
[EMAIL PROTECTED], 2821.Mail_From: [EMAIL PROTECTED]
Feb 19 01:37:06 linux amavis[32325]: (32325-09) p001 1 Content-Type: 
text/html, size: 5950 B, name:
Feb 19 01:37:06 linux amavis[32325]: (32325-09) Checking for banned 
types and filenames
Feb 19 01:37:06 linux amavis[32325]: (32325-09) collect banned table[0]: 
[EMAIL PROTECTED], tables: 
DEFAULT=Amavis::Lookup::RE=ARRAY(0x8a43c18)
Feb 19 01:37:06 linux amavis[32325]: (32325-09) p.path 
[EMAIL PROTECTED]: P=p001,L=1,M=text/html,T=html
Feb 19 01:37:06 linux amavis[32325]: (32325-09) Using ClamAV-clamd: 
(built-in interface)
Feb 19 01:37:06 linux amavis[32325]: (32325-09) Using (ClamAV-clamd) on 
dir: CONTSCAN /var/spool/amavis/tmp/amavis-20080219T010829-32325/parts\n
Feb 19 01:37:06 linux amavis[32325]: (32325-09) ClamAV-clamd: Connecting 
to socket  /var/lib/clamav/clamd-socket
Feb 19 01:37:06 linux amavis[32325]: (32325-09) ClamAV-clamd: Sending 
CONTSCAN /var/spool/amavis/tmp/amavis-20080219T010829-32325/parts\n to 
UNIX socket /var/lib/clamav/clamd-socket
Feb 19 01:37:06 linux amavis[32325]: (32325-09) ask_av (ClamAV-clamd): 
/var/spool/amavis/tmp/amavis-20080219T010829-32325/parts CLEAN
Feb 19 01:37:06 linux amavis[32325]: (32325-09) ClamAV-clamd result: clean
Feb 19 01:37:06 linux amavis[32325]: (32325-09) Using AVG Anti-Virus: 
(built-in interface)
Feb 19 01:37:06 linux amavis[32325]: (32325-09) Using (AVG Anti-Virus) 
on dir: SCAN /var/spool/amavis/tmp/amavis-20080219T010829-32325/parts\n
Feb 19 01:37:06 linux amavis[32325]: (32325-09) AVG Anti-Virus: 
Connecting to socket  127.0.0.1:5
Feb 19 01:37:06 linux amavis[32325]: (32325-09) AVG Anti-Virus: Sending 
SCAN /var/spool/amavis/tmp/amavis-20080219T010829-32325/parts\n to INET 
socket 127.0.0.1:5
Feb 19 01:37:06 linux amavis[32325]: (32325-09) ask_av (AVG Anti-Virus): 
/var/spool/amavis/tmp/amavis-20080219T010829-32325/parts CLEAN
Feb 19 01:37:06 linux amavis[32325]: (32325-09) AVG Anti-Virus result: clean
Feb 19 01:37:07 linux postfix/smtpd[567]: disconnect from 
anna.int.kiev.ua[194.242.60.75]
Feb 19 01:37:34 linux amavis[32325]: (32325-09) spam_scan: 
score=-109.401 autolearn=no 
tests=[AWL=-135.491,BAYES_80=2,CONTENT_RETURN=2.9,FAKE_MSN=3.9,FREE=1.9,GIF=2.9,HTML_MESSAGE=0.2,MIME_HTML_ONLY=0.9,URIBL_AB_SURBL=1.86,URIBL_BLACK=1.955,URIBL_JP_SURBL=1.501,URIBL_OB_SURBL=1.5,URIBL_SC_SURBL=0.474,URIBL_WS_SURBL=2.9,VIRUS_CLEAN=0.3,WORD_HAS_PIPE=0.9]
Feb 19 01:37:34 linux amavis[32325]: (32325-09) do_notify_and_quar: 
ccat=Clean (1,0) (1:Clean, 0:CatchAll) ccat_block=(), q_mth=, qar_mth=
Feb 19 01:37:34 linux amavis[32325]: (32325-09) smtp creating socket by 
IO::Socket::INET: 127.0.0.1
Feb 19 01:37:34 linux postfix/smtpd[672]: connect from 
localhost.shaker-net.com[127.0.0.1]
Feb 19 01:37:34 linux amavis[32325]: (32325-09) smtp resp to greeting: 
220 linux.shaker-net.com ESMTP Spamkiller on SuSE Linux 7.3 (i686)
Feb 19 01:37:34 linux amavis[32325]: (32325-09) smtp cmd EHLO localhost
Feb 19 01:37:34 linux amavis[32325]: (32325-09) smtp resp to EHLO: 250 
linux.shaker-net.com\nPIPELINING\nSIZE 1073741824\nETRN\n8BITMIME
Feb 19 01:37:34 linux amavis[32325]: (32325-09) AUTH not needed, 
user='', MTA offers ''
Feb 19 01:37:34 linux amavis[32325]: (32325-09) smtp cmd MAIL 
FROM:[EMAIL PROTECTED]
Feb 19 01:37:34 linux amavis[32325]: (32325-09) smtp cmd RCPT 
TO:[EMAIL PROTECTED]
Feb 19 01:37:34 linux amavis[32325]: (32325-09) smtp cmd DATA
Feb 19 01:37:34 linux postfix/smtpd[672]: 6E8F1404B6: 
client=localhost.shaker-net.com[127.0.0.1]
Feb 19 01:37:34 linux amavis[32325]: (32325-09) smtp resp to MAIL (pip): 
250 Ok
Feb 19 01:37:34 linux amavis[32325]: (32325-09) smtp resp to RCPT (pip) 
([EMAIL PROTECTED]): 250 2.1.0 Ok, id=32325-09, from 
MTA([127.0.0.1]:10025): 250 Ok
Feb 19 01:37:34 linux amavis[32325]: (32325-09) smtp resp to DATA: 354 
End data with 

Re: [AMaViS-user] Runaway amavis check eating CPU

2008-02-19 Thread James
Regarding this in case anyone wanted to know it was a spamassassin problem,

Apparently spamhaus firewalled me for too many queries and i had the 
dnsbl check plugin on spamassassin enabled which was causing the process 
to kind of go stale i think.
I disabled the plugin and the cpu usage went back to normal.

Thanks for the input from earlier
-James

Mark Martinec wrote:
 Check the timing report (at log level 2) to see what task was taking
 most of the resources.

 A message transfer from MTA to amavisd can take about ten seconds
 for a 100 MB message on a reasonably fast machine, the rest depends
 much on a contents type - decoding and virus checking. You won't know
 what was it until you look at the timing report. A transfer of a message
 from amavisd back to MTA is about an order of magnitude faster than
 receiving it (unless you have a very old version of amavisd),
 so should not be a problem. For a message of this size, spam scanning
 was skipped ($sa_mail_body_size_limit).

   Mark


   

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/


Re: [AMaViS-user] help on notify_method please

2008-02-19 Thread Gary V
On 2/19/08, web master wrote:

 I read the sample config file and various docs but this notify_method  
 parameter in the config file is still a mystery to me.  Can someone kindly 
 help me understand ?
 What exactly does it do ?
 Do I need to use it ?
 What is the fundamental difference between notify_method  and forward_method ?


 If I  have  MTA X  (192.168.0.1)  sending to  Amvavisd-new (192.168.0.2) and 
 the resulting messages are to be forwarded to yet a 3rd server: 192.168.0.3,  
 what should my notify_method and forward_method  be like ?

 Many thanks again in advance for any help.

 Cauba


$forward_method = 'smtp:[192.168.0.3]:10025';

The default:
#$notify_method = $forward_method;

should serve your needs. $forward_method lets amavisd-new know how to
get to the next-hop server (typically the same server it's already on
- but in your case a different server) for mail amavisd-new has
received. $notify_method lets amavisd-new know how to get to the
next-hop server for notification messages that amavisd-new creates
(notes to administrators about viruses, banned files etc. for
example). It's rare that they would need to be different.

-- 
Gary V

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/


[AMaViS-user] Playing with the amavisd-new custom hooks

2008-02-19 Thread Jacob Leaver
Dear All,

I've been playing around with the Amavis::Custom hooks for fun and
entertainment, it's cool stuff.  I'm not seeing, however, and maybe I
just missed it, a nice hookable way to add per-recipient headers.  If I
haven't missed something clever, would there be any interest in a patch
for this?
If so, which would be the preferable method:
1.) add a per_recip header array to be added by
add_forwarding_header_per_recip
2.) add another hook somewhere

or some other ingenious something I doubtless haven't though of, yet.

Jacob Leaver
C-Corp.net


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/