You need to figure out how to have your PDA work like a mail client where it will produce a login request.
Otherwise your only solution would be to turn of DNS checking for your Zimbra server.
You need to figure out how to have your PDA work like a mail client where it will produce a login request.
Otherwise your only solution would be to turn of DNS checking for your Zimbra server.
DNS checking is off on the server.
A weird thing occured. I managed to track down, why I couldn't send mail from my PDA. If I disable the "TLS authentication only" in the MTA tab then I can send to any outside address not only the domain. If I enable it then it comes back with relay access denied.
This is weird since it requires me to authenticate myself with username/password when sending (otherwise sending fails) but if I enable SSL on the PDA it cannot connect. WM6 does not have TLS provisions only SSL ones.
So I set the smtp to zimbraserver:465 and disabled SSL on the PDA and disabled TLS only on the server and it worked. Any ideas as to how this is possible? This doesn't mean that the host does not resolve, it just means that the SSL is not working properly.
The same thing occurs when using outlook and thunderbird. In Thunderbird I can enable SSL and SMTP works fine, under Outlook 2007 SSL does not work, only TLS.
Any ideas?
Last edited by Miklos Kalman; 03-01-2008 at 03:40 PM.
Back when I was testing this with 4.5.1 I had to put any external IP address into the MTA trusted networks to get it to work....this could have changed since then but I haven't done any further testing on it. I'll have to check this out since if that is true then that changes a few things.
That would be ZimbraMtaMyNetworks - Zimbra :: Wiki. Sound's like Bill is referring to the fact that you don't need to add every last IP of people who are connecting remotely. He just didn't elaborate on how the authenticated user capability simply needs to have your local interfaces listed. You used to have to add these manually, but now in 5.0.x we do some checking to make sure 128.0.0/8 stays in & the local interfaces are added on install, as well as harder to remove from the admin console accidentally. See Bug 17753 - validation of MTA related inputs : comment #25
Last edited by mmorse; 03-02-2008 at 12:11 AM.
-Mike Morse (MCode151)
ZCS-to-ZCS Migrations & Moves | Admin Tools & Tidbits » ZimbraBlog.com | ZimbraCommunity.com
I still think that your PDA is not trying to authenticate. The original log you sent looks like one server talking to another instead of a client connecting to authenticate.
Below is a log entry for a successful client to server conversation:
Mar 2 07:04:52 webmail postfix/smtpd[11488]: connect from h134.6.249.24.cable.mcls.cablerocket.net[24.249.6.134]
Mar 2 07:04:52 webmail postfix/smtpd[11488]: setting up TLS connection from h134.6.249.24.cable.mcls.cablerocket.net[24.249.6.134]
Mar 2 07:04:52 webmail postfix/smtpd[11488]: TLS connection established from h134.6.249.24.cable.mcls.cablerocket.net[24.249.6.134]: TLSv1 with cipher RC4-MD5 (128/128 bits)
Mar 2 07:04:52 webmail postfix/smtpd[11488]: 8951D2F19D: client=h134.6.249.24.cable.mcls.cablerocket.net[24.249.6.134], sasl_method=LOGIN, sasl_username=bill@brocknetworks.com
Mar 2 07:04:52 webmail postfix/cleanup[11491]: 8951D2F19D: message-id=<000001c87c61$8e324430$6401a8c0@brocknetworks.c om>
Mar 2 07:04:52 webmail postfix/qmgr[4638]: 8951D2F19D: from=<bill@brocknetworks.com>, size=1609, nrcpt=1 (queue active)
Mar 2 07:04:52 webmail postfix/smtpd[11488]: disconnect from h134.6.249.24.cable.mcls.cablerocket.net[24.249.6.134]
Mar 2 07:04:57 webmail postfix/smtpd[11537]: connect from localhost[127.0.0.1]
Mar 2 07:04:57 webmail postfix/smtpd[11537]: 36F8425A61: client=localhost[127.0.0.1]
Mar 2 07:04:57 webmail postfix/cleanup[11491]: 36F8425A61: message-id=<000001c87c61$8e324430$6401a8c0@brocknetworks.c om>
Mar 2 07:04:57 webmail postfix/smtp[11492]: 8951D2F19D: to=<bjbrock@allegiance.tv>, relay=127.0.0.1[127.0.0.1]:10024, delay=4.8, delays=0.1/0.01/0/4.6, dsn=2.0.0, status=sent (250 2.0.0 Ok: qu0 OK 4B/67-29664-88E9AC74)
Mar 2 07:05:08 webmail postfix/qmgr[4638]: 36F8425A61: removed
And why is it that Outlook cannot connect via SSL whereas Thunderbird can. Outlook needs TLS to work correctly and won't budge in SSL mode.
This is the same for my PDA (WM6), but there I cannot setup TLS only SSL or plain authentication. So if I want to send mail from my PDA I can only use Plain text authentication for the outgoing SMTP connection. In case of incoming WM6 allows the SSL. This is a very weird behavior don't you think?
I run both Outlook 2000 and 2003 and have no problem connecting using SSL over either port 25 or 465.
You're not checking the "Use encrypted Password" box in Outlook are you?
Can you post a more detailed log similar to the one I posted?
The first Log you posted clearly shows no login attempt.
There are currently 1 users browsing this thread. (0 members and 1 guests)