lock relay in zimbra support

[arisan]

how to configure zimbra to not work as relay, then I found that in non-work days is still sending and receiving mail

[uxbod]

Would you please explain in more detail what you are trying to achieve please

[arisan]

a test page on my smtp relay and said possible as you can see May be an open relay, as you can see below

Command:
smtp:farmedis.com.py smtp
220-wedmore.webserversystems.com ESMTP Exim 4.69 #1 Wed, 24 Mar 2010 10:36:01 -0500


May be an open relay.
0 seconds - Good on Connection time
0.842 seconds - Good on Transaction time
OK - 174.120.172.162 resolves to wedmore.webserversystems.com
OK - Reverse DNS matches SMTP Banner

[uxbod]

What have you set for the trusted networks in the Admin GUI or you can check using

su - zimbra
zmprov gs `zmhostname` zimbraMtaMyNetworks

Have you by any chance included the IP address of your router ?

[arisan]

[zimbra@mail ~]$ zmprov gs `zmhostname` zimbraMtaMyNetworks
# name mail.farmedis.com.py
zimbraMtaMyNetworks: 127.0.0.0/8 192.168.0.0/24

[uxbod]

Looks okay when I use Email Server Test - Online SMTP diagnostics tool - MxToolbox.

[jrefl5]

Originally Posted by arisan

[zimbra@mail ~]$ zmprov gs `zmhostname` zimbraMtaMyNetworks
# name mail.farmedis.com.py
zimbraMtaMyNetworks: 127.0.0.0/8 192.168.0.0/24

Is your router possibly at 192.168.0.1?
if so try specifying each IP that you want to be able to relay through the server

I use the following script if things don't appear right on my system.

#!/bin/bash
#  run this to reset Zimbra's Trusted networks back to:
# loopback               127.0.0.0/8
# mail server   10.168.30.60/32
# server2     10.168.30.7/32
# server3 10.168.30.22/32
# server4   10.168.30.5/32
#
# Never put in MyNetworks, all external bail will be treated as trusted i.e. "OPEN RELAY" !!!
# Firewall/router        10.168.30.1/32
#
# # #
# # #
# #     This should be run if Administrator console Server Configuration MTA Tab's
# #      MTA Trusted Networks reverts back to the values '127.0.0.0/8 10.168.30.0/24'
# #      otherwise we seem to act as an open relay for some reason (internal "owned" system?)
# # #  ME 2/1/2008
# # #     Reason we get treated as Open Relay is that all e-mail that arrives comes from either
# #     an external source ( identified to Zimbra as the Firewall 10.168.30.1 ) or from an
# #     internal source also on the same network 10.168.30.0/24 so we must identify the only allowed
# #     relay from servers.
# #       Only Zimbra, server2, server3, and server4 server are allowed to send e-mail through Zimbra to
# #     externam internet addresses.
# # #  ME 6/30/2008   Yes it took awhile for it to sink in.
# # #
#
# should be run as user zimbra
# su - zimbra
# change ServerName if run on a different zimbra server.
ServerName="zimbra.server.com"
# list current settings
zmprov gas -v | grep MyNetwork
# make the change
# zmprov modifyserver $ServerName zimbraMtaMyNetworks '127.0.0.0/8 10.168.30.60/32 10.168.30.1/32 10.168.30.7/32 10.168.30.22/32'
zmprov modifyserver $ServerName zimbraMtaMyNetworks '127.0.0.0/8 10.168.30.60/32 10.168.30.7/32 10.168.30.22/32'
# reset to correct postfix settings,
zmprov mcf +zimbraMtaRestriction reject_unlisted_recipient
zmprov mcf +zimbraMtaRestriction reject_non_fqn_hostname
zmprov mcf +zimbraMtaRestriction reject_non_fqn_sender
zmprov mcf +zimbraMtaRestriction "reject_rbl_client dnsbl.njabl.org"
zmprov mcf +zimbraMtaRestriction "reject_rbl_client cbl.abuseat.org"
zmprov mcf +zimbraMtaRestriction "reject_rbl_client bl.spamcop.net"
# Confirm change
zmprov gas -v | grep MyNetwork

[arisan]

if there is any problem, how I can change this modification?

[uxbod]

We do not know if there is a problem as you have not really told us what the issue is The relay check I performed said your server was not a open relay.

[arisan]

thank you very much for the clarification and patience I hope to help further with my purchase experiecia