You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, download files, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!
If you have any problems with the registration process or your account login, please contact contact us.
Using the Q on Sprint's network, I can send one email per session from outlook via my university's email servers. If I attempt to send another email I get the standard "Check that you have coverage, etc." error message. If I kill outlook and restart it, it will send the messages that I had in my outbox. However after sending the ones from the previous session, I can't send mail again for the new session until I kill outlook and start it again.
I've noticed that if I change the outgoing server address from email.xyz.edu to email.xyz.edu:25 it will send mail again once. I either have to restart outlook or change the outgoing server address again to get it to send mail after that.
I've read the thread about using Sprint's smtp servers, but I figured that was a fix if you could not send mail at all using your Q. I can send mail, but only for the first time it connects to the outgoing server. Any attempts thereafter outlook returns that standard error about sending messages failed. Again, killing outlook and restarting it will allow me to send mail one time only.
I doubt it is an issue with the mail server, because after I kill outlook on the Q and start it again I can send mail immediately, once. The issue reproduces itself every time I use outlook to send messages.
From the error message you are getting it sounds like the Q is unable to reach the outgoing email server more than once per session. This could be a DNS issue. Have you tried replacing email.xyz.edu with the IP address of email.xyz.edu? Anyway, not sure why the DNS lookup would fail the second time but not the first, but I'm just trying to throw out some ideas.
If the Q is actually making the connection, then it would be difficult to troubleshoot this issue without being able to monitor the Q's connection to the email server at the email server to see exactly what commands it is sending to cause the error.
Either way, the Sprint SMTP fix will work around the issue.
Figured it out... Even though there is a check box for "Use the same username and password" under the outgoing server settings I had to manually specify my username and password for my smtp server. Sounds like the Q expected the connection to the smtp server to not require authentication every time it sent mail, however the email server did.