Daily only Spamreport for one main address and many aliases

H

hkais

Well-Known Member
Feb 3, 2020
32
1
48
45
Hi there,

i am having a test setup of the mail gateway. Sadly I cannot identify how I can tell mail gateway to report only n times a day a summarized spam report

Right now I get each spam e-mail-address as individual mail with the issue, that now of course I get it classified, but still i have to process each mail individually and delete it from the mailbox.

[updated]
Means I am having a main e-mail address (e.g. technical mails) and many alternative mail addresses (alias e-mail addresses). Now the spam filter is collecting this mail addresses individually in a quarantine mail. So assume you have many it-systems and per system different user groups to manage you come quickly around multiple 100er e-mail address aliases. But in fact the admins do not require for each of this e-mail address ONE quarantine mail, they would like to have ONE quaranteine for ALL e-mail aliases.

I would like to have a configurable somehomw the way of handling mail e-mail addresses with the corresponding aliases, so it would reduce the amount of quarantaine mails massively...

How can I achieve this with mail gateway?
 
Last edited:
This is the default setting - if you enable spam-report each of your users that gets a mail put in quarantine (usually due to it being considered spam by SpamAssassin) - will get a mail with a link to their quarantine where they can manage their mails.
See:
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_spamdetector_quarantine

please share logs/settings/any modifications you made - because currently I don't see how this can happen.
 
Hi Stoiko,
sorry I was not clear enough.

We have a main e-mail and alias e-mail addresses. Now all alias e-mail addresses get also a daily notification.
Which is odd especially on technical e-mail addresses which generate a lot of work.

So my clearer question shall be, how can i define a main e-mail address to which the quarantine is getting sent and the aliases are summarized underneath this main e-mail address.
This alias E-mail-addresses can be the same domain but mostly it is from different domains.

Ideally the aliases are configurable via UI, but they shall be available to provide the alias table via commandline so we could synchronize them automatically from the MTAs
 
Last edited:
hi there,
no hints from the community for my named issue?

This issue is the last feature which I could not find to get rid of a commercial vendor... Would reakly like to switch to proxmox here.
 
hkais said:
So my clearer question shall be, how can i define a main e-mail address to which the quarantine is getting sent and the aliases are summarized underneath this main e-mail address.
Click to expand...
This should be doable, if you have configured an LDAP profile and all aliases are stored in LDAP.

otherwise it's currently not possible to group e-mail-addresses for the spam-reports - see https://bugzilla.proxmox.com/show_bug.cgi?id=2629
(it's not requested often, so it's not high on our priority list)

I hope this helps!
 
SteveITS said:
Just so I understand, one user@example.com with three aliases (alias1@example.com, etc.) would receive up to four daily reports? That would be a blocker for us as well.
Click to expand...
yes, right now we have exactly this behavior. The issue is, that the technical e-mails are often having far more aliases than 3 and each e-mail address is having an own spam report.

Maybe we do something totally wrong?

[internal MTAs] <-> [our edge MTA with ldap and the mappings of aliases2mailboxes] <-> [PMG without ldap integration]

right now it reports for all received e-mail addresses a quarantine.
Based on your reply I rechecked the UI and found that it is possible to map the aliases via ldap. We intentionally did not integrate ldap to PMG to avoid HA dependencies to a external resource (LDAP)

So the first question would be, can we provide the user2aliases mapping in a way that the online LDAP-HA requirement for the PMG is not required?
E.g. via a generated file, which we generate once a night. Or alternatively does PMG support to replicate the LDAP locally to have it as a independent node from the edge or internal MTAs?
 
hkais said:
. We intentionally did not integrate ldap to PMG to avoid HA dependencies to a external resource (LDAP)
Click to expand...
PMG caches the LDAP lookups and aliases - it refreshes that cache with the pmg-hourly.timer (and associated service) once per hour.

from a quick look it should keep the old data in case LDAP is not reachable for the resync.

I'd suggest to simply try integrating it (in a test machine), and to see what happens when the LDAP is not reachable for a while

I hope this helps!
 
okay thank you will go this approach.
Do you maybe have a doc/tutorial to review how to configure the LDAP integration for the aliases?

Anyway is there a different option to replicate the mailbox2alias mappings to PMG without coupling to LDAP?
So in the case LDAP approach fails, we could implement a replication as planB
 
Last edited:
You must log in or register to reply here.
Top Bottom