Jared Markell wrote:
I totally agree that local-to-locals should not be scanned, and I really
don't want to adjust my system to scan local-to-local just to "ductape" the
real problem, when I'd rather just fix the real problem. The real problem is
what I can't figure out.
Basically happens when an email comes to a virtual domain on our box, and
that email address is really a forward to our domain which is also virtual
on the same box. Mapped out it looks kind of like this:
smtp email for [EMAIL PROTECTED]
qmail forwards [EMAIL PROTECTED] to [EMAIL PROTECTED]
[EMAIL PROTECTED] splits the email to [EMAIL PROTECTED] and
another coworker of mine.
The problem occurs that SA decides not to scan those emails, and I can't
figure out why. My only guess is that it's confused and THINKS it's
local-to-local (since it's jumping domains), when it's really not...
does this ring a bell? I think it has to do with order of operations? Is SA
ran before email is delivered? For example, is it scanned before delivered
to [EMAIL PROTECTED] or is it scanned after it reaches
[EMAIL PROTECTED] (thus thinking it's local-to-local, an email from
[EMAIL PROTECTED], even though it isn't).
Hmm. I just sent a message from this email account (jake @ v2gnu.com)
(box #1) to one of my other Toaster boxes (#2) to an address that is an
[EMAIL PROTECTED] to a [EMAIL PROTECTED] on the same box (#2)
and it showed the SpamAssassin headers (gave it a -2 score, since I was
in the auto_whitelist). What does the header show in your email? If need
be, I'll recreate your scenario on my box(es) and see how it's flowing.
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
