http://bugzilla.spamassassin.org/show_bug.cgi?id=3621
------- Additional Comments From [EMAIL PROTECTED] 2004-07-19 19:42 ------- Created an attachment (id=2150) --> (http://bugzilla.spamassassin.org/attachment.cgi?id=2150&action=view) draft patch, not finished I'm still working on this, it's not complete yet, but I'm looking for feedback on the patch. I have hopes of getting this to the point where we can put it into SpamAssassin 3.0. It will have a very limited effect on the code base. Julian has been helping define what is needed and desired. Summary of patch: - some minor cleanup of the documentation - add dont_report_to_spamcop option to report_as_spam() - add base64_encode() to Util.pm - add is_spamcop_available() to Dns.pm - new options in Conf.pm: * email_address * spamcop_submission_address - minor cleanup in Reporter.pm (just some reordering) - add spamcop reporting to Reporter.pm The mechanism used to actually send the mail will probably change. Some of the options under discussion: - use mail on port 587 (avoid port 25 filtering) - HTTP submission (probably not) - connecting direct to SpamCop MX instead of relaying through localhost My inclination is to go with port 587 direct and if that fails, do nothing. Using sendmail might have the bad side effect of resulting in a lot of bounce messages, alarming sysadmins, etc. Julian has a short SMTP email routine he thinks we can use. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
