1

Topic: Remove option to attach anything to a single email user

==== Required information ====
- iRedMail version: 0.8.7
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Linux/BSD distribution name and version: Ubuntu 12.04.3 LTS 64-bit
- Related log if you're reporting an issue:
====

Hi, is it possible to remove the option to attach or restrict one user to attach anything to his/her emails?

Thanks!

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Remove option to attach anything to a single email user

You can try to implement this with Amavisd (with parameter "$banned_filename_re ="), ban all file types.

3

Re: Remove option to attach anything to a single email user

Thanks for the reply Zhang but how to implement it exactly?

When I go to /etc/amavis/conf.d/ i see alot of configuration files. Where will I append the parameter.

ZhangHuangbin wrote:

You can try to implement this with Amavisd (with parameter "$banned_filename_re ="), ban all file types.

4

Re: Remove option to attach anything to a single email user

*) On Debian/Ubuntu, you can always override Amavisd default settings in /etc/amavis/conf.d/50-user. Check our short comment here: http://www.iredmail.org/docs/file.locat … ml#amavisd

*) Check Amavisd official document to find examples of how to set '$banned_filename_re'.

5

Re: Remove option to attach anything to a single email user

Do I have to set any ldap attribute to that user so he is the only one affected by the banning of all attachments?

ZhangHuangbin wrote:

*) On Debian/Ubuntu, you can always override Amavisd default settings in /etc/amavis/conf.d/50-user. Check our short comment here: http://www.iredmail.org/docs/file.locat … ml#amavisd

*) Check Amavisd official document to find examples of how to set '$banned_filename_re'.

6

Re: Remove option to attach anything to a single email user

freeda.suing wrote:

Do I have to set any ldap attribute to that user so he is the only one affected by the banning of all attachments?

LDAP integration will be dropped in upcoming iRedMail-0.9.0, so, for per-user restriction, I suggest you enable policy lookup in Amavisd, then you can manage it in SQL table "amavisd.policy".

Reference:
- http://www.iredmail.org/docs/amavisd.pe … ookup.html
- http://www200.pair.com/mecham/spam/bypassing.html#8

By the way, upcoming iRedAdmin-Pro release supports manage per-recipient policy, although Amavisd supports query per-recipient 'banned_rulenames' from policy table, but iRedAdmin-Pro doesn't manage its value yet. Will try to improve it in iRedAdmin-Pro in the future.