[GH-ISSUE #168] Use django's orm to communicate with amavis tables #153

New issue

Closed

opened 2026-02-27 11:10:21 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 11:10:21 +03:00

Owner

Originally created by @tonioo on GitHub (Dec 4, 2013).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/168

Originally assigned to: @tonioo on GitHub.

Originally created by Antoine Nguyen on 2011-07-28T11:45:06Z

Currently, Modoboa is using raw SQL queries to communicate with Amavis. Some problems with that:

Only MySQL is supported,
Queries are not really optimised,
It represents more maintenance work.

Since Django is able to communicate with multiple databases at a time, it represents a better option.

Originally created by @tonioo on GitHub (Dec 4, 2013). Original GitHub issue: https://github.com/modoboa/modoboa/issues/168 Originally assigned to: @tonioo on GitHub. **Originally created by Antoine Nguyen on 2011-07-28T11:45:06Z** Currently, Modoboa is using raw SQL queries to communicate with Amavis. Some problems with that: - Only [[MySQL]] is supported, - Queries are not really optimised, - It represents more maintenance work. Since Django is able to communicate with multiple databases at a time, it represents a better option.

kerem

2026-02-27 11:10:21 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-27 11:10:22 +03:00

Author

Owner

@tonioo commented on GitHub (Dec 4, 2013):

Posted by Redmine Admin on 2011-08-23T14:36:53Z

In [d1737f2c152bca64997cda976f9587459c28823b]:

#!CommitTicketReference repository="" revision="d1737f2c152bca64997cda976f9587459c28823b"
Quarantine plugin update:
* Using django's orm to access amavis database
* Many UI improvments
* Better use of the RS field
fixed #88 & #72
see #155

@tonioo commented on GitHub (Dec 4, 2013): **Posted by Redmine Admin on 2011-08-23T14:36:53Z** In [d1737f2c152bca64997cda976f9587459c28823b]: <pre> #!CommitTicketReference repository="" revision="d1737f2c152bca64997cda976f9587459c28823b" Quarantine plugin update: * Using django's orm to access amavis database * Many UI improvments * Better use of the RS field fixed #88 & #72 see #155 </pre>

kerem commented

2026-02-27 11:10:22 +03:00

Author

Owner

@tonioo commented on GitHub (Dec 4, 2013):

Posted by Redmine Admin on 2011-08-24T13:40:14Z

In [e5373c5cf3f5df38002bf9e76f1cd4a81842efba]:

#!CommitTicketReference repository="" revision="e5373c5cf3f5df38002bf9e76f1cd4a81842efba"
Some fixes.
see #155

@tonioo commented on GitHub (Dec 4, 2013): **Posted by Redmine Admin on 2011-08-24T13:40:14Z** In [e5373c5cf3f5df38002bf9e76f1cd4a81842efba]: <pre> #!CommitTicketReference repository="" revision="e5373c5cf3f5df38002bf9e76f1cd4a81842efba" Some fixes. see #155 </pre>

kerem commented

2026-02-27 11:10:22 +03:00

Author

Owner

@tonioo commented on GitHub (Dec 4, 2013):

Posted by Redmine Admin on 2011-08-26T08:14:01Z

In [12f8cf410524daef683c86ea80361c37662d001b]:

#!CommitTicketReference repository="" revision="12f8cf410524daef683c86ea80361c37662d001b"
Columns must be restored each time a new instance of SQLlisting is created. (static member issue)
see #155

@tonioo commented on GitHub (Dec 4, 2013): **Posted by Redmine Admin on 2011-08-26T08:14:01Z** In [12f8cf410524daef683c86ea80361c37662d001b]: <pre> #!CommitTicketReference repository="" revision="12f8cf410524daef683c86ea80361c37662d001b" Columns must be restored each time a new instance of SQLlisting is created. (static member issue) see #155 </pre>

kerem commented

2026-02-27 11:10:22 +03:00

Author

Owner

@tonioo commented on GitHub (Dec 4, 2013):

Posted by Redmine Admin on 2011-08-26T15:55:43Z

In [ac7291727da5b87e932c62ff2f5462f37596d76b]:

#!CommitTicketReference repository="" revision="ac7291727da5b87e932c62ff2f5462f37596d76b"
Fixed navigation issue that occured after a message removal.
see #155

@tonioo commented on GitHub (Dec 4, 2013): **Posted by Redmine Admin on 2011-08-26T15:55:43Z** In [ac7291727da5b87e932c62ff2f5462f37596d76b]: <pre> #!CommitTicketReference repository="" revision="ac7291727da5b87e932c62ff2f5462f37596d76b" Fixed navigation issue that occured after a message removal. see #155 </pre>