Spam Filter ISP Support Forum

  New Posts New Posts RSS Feed - A Couple of Comments on Beta .162
  FAQ FAQ  Forum Search   Register Register  Login Login

A Couple of Comments on Beta .162

 Post Reply Post Reply
Author
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4065
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Topic: A Couple of Comments on Beta .162
    Posted: 21 June 2003 at 1:01am

Don, yes, you can use RegEx in the black/white domain lists.

In build .151 we added RegEx searches to the email body as well. When that was done, I remember we fixed a couple of RegEx bugs as well. This may have caused your expressions not to work.

In the latest builds we added a tab where you can test your RegEx expressions to see if they trigger a match. I tried a couple of your and they seemed to work fine.

Could you post an example of an incoming email that is blocked and the RegEx expression that should have allowed it thru so we can try to duplicate this?

Roberto Franceschetti
LogSat Software

Back to Top
DonWMason View Drop Down
Guest Group
Guest Group
Post Options Post Options   Thanks (0) Thanks(0)   Quote DonWMason Quote  Post ReplyReply Direct Link To This Post Posted: 17 June 2003 at 9:44pm

I've been running Spamfilter for two months now. I like the software, however, I'm confused about some things that could be cleared up with minor changes to the documentation.

  1. Can I use RegEx's in both the white and black domain lists? I like to specify domain names that are very specific, yet very flexible in both the white and black domain lists.  For example, I want to receive all emails from intel.com. Sometimes Intel will send them with @intel.com, sometimes with @mailhost.intel.com and somtimes with @intel.rsc01.com domains. The standard domain wildcards you specify in various places in the documentation are not specific enough for me because I don't want to receive messages from @wintel.com or from @intelligent.com. which would be allowed with *intel*.com or any non-RegEx expressions. I personally use the following one for @intel.com and intel.net: "((.*.)*intel.(.*.)*(com|net)$)".  I use the leading "(" and trailing ")" because it seems to be required in some of the configuration files. The front and end "(.*.)*" matches any zero or more domain segments like "mailhost." in "mailhost.intel.com" or "rsc01." in "intel.rsc01.com". This form of white/black list processing worked well in the non-beta versions, but not the beta ones so far.
  2. Depending on the answer to the previous question, the white lists are not being processed correctly. Mail from domains that appear in my whitelists (and were processed correctly with non-beta versions) are now being quarantined by the beta versions .154 and .162 because of keyword matches which should happen last in the white/black list sequence of events.

Here's a few lines from my domain whitelist file showing various example domain names:

((.*.)*cr-mail.(.*.)*org$)
((.*.)*crystaluser.(.*.)*info$)
((.*.)*hotjobs.(.*.)*com$)
((.*.)*iambic.(.*.)*com$)
((.*.)*intel.(.*.)*(com|net)$)
((.*.)*shaw.(.*.)*ca$)
((.*.)*sourceforge.(.*.)*net$)

Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.047 seconds.