1

Topic: outgoing gets quarantined after 0.9.2

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.5.1
- Linux/BSD distribution name and version: Debain Jessie
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? no
- Related log if you're reporting an issue:
====
I have recently upgraded from 0.9.2 to 0.9.5.1 and apart from making the configuration changes as described in the upgrade notes nothing else has changed. But somewhere in the process going from 0.9.2 to 0.9.5.1 suddenly outgoing emails gets quarantined if mails have attached banned content. What have changed and where to fix this issue?

----

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

2

Re: outgoing gets quarantined after 0.9.2

There's one change in iRedMail upgrade tutorial impacts this. To fix it, please open Amavisd config file (/etc/amavis/conf.d/50-user on Debian/Ubuntu), find this line:

$policy_bank{'ORIGINATING'} = {
    ...
    #bypass_banned_checks_maps => [1],
    ...
};

Uncomment out the "bypass_banned_checks_maps" setting, then restart Amavisd service.

3

Re: outgoing gets quarantined after 0.9.2

I will try that option.

Question:
SASL authenticated has this content:
$policy_bank{'SASLBYPASS'} = {  # mail from submission and smtps ports
    bypass_spam_checks_maps   => [1],  # don't spam-check this mail
    bypass_banned_checks_maps => [1],  # don't banned-check this mail
    bypass_header_checks_maps => [1],  # don't header-check this mail
};

Should $policy_bank{'ORIGINATING'} not have a similar contents?

4

Re: outgoing gets quarantined after 0.9.2

Above does not work. From mail.log:

May 25 17:20:01 iredmail amavis[13093]: (13093-01) Blocked SPAM {DiscardedOutbound,Quarantined}, MYNETS LOCAL [192.168.2.79]:36216 <user@local.tld> -> <user@remote.tld>, quarantine: D_8DZoBMcV4l, Queue-ID: 60658120098, Message-ID: <20160525172000.4f4ce7fe@x.local.tld>, mail_id: D_8DZoBMcV4l, Hits: -, size: 3244, 114 ms

5

Re: outgoing gets quarantined after 0.9.2

mir wrote:

Should $policy_bank{'ORIGINATING'} not have a similar contents?

You can add them in ORIGINATING.
Note: SASLBYPASS is not enabled by default.

mir wrote:

Above does not work. From mail.log:
May 25 17:20:01 iredmail amavis[13093]: (13093-01) Blocked SPAM

This email is blocked due to spam, not banned file types (the reason in your first post).

6

Re: outgoing gets quarantined after 0.9.2

ZhangHuangbin wrote:

This email is blocked due to spam, not banned file types (the reason in your first post).

What reason what that?

But, why is outgoing mail scanned for spam? I do not want outgoing mail scanned in any way?

7

Re: outgoing gets quarantined after 0.9.2

From: http://www.iredmail.org/docs/upgrade.ir … ernal-user

Find $policy_bank{'ORIGINATING'} = { block, comment out forward_method line in the block:
  #forward_method => 'smtp:[127.0.0.1]:10027',

Should that not be:
Find $policy_bank{'ORIGINATING'} = { block, comment out forward_method line in the block:
  #forward_method => 'smtp:[127.0.0.1]:10026',

Nothing is configured to listen on port 10027?

8

Re: outgoing gets quarantined after 0.9.2

mir wrote:

But, why is outgoing mail scanned for spam? I do not want outgoing mail scanned in any way?

Fixed this problem by adding below to $policy_bank{"MYNETS"}

bypass_spam_checks_maps   => [1],  # don't spam-check this mail
bypass_banned_checks_maps => [1],  # don't banned-check this mail
bypass_header_checks_maps => [1],  # don't header-check this mail