Hi, I'm having trouble (in v.2.7.532) with receiving emails from a white-listed sender when they send to a large # of recipients - while my Max RCPT To filter is turned on (which is set to "7" max RCPTs when on)...

A little background story...: Each Thursday morning, for the past 3 months, 30 users of our domain are sent an email from this white-listed user.  Every time, only 8 of the 30 recipients actually receive the message.  While trying to track down the problem, I checked my SpamFilter and Microsoft Exchange logs, and reached some inconsistencies.

(My SpamFilter setup forwards emails over to Microsoft Exchange, which then puts messages into the appropriate mail boxes)

Basically, the SpamFilter log notes that they are a bypassed sender, and acknowledges that the message will be forwarded to each of the 30 users.  But when I check Exchange, it notes only the first 8 recipients - not recording any acknowledgement of accepting (nor rejecting) other recipients.  The rest are not in the log, and not surprisingly, those left over 22 people have been telling me that they are not getting the message.

Now, last week before Thursday (the 18th) hit, I decided to try turning off my Max RCPT To filter, and see we'd have better luck receiving our Thursday morning email... and yes, every one of our 30 received the message.  SpamFilter and Exchange both report forwarding the message to 30 recipients, as usual.

Has anyone else has similar issues with delivering large RCPT To msgs from whitelisted senders?

Roberto, I do not wish to have you spin your wheels for me - especially because I am a long-time Unregistered user of your product, and you've pampered me with great support all this time.  However, if my email logs may be helpful to you in identifying any potential issues for your latest Registered version of SpamFilter, I'd be happy to provide anything that would be useful.

Thanks!
Stephen

Edited by sgeorge

sgeorge, you are correct. In version 2.7.1.517 we added this fix:

// New to VersionNumber = '2.7.1.517';
{TODO -cFix : Customer-reported problem. High CPU for messages with large number of "To:" or "CC" headers}

The fix, in addition to improving the code's performance for the high CPU, included adding a limit on the number of recipients, regardless of the whitelisting settings.

This created a problem with internal users who had their outgoing email going thru SpamFilter (i.e. listservers, owned by the SpamFilter administrator, whitelisted by IP, that would send out emails thru SpamFilter).

We already have build 3.0.1.565 ready that still limits the number of recipients for incoming emails, while allowing whitelisted senders unlimited recipients.

If you like it so much you should buy it like the rest of us did and help keep up that level of terrific support.

A fair point by both of you (and Marco, thank you for that suggestion).

SpamFilter is an excellent product, and I would love to support Roberto's continued hard work.  But I work for a non-profit organization, and we frankly would see better use of the funds that we receive from the public being used for public good than to invest in email filtering software that only benefits our staff.

Albeit, the registered version of SpamFilter comes at a fantastic value.  It is constantly being improved and the support given to users is unparalleled.  You'd be hard pressed to find anyone who pays such close attention to the input from users - registered and unregistered -for their product.

Thank you again, Roberto.

-Stephen