Problems with port 25

[dajwalia]

I did not start a new thread because the exact same issue is being discussed here.

I already tried telnetting on port 25 and it can't connect there.

zmcontrol status has postfix and mta not running.

netstat -na | grep 25 when zimbra is stopped does not return anything listening on port 25.

I have tried postfix start but that does not start postfix.

Here is excerpt from zimbra.log
-------------------------------------------
Sep 22 15:28:12 zimbra zimbramon[14141]: 14141:info: 2006-09-22 15:28:01, STATUS: zimbra.trivenidigital.com: ldap: Running
Sep 22 15:28:12 zimbra zimbramon[14141]: 14141:info: 2006-09-22 15:28:01, STATUS: zimbra.trivenidigital.com: logger: Running
Sep 22 15:28:12 zimbra zimbramon[14141]: 14141:info: 2006-09-22 15:28:01, STATUS: zimbra.trivenidigital.com: mailbox: Running
Sep 22 15:28:12 zimbra zimbramon[14141]: 14141:info: 2006-09-22 15:28:01, STATUS: zimbra.trivenidigital.com: mta: Stopped
Sep 22 15:28:12 zimbra zimbramon[14141]: 14141:info: 2006-09-22 15:28:01, STATUS: zimbra.trivenidigital.com: snmp: Running
Sep 22 15:28:30 zimbra postfix/postfix-script: fatal: the Postfix mail system is not running
Sep 22 19:28:40 zimbra postfix/postqueue[14483]: fatal: Queue report unavailable - mail system is down
Sep 22 15:29:17 zimbra postfix/postfix-script: warning: not owned by root: /opt/zimbra/postfix-2.2.9/conf/main.cf
Sep 22 15:29:17 zimbra postfix/postfix-script: starting the Postfix mail system
Sep 22 15:29:17 zimbra postfix/master[14909]: fatal: bind 0.0.0.0 port 25: Address already in use
-------------------------------

[marcmac]

Sep 22 15:29:17 zimbra postfix/master[14909]: fatal: bind 0.0.0.0 port 25: Address already in use

Shut down sendmail, or whatever is running on port 25.

[dajwalia]

My installation is RHEL and I did not select sendmail while installing the OS. Infact I chose bare minimum compnents.

What else should be causing this ? Let me explain my issue in detail and you guys would have a clearer picture.

We are already having Exchange 2003 in our environment as our mail server. Purpose of Zimbra is to function as Calendar Server only (and send email notifications through my regular Exchange 2003 for meetings and appointments).

How should my MTA setting look like? I am in a test environment and do not mind starting it all over again in regards to zimbra installation and/or RHEL4 .

Thanks all for your replies,
-Dhaval

[brian]

I tend to prefer

 lsof -i TCP:25

as it will give you the command, process id and user of the process bound to that port.

[Klug]

Originally Posted by dajwalia

My installation is RHEL and I did not select sendmail while installing the OS. Infact I chose bare minimum compnents.

I think it got itself installed anyway.

Try : /etc/init.d/sendmail stop

Then either delete the full sendmail package or just the /etc/init.d/sendmail file (this way sendmail won't start automatically after a reboot).

Originally Posted by dajwalia

We are already having Exchange 2003 in our environment as our mail server. Purpose of Zimbra is to function as Calendar Server only (and send email notifications through my regular Exchange 2003 for meetings and appointments).

Could you be a bit more clear on that one ?
If you have Exchange, why not using it's own Calendar ?
If you setup Zimbra, why not removing the Exchange setup ?

[dajwalia]

I reinstalled the Zimbra Setup on a completely new machine, and everything seems to be getting in place.

Thanks folks for all your replies so far.

Regarding Why not using Exchange's Calendar is that our organization has mixed clients as far as OS are concerned and Mail clients too. We have been comfortable with Exchange for emails since we are using it for a long time now (8+ years).

Zimbra's web access works exactly the same across any browser. Exchange Outlook Web Access does not. And one more thing from design of OWA I did not like is that the calendar gets updated from client only. Means if a user does not log on for 10 days, his calendar will not get updated with all the propsed meetings, or something to that effect.

[LowWalker]

I have an install of centos 5.2 x64 with zimbra 5.0.14, I ran in to issues with almost the exact same errors. Using this and a couple of similar threads I found that when installing fetchmail, it also installs exim... exim is what was hosing up my MTA. I found it after pulling off zimbra and then checking what was on port 25.

Thanks for the help, just wanted to share a specific because the issue was kind of wonky.