Fred Viles wrote:
| On 30 Dec 2004 at 10:48, Justin Koivisto wrote about
| "[exim] Denying messages":
|
| | my data acl:
| |
| | # Reject messages containing malware.
| | deny message = Rejected message contains a virus ($malware_name)
| | malware = *
| | .ifdef TEERGRUBE
| | ~ delay = TEERGRUBE
| | .endif
| |
| | OK, so all is good. However, I think that when the deny message is sent,
| | the virus is sent back with it...
|
| Not from this server, it isn't. Rejecting at SMTP time means that it
| never accepted the message in the first place - it is not generating
| a "bounce" (Delivery Status Notification) message at all.
|
| The MTA that tried to send you the virus may be generating a bounce,
| if it is relaying the message, but that's not your problem unless you
| also control that server. It may be sending the bounce to your
| server, if the (likely forged) original sender address was in your
| domain.
|
| | I have a loop going on
| | between 2 servers right now - both sending the virus back and forth.
|
| That shouldn't happen in any case. Any DSN should have <> as the
| sender, so rejection of the DSN should not cause an additional DSN.
|
| Maybe your log can shed some light on what's really going on?
WTF.. That's right, my server doesn't generate a bounce, just a deny
message, the way it should...
I hate it when people tell me its my fault when it isn't, that just
wasted about 6 hours of my time... time for them to hunt it down on
their end.
Thanks!
- --
Justin Koivisto - justin@???
http://www.koivi.com
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE40C674D
