|
|
SA Bugzilla – Full Text Bug Listing |
- Home
- | New
- | Browse
- | Search
- | [?]
- | Reports
- | Help
- | New Account
- | Log In
- | Forgot Password
|
|
|
SA Bugzilla – Full Text Bug Listing |
| Summary: | Add VERSION to spamd protocol | ||
|---|---|---|---|
| Product: | Spamassassin | Reporter: | Jorge Valdes <jorge> |
| Component: | spamc/spamd | Assignee: | SpamAssassin Developer Mailing List <dev> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | enhancement | CC: | apache |
| Priority: | P5 | ||
| Version: | 3.2.5 | ||
| Target Milestone: | Undefined | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Attachments: | patch to add VERSION option to spamc/spamd | ||
Closing ancient stale bug. |
Created attachment 4385 [details] patch to add VERSION option to spamc/spamd When running SPAMC/SPAMD in several servers to scan messages, we should know the version of the spamd server in order to determine what options are available. This is not generally a problem, because the SPAMD protocol rarely changes, but when the protocol changes in order to accomodate new methods, we need to know. Using SIMSCAN as the agent calling spamd, I wanted to know the version of the spamd server in order to record the correct scanner version in the header, so I came up with a patch in order to be able to get this information, and realized that unless the spamd protocol changes, or spamc options are added, upgrades are only needed on the scanning servers, mailstores only need to have a very "recent" version of spamc in order to scan a message/file. Also, with this new option, I will always have the correct scanner version in my simversions.cdb file my calling this option instead of getting the spamc version which may not be the same.