Checking authorization from local nodes

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
Advanced member
Advanced member
Posts: 95
Joined: Sat Sep 13, 2014 12:50 am

Checking authorization from local nodes

Postby GlooM » Fri May 29, 2020 8:27 am


On one of our third-party services, the script that sends out reports to users broke down. As a result, spam was sent to users mailboxes. When I blocked the mailbox used for sending reports, spam did not stop being sent until the mailing script itself was disabled. The script was able to send mail via blocked account.

The log contains information about authorization refusal.

May 29 06:25:38 mail saslauthd[15664]: auth_zimbra: auth failed: authentication failed for []
May 29 06:25:38 mail saslauthd[15664]: do_auth : auth failure: [] [service=smtp] [] [mech=zimbra] [reason=Unknown]
May 29 06:25:38 mail postfix/smtpd[26184]: warning: unknown[]: SASL login authentication failed: authentication failure

But the sending occurred

As I understand it, the mail has been sent because the sender node belongs to the internal LAN address (MYNETWORKS RULE)

May 29 06:25:37 mail postfix/postscreen[17173]: CONNECT from []:63627 to []:25
May 29 06:25:37 mail postfix/postscreen[17173]: WHITELISTED []:63627

It turns out that any unauthorized node can send spam if it is connected from "MYNETWORK" subnet?
How can I prevent sending from unauthorized users?

smtpd_sender_restrictions = check_sender_access regexp:/opt/zimbra/common/conf/, permit_mynetworks, permit_sasl_authenticated, permit_tls_clientcerts, check_sender_access regexp:/opt/zimbra/common/conf/tag_as_foreig

As I understand it rule "permit_mynetworks" will be processed earlier than the rule "permit_sasl_authenticated". How to change the processing order? Will it be enough to just edit it manually /opt/zimbra/common/conf ?

Return to “Administrators”

Who is online

Users browsing this forum: No registered users and 12 guests