Paul, did you try also whitelisting the ip itself as a From: in addition to whitelisting the users name. The other possibility might be that you have a range of ip's set in the security rules which deny this ip [Mail Deny] section?
Dave Culbertson On 12/Nov/2003 20:52:57, Paul Alger \(Ironclad\) wrote: > I'm still having problems white-listing this user so she can receive this > newsletter. I have white-listed her e-mail address and she does get all of > her spam now, but still no newsletter. Boy, is she pissed! > > When the newsletter attempts delivery, I get this log entry: > > [2003-11-12 03:08:59] OK [35896888] [140.239.85.2] [CONNECT] > [2003-11-12 03:08:59] OK [35896888] [140.239.85.2] [DISCONNECT] > > Not a lot of info there. > > At the sender's end, they get: > > 220-No UCE. This server does not authorize use of its computers or network� > > The white-list of her e-mail address works fine for any message that is > caught by DNSBL or the spam.flt file. I can see the entries in the log as > "whitelisted". > > According to the docs, Sambar has these built in spam features when spam > control is turned on: > > Message does not contain a From: line. > Message does not contain a To: line. > Message contain "Apparently-To:" in the header lines. > > If ANY message is caught for the above built-in rules, white-listing does > not seem to work. Is this a BUG? I need to be able to whitelist this > lady's newsletter and the only solution I have right now is to turn spam > control off for everybody! I can't do that. > > Can anyone verify that Sambar's built in spam rules can not be whitelisted? > > Paul Alger > Ironclad Internet > > > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.536 / Virus Database: 331 - Release Date: 11/3/2003 > ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/ ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
