1

Topic: Problem with blocked emails

==== Required information ====
- iRedMail version (check /etc/iredmail-release):  0.9.4
- Linux/BSD distribution name and version:  Ubuntu 14.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- Related log if you're reporting an issue:
====

Sometimes my server blocks content with virus attachment...and the mailer daemon tries to send an email to the email account that tryed to send that blocked email. The problem is that the sender is impersonating an inexistent account from a real domain. And for this reason my server ip was listed in some blacklist email servers.

How do I resolv this blocked emails problem?

----

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

2

Re: Problem with blocked emails

Search Amavisd config file under /etc/amavis/conf.d/, if you see any "warnvirussender", set it to 0 to disable this behaviour.

3

Re: Problem with blocked emails

I didn't find this "warnvirussender" in any files under  /etc/amavis/conf.d/

4

Re: Problem with blocked emails

Try to search 'warn' in Amavisd config file, any parameters?

5

Re: Problem with blocked emails

I found in 50-user

$policy_bank{'ORIGINATING'} = {  # mail supposedly originating from our users
    originating => 1,  # declare that mail was submitted by our smtp client
    allow_disclaimers => 1,  # enables disclaimer insertion if available

    # notify administrator of locally originating malware
    virus_admin_maps => ["root\@$mydomain"],
    spam_admin_maps  => [],
    bad_header_admin_maps => [],
    banned_admin_maps => ["root\@$mydomain"],
    warnbadhsender   => 1,
    warnbannedsender => 1,
  ......

Should  both set to 0?

6

Re: Problem with blocked emails

*) "warnbadhsender", is "warn bad-header sender" (email with bad mail headers)
*) "warnbannedsender", is "warn banned file type sender" (email with banned file type in attachment)

In Amavisd-new-2.6.4 and earlier versions, you can use "warnvirussender" parameter, but it's retired since Amavisd-2.6.5.

According to ChangeLog of Amavisd-2.6.5: https://www.amavis.org/release-notes.txt

- retired often misused settings $warnvirussender and $warnspamsender
  (but kept marginally useful $warnbannedsender, $warnbadhsender, and their
  parent %warnsender_by_ccat). To bounce or reject viruses and spam use
  D_REJECT and D_BOUNCE settings for corresponding $final_*_destiny. It
  is no longer supported to both deliver (D_PASS) a virus or spam message
  while also sending a notification to sender. Both retired variables are
  still declared for compatibility with old config files, but their value
  is ignored. An attempt to set their value to a non-default value produces
  a warning.

So you should set "$final_virus_destiny = D_DISCARD;" (not set inside any policy_bank block). And this is default setting in iRedMail.

7

Re: Problem with blocked emails

At least I want that this emails not to be blocked but marked as SPAM.

8

Re: Problem with blocked emails

noob wrote:

At least I want that this emails not to be blocked but marked as SPAM.

I'm confused here, you want to mark VIRUS as SPAM?

9

Re: Problem with blocked emails

If is not possible to stop mailer daemon to send those warn emails...then yes, i would like mark VIRUS as SPAM.