AT&T 8525 - can't send with IMAP account

Home | NewsGroups | Search | About

Lost Password?

microsoft.public.pocketpc.activesync

get this group's latest topics as an RSS feed

add this group's latest topics to your My MSN content

add this group's latest topics to your My Yahoo content

Subject

Author

Date

AT&T 8525 - can't send with IMAP account

<cmcgroarty

09-21-2007

Re: AT&T 8525 - can't send with IMAP account

Todd Allcock

09-21-2007

Re: AT&T 8525 - can't send with IMAP account

<cmcgroarty

09-22-2007

Re: AT&T 8525 - can't send with IMAP account

<cmcgroarty

10-10-2007

Posted by <cmcgroarty on September 21, 2007, 9:38 pm

Please log in for more thread options

: quoted-printable

Team,

First off, thanks in advance for any suggestions.

I have an AT&T 8525 (recent purchase / wireless carrier change) and get =
the following error when attempting to send email via an IMAP account:

The message(s) could not be sent.
Check that you have network coverage and that your account information =
is correct.
Then try sending again.

The 8525 has a connection via ActiveSync to an Exchange server that =
functions correctly.
The 8525 has one account that uses IMAP that functions correctly. (This =
account does not require SSL for SMTP traffic.)
The troublesome account uses IMAP to connect to an Exchange server and =
requires SSL for SMTP traffic.

The fact that one IMAP/SMTP account functions correctly tells me that =
port 25 is open.
I recently changed from Verizon to AT&T and was formerly using a =
Motorola Q to connect to the Exchange server that I'm now having trouble =
with and was able to function without issue. This tells me the Exchange =
server is functioning correctly. I can also use OE or Windows Mail to =
establish IMAP/SMTP conenctions without error.
There are no certificate issues. A different error would be present if =
that was the case. (OWA and RPC over TCP/IP work correctly)
The SMTP connection that I'm having trouble with requires the same login =
credentials for sending and receiving mail. This particular phone model =
requires that one check the box for "Use Separate Settings" for outgoing =
mail in order to access the "Require SSL for outgoing mail" option. The =
Q allowed one to select SSL without checking this box. That is the only =
differences in setup options that I've observed.

I've tried a number of configuration permutations (there are only a few =
to really try) and have had no success. Any suggestions would be =
welcome. My apologies in advance if this is not the right forum as this =
is technically not an active sync issue, however, I thought that this =
forum would be visited by folks with the most experience with this type =
of issue.

Again, thanks for your input.

Kind Regards,

--=20

Colin M. McGroarty, MCSE, MCSA, MCP+I
------=_NextPart_000_0012_01C7FC8F.4D1827A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16527" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Team,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>First off, thanks in advance for any=20
suggestions.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I have an AT&T 8525 (recent =
purchase / wireless=20
carrier change) and get the following error when attempting to send =
email via an=20
IMAP account:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The message(s) could not be =
sent.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Check that you have network coverage =
and that your=20
account information is correct.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Then try sending again.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The 8525 has a connection via =
ActiveSync to an=20
Exchange server that functions correctly.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The 8525 has one account that uses =
IMAP that=20
functions correctly.  (This account does not require SSL for SMTP=20
traffic.)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The troublesome account uses IMAP to =
connect to an=20
Exchange server and requires SSL for SMTP traffic.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The fact that one IMAP/SMTP account =
functions=20
correctly tells me that port 25 is open.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I recently changed from Verizon to =
AT&T and was=20
formerly using a Motorola Q to connect to the Exchange server that I'm =
now=20
having trouble with and was able to function without issue.  This =
tells me=20
the Exchange server is functioning correctly.  I can also use OE or =
Windows=20
Mail to establish IMAP/SMTP conenctions without error.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>There are no certificate issues.  =
A different=20
error would be present if that was the case. (OWA and RPC over TCP/IP =
work=20
correctly)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>The SMTP connection that I'm having =
trouble with=20
requires the same login credentials for sending and receiving =
mail.  This=20
particular phone model requires that one check the box for "Use =
Separate=20
Settings" for outgoing mail in order to access the "Require SSL for =
outgoing=20
mail" option.  The Q allowed one to select SSL without checking =
this=20
box.  That is the only differences in setup options that I've=20
observed.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I've tried a number of configuration =
permutations=20
(there are only a few to really try) and have had no success.  Any=20
suggestions would be welcome.  My apologies in advance if this is =
not the=20
right forum as this is technically not an active sync issue, however, I =
thought=20
that this forum would be visited by folks with the most experience with =
this=20
type of issue.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Again, thanks for your =
input.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Kind Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR>-- <BR><BR>Colin M. McGroarty, =
MCSE, MCSA,=20
MCP+I</FONT></DIV></BODY></HTML>

------=

Posted by Todd Allcock on September 21, 2007, 10:51 pm

Please log in for more thread options

At 21 Sep 2007 20:38:00 -0500 cmcgroarty@hotmail.com wrote:

> I have an AT&T 8525 (recent purchase / wireless carrier change) and

> get the following error when attempting to send email via an IMAP

account:

> The message(s) could not be sent.

> Check that you have network coverage and that your account

> information is correct.

> Then try sending again.

Two things can cause that error- the carrier blocking the connection
or the e-mail server blocking it.

You said you were using port 25- are you SURE? Doesn't SSL SMPT
often use 587 these days? (My IMAP server does, but thankfully
allows 25 as a "backup" since my carrier, T-Mobile, blocks 587!)

> The troublesome account uses IMAP to connect to an Exchange server

> and requires SSL for SMTP traffic.

> The fact that one IMAP/SMTP account functions correctly tells me

> that port 25 is open.

Why not force 25 in your setup to be sure (for the outgoing server
setting append it with :25, i.e. "smtp.myserver.com:25") If that
doesn't work, force 587 with :587 (if your carrier and server support
it.)

> I recently changed from Verizon to AT&T and was formerly using a

> Motorola Q to connect to the Exchange server that I'm now having

> trouble with and was able to function without issue.

Did you connect via Activesync push, or IMAP with the Q?

> I've tried a number of configuration

> permutations (there are only a few to really try) and have had no

> success. Any suggestions would be welcome.

You might check with AT&T and see if they support SSL SMTP. I know
they offer an alternative SMTP servier (cmwx.com, IIRC) that would
allow you to send your e-mail, but that obviously wouldn't show up on
your Exchange account's "sent" folder which you'd likely prefer.

Good luck!

--

"I don't need my cell phone to play video games or take pictures
or double as a Walkie-Talkie; I just need it to work. Thanks for
all the bells and whistles, but I could communicate better with
ACTUAL bells and whistles." -Bill Maher 9/25/2003

Posted by <cmcgroarty on September 22, 2007, 5:12 pm

Please log in for more thread options

Todd,

Thank you for your input and your speedy response. At this point I've tested
SMTP with ports 25, 587, and 465 without any luck at this point.

With the Q/Verizon I used the same configuration, IMAP/SMTP, without any
issues.

Sounds like it is time for a call to AT&T to see if there are any "gothchas"
that I need to be aware of with their network.

Kind Regards,

--
Colin M. McGroarty, MCSE, MCSA, MCP+I

> At 21 Sep 2007 20:38:00 -0500 cmcgroarty@hotmail.com wrote:

>> I have an AT&T 8525 (recent purchase / wireless carrier change) and

>> get the following error when attempting to send email via an IMAP

> account:

>> The message(s) could not be sent.

>> Check that you have network coverage and that your account

>> information is correct.

>> Then try sending again.

> Two things can cause that error- the carrier blocking the connection

> or the e-mail server blocking it.

> You said you were using port 25- are you SURE? Doesn't SSL SMPT

> often use 587 these days? (My IMAP server does, but thankfully

> allows 25 as a "backup" since my carrier, T-Mobile, blocks 587!)

>> The troublesome account uses IMAP to connect to an Exchange server

>> and requires SSL for SMTP traffic.

>> The fact that one IMAP/SMTP account functions correctly tells me

>> that port 25 is open.

> Why not force 25 in your setup to be sure (for the outgoing server

> setting append it with :25, i.e. "smtp.myserver.com:25") If that

> doesn't work, force 587 with :587 (if your carrier and server support

> it.)

>> I recently changed from Verizon to AT&T and was formerly using a

>> Motorola Q to connect to the Exchange server that I'm now having

>> trouble with and was able to function without issue.

> Did you connect via Activesync push, or IMAP with the Q?

>> I've tried a number of configuration

>> permutations (there are only a few to really try) and have had no

>> success. Any suggestions would be welcome.

> You might check with AT&T and see if they support SSL SMTP. I know

> they offer an alternative SMTP servier (cmwx.com, IIRC) that would

> allow you to send your e-mail, but that obviously wouldn't show up on

> your Exchange account's "sent" folder which you'd likely prefer.

> Good luck!

> --

> "I don't need my cell phone to play video games or take pictures

> or double as a Walkie-Talkie; I just need it to work. Thanks for

> all the bells and whistles, but I could communicate better with

> ACTUAL bells and whistles." -Bill Maher 9/25/2003

Posted by <cmcgroarty on October 10, 2007, 10:04 am

Please log in for more thread options

For those interested in the answer...

In this case the culprit was the AT&T network. The root cause identified to
me was "an issue with a router." I was unable to obtain any details. I
will say thought that I was quite happy with the AT&T support team.

Kind Regards,

--
Colin M. McGroarty, MCSE, MCSA, MCP+I

> Todd,

> Thank you for your input and your speedy response. At this point I've

> tested SMTP with ports 25, 587, and 465 without any luck at this point.

> With the Q/Verizon I used the same configuration, IMAP/SMTP, without any

> issues.

> Sounds like it is time for a call to AT&T to see if there are any

> "gothchas" that I need to be aware of with their network.

> Kind Regards,

> --

> Colin M. McGroarty, MCSE, MCSA, MCP+I

>> At 21 Sep 2007 20:38:00 -0500 cmcgroarty@hotmail.com wrote:

>>> I have an AT&T 8525 (recent purchase / wireless carrier change) and

>>> get the following error when attempting to send email via an IMAP

>> account:

>>>

>>> The message(s) could not be sent.

>>> Check that you have network coverage and that your account

>>> information is correct.

>>> Then try sending again.

>> Two things can cause that error- the carrier blocking the connection

>> or the e-mail server blocking it.

>> You said you were using port 25- are you SURE? Doesn't SSL SMPT

>> often use 587 these days? (My IMAP server does, but thankfully

>> allows 25 as a "backup" since my carrier, T-Mobile, blocks 587!)

>>> The troublesome account uses IMAP to connect to an Exchange server

>>> and requires SSL for SMTP traffic.

>>>

>>> The fact that one IMAP/SMTP account functions correctly tells me

>>> that port 25 is open.

>> Why not force 25 in your setup to be sure (for the outgoing server

>> setting append it with :25, i.e. "smtp.myserver.com:25") If that

>> doesn't work, force 587 with :587 (if your carrier and server support

>> it.)

>>> I recently changed from Verizon to AT&T and was formerly using a

>>> Motorola Q to connect to the Exchange server that I'm now having

>>> trouble with and was able to function without issue.

>> Did you connect via Activesync push, or IMAP with the Q?

>>> I've tried a number of configuration

>>> permutations (there are only a few to really try) and have had no

>>> success. Any suggestions would be welcome.

>> You might check with AT&T and see if they support SSL SMTP. I know

>> they offer an alternative SMTP servier (cmwx.com, IIRC) that would

>> allow you to send your e-mail, but that obviously wouldn't show up on

>> your Exchange account's "sent" folder which you'd likely prefer.

>> Good luck!

>> --

>> "I don't need my cell phone to play video games or take pictures

>> or double as a Walkie-Talkie; I just need it to work. Thanks for

>> all the bells and whistles, but I could communicate better with

>> ACTUAL bells and whistles." -Bill Maher 9/25/2003

Similar Threads	Posted
Syncing Inbox w/ IMAP Account	February 6, 2007, 2:02 pm
Switched to IMAP server	September 12, 2005, 11:56 am
xfer IMAP files	November 16, 2005, 3:20 am
Empty account syncs OTA but not an account with content.	October 26, 2006, 7:48 am
Cingular 8525 PPC and Bluetooth	February 14, 2007, 4:14 pm
Cingular 8525 and DirectPush problems	May 31, 2007, 3:15 pm
SAME THING: Vista WMDC and Cingular 8525	May 17, 2007, 4:09 am
cingular 8525, outlook 2007, win mobile device center 6.1 won't sync	June 30, 2007, 12:51 pm
Can not send file to the device	June 25, 2005, 3:24 am
Unable to send items using AS4.2	August 25, 2006, 8:25 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML Sitemap

XML Sitemap