External IP, Cant Send IMAP

[FastEddy760]

Hello All,

I want to send email from an external IP, roaming, Laptop. I can receive IMAP just fine. Sending from the web interface is also fine.

Client = OS X's Apple mail.app

I have searched the forums and read lots of similar posts, and the admin manual also.... But have not found the answer to my problem. Please point me in the right direction(s) and I will do the reading.

P.S. love the Zimbra app =]

[phoenix]

Are you saying that your IMAP connects to receive messages and that it won't deliver any mail? Does the message stay in your client? Are there any error messages in the client? Is there anything in the Zimbra logs? I'm afraid I know absolutely nothing about Apple stuff so I probably won't be much help.

[FastEddy760]

IMAP client receives - yes
Delivery fails, stays in client - yes
Error Message in client - no, none found, email remains in outbox

I downloaded Thunderbird for, hopefully, better logging....

BBIAF

Nothing in the Zimbra logs

[FastEddy760]

Telnet 465 ....

Welcome to Darwin!
mini01:~ root# telnet localhost 465
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
telnet: Unable to connect to remote host
mini01:~ root#

[bobby]

1. make sure you have smtp authentication enabled for the server

2. make sure you have authentication settings entered for smtp server in mail.app (or thunderbird) prefs

3. run "tail -f /var/log/zimbra.log" and "tail -f /opt/zimbra/log/zimbra.log" while you try to send mail



btw zimbra smtp currently only operates on 25 (not 465)

[FastEddy760]

1. smtp auth enabled, yes
2. auth settings for smtp for mail.app & thunderbird, yes

Ok, changed the defualt port of 465 to port 25 in the client(s). Not sure why 465 is labeled as default for SSL if it needs to be port 25 (in the client(s)).

Hrm, my provider, COX, is blocking port 25, so telnet times out to port 25.
My partner was able to send from his cable co., while using ssl.

3. The logs are clean for the send request, as in they never see the request. Which led to my discovery of blocked port 25 outbound from my SOHO.

Wild, how do I send from behind my provider, and why is the default port for SSL different than port 25 in my client(s)? Do you choose the port and then SSL does not care when yo uadjust to port 25?

Thanks for playing,
Eddy

[bobby]

Wild, how do I send from behind my provider,

in the admin UI, you can set the "Relay MTA for external delivery:" under the MTA tab for the server (or for global settings) to tell zimbra to send outbound mail via your isp's smtp server. if cox requires smtp auth you'll want to see the wiki page about outgoing smtp auth

and why is the default port for SSL different than port 25 in my client(s)?

i guess it's actually tls so the client just connects on the regular port then tells the server STLS (start tls)

[FastEddy760]

Okay, the provider mentioned in previous posts was a reference to my house, and not the datacenter. After a few telnets to port 25 from various hosts, I realized that COX blocks port 25 as mentioned. However they provide a box to send email through. So when in Rome, or behind COX's network, I must use their SMTP host to send. I guess this works as typically there would be a viable send option should port 25 be blocked. And at the least, I can use the web interface.

Thanks for the help.