Are the original emails generated by end-users just using a regular email client? Or are they created through some process and/or template? If it's the latter, why not add something specific to the subject line, something the spammers don't know? For example, suppose your system is called Acme Help Desk. You could configure your process/template to send emails with a specific subject like "AHD: Trouble Ticket Request" or something similar.
Then set up a rule that deletes any incoming mail that doesn't have "AHD:" somewhere in the subject line. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Remedy Maniac Sent: Friday, February 13, 2009 2:22 AM To: arslist@ARSLIST.ORG Subject: finding a good spam killer for remedy dear all, I have been asked to find some way of reducing the number of spams ending in one of our schemas. Obviously and unfortunately, the existing tools are not capable of blocking all the spams. The email lifecycle is quiet a bit cumbersome but I have to live with it. Emails are sent to IMAP server. On my remeyd box, fetchmail pools them and give them to procmailrc. This later does first checks, formats then the emails to fit a certain criterias and give them to the email engine. Upon arrival in the Email Box, my Remedy workflow fires and creates the necessary tickets for Helpdesk or other in-house schema that I wrote. So my idea is to plug something like spamassassin to the procmail. Does anybody have any experience of infos regarding this spam killer? Or any other further hints/tips would be very welcomed. Serouche ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
