A2 Hosting Forums

Hi!  a2s20 has been shifted back to use spamd/spamc now.  However:

1) my mail volume has dropped *a lot*.  I think it's related to #2 below, but ???  I've received 2 pieces of spam in the last 20 hours or so, where the volume had been about 250 per day.  I'd rather you not throw the email away, just in case.  See #3 below.

2) the .filter file seems munged.  It had a /dev/null entry already, even after I "disabled" spam discard.  There's no whitespace between the contains entry and the /dev/null either (whether enabled or disabled).  Plus signs fill up the whitespace it seems.  How much can we customize the '.filter' file?

3) I would like to see spam moved to a Junk folder within my email space.  Can this be done via the '.filter' file?

Comments or (polite) suggestions are welcome.

Thanks ... Gerard

The new system cuts off a lot more mail right at the SMTP level so a ton of spam is just plain not going to be accepted to begin with.

In any case, please submit a support ticket if you are having specific support issues like the other ones mentioned below and we'll be happy to try to work with you.

You can setup filters based on the Spam Status to move emails into any folder you like in the control panel.  Either globally or per account.

Thanks.

It really is amazing. I too was unsettled at the drop in email, but I have yet to find any evidence that a non-spam message did not make it through.

Given that email addresses don't generally become less known to spammers, I never expected my email accounts to be so clean again.

If every system screened that well, it would not pay to spam and spammers would become extinct.

Thanks A2hosting.

Hi!

The two examples that I know of, are both password reset emails which used non-existant email addresses, in order to avoid being SPAMmed by being in an infected machine's inbox, I guess.  A2hosting temporarily shut off sender-verify (appreciated) so I could receive the first one, and the second found a work around.

Unless you know a mail is expected, you won't know what's being bounced.  A mail log scan is required to verify errors when you know to expect them.

Gerard

My server had never been switched away from SpamAssassin, but I guess in the switch of the other servers back to SpamAssassin mine got downgraded.  And by downgraded I mean that subject rewrite rules no longer work.  I used to have my SpamAssassin configured to rewrite the subjects so that the SpamAssassin score was in the subject.  That way when I checked my Spam folder online every week or so I could sort by subject and quickly scan low-scoring messages to see if any non-Spam messages had been incorrectly flagged as Spam.  Now all the messages just come through with "*** SPAM ***" at the start of the subjects, meaning that I have to scan through ALL of the Spam.  Not new and improved functionality for me, but new and definitely unimproved!

Yes, since I still have my old university account and have the full .forward->procmail->spamassassin chain there, I, too, would prefer having the score in the subject line.  I have 'rewrite_header Subject SA(_SCORE_)!' as the line in .spamassassin/user_prefs, only one character shorter (usually) than '***SPAM***', but visually shorter since the parens and exclamation are quite thin in a proportional font.  I would not mind seeing some variation of this as a standard in the A2hosting setup (since we are rewriting the subject line, regardless), maybe 'SA!_SCORE_!' would work for most.

Gerard