You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Alex <my...@gmail.com> on 2018/11/21 00:58:25 UTC
whitelisting DCC messages
Hi,
This is perhaps off-topic, but does anyone have any tips on how to
whitelist a message that hits DCC? I believe it's hitting DCC because
it has an empty body.
I've created digests for pyzor and razor, but DCC is much more involved.
I've tried generate a checksum, but I don't know if this is right or
what to do with it next.
$ /var/lib/dcc/bin/dccproc -QCw whiteclnt < dcc-empty
X-DCC--Metrics: mail01.example.com 1102; Body=0 Fuz1=0 Fuz2=many
reported: 0 checksum server
env_From: d41d8cd9 8f00b204 e9800998 ecf8427e
From: 7c09f5ba dd3f6a43 24f75466 afda2915
Message-ID: 145d9d01 f7b21152 a86b0141 1fd5c0f1
Received: 9d8accc4 f9eeba67 8dde18da fbe46c50
Body: 3de7141d 134f5fb4 0186aa32 545805ad 0
Fuz1: 104f1b8d 6fc72af7 ff2d1c1f 2a7c9f6d 0
Fuz2: ad6b5492 77db8305 4fddeebd fdb30168 many
Is it possible to enable checksum logging in addition to what SA
reports when not running a dcc daemon?
Re: whitelisting DCC messages
Posted by Alex <my...@gmail.com>.
Hi,
> $ /var/lib/dcc/bin/dccproc -QCw whiteclnt < dcc-empty
> X-DCC--Metrics: mail01.example.com 1102; Body=0 Fuz1=0 Fuz2=many
> reported: 0 checksum server
> env_From: d41d8cd9 8f00b204 e9800998 ecf8427e
> From: 7c09f5ba dd3f6a43 24f75466 afda2915
> Message-ID: 145d9d01 f7b21152 a86b0141 1fd5c0f1
> Received: 9d8accc4 f9eeba67 8dde18da fbe46c50
> Body: 3de7141d 134f5fb4 0186aa32 545805ad 0
> Fuz1: 104f1b8d 6fc72af7 ff2d1c1f 2a7c9f6d 0
> Fuz2: ad6b5492 77db8305 4fddeebd fdb30168 many
I believe I figured it out. The "body" hash above must be for either
an empty text body or the "empty" quoted-printable HTML body. Adding
the following to /var/lib/dcc/whiteclnt appears to work.
ok hex fuz2 ad6b5492 77db8305 4fddeebd fdb30168
ok hex body 3de7141d 134f5fb4 0186aa32 545805ad