Quote:
Originally Posted by marcmac  My friend, if you're getting different banners on port 25, you're connecting to different postfix instances.
ps auxww | grep postfix
kill -9 everything listed
su - zimbra
postfix start
Make sure you're not starting some system-default postfix on boot. |
Hi, My first post (not first search).
The problem (this one anyway) is SMTP AUTH. This thread matched all the way until here. But now, this message is wholly inacurate. I'm running the postfix server that comes with zimbra only and I get two banners.. one supports ehlo( internal ) the other does not (external via firewall). I've hacked quite a few things the past couple of days and this is my fourth iteration of the install.
So, if you take everything up to here it pretty much all applies to my existing configuration;
zmprov gs mail.domain.com |grep Auth
zimbraMtaAuthEnabled: TRUE
zimbraMtaAuthHost: mail.notthedomain.com
zimbraMtaAuthURL:
http://mail.notthedomain.com:81/service/soap/
zimbraMtaTlsAuthOnly: FALSE
zimbra@dev1l3:~$ zmprov gs mail.notthedomain.com |grep MailMode
zimbraMailMode: mixed
zimbra_url:
http://mail.domain.com:81/service/soap/
My other problem.. apache rewrites for my 81and444 zimbra engines .. one that work are proving rather elusive. hints..?? thread search hints?? help??..
Thank you very much for your time.
Randy
As a post-edit to my original above: The problem was the company firewall (CISCO) which utilises an "SMTP fixup" port setting which is rather limiting. Disable "fix up smtp port" solves the problem. However, it then adversises everything smtp can do which, of course, you must be sure to disallow at the actual smtp server proxying to your firewall. -rpp