http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4828
------- Additional Comments From [EMAIL PROTECTED] 2006-03-17 03:45 ------- I just noticed that we already have a dcc_options for DCC, just nothing for dccifd. dcc_options cleans the input to make sure it only contains legal characters. For security reasons I would want the same in a dcc_dccifd_options addition. I'm still not sure about this. If it is the case that you cannot know for sure what 'n' will be, what sense does it make to configure a fixed number of rcvd_nxt options? And I don't see what other options could be used and still let dccifd to work with SpamAssassin. The choices are spam, body, header, query, grey-query, no-reject, and rcvd-nxt. Of those, spam makes no sense (report all email as spam); header is always included; body contradicts header and would not work; grey-query and no-reject would prevent a return code that SA would recognize; query would not break things, but could be accomplished by running the dcc daemon with the -Q option; and rcvd-nxt is what we are talking about whether to use. If we have access to the SMTP client ip address and host name and the EHLO string, why would it not be better to always pass them along instead of forcing dccifd to find the correct Received header and hope that it parses them correctly? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
