14, 2003 9:01 PM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] Passing SPAM that should be bounced
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
Now the manual says this under the Acting as a gateway for domains on
other servers heading - The only catch as far as Declude JunkMail is
concerned is that IMail will treat the E-mail to the gateway domain as
outgoing mail, since it is not stored on the IMail server. Therefore, by
default,
Essentially all I am doing is acting as a gateway for another domain.
This way they can utilize the virus scanning and spam detection we have
in place.
Ah, I see now. I had thought that you were acting as a backup mailserver
(in case they were down), rather than a gateway (to scan all their
PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of John Tolmachoff
Sent: Wednesday, January 15, 2003 10:58 AM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] Passing SPAM that should be bounced
Now the manual says this under the Acting as a gateway for domains on
other servers heading
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of R. Scott Perry
Sent: Wednesday, January 15, 2003 11:02 AM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] Passing SPAM that should be bounced
Essentially all I am doing is acting as a gateway for another
Normally outgoing mail actions are specified in the Global.Cfg file.
However, when using per domain settings it only looks at the actions in
the $default$.JunkMail file for that domain.
For a domain not hosted on the Imail server, yes. For a domain hosted on the
Imail server, it controls the
The headers below also came through. @uem-info.com is in my blacklist file.
Any ideas?
Sheldon
Received: from StarGazer.TenForward.com [65.161.10.3] by tenforward.com
(SMTPD32-7.13) id A2F84D620126; Wed, 15 Jan 2003 04:24:24 -0800
Received: from data.welchmedia.com (unknown [66.216.98.224])
The headers below also came through. @uem-info.com is in my blacklist file.
The important question here is what the return address is, since it doesn't
appear in the headers. Most likely, the return address is not
@uem-info.com, but instead something like @mailer1.uem-info.com.
You'll need
Isn't there an option now to be able to block an email if the blacklist info
is ANYWHERE in the header?
With Declude JunkMail Pro, you can use a filter such as:
HEADERS 3 CONTAINS@uem-info.com
(this would need to go in a file used by a file, not the global.cfg file).
The important question here is what the return address is, since it
doesn't
appear in the headers. Most likely, the return address is not
@uem-info.com, but instead something like @mailer1.uem-info.com.
You'll need to either use the XSENDER ON option to get the return address
to appear in
Declude JunkMail *always* uses the recipient to determine which
configuration file to use. Always.
So for domains hosted on the IMail server, you can't have outgoing
mail. Outgoing E-mail *from* locally hosted domains will use a
configuration file based on who they are sent to.
Thanks
It appears as if Declude is allowing mail that fails spam tests that
have been funneled through our backup mail server to pass.
That's because outgoing mail isn't normally scanned (with Declude JunkMail
Pro, the outgoing actions in the \IMail\Declude\global.cfg file will be used).
Now the
]] On Behalf Of R. Scott Perry
Sent: Tuesday, January 14, 2003 5:48 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] Passing SPAM that should be bounced
It appears as if Declude is allowing mail that fails spam tests that
have been funneled through our backup mail server to pass.
That's because
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
14 matches
Mail list logo
