Ticket #48 (assigned enhancement)

Opened 6 years ago

Last modified 4 years ago

Add hierarchical banned file attachment lists

Reported by: rjl Owned by: rjl
Priority: normal Milestone: 1.1.0
Component: amavisd-maia Version: 1.0.0 RC5
Severity: normal Keywords: hierarchical banned file attachment pattern regexp regular expression
Cc:

Description

Currently Maia (or rather amavisd-new) only supports a single global list of regular expressions for matching banned file attachments. Ideally, this should be handled on a hierarchical basis--system-wide, domain-wide, and finally per-user. The actual list of patterns to be used for a given user should be the union of these three pattern lists, combined into a compiled regular expression at runtime. The settings.php and domainsettings.php pages would then let users and administrators maintain their pattern lists.

Note: I've already implemented this for a private client who has agreed to release the code at some point in the future for use in the open source Maia Mailguard project.

Change History

Changed 4 years ago by rjl

  • patch set to 0
  • milestone changed from 1.1.0 to 1.0.2

Changed 4 years ago by rjl

  • status changed from new to assigned

Changed 4 years ago by rjl

For better efficiency, this feature should be implemented with/after #377, which adds support for the Regexp::Assemble module.

Changed 4 years ago by dmorton

I just had a private client request this too...

Changed 4 years ago by dmorton

  • milestone changed from 1.0.2 to 1.1.0

moving to 1.1 milestone, we can always backport it if needed.

Changed 4 years ago by anonymous

Hi,

Is there anyway that we could get some help with adding hierarchical banned file attachment's to MAIA sooner rather than later. We are considering the product in an ISP environment and this would most definatley be a requirement.

Regards

Vaughan

Replying to rjl: > Currently Maia (or rather amavisd-new) only supports a single global list of regular expressions for matching banned file attachments. Ideally, this should be handled on a hierarchical basis--system-wide, domain-wide, and finally per-user. The actual list of patterns to be used for a given user should be the union of these three pattern lists, combined into a compiled regular expression at runtime. The settings.php and domainsettings.php pages would then let users and administrators maintain their pattern lists. > > Note: I've already implemented this for a private client who has agreed to release the code at some point in the future for use in the open source Maia Mailguard project.

Note: See TracTickets for help on using tickets.