>>> If have Squirrel Mails outgoing service set to Sendmail and not SMTP I
>>> suggest you set it to SMTP and try again.  If that fails then I'd get
>>> Optonline to check THEIR mail configuration.
>>>
>>
>> Thanks again for your patience,
>>
>> but I have said it in each and every message!  Squirrel mail is set to
>> use
>> SMTP  *NOT* sendmail for outgoing messages.
>>
>> Maybe this will help:
>> This is how my message scored on a third party system running
>> SpamAssassin
>> notice the fact that my IP 24.44.185.239 is triggering the RBL rule to
>> mark the message as spam?  Well that IP is the IP assigned to my system
>> by
>> my ISP.  Maybe I was mislead by the *Reply* from the Spamassassin list
>> but
>> from his/her message (provided below the Spam Assassin rules) but it
>> makes
>> sense to me (and it also explains why mail I send through through
>> Outlook
>> express is not marked as Spam) and I am hoping that someone here has a
>> work around or solution for me!
>>
>>>  pts rule name              description
>>> ---- ----------------------
>> --------------------------------------------------
>>> -0.0 BAYES_00               BODY: Bayesian spam probability is 0 to 1%
>>>                             [score: 0.0000]
>>>  3.5 RCVD_IN_NJABL_DIALUP   RBL: NJABL: dialup sender did non-local
>>> SMTP
>>>                             [24.44.185.239 listed in dnsbl.njabl.org]
>>>  2.6 RCVD_IN_DYNABLOCK      RBL: Sent directly from dynamic IP address
>>>                             [24.44.185.239 listed in dnsbl.sorbs.net]
>>>  0.1 RCVD_IN_SORBS          RBL: SORBS: sender is listed in SORBS
>>>                             [24.44.185.239 listed in dnsbl.sorbs.net]
>>>  0.1 RCVD_IN_NJABL          RBL: Received via a relay in
>>> dnsbl.njabl.org
>>>                             [24.44.185.239 listed in dnsbl.njabl.org]
>>>  1.2 PRIORITY_NO_NAME       Message has priority setting, but no
>>> X-Mailer
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>
>> ========Explanation of my problem from the SpamAssassin Mailing list===
>> =======================================================================
>> As far as it working using Outlook Express that's because Squirrelmail
>> is
>> inserting its own Received header in there before delivering it to your
>> ISP.
>> When you send through Outlook Express the first hop is your ISP
>> receiving
>> the mail from you which has your dynamic IP as the sender.  SpamAssassin
>> knows to ignore this first hop and start looking for IP's to lookup in
>> RBLs
>> at the second hop.  Since Squirrelmail is inserting it's own header
>> BEFORE
>> delivering it to your ISP SpamAssassin ignores Squirrelmail's header
>> (since
>> it's the first) and starts looking at the second header.  The second
>> header
>> shows your dynamic IP as the sender and SpamAssassin performs RBL checks
>> on
>> it.
>> ========================================================================
>>
>> Thanks,
>> JP
>>
> Jp,
>
> The PRIORITY_NO_NAME was fixed in the lastes release.  I had to manually
> add the X-Mailer entry in my previous version in
> squirrelmail/class/deliver/deliver.class/php.  I have also been having
> some issues with spam software, but mine were pretty much resolved when I
> moved to 1.4.3a.  I don't have your original post so I don't know what
> version that you are running.  I hope this helps.

PRIORITY_NO_NAME was not fixed, because we are not the ones that should
fix it. X-Mailer is added in 1.4.3 in order to avoid triggers in unfixed
spamassasin installs. Currently SpamAssassin 3.0 is already released and
contains User-Agent string checks. SquirrelMail 1.4.4 and 1.5.1 won't add
X-Mailer header.

If SquirrelMail triggers PRIORITY_NO_NAME rule in SpamAssassin, ask to fix
that spamassassin install or ask to lower PRIORITY_NO_NAME scores. The fix
is only one new line and one modified line in rules/20_head_tests.cf

Talks about Recieved From: header inserted by SquirrelMail, can be found at
https://sourceforge.net/tracker/index.php?func=detail&aid=847107&group_id=311&atid=100311

SquirrelMail 1.5.1 contains options that disable that header, but if
1.5.1cvs implementation does not change, I'll argue against porting it to
any stable squirrelmail release or making that option visible to
squirrelmail installer or end users.

-- 
Tomas


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
--
squirrelmail-users mailing list
Posting Guidelines: 
http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines
List Address: [EMAIL PROTECTED]
List Archives: 
http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user
List Archives:  http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users

Reply via email to