[jira] [Closed] (JAMES-3797) Moving all source code related to SpamAssassin to module third-party/spamassassin

2022-08-22 Thread Benoit Tellier (Jira)
[ https://issues.apache.org/jira/browse/JAMES-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3797. - Fix Version/s: 3.8.0 Resolution: Fixed Merged > Moving all source code related

[jira] [Created] (JAMES-3797) Moving all source code related to SpamAssassin to module third-party/spamassassin

2022-08-04 Thread Tung TRAN (Jira)
Tung TRAN created JAMES-3797: Summary: Moving all source code related to SpamAssassin to module third-party/spamassassin Key: JAMES-3797 URL: https://issues.apache.org/jira/browse/JAMES-3797 Project

Re: Moving all source code related to SpamAssassin to module third-party/spamassassin

2022-08-01 Thread Benoit TELLIER
+1 IMO thrid-party/spamassassin should also contain relevant mailets, SMTP hooks in addition to the existing "mailbox plugin". Such a change would require operational changes: users relying on the existing SpamAssassin extension would need to drop the corresponding JAR in the extensions-jars

Moving all source code related to SpamAssassin to module third-party/spamassassin

2022-07-31 Thread Tung Tran Van
Hi all, When integration RSpamD, I see the separate between 2 modules: - mailbox/plugin/spamassassin - third-party/spamassassin Should we move spamassassin stuff in one thrid-party/spamassassin module? It will more consistency, that will similar with third-party/rspamd (WIP) Ref: https://issues.