RE: [Declude.JunkMail] Passing SPAM that should be bounced

[R. Scott Perry]

1.) Since the mail was already incoming and has gone through all the
spam checks inbound is there anyway to override the current behavior of
discarding those results and actually have the message react to the
incoming spam checks.

Declude JunkMail will only scan an E-mail once.

E-mail can be very confusing because every E-mail handled by a mailserver is technically incoming E-mail (as in the IMail server receives it from somewhere else), whereas some of those are local deliveries and some are remote deliveries. In any case, an E-mail should only be scanned once by Declude (unless it arrives more than once).

2.) If I can't override the default behavior, can I setup per domain
outgoing processing for just this domain - even though this domain does
not exist on this mail server?

Yes, but not the way I think you want.

You can set up per-domain settings for the *recipient* domain. But, you can't set up per-domain settings for the *sender* domain. In this case, I'm guessing you would want the per-user settings for the sender domain, which isn't possible (remember, spammers love to use the same return address as the "To:" address).

3.) If it is possible to setup per domain filtering for this domain even
though it does not exist on this server, Should I whitelist the incoming
mail so it doesn't go through all those checks?  Or is Whitelisting
global in regards that it applies to both incoming and outgoing mail?

The whitelisting applies to whatever type of whitelist it is. For example, "WHITELIST IP 192.0.2.25" will whitelist E-mail coming from 192.0.2.25, no matter whether it is incoming or outgoing E-mail.

Please advise on what you think would be the best course of action here.

The ultimate problem seems to be that the backup mailserver isn't really a backup mailserver -- it seems to accept all E-mail, and send it out. If the backup mailserver accepts an E-mail, sends it to the primary mailserver, and then the primary mailserver sends it out to a remote location, you probably have a problem. Unless there is a good reason for this (for example, forwarding on the primary mailserver that is causing the E-mail to be sent to a remote location), you are running an open relay on the backup mailserver.
-Scott

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.