1

Topic: Allow comma separated mail's if user disabled ?

Hello,

We have CRM system which send email's to users via comma separated method.
Something like <TO: "email1@myserver.me, email2@myserver.me, email3@myserver.me, ... emailN@myserver.me">

When email2@myserver.me is disable then system got an error:
"code":550,"message":"5.1.1 and none of the user received email.

How to change configuration to allow system send email in case of some of them disabled ?

----

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

2

Re: Allow comma separated mail's if user disabled ?

Any ideas ?

3

Re: Allow comma separated mail's if user disabled ?

Open file /etc/postfix/main.cf, find parameter "smtpd_recipient_restrictions" like below:

smtpd_recipient_restrictions =
    reject_non_fqdn_recipient
    reject_unlisted_recipient
    check_policy_service inet:...
    permit_mynetworks
    permit_sasl_authenticated
    reject_unauth_destination
    check_policy_service inet:...

Place "reject_unlisted_recipient" after "reject_unauth_destination":

smtpd_recipient_restrictions =
    reject_non_fqdn_recipient
    check_policy_service inet:...
    permit_mynetworks
    permit_sasl_authenticated
    reject_unauth_destination
    reject_unlisted_recipient
    check_policy_service inet:...

Then restart or reload postfix service.

4

Re: Allow comma separated mail's if user disabled ?

ZhangHuangbin wrote:

Open file /etc/postfix/main.cf, find parameter "smtpd_recipient_restrictions" like below:

smtpd_recipient_restrictions =
    reject_non_fqdn_recipient
    reject_unlisted_recipient
    check_policy_service inet:...
    permit_mynetworks
    permit_sasl_authenticated
    reject_unauth_destination
    check_policy_service inet:...

Place "reject_unlisted_recipient" after "reject_unauth_destination":

smtpd_recipient_restrictions =
    reject_non_fqdn_recipient
    check_policy_service inet:...
    permit_mynetworks
    permit_sasl_authenticated
    reject_unauth_destination
    reject_unlisted_recipient
    check_policy_service inet:...

Then restart or reload postfix service.

Dear ZhangHuangbin, thank you for you reply.
I've made as you told.
Here screenshot of my config.
I reboot my server and checked. The problem still exist.

Post's attachments

Screenshot_291.png
Screenshot_291.png 9.41 kb, file has never been downloaded. 

Screenshot_292.png
Screenshot_292.png 31.28 kb, 1 downloads since 2020-10-29 

You don't have the permssions to download the attachments of this post.

5

Re: Allow comma separated mail's if user disabled ?

Did you configure the MUA to send email with smtp authentication?
Please show us Postfix log lines related to this email.

6 (edited by koval.roma 2020-10-29 21:25:31)

Re: Allow comma separated mail's if user disabled ?

ZhangHuangbin wrote:

Did you configure the MUA to send email with smtp authentication?
Please show us Postfix log lines related to this email.

I send email from Thunderbird, where:
to: putted existing email,
cc: putted not existed email.

Here is Postfix log:
Oct 29 14:09:12 mail postfix/submission/smtpd[14271]: connect from ***HIDE_SENSITIVE_INFO***[***HIDE_SENSITIVE_INFO***]
Oct 29 14:09:12 mail postfix/submission/smtpd[14271]: Anonymous TLS connection established from ***HIDE_SENSITIVE_INFO***: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)
Oct 29 14:09:13 mail postfix/submission/smtpd[14271]: NOQUEUE: reject: RCPT from ***HIDE_SENSITIVE_INFO***: 550 5.1.1 <***HIDE_SENSITIVE_INFO***>: Recipient address rejected: User unknown in virtual mailbox table; from=<***HIDE_SENSITIVE_INFO***> to=<***HIDE_SENSITIVE_INFO***> proto=ESMTP helo=<***HIDE_SENSITIVE_INFO***>
Oct 29 14:09:17 mail postfix/submission/smtpd[14271]: disconnect from ***HIDE_SENSITIVE_INFO*** ehlo=2 starttls=1 auth=1 mail=1 rcpt=0/1 quit=1 commands=6/7

Then changed my configuration:
to: putted existing email,
cc: putted existing email.

Oct 29 14:11:18 mail postfix/submission/smtpd[14271]: connect from ***HIDE_SENSITIVE_INFO***
Oct 29 14:11:18 mail postfix/submission/smtpd[14271]: Anonymous TLS connection established from ***HIDE_SENSITIVE_INFO***: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)
Oct 29 14:11:18 mail postfix/submission/smtpd[14271]: E1CFD7C3089: client=***HIDE_SENSITIVE_INFO***, sasl_method=PLAIN, sasl_username=***HIDE_SENSITIVE_INFO***
Oct 29 14:11:19 mail postfix/cleanup[13952]: E1CFD7C3089: message-id=<***HIDE_SENSITIVE_INFO***>
Oct 29 14:11:19 mail postfix/qmgr[1794]: E1CFD7C3089: from=<***HIDE_SENSITIVE_INFO***>, size=2216, nrcpt=3 (queue active)
Oct 29 14:11:19 mail postfix/submission/smtpd[14271]: disconnect from ***HIDE_SENSITIVE_INFO*** ehlo=2 starttls=1 auth=1 mail=1 rcpt=1 data=1 quit=1 commands=8

In both cases used the same client with the same configuration.
Thunderbird uses StartTLS with Normal password auth.

7

Re: Allow comma separated mail's if user disabled ?

Try to update "smtpd_reject_unlisted_recipient = yes" in /etc/postfix/main.cf to "smtpd_reject_unlisted_recipient = no".

8

Re: Allow comma separated mail's if user disabled ?

ZhangHuangbin wrote:

Try to update "smtpd_reject_unlisted_recipient = yes" in /etc/postfix/main.cf to "smtpd_reject_unlisted_recipient = no".

Yes, this help. Thank you!

Do I need to leave this
"Place "reject_unlisted_recipient" after "reject_unauth_destination":" or I need to change as it was before ?