What we have done, is create a set of forms and workflow within Remedy that looks at incoming emails (AR System Email Messages) looking at variables like, from address (from domains), to address, subject and key words within the body of the email and then skips or deletes records basically a spam killer within Remedy (Granted a record is still created in AR System Email Messages but we clean these up nightly anyway. Of course I love to make Remedy's (UWIP) Email engine dance, being the architect of Rem-Mail
Doug -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Kaiser, Norm E CIV USAF AFMC 96 CS/SCCE Sent: Friday, February 13, 2009 9:18 AM To: [email protected] Subject: Re: finding a good spam killer for remedy 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:[email protected]] On Behalf Of Remedy Maniac Sent: Friday, February 13, 2009 2:22 AM To: [email protected] 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" DISCLAIMER Important! This message is intended for the above named person(s) only and is CONFIDENTIAL AND PROPRIETARY. If you are not the intended recipient of this e-mail and have received it in error, please immediately notify the sender by return email and then delete it from your mailbox. This message may be protected by the attorney-client privilege and/or work product doctrine. Accessing, copying, disseminating or re-using any of the information contained in this e-mail by anyone other than the intended recipient is strictly prohibited. Finally, you should check this email and any attachments for the presence of viruses, as the sender accepts no liability for any damage caused by any virus transmitted by this email. Thank you. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
