No, spamdyke isn't designed to block messages based on message headers.
Header information (such as the Subject line) isn't available until
after spamdyke has decided to accept the message. I intend to add
Subject line logging to spamdyke in a future version, to make it easier
to troubleshoot problems, but blocking based on Subject would require a
major rewrite.
I wrote more about this question here:
http://www.spamdyke.org/documentation/FAQ.html#SUGGESTION3
-- Sam Clippinger
J-P Raymond wrote:
> No server 1 is not running qmail (eims), but it's not a front-end server
> they are both fully fonctionnal server. The only reason I did that is
> because server 1 spam filters are much more complete than server 2.
>
> When I start working on those server I had less knowledge in linux so I
> didn't want to mess to much with the qmail setup.
>
> I've build a very efficient filter on server 1 but now clients on qmail
> complain they receive too much spam :-) (only 2 clients are filtered by
> going on server1) so when I found spamdyke I saw an opportunity to
> improve qmail. So far it's working .
>
> On server 1 I'm able to analyse the header of my emails is it possible
> to do that with spamdyke ?
>
> Ex :
> ehlo domain (I think this one is possible)
> mail from
> mail to
> subject
>
> Thanks
>
>
> > Date: Fri, 18 Jan 2008 22:29:34 -0600
> > From: [EMAIL PROTECTED]
> > To: spamdyke-users@spamdyke.org
> > Subject: Re: [spamdyke-users] reject-missing-sender-mx problem
> >
> > Correct. spamdyke returns 4xx codes for filters that are triggered by
> > missing DNS records (missing MX, missing rDNS, unresolvable rDNS). This
> > is because spamdyke can't know if the record truly doesn't exist or if
> > the DNS servers are just slow. Using a 4xx code will cause the remote
> > server to try again. If the problem was a slow DNS server, a second
> > attempt may be successful. Other filters use 5xx codes because the
> > answers are definite (rDNS keywords, blacklists, earlytalkers).
> >
> > The line you found in spamdyke.h is the one you want. If you change
> > "REJECT_SEVERITY_TEMPORARY" to "REJECT_SEVERITY_PERMANENT", spamdyke
> > will return a 5xx code for the missing MX test. Be aware, however, that
> > a slow or overloaded DNS server could cause some of your mail to be
> > rejected incorrectly.
> >
> > In your setup, is server 1 running qmail? It would be better to install
> > spamdyke there if possible.
> >
> > -- Sam Clippinger
> >
> > J-P Raymond wrote:
> > > I think I found my answer : spamdyke.h
> > >
> > > #define REJECTION_DATA_SENDER_NO_MX { REJECT_SEVERITY_TEMPORARY,
> > > ERROR_SENDER_NO_MX, STRLEN(ERROR_SENDER_NO_MX), "DENIED_SENDER_NO_MX" }
> > >
> > > REJECT_SEVERITY_TEMPORARY
> > >
> > > Why temporary because DNS could failed to answer and this email
> would be
> > > bounced for no reason ?
> > >
> > > Thanks
> > >
> > >
> ------------------------------------------------------------------------
> > > From: [EMAIL PROTECTED]
> > > To: spamdyke-users@spamdyke.org
> > > Date: Fri, 18 Jan 2008 15:10:05 -0500
> > > Subject: Re: [spamdyke-users] reject-missing-sender-mx problem
> > >
> > > Hi,
> > >
> > > I'm having problems with this rule ! It will be a bit difficult to
> > > explain so stay with me:
> > >
> > > Setup : 2 servers
> > >
> > > server 1 is filtering mail for server 2
> > > server 2 is running spamdyke with qmail
> > >
> > > If qmail refuse a message (sent by server1) with a non permanent
> > > error code 4XX, server 1 keep that email in queue until it can be
> > > sent again or timeout ! (fine) (That was my problem with the bare LF
> > > because stray LF is always 4xx on qmail not 55X permanent.)
> > >
> > > But server 1 don't deliver the other message received after the one
> > > with the 4xx error until this message timout. (bad)
> > > So basicaly queue to that domain can build up until this message is
> > > bounce or timeout.
> > >
> > > If qmail sends a 550 permanent error no problem the email is
> > > discarded and the other emails can be delivered.
> > >
> > > That beeing said,
> > >
> > > Now I've tried to activate the reject-missing-sender-mx setting
> > > on spamdyke but this rule did the same thing. I've check my log
> > > (server1) and I saw : 554 Refused. The domain of your sender address
> > > has no mail exchanger (MX).
> > >
> > > So fine 554 is a permanent error but why my other server act like a
> > > 4XX error code. I would like to know if their is an error in the
> > > error code sent by spamdyke on that particular filter ?
> > >
> > > I know it's really specific and not many of you will experience
> > > something like that but it's worth asking
> > >
> > > Thanks
> > >
> > >
> > >
> > >
> > >
> > >
> ------------------------------------------------------------------------
> > > <http:///>
> > >
> > >
> > >
> ------------------------------------------------------------------------
> > >
> > >
> > >
> ------------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > spamdyke-users mailing list
> > > spamdyke-users@spamdyke.org
> > > http://www.spamdyke.org/mailman/listinfo/spamdyke-users
> > _______________________________________________
> > spamdyke-users mailing list
> > spamdyke-users@spamdyke.org
> > http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> spamdyke-users mailing list
> spamdyke-users@spamdyke.org
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
_______________________________________________
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
