View source for Prevent spam problem with Zimbra server

<yambe:breadcrumb>Zimbra_server_configuration|Zimbra</yambe:breadcrumb>
=Prevent spam problem with Zimbra server=

Often Zimbra server is used as relay to send bulk SPAM messages.  This can be done if at least one of the accounts on server is compromised.  An attacker can use compromised account to login into SMTP server over SSL/TLS and then send SPAM messages.  These spam messages can be sent from any email address to any other email address.  Thus, detecting which accounts have been compromised is tricky. 


==Analyze log file to detect compromised account==
One very quick way of detecting the attack source and also compromised login is to analyze /var/log/zimbra.log file.  Use steps suggested at [[Get count of IP addresses in a log file arranged in descending order of frequency]] to get IPs which are contacting Zimbra server to often.  Some of these IPs could belong to attacker and others would belong to popular email servers such as Gmail, Yahoo, etc. which the compromised server might be contacting to send SPAM.  For first 10-20 top IPs use following command to see name of user logged in:
<pre>
grep '<public-ip>' zimbra.log | grep 'sasl_user' | head -15
</pre>
If there is no output then perhaps the IP belongs to Google, Yahoo, etc. popular destinations.  This can be verified by using http://www.whatismyipaddress.com/ip/<public-IP> facility to determine owner of particular IP.

If the output contains name of user authenticated and there is no good reason for one single user to send that many emails then perhaps the listed account is compromised.  Such compromised accounts can be disabled or their password can be reset to prevent further abuse.  This should be done for all top IPs as more than one account might have been compromised. 

Note that attackers send multiple phising emails to all users on the same domain hoping that some of them would also reply with their password.  This causes multiple accounts to get compromised in short time.


==Enable sender policy to ensure that login user name matches from address in email==

===Enabling sender policy to ensure that login user name matches from address in email in Zimbra 8.0 series===

To enable sender policy to for preventing abuse in Zimbra 8.0 use following steps:
# Edit file '<tt>/opt/zimbra/conf/zmconfigd.cf</tt>' and append line
#:<pre>
#::POSTCONF smtpd_sender_login_maps       FILE postfix_sender_login_maps.cf
#:</pre>
#::This line must be appended immediately after line '<tt>POSTCONF smtpd_sender_restrictions FILE zmconfigd/smtpd_sender_restrictions.cf</tt>'
#::'''Please ensure that there is tab at beginning of new appended line
#Edit file '<tt>/opt/zimbra/conf/zmconfigd/smtpd_sender_restrictions.cf</tt>' and insert following line at top of the file
#:<pre>
#::reject_authenticated_sender_login_mismatch
#:</pre>
#Edit/create file '<tt>/opt/zimbra/conf/postfix_sender_login_maps.cf</tt>' with following contents:
#:<pre>
#::hash:/opt/zimbra/conf/exceptions-db ldap:/opt/zimbra/conf/ldap-restricrelay.cf
#:</pre>
#Create file '<tt>/opt/zimbra/conf/exceptions-db</tt>' with email ID and username pairs where given user can send emails with listed email address
#:<pre>
#::johndoe@otherdomain.com admin
#::janedoe@otherdomain.com admin
#:</pre>
#Create db file by using:
#:<pre>
#::cd /opt/zimbra/conf
#::/opt/zimbra/postfix/sbin/postmap exceptions-db
#:</pre>
#::Thist must be done everytime '<tt>/opt/zimbra/conf/exceptions-db</tt>' file is modified for changes to take effect.  Just running postmap is enough and there is no need to reload/restart Zimbra for new settings to take effect
#Get values of 'server_host' and 'bind_pw' using:
#:<pre>
#::grep server_host /opt/zimbra/conf/ldap-vam.cf
#::grep bind_pw /opt/zimbra/conf/ldap-vam.cf
#:</pre>
#Edit/create file '<tt>/opt/zimbra/conf/ldap-restricrelay.cf</tt>' with following contents:
#:<pre>
#::server_host = ldap://srvXX.company.com:389 
#::server_port = 389 
#::search_base = 
#::query_filter = (&(|(uid=%s)(zimbraMailDeliveryAddress=%s)(zimbraMailAlias=%s)(zimbraMailCatchAllAddress=%s))(zimbraMailStatus=enabled)) 
#::result_attribute = uid,zimbraMailDeliveryAddress,zimbraMailForwardingAddress,zimbraPrefMailForwardingAddress,zimbraMailCatchAllForwardingAddress
#::version = 3
#::start_tls = yes
#::tls_ca_cert_dir = /opt/zimbra/conf/ca
#::bind = yes 
#::bind_dn = uid=zmpostfix,cn=appaccts,cn=zimbra
#::bind_pw = XXXXXXXXXX
#::timeout = 30
#:</pre>
#::Here replace server_host and bind_pw with values found in previous step.  Note that if you are using external LDAP for authentication then values in server_host, server_port, search_base, bind_dn, bind_pw, etc. should reflect external LDAP server values and not values found in previous step.
#Set correct permissions on all new files using:
#:<pre>
#::cd /opt/zimbra/conf
#::chown zimbra: postfix_sender_* exceptions-db* ldap-restricrelay.cf
#:</pre>
#Run following command as Zimbra user for new settings to take effect
#:<pre>
#::zmmtactl restart
#:</pre>

These steps have been learned from https://wiki.zimbra.com/wiki/Enforcing_a_match_between_the_FROM_address_and_the_sasl_username


===Enabling sender policy to ensure that login user name matches from address in email in Zimbra 8.5 series===

Refer https://wiki.zimbra.com/wiki/Enforcing_a_match_between_FROM_address_and_sasl_username_8.5


===Troubleshooting sender policy configured===

If sender policy configured is not working properly monitor '<tt>/var/log/zimbra.log</tt>' using tail command to see possible reasons why settings are not working.


===Verifying sender policy configuration===
It is important to verify sender policy configuration.  Following tests are recommended
*[[Testing external emails are received without forcing authentication]]
*[[Testing intra-domain emails are received without forcing authentication]]
*[[Testing intra-domain emails are working after SMTP authentication]]
*[[Testing external emails are being sent after SMTP authentication]]


==Resolving sender not allowed issues after implementing sender email and authenticated user name match==

It is possible that server might not allow user 'saurabh' authenticated with username 'saurabh' to send emails from domain saurabh@companydomain.com.  This can be tried to be resolved partially by authenticating with full email address 'saurabh@companydomain.com' and not just with user-name.  However propagating this change to all already configured email clients / mobiles might be an issue.  To work around this problem a list of all company email IDs and the corresponding usernames can be added to /opt/zimbra/conf/exceptions-db file.  This would allow user 'saurabh' to send emails from saurabh@companydomain.com based on exceptions.  To achieve this use following steps:
#List all Zimbra users using '<tt>zmprov -l gaa</tt>' command.  A more exhaustive list which also includes all aliases can be obtained using:
#:<pre>
#::/opt/zimbra/openldap/bin/ldapsearch -LLL -x -D"`/opt/zimbra/bin/zmlocalconfig -s zimbra_ldap_userdn | \
#::       awk '{print $3}'`" -w"`/opt/zimbra/bin/zmlocalconfig -s zimbra_ldap_password | \
#::       awk '{print $3}'`" -H `/opt/zimbra/bin/zmlocalconfig ldap_url | \
#::       awk '{print $3}'` $* | \
#::       grep ^mail | \
#::       awk '{print $2}' | \
#::       sort > zimbra_recipients.list
#:</pre>
#Install erlang on server using '<tt>yum -y install erlang</tt>'
#Create convert.erl file with following erlang program:
#:<pre>
#::-module(convert).
#::-compile(export_all).
#::
#::main() ->
#::   {ok, Data1} = file:read_file("zimra_recipients.list"),
#::   Data2=binary_to_list(Data1),
#::   Email_list1=string:tokens(Data2, "\n"),
#::   Output_lines1=lists:map(fun(Email1) ->
#::	   Username=hd(string:tokens(Email1, "@")),
#::	   lists:flatten(io_lib:format("~s ~s", [Email1, Username]))
#::	end,
#::	Email_list1),
#::%%   Output_lines2=lists:map(fun(Email1) ->
#::%%	   Username=hd(string:tokens(Email1, "@")),
#::%%	   lists:flatten(io_lib:format("~s@company-other-domain.com ~s", [Username, Username]))
#::%%	end,
#::%%	Email_list1),
#::   Output_data=string:join(Output_lines1, "\n"),
#::   file:write_file("exceptions-db", Output_data),
#::   ok.
#:</pre>
#Compile and run this program using:
#:<pre>
#::erlc convert.erl
#::erl -noshell -s convert main -s init stop
#:</pre>
#Replace or append the exceptions-db file created by running this program with previous exceptions-db file
#Run postmap again for new exceptions to take effect

More zmprov commands can be learned from https://wiki.zimbra.com/wiki/Zmprov_Examples    
Technique of exporting all email IDs including aliases learned from https://wiki.zimbra.com/wiki/Exporting_all_addresses



<yambe:breadcrumb>Zimbra_server_configuration|Zimbra</yambe:breadcrumb>