SMTP Relay

[alohrer]

Sounds good. I'll try that tonight. That may be to problem is that I didn't have the relayhost set in the admin console so when postfix was reloaded it took the value from the zimbra config. Anyway, I'll let you know. Thanks for your help.

[alohrer]

Well, I'm still getting an error on this. It's still telling me I need authentication like one of my above posts. Let me know if there is anything else I can try.

[KevinH]

Originally Posted by alohrer

Well, I'm still getting an error on this. It's still telling me I need authentication like one of my above posts. Let me know if there is anything else I can try.

Were you able to get the config file to keep your value that was set in the admin UI? Is the error the exact same in /var/log/zimbra.log when you test this?

[alohrer]

I did a tail of the main.cf after reloading postfix. I'll check the logs tonight and let you know. Also, I was wondering, I can't connect to the admin UI outside of my LAN. Is this setup in the iptables for zimbra? It'd be nice if I could connect to the admin outside. Still learning the more advanced functions of Linux right now but I'm still enjoying the product. If I can get past this hurdle, there's no doubt in my mind that I'll be implementing this. I'm just afraid that my ISP is going to require that I authenticate with their SMTP server to send mail outside my domain.

[alohrer]

Wow. Well, I got it to work.

So here is the tail of my main.cf file.

content_filter = smtp-amavis:[127.0.0.1]:10024
smtpd_sasl_auth_enable = yes
smtpd_tls_auth_only = yes
disable_dns_lookups = no
message_size_limit = 10240000
relayhost =
smtp_sasl_password_maps = /opt/zimbra/conf/relay_password

I have my relay on the relay_password set to mailrelay.host.com username: password.

The ONLY thing that seemed to get it to work was in the Admin UI, I put the IP address of the server and not the hostname. I'm not sure why this works but it is. Just wanted to pass this along with you. You may want to keep this for future reference just in case someone else has this type of problem again.

~A

[KevinH]

Originally Posted by alohrer

The ONLY thing that seemed to get it to work was in the Admin UI, I put the IP address of the server and not the hostname. I'm not sure why this works but it is. Just wanted to pass this along with you. You may want to keep this for future reference just in case someone else has this type of problem again.

Glad you got it working.

Did you check to see if you could resove that hostname via DNS on the server?

[alohrer]

That was the weird thing. I was able to do resolve the hostname. I'll double check. This is a testing server that is run locally. It may be different in a the production environment I'm planning on deploying to later. I'm hoping to get this in by end of this year or beginning of next year.

[demanl]

...this solution worked great for me.... ....thanks...

Originally Posted by anand

Haven't tested, but this should do it.

Suppose your ISP relay host is "mailrelay.example.com" and the user
name and password to use there is "user" and "password" respectively.

Enable SMTP authentication on outbound messages:

  $ postconf -e smtp_sasl_auth_enable=yes

Create a file text file mapping which name/password should be used for
which given outbound destination. This file can contain multiple
lines.

$ echo mailrelay.example.com user:password > /opt/zimbra/conf/relay_password

Create a postfix lookup table from this text file:

$ postmap /opt/zimbra/conf/relay_password

Test that the map is okay and that the user: password pair is returned.

$ postmap -q mailrelay.example.com /opt/zimbra/conf/relay_password
user:password

Make postfix use this:

$ postconf -e smtp_sasl_password_maps=hash:/opt/zimbra/conf/relay_password
$ postfix reload

reload should do it - in this case no stop/start should be needed.

Also take a look at all the other smtp_sasl config options in
postfix documentation, starting at.

http://www.postfix.org/postconf.5.ht...sl_auth_enable

Beware of smtpd_ vs smtp_ sasl options. For mail being sent out via
SMTP, you care about the latter. smtpd_sasl_* are used for mail client
authentication, and the zimbra install already sets those up.

[brianj]

Hi, All,

I'd been fighting with this for over a week or so and kept getting the following errors in my /var/log/zimbra.log file:

(Authentication failed: cannot SASL authenticate to server smtp.sbc.mail.yahoo4.akadns.net[68.142.229.41]: no mechanism available)

Finally, I stumbled over the magic incantation for Google and found the following at http://www.postfix.org/SASL_README.html#debugging :

Note: some SMTP servers support PLAIN or LOGIN authentication only. By default, the Postfix SMTP client does not use authentication methods that send plaintext passwords, and defers delivery with the following error message: "Authentication failed: cannot SASL authenticate to server". To enable plaintext authentication specify, for example:

/etc/postfix/main.cf:
smtp_sasl_security_options = noanonymous

Once I added smtp_sasl_security_options = noanonymous , outbound mail started working and I was finally able to enjoy a hard-earned single malt scotch.

Hopefully, this will help someone else.

Brian

[nick]

Hi, I've been trying to make the steps above work (on an Intel Mac, if that matters), and I get:

Apr 15 21:53:22 macmini postfix/smtp[14473]: fatal: open database /opt/zimbra/conf/relay_password.db: Invalid argument

errors in my log each time I try to send a message. Any ideas what could be causing that error? The 'postmap -q' test command works fine.

I'm completely stumped. I was able to send mail ok when I was using a different SMTP server.

thanks,
-Nick