David B Funk engineering.uiowa.edu> writes:
> Exactly so.
> Usually you can find the related message by matching the time-stamp
> from your maillog to your spamd log. You can also do some detective work,
> eliminate maillog entries that have an incoming msgid (IE one from the
> sending MTA) and ju
On Thu, 13 Apr 2006, martin wrote:
> thx info, that mean that if email don't given msgid when arrived, sendmail
> default will add itself id for this mail and this msgid will not pass to
> milter?
> So is it no method to find related message from maillog at such case?
Exactly so.
Usually you c
David B Funk engineering.uiowa.edu> writes:
> Because some messages arrive at your MTA without a msgid to log
> (usually a sign of either a forged message or a brain-damaged
> sending MTA).
>
> The standard sendmail config will add a locally generated msgid to
> such messages but the "milter" i
On Wed, 12 Apr 2006, martin wrote:
>also, just wonder why at spam.log, some scanned message can't log down
> msgid
> (which at maillog using)
Because some messages arrive at your MTA without a msgid to log
(usually a sign of either a forged message or a brain-damaged
sending MTA).
The stand
Matt Kettler comcast.net> writes:
>
> martin wrote:
> > Matt Kettler comcast.net> writes:
> >
> >
> >> martin wrote:
> >thx info, that seem the cause, becoz the email att. with a
> >image around 250k in size.
> >just wonder, can this parameter tuneable from config file? And SA had a
martin wrote:
> Matt Kettler comcast.net> writes:
>
>
>> martin wrote:
>>
>>> using spamassassin-3.0.4-2, spamass-milter-0.3.0, clamav-0.88,
>>> clamav-milter-0.88, sendmail-8.13.1 under FC3. All parts seem work fine, but
>>> found some mails had dropped to mbox directly and seem not sca
Matt Kettler comcast.net> writes:
>
> martin wrote:
> > using spamassassin-3.0.4-2, spamass-milter-0.3.0, clamav-0.88,
> > clamav-milter-0.88, sendmail-8.13.1 under FC3. All parts seem work fine, but
> > found some mails had dropped to mbox directly and seem not scanned
> > by sa (X-Spam head
martin wrote:
> using spamassassin-3.0.4-2, spamass-milter-0.3.0, clamav-0.88,
> clamav-milter-0.88, sendmail-8.13.1 under FC3. All parts seem work fine, but
> found some mails had dropped to mbox directly and seem not scanned by sa
> (X-Spam
> header had not added, spam.log can't found related
using spamassassin-3.0.4-2, spamass-milter-0.3.0, clamav-0.88,
clamav-milter-0.88, sendmail-8.13.1 under FC3. All parts seem work fine, but
found some mails had dropped to mbox directly and seem not scanned by sa (X-Spam
header had not added, spam.log can't found related message). The system (P4,
