HOWTO leave all email in inbox? rule? disable AV? etc?

[sjobeck]

Hey, hi, all,

I hope this finds you well.

I have googled a slug on this as well as the forums here & gotten close but not quite right on to it for a solution to an issue we are having for some users.

Users who use IMAP are fine since they see their "junk" folder on the server & can handle those items on their own.

Users who use POP can not, as we all know, it only downloads from the inbox, so if the server moves an item to junkmail, and that user does not log-in to the webmail page for a week or two or ever, then those items sit in "junk" folder & they think the message never got delivered.

I made a rule to move items in to the inbox but I either did not get the rule quite right, or it is not possible, or it is not the best way to crack this nut.

Since every user connects in their own way (ie: web, pop, imap, etc) I can not make one adjustment to the entire system. I am not sure I can make on adjustment for an entire domain, but I would be more able & more willing to do that if I could. I could tell the office manager for that office (for that domain name) that we have set such-n-such policy for them & that is how they need to handle their mail. That is a possibility.

The perfect solution, though, if someone out there has cracked this puzzle before would be how to leave AV, AS, and so forth, all enabled on the server, but for some users (or possibly one domain name) force messages to stay in the inbox. If all messages were not moved from the inbox, then those POP users would download them & handle junk on their own at the desktop. Or, if junk was moved to junk but a rule fired off to move them back again, that would work too.

I considered that the tagging level that AV (ie: SpamAssassin) uses to tag messages could come in to play here & a tiny bit (admittedly no much) of tweaking there did not yield results. I would like AV to tag every email received, so that those users who use Rules inside their own emailer/MUA/client/etc can use the header inside the email if they want to. Even if tagging is set to "0", it can tag every single email as spam is yes or no, and that's cool by us, and users can use that or not. So, I think I want tagging set to "0". Nor sure how this overlaps with the greater (above) issue.

I am open to all advice. I am most appreciative. I would be willing to donate to someone's Amazon Wishlist. I would like to thank this active & great community/forum/etc for this incredibly great software. I cant wait to cross this issue off of my to do list & make a whole slug of users happy again. I also hope that this helps others wrestling with this same issue (as I know there are a lot of, from my search results).

Cheers.

Thanks !

Jason

[vavai]

How about whitelisting the specified account and give it a higher negative score so the email will not marking as junk anymore, even the email seems to be identified as spam but the negative score will whitelists it.

[uxbod]

I believe this would be possible using the PolicyBank feature of Amavis. You would still be able to perform AV/AS scanning but not insert any headers. The subject could still be set to [SPAM] but the message would be left in the Inbox and not filed in Junk. The caveat is that for your POP3 users you would need to create a regex filter that would be parsed by the header_checks in Postfix so it would know when to send the email to the different policy bank.

[sjobeck]

uxbod:

Thx so much for this. I will look in to it. Do you happen to have any more pointers or URL's or otherwise? I will be googling on it for sure though.

If any one else out there has any tips for us, I would be so very appreciative.

Thanks all.

Keep the ideas coming.

Thanks.

[sjobeck]

I am trying a few filters made inside the GUI where in I say X-Spam-Flag contains YES is then filed in the Inbox. But this rule seems to have no effect. I am still on this. Any one else out there cracked this code? I promise to post my final working recipe.

[sjobeck]

Looks like this is our only option for now (until the next release)

zmprov modifyAccount user@domain.com amavisBypassSpamChecks TRUE amavisSpamLover TRUE

Bug 7502 – Deactivate SPAM filter for particular users.

[uxbod]

Client does NOT want a junk folder