Hi,
Is there a way to whitelist a SquirrelMail frontend machine?
A recent email got FP tagged as spam even though the user had send the email
via the SquirrelMail web frontend (with an Earthlink account to access the
web page). How can I make it so that any email sent via the web frontend
gets trusted or whitelisted?
I have trusted_networks set to my IP block but that didn't seem to work in
this case.
Thanks.
--Henry Kwan
P.S. By the way, this was the scoring:
Content analysis details: (7.0 points, 7.0 required)
pts rule name description
---- ----------------------
--------------------------------------------------
0.2 NO_REAL_NAME From: does not include a real name
-0.0 BAYES_44 BODY: Bayesian spam probability is 44 to 50%
[score: 0.4986]
3.5 RCVD_IN_NJABL_DIALUP RBL: NJABL: dialup sender did non-local SMTP
[209.86.2.85 listed in dnsbl.njabl.org]
2.6 RCVD_IN_DYNABLOCK RBL: Sent directly from dynamic IP address
[209.86.2.85 listed in dnsbl.sorbs.net]
0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org
[209.86.2.85 listed in dnsbl.njabl.org]
0.5 RCVD_IN_SORBS RBL: Received via a relay in dnsbl.sorbs.net
[209.86.2.85 listed in dnsbl.sorbs.net]
1.2 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
-1.1 AWL AWL: Auto-whitelist adjustment
