s.ivanov at proxmox.com
Fri May 17 16:10:11 CEST 2019
Thanks for the suggestions.
We track enhancement-requests in our bugzilla  (just pick 'pmg' as
product when opening a new request).
Please open one request per feature-request.
Some comments ininline...
On Tue, 14 May 2019 16:54:24 +0200 (CEST)
sandermoors at telenet.be wrote:
> I have some suggestions for the next release/update:
> 1. Add a "SPAM" and "HAM" button on the quarantaine page and have it
> run "sa-learn --spam mail.msg" or "sa-learn --ham mail.msg"
> respectively in order to train the spamassassin bayes database
I think that this is one of the cases, where half of the users would
like to have this functionality (because they trust their
downtstream users to klick the right things) and the other half could
not work with it (because they do not trust their downstream users and
having a untrustworthy bayes-db is worse than not having one at all.
In general I'm not too sure that Bayes filtering is too effective in an
environment with one classification body for many users.
> 2. Add subject logging. Someone already modified pmg-smtp-filter (see
> ) in order to do this. But it would be much better if the tracking
> centers gets a new column (subject) for a nice overview.
I think that this would be problematic for many users, because the
subject contains quite sensitive information (and is not necessary for
routing mail as opposed to from/to mail-addresses) - so if we add
something like that it would need to be optional!
> 3. add support for OpenDKIM signing for outgoing email.
> It's just a matter of installing an additional debian package and
> some postfix templates changes (very minimal) and it's a serious
> request many people are waiting for a long time already.
(and comment that you'd like to see that as well)
It seems nobody has had the time to pick up that topic yet, but we
could provide some help and feedback if somebody wants to implement it.
see PVE's developer documentation for an overview of our workflow .
> 4. Option to activate/deactivate spam reports on a per recipient
> basis. Some users don't want it, others need it.
This would be quite difficult to implement, because PMG does not have
an explicit list of mailboxes it delivers mails to.
If you use LDAP for your mailboxes you can do this already with a
fitting ruleset (put those users who wish to get the mails into one
group and put their mail into the quarantaine, tag the mails only and
deliver them directly for others)
> 5. As an admin you have to walk through all mailboxes, one by one, if
> you want to look at the spam quarantaine. Why not add an option to
> show all at once? Especially useful in the beginning when monitoring
> for false positives.
The Spamquarantine is meant as a self-service portal for individual
mailboxes and depending on the setup can contain very much information,
(and sensitive information, which should only be looked at in limited
cases) - I would use the statistics or logs to get an overview about
More information about the pmg-devel