https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5402
--- Comment #3 from Steven Chamberlain <[EMAIL PROTECTED]> 2008-08-01 14:34:46 PST --- That sounds like a nice idea to me -- a configuration option for an SMTP relay to use for sending the report, rather than connecting directly to the SpamCop MXes. That feature has already been requested as bug #4684, and I think it may be a better solution for this bug also. But I notice the reports are submitted to the SpamCop MXes on port 587 instead of the standard port. I imagine that is to avoid transparent, filtering SMTP relays which some ISPs seem to use. Hopefully it's still possible for people to submit the report to SpamCop on the standard SMTP port if they know their ISP does not do this kind of filtering. And otherwise, their SMTP relay would have to be configured to deliver SpamCop reports on port 587 (assuming that port isn't filtered too). In my situation I could simply put the report into the system's normal mail queue and I think it would be delivered. The reporter would 'complete' almost immediately, whilst the relay takes care of delivery attempts. Although some people might want to be able to specify an SMTP relay for situations where they filter their outgoing mail, or need to deliver to port 587 as I mentioned above. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
