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

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


"Todd Allcock" <> wrote in message
news:Zu%Ii.10325$.. .
> At 21 Sep 2007 20:38:00 -0500 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
>

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


<> wrote in message
news:1445AC86-0EF6-473F-BAFB-...
> 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
>
>
> "Todd Allcock" <> wrote in message
> news:Zu%Ii.10325$.. .
>> At 21 Sep 2007 20:38:00 -0500 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
>>
>