starred/modoboa-modoboa

Fork 0

mirror of https://github.com/modoboa/modoboa.git synced 2026-04-26 17:36:01 +03:00

[GH-ISSUE #368] amavis extension: list messages by class (spam, virus, etc.) #354

New issue

Closed

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

kerem commented

2026-02-27 11:11:20 +03:00

Owner

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

Originally assigned to: @tonioo on GitHub.

Originally created by Louis-Dominique Dubeau on 2013-02-14T12:55:11Z

This is another thing that I found useful when I was using Maia Mailguard.

Currently the amavis extension shows all messages together. The "Content Class" drop down allows to select by class (spam, virus, etc.) but there is no function to see only messages of a specific class. Being able to see only messages of a specific class is useful, cognitively speaking. The way I look at the list of messages flagged by amavis changes depending on what kind of message it is:

Spam: could have been flagged erroneously, so I have to at least cursorily check whether there's been a mistake.
Bad header or bad mime: their presence in quarantine is merely informative because my amavis still passes them to me, so I can delete them at will. If one of the messages is from someone I know, I might send them an email informing them that they are sending emails with bad headers or mime.
Virus: I've never had to rescue a message flagged as virus, so my approach is to delete them without examination. I've never receive a virus from someone I know but if I had I would want to notify them.

Because what I do changes depending on the type of message I'm looking at, I find it easier to go through quarantine if I can look at all virus messages (and only them) at once, then all bad header messages, etc.

The selection drop down falls short of what I'd like, because if I tell it to select of "virus" messages, for instance, I have to visually search for those messages on the screen and I could miss one.

Originally created by @tonioo on GitHub (Dec 4, 2013). Original GitHub issue: https://github.com/modoboa/modoboa/issues/368 Originally assigned to: @tonioo on GitHub. **Originally created by Louis-Dominique Dubeau on 2013-02-14T12:55:11Z** This is another thing that I found useful when I was using Maia Mailguard. Currently the amavis extension shows all messages together. The "Content Class" drop down allows to _select_ by class (spam, virus, etc.) but there is no function to _see_ only messages of a specific class. Being able to see only messages of a specific class is useful, cognitively speaking. The way I look at the list of messages flagged by amavis changes depending on what kind of message it is: - Spam: could have been flagged erroneously, so I have to at least cursorily check whether there's been a mistake. - Bad header or bad mime: their presence in quarantine is merely informative because my amavis still passes them to me, so I can delete them at will. If one of the messages is from someone I know, I might send them an email informing them that they are sending emails with bad headers or mime. - Virus: I've never had to rescue a message flagged as virus, so my approach is to delete them without examination. I've never receive a virus from someone I know but if I had I would want to notify them. Because what I do changes depending on the type of message I'm looking at, I find it easier to go through quarantine if I can look at _all_ virus messages (and _only_ them) at once, then all bad header messages, etc. The selection drop down falls short of what I'd like, because if I tell it to select of "virus" messages, for instance, I have to visually search for those messages on the screen and I could miss one.

kerem

2026-02-27 11:11:20 +03:00

closed this issue
added the
enhancement
label

kerem commented

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

Author

Owner

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

Posted by Antoine Nguyen on 2013-02-14T20:18:22Z

That's another way to filter the listing but I like it. I'll need to find a cleaner way to propose those options.

Thanks for the proposal :)

@tonioo commented on GitHub (Dec 4, 2013): **Posted by Antoine Nguyen on 2013-02-14T20:18:22Z** That's another way to filter the listing but I like it. I'll need to find a cleaner way to propose those options. Thanks for the proposal :)

kerem commented

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

Author

Owner

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

Posted by Antoine Nguyen on 2013-11-05T17:29:01Z

Hi Louis,

I'm thinking about this feature and how to implement it. I think the easiest would be to limit the filtering to one type at a time.

What do you think about it ?

@tonioo commented on GitHub (Dec 4, 2013): **Posted by Antoine Nguyen on 2013-11-05T17:29:01Z** Hi Louis, I'm thinking about this feature and how to implement it. I think the easiest would be to limit the filtering to one type at a time. What do you think about it ?

kerem commented

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

Author

Owner

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

Posted by Louis-Dominique Dubeau on 2013-11-05T17:32:30Z

Antoine Nguyen wrote:

I'm thinking about this feature and how to implement it. I think the easiest would be to limit the filtering to one type at a time.

Yep. That's what I think.

@tonioo commented on GitHub (Dec 4, 2013): **Posted by Louis-Dominique Dubeau on 2013-11-05T17:32:30Z** Antoine Nguyen wrote: > I'm thinking about this feature and how to implement it. I think the easiest would be to limit the filtering to one type at a time. Yep. That's what I think.

kerem commented

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

Author

Owner

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

Posted by Antoine Nguyen on 2013-11-05T17:33:41Z

Louis-Dominique Dubeau wrote:

Antoine Nguyen wrote:

I'm thinking about this feature and how to implement it. I think the easiest would be to limit the filtering to one type at a time.

Yep. That's what I think.

Great :)

@tonioo commented on GitHub (Dec 4, 2013): **Posted by Antoine Nguyen on 2013-11-05T17:33:41Z** Louis-Dominique Dubeau wrote: > Antoine Nguyen wrote: > > > I'm thinking about this feature and how to implement it. I think the easiest would be to limit the filtering to one type at a time. > > Yep. That's what I think. Great :)