Re: Spam features

Not his account but one of the recipients did have a very
low setting that
was causing it to be rejected. Thanks for pointing me in the
right
direction.

----- Original Message -----
From: Jody McAlister <jodymaciscweb.com>
To: surgemail-listnetwinsite.com
Subject: Re: [SurgeMail List] Spam features
Date: Mon, 23 Apr 2007 14:42:50 -0700

>That would be the spam settings option for their
account.  They 
>probably set their reject option on or too low.
>
>On Apr 23, 2007, at 2:37 PM, Kevin W. Gagel wrote:
>
>> ----- Original Message -----
>>> Kevin W. Gagel wrote:
>>>> I activated the spam features for my users
a couple of months back 
>>>> and
>>>> have just come accross a complaint that a
user cannot send email to
>>>> another user. The system is detecting his
message as a spam message 
>>>> and
>>>> will not allow it.
>>>>
>>>> How do I go about tracking down the root
cause of the problem?
>>>>
>>> Is the user authenticating to your server? If
not, that could flag the
>>> email as fraudulent depending on other settings
you may have 
>>> configured.
>>
>> The user is using outlook 2003. I just had him do a
check for mail and 
>> then
>> try sending it again. It still fails.
>>
>> Here is what the log says on this attempt to send:
>> 23 14:33:17[199934] Failed 142.X.X.23 <XXXcnc.bc.ca> <BBBcnc.bc.ca> 
>> 3079
>> <001401c785ef$0d331d00$27995700$bc.ca>
"[142.X.X.23] Bounced *******:
>> 7.488889 From3consonants=0.5, SPF Fail=8.0,
X-Verify-SMTP present=0.6,
>> Aspam=-1.6"
>> 23 14:33:17[199934] Failed 142.X.X.23 <XXXcnc.bc.ca> <CCCcnc.bc.ca> 
>> 3079
>> <001401c785ef$0d331d00$27995700$bc.ca>
"[142.27.64.23] Message looks 
>> like
>> spam, sorry not wanted here q=199934"
>>
>> In all there were four recipients, the logs
indicate a problem only 
>> with
>> the two that were on the To: line. The two that
were on the CC line 
>> are not
>> mentioned in the logs.
>>
>> =================================
>> Kevin W. Gagel
>> Network Administrator
>> Information Technology Services
>> (250) 562-2131 local 448
>> My Blog:
>> http://mail.cnc.bc.
ca/blogs/gagel
>>
>>
------------------------------------------------------------
-------
>> The College of New Caledonia, Visit us at http://www.cnc.bc.ca
>> Virus scanning is done on all incoming and outgoing
email.
>> Anti-spam information for CNC can be found at http://avas.cnc.bc.ca
>>
------------------------------------------------------------
-------
>>
>
>

=================================
Kevin W. Gagel
Network Administrator
Information Technology Services
(250) 562-2131 local 448
My Blog:
http://mail.cnc.bc.
ca/blogs/gagel

------------------------------------------------------------
-------
The College of New Caledonia, Visit us at http://www.cnc.bc.ca
Virus scanning is done on all incoming and outgoing email.
Anti-spam information for CNC can be found at http://avas.cnc.bc.ca
------------------------------------------------------------
-------

Kevin

If this mail is all internal to your network, then there is
something 
wrong with your SPF records.

Note that one of the biggest hits in the spam score is
"SPF Fail=8.0".

The SPF record for cnc.bc.ca only allows the declared MXes
and fails all 
others. The declared MX is avas.cnc.bc.ca 142.27.70.214. But
the 
rejected mail is showing an IP of 142.27.64.23.

So either I am very confused about what goes where, or
something is 
wrong in SPFville.

Neil

Kevin W. Gagel wrote:
> Not his account but one of the recipients did have a
very low setting that
> was causing it to be rejected. Thanks for pointing me
in the right
> direction.
> 
> ----- Original Message -----
> From: Jody McAlister <jodymaciscweb.com>
> To: surgemail-listnetwinsite.com
> Subject: Re: [SurgeMail List] Spam features
> Date: Mon, 23 Apr 2007 14:42:50 -0700
> 
>> That would be the spam settings option for their
account.  They 
>> probably set their reject option on or too low.
>>
>> On Apr 23, 2007, at 2:37 PM, Kevin W. Gagel wrote:
>>
>>> ----- Original Message -----
>>>> Kevin W. Gagel wrote:
>>>>> I activated the spam features for my
users a couple of months back 
>>>>> and
>>>>> have just come accross a complaint that
a user cannot send email to
>>>>> another user. The system is detecting
his message as a spam message 
>>>>> and
>>>>> will not allow it.
>>>>>
>>>>> How do I go about tracking down the
root cause of the problem?
>>>>>
>>>> Is the user authenticating to your server?
If not, that could flag the
>>>> email as fraudulent depending on other
settings you may have 
>>>> configured.
>>> The user is using outlook 2003. I just had him
do a check for mail and 
>>> then
>>> try sending it again. It still fails.
>>>
>>> Here is what the log says on this attempt to
send:
>>> 23 14:33:17[199934] Failed 142.X.X.23
<XXXcnc.bc.ca> <BBBcnc.bc.ca> 
>>> 3079
>>> <001401c785ef$0d331d00$27995700$bc.ca>
"[142.X.X.23] Bounced *******:
>>> 7.488889 From3consonants=0.5, SPF Fail=8.0,
X-Verify-SMTP present=0.6,
>>> Aspam=-1.6"
>>> 23 14:33:17[199934] Failed 142.X.X.23
<XXXcnc.bc.ca> <CCCcnc.bc.ca> 
>>> 3079
>>> <001401c785ef$0d331d00$27995700$bc.ca>
"[142.27.64.23] Message looks 
>>> like
>>> spam, sorry not wanted here q=199934"
>>>
>>> In all there were four recipients, the logs
indicate a problem only 
>>> with
>>> the two that were on the To: line. The two that
were on the CC line 
>>> are not
>>> mentioned in the logs.
>>>
>>> =================================
>>> Kevin W. Gagel


-- 
Neil Herber
Corporate info at http://www.eton.ca/