|Main Archive Page > Month Archives > spamassassin-users archives|
The MTA is not controlled by me. The mails are received at a Google Apps
email address. Hence I don't have the option to implement SpamAssassin at
the front end( before the mail is delivered to the mailbox)
On Fri, Apr 22, 2011 at 8:46 PM, Martin Gregorie <email@example.com>wrote:
> On Fri, 2011-04-22 at 20:04 +0530, Shankar wrote:
> > Introduction:
> > I have a ticket system in PHP. People report tickets over email. A mail
> > parser connects to the mailbox using IMAP, downloads the email and parses
> > to create a ticket which can be viewed/updated over the web interface.
> Who controls the IMAP mailbox and the MTA that puts incoming messages
> into it?
> If its you or you are in a position to run your own MTA, your best bet
> is to let it pass incoming mail to Spamassassin and put the scored mail
> in the mailbox. This way your application can check for spam by looking
> at the X-Spam-Status header and you also have the opportunity of using
> the MTA's SMTP-time checks to apply blacklists etc and reject spam
> without needing to process it further.
> Configure the MTA to use spamc/spamd rather than calling the
> spamassassin script because its faster: where spamassassin goes through
> startup/shutdown for every message it scans, spamd only does so once,
> when the system is booted.
-- Regards, Varun Shankar