| View previous topic :: View next topic |
| Author |
Message |
maddox
Joined: 22 Feb 2007
Posts: 8
|
 Posted: Tue Aug 11, 2009 9:09 pm Post subject: email addresses not added to white list |
 |
|
email addresses I sent email to, they should be added to white list of email addresses, right? they are not added, I use default settings of freshly installed newest version of antispamsniper
also it seems when I make an email 'mark as not junk' the email address is also not added to white list.
is it normal? I am pretty sure it was not like this in a previous versions |
|
| Back to top |
|
 |
vetaltm
Author
Joined: 05 Feb 2006
Posts: 748
|
| Posted: Tue Aug 11, 2009 9:17 pm Post subject: |
|
|
Please check the following:
- The checkbox "Update the whitelist automatically" must be enabled on Filtering | Training page.
- The whitelist must not contain items with too common masks. E.g. new addresses are not added when the whitelist contains an item with * or *@* in address field. |
|
| Back to top |
|
|
maddox
Joined: 22 Feb 2007
Posts: 8
|
| Posted: Tue Aug 11, 2009 10:05 pm Post subject: |
|
|
the checkbox is enabled
there are no addresses with * at all on the white list
now I see 'sometimes' the addresses are added to whitelist when 'mark as not junk' is selected however when I send an email to someone, it does not go to white list at all (just checked for the second time) |
|
| Back to top |
|
|
vetaltm
Author
Joined: 05 Feb 2006
Posts: 748
|
| Posted: Tue Aug 11, 2009 10:15 pm Post subject: |
|
|
| maddox wrote: | now I see 'sometimes' the addresses are added to whitelist when 'mark as not junk' is selected
|
If it worked once, it should work in other cases too.
| maddox wrote: |
however when I send an email to someone, it does not go to white list at all (just checked for the second time) |
Auto-training on outgoing mail works only for regular unprotected connections. SMTP connections protected with TLS or STARTTLS (SSL) are not checked. |
|
| Back to top |
|
|
maddox
Joined: 22 Feb 2007
Posts: 8
|
| Posted: Tue Aug 11, 2009 10:37 pm Post subject: |
|
|
the connection I use is regular, unprotected
the port that SMPT is listening at was changed to 587
but other than that it is normal connection, no encoding, pure text
btw, why don't you add an option to whitelist a domain? (in right click context menu I mean) |
|
| Back to top |
|
|
vetaltm
Author
Joined: 05 Feb 2006
Posts: 748
|
| Posted: Wed Aug 12, 2009 6:01 am Post subject: |
|
|
| maddox wrote: | the connection I use is regular, unprotected
the port that SMPT is listening at was changed to 587
but other than that it is normal connection, no encoding, pure text
|
The problem is in non-standard port. The plug-in filters only standard SMTP port 25, and it is not possible to change this in current version.
| maddox wrote: |
btw, why don't you add an option to whitelist a domain? (in right click context menu I mean) |
There is a context menu item "Add sender to White list" in Filtering log. To whitelist a domain replace the user name and mailbox name with "*", e.g. add a whitelist item with name: *, address: *@domain.com. |
|
| Back to top |
|
|
maddox
Joined: 22 Feb 2007
Posts: 8
|
| Posted: Wed Aug 12, 2009 8:35 am Post subject: |
|
|
does the port affect filtering received mail as well (but I use default pop3)?
I have a domain added to white list like *@domain.com
even though email from billing@domain.com lands in spam
there are no other @domain.com in white list so there must be no mismatch |
|
| Back to top |
|
|
vetaltm
Author
Joined: 05 Feb 2006
Posts: 748
|
| Posted: Wed Aug 12, 2009 10:29 am Post subject: |
|
|
| maddox wrote: | does the port affect filtering received mail as well (but I use default pop3)?
|
No. Using non-standard port for SMTP affects only auto-training on outgoing mail. The other features work properly in this case.
| maddox wrote: |
I have a domain added to white list like *@domain.com
even though email from billing@domain.com lands in spam
there are no other @domain.com in white list so there must be no mismatch |
The whitelist is not used when the sender address (From field) appears in fields To or CC. Spammers often use the address of recipient in From to evade the spam filters. So when one of the recipients appears in From, the plug-in treats it as a fake and doesn't check the whitelist to avoid autotraining on spam. Use the white rules for classifying this kind of messages unconditionally. The following rule classifies as non-spam all messages having @domain.com in From:
Header{From} =~ @domain.com
It is possible to add several domains in the same condition:
Header{From} =~ @domain1.com|@domain2.com|@domain3.com |
|
| Back to top |
|
|
maddox
Joined: 22 Feb 2007
Posts: 8
|
| Posted: Wed Aug 12, 2009 2:44 pm Post subject: |
|
|
I checked this particular email that landed in spam even though the email address was listed on white list
I looked on headers, and the whitelisted email is in FROM: header
header TO contains my email address
and there is no CC header or BCC |
|
| Back to top |
|
|
maddox
Joined: 22 Feb 2007
Posts: 8
|
| Posted: Wed Aug 12, 2009 4:16 pm Post subject: |
|
|
| well, actually after my short experience with this program (I am the paid user) I would like to say that I would never buy it again. The software is buggy and it does not work as expected, sorry to say so but this is the truth |
|
| Back to top |
|
|
|
FAQ
Search
Profile
Log in
Register
