That is by design. Whitelisting does just that, bypass *all* of SpamFilter rules. The only exception is the antivirus filter.

No, currently that is not possible. The whitelist was created as certain domains/users do not want to have their email filtered. If we were to "skip" that specific rule for the whitelist, there will be *many* more admins who'd want it back as they'll have angry customers who now won't be able to receive large emails. That would also open the way to generate more requests to bypass other filters as well, and would make things rather confusing as there will be some filters to which the whitelist applies and others where it won't.

The only solution will be to allow further customizations to the filters, and we're working on that...

My whole point here is in the configuration panel I have it set for max connections per ip set to 10.

Just because an ip is whitelisted doesn't mean it should be allowed to exceed the max allowed connections. I've had to whitelist some large isps in my area because of alot of the emails we recieve, so does this mean that they will exceed the max connections limit? That doesn't make any sense. Trusted or not, I only want 10 connections per ip. It's kind of defeating the rule....

I was actually mistaken and talked about the wrong filter (max message size instead of the max connection limit). However the reply still stands. The whitelist will overwrite everything except the anti-virus filter. The reasoning is the same. Admins may have a connection limit set, but for example may not want to impose that limit to their secondary MX server, or their customer's SMTP server. In any case, if we were to impose the connection limit on whitelisted IPs as well, we'd always have customers who would then say "my whitelist is supposed to bypass all filters, why are certain filters not affected by it?"

Again, the only solution will be to have more flexibility in the filtering rules.