Bug 269 - DCC support doesnt use existing headers
Summary: DCC support doesnt use existing headers
Status: RESOLVED WONTFIX
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: All All
: P3 enhancement
Target Milestone: ---
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-02 02:58 UTC by Steve Hill
Modified: 2002-05-02 12:02 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Hill 2002-05-02 02:58:03 UTC 
All mail at my site has been passed through a DCC client by the time it is
delivered and hence already contains the X-DCC headers. Spamassassin does not
make use of these headers but instead filters the mail through dccproc again.

This causes all my mail (and that of anyone else that does the same thing) to be
submitted to DCC twice (and also spawns unnecesary processes on my box).
Comment 1 Charlie Watts 2002-05-02 08:35:24 UTC 
Subject: Re: [SAdev]  New: DCC support doesnt use existing headers

> All mail at my site has been passed through a DCC client by the time it
> is delivered and hence already contains the X-DCC headers. Spamassassin
> does not make use of these headers but instead filters the mail through
> dccproc again.
>
> This causes all my mail (and that of anyone else that does the same
> thing) to be submitted to DCC twice (and also spawns unnecesary
> processes on my box).

So ... why don't you disable either the first DCC check or disable the DCC
check in SA for your site?

Obeying a pre-existing X-DCC header would be an abusable hole.
Comment 2 Charlie Watts 2002-05-02 08:36:43 UTC 
Subject: Re: [SAdev]  New: DCC support doesnt use existing headers

> All mail at my site has been passed through a DCC client by the time it
> is delivered and hence already contains the X-DCC headers. Spamassassin
> does not make use of these headers but instead filters the mail through
> dccproc again.
>
> This causes all my mail (and that of anyone else that does the same
> thing) to be submitted to DCC twice (and also spawns unnecesary
> processes on my box).

So ... why don't you disable either the first DCC check or disable the DCC
check in SA for your site?

Obeying a pre-existing X-DCC header would be an abusable hole.

-- 
Charlie Watts
cewatts@frontier.net
Frontier Internet, Inc.
http://www.frontier.net/


_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
Spamassassin-devel mailing list
Spamassassin-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spamassassin-devel
Comment 3 Craig Hughes 2002-05-02 20:02:28 UTC 
Agree with Charlie 100% -- we can't trust a X-DCC header, because a spammer might have inserted 
it themselves.  You should turn off DCC in SA by setting its score to 0, or else stop doing DCC 
outside of SA.