On Sat, Jun 26, 2010 at 11:51:14AM -0600, LuKreme wrote:
> On 25-Jun-2010, at 10:50, Ted Mittelstaedt wrote:
> > SA would parse the entire attachment except that there's a default setting
> > saying to stop processing after a certain amount of KB of
> > data has been processed. The idea is that
On 25-Jun-2010, at 10:50, Ted Mittelstaedt wrote:
> SA would parse the entire attachment except that there's a default setting
> saying to stop processing after a certain amount of KB of
> data has been processed. The idea is that a spammer isn't going to send
> a large attachment on every spam.
Ashish,
SA itself mainly does rule matching, it reads the decoded mail line by
line, comparing it to it's rules and (optionally) bays database.
SA would parse the entire attachment except that there's a default
setting saying to stop processing after a certain amount of KB of
data has been
On 6/25/10 7:53 AM, Sharma, Ashish wrote:
Hi,
I want to know how spamassassin works from a developers point of view,
specifically I want an answer to following questions:
1. How is an email rendered on spamassassin once it's received?
I am not one of the spamassassin developers, but I am
Hi,
I want to know how spamassassin works from a developers point of view,
specifically I want an answer to following questions:
1. How is an email rendered on spamassassin once it's received?
2. How are email attachments handled on spamassassin for rule parsing?
3. How is spamassassin able to
