Nope,
Tried that also, virussess keep bouncing and repeating. This morning i
had more than 100 messages about virus detected, did not had this
behavioure before!
Micheal Espinola Jr schreef:
Matti Haack wrote:
Mybe you should better send Error 554 (Transaction failed)
instead of 500
Similar symptoms here. An E-mail with an Eicar signature has been bouncing
back and forth for four days.
Pascal Dreissen wrote:
Hi,
When there is a virus detected is the smtp connection with the sending
host dropped ?
I am asking this because i got repeating virusses this morning from
Questions and Answers for users of ASSP Anti-Spam SMTP Proxy
assp-user@lists.sourceforge.net schreibt:
When there is a virus detected is the smtp connection with the
sending
host dropped ?
They got the smtp error defined in viruserror
I am asking this because i got repeating virusses this
Similar symptoms here. An E-mail with an Eicar signature has been
bouncing
back and forth for four days.
ASSP does not bounce. ASSP returns the error you define. So what do
think should ASSP do , to prevent the virus from coming again?
Should ASSP drop the connection without proper error
Matti, I just tried that and set the message to 554. The error message still
doesn't make it back to the sender Inbox. My test messages are sent from my
'home' ISP smarthost to ASSP at work. I know that my 'home' ISP also filter
e-mail for viruses. Could it be that my sending 'home' ISP is not
You are right - there is something wrong with the handling,
because the session is not closed after when a virus is
found.
The Error message is not send to the server.
You can easyly test this if you disable your desktop
email/virusscanner, create a textfile and put the eicar test
string into it:
a small detail in the recent releases: the reason for a failed helo is no
longer shown in the log files
it would be nice to have this back
Pascal Dreissen wrote:
Hi,
When there is a virus detected is the smtp connection with the sending
host dropped ?
I am asking this because i got
Matti Haack wrote:
Mybe you should better send Error 554 (Transaction failed)
instead of 500 (Command not recognized 'command')
I use:
~~~
550 5.7.7 [BLOCK REASON] Mail appears infected with '$infection'. Clean
and resend. This attempt has been logged.
Because
a small detail in the recent releases: the reason for a failed helo
is no
longer shown in the log files
it would be nice to have this back
?
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's
Previously the log entry for a failed Helo used to be as follows:
Jan-7-07 19:48:23 PB: 201.1.121.97 score: 0+25 = 25
reason:201.1.121.97:ValidHelo-Check
Jan-7-07 19:48:23 201.1.121.97 [EMAIL PROTECTED] Validate Sender:
Invalid HELO Format '201.1.121.97'
Jan-7-07 19:48:32 PB: 24.61.137.244
I am missing the line telling me the (usually faked) sender and
Invalid Helo
Format.
Your logging is turned off for sender validation, turn it on.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join
11 matches
Mail list logo
