Ricardo P. Jasinski wrote: > Hi all, > > the system administrator in our university recently started using > spamassassin in our mail server. Unfortunately, I can't say this has > been a good thing for me and for many other users, and I'll try to > explain why. > > First, for each mail that the tool assumes to be a spam, I receive an > email with the original message as an attachment. Obviously, this way > my spam count could never decrease. > > Second, now I have no control over what I consider as a spam. What I > evaluate as spam is not the same as what my colleagues do. But now, > we are forced to living by the same rules. > > As a previous spambayes outlook plugin user, I was used to having > really good results on spam elimination and customization. My > immediate feeling is that the adoption of spamassassin has > tremendously worsened my spam-dealing routine. Since for every mail > that spamassassin considers a spam it generates new a message > describing the rules it used, spambayes has no way of sorting it by > the contents anymore. > > This is what upsets me: I (almost) was free from spam hell, now I'm > back at having to open manually all my messages, which are now hidden > inside attachments, and there is no way of improving or training my > spam detecting engine. > > I hope you understand that I am having a terrible experience with > spamassassin. Since my system administrator will not tell this to me, > I would like to know from you guys if there is a way of disabling > spamassassin for my individual mail address, and if this is an easy > thing to do. > > Thank you immensely for your replies. Also, I would like to receive > comments if you guys can think of any other way out of my situation. > Any solution that does not depend on the admin is more likely to work > for me, though. > > Ricardo.
Ouch! That doesn't sound like a good situation. Hopefully, your admin is still trying to figure out the best way to configure SpamAssassin and will be receptive to some suggestions. Unfortunately, I can't think of anything that you can do that doesn't involve the admin. The quickest fix for the problem is to request that the admin add "report_safe 0" to his local.cf file. This will simply allow the spam messages to be delivered normally (with the added header and subject markup). A side-effect of this is that you will have the ability to ignore his markup and continue using your Outlook plugin if you prefer. You can also suggest that he come here for some suggestions on configuring and using SpamAssassin. We can help him figure out the best configuration for his server. -- Bowie
