Suddenly can't send mail

I have often received the alert box that the selected server can not send the mail and I have to change the server,or wait, or restart mail to get it to work. This is annoying, but I have dealt with it (although I'd like to know what's going on). But, now, it seems I can't send mail at all, from any server, with a restart or otherwise. It's been happening for the last day.
Can anyone lend a hand? Is it a problem with Apple? I've chosen a variety of different servers (I have many e-mail accounts set up). I've relaunched. Tried to send from various e-mail addresses (although my .mac is my default). No luck.
Thanks for the help,
J.

We have the same problem here and for a few weeks we've resorted to signing in to a browser email program as mac mail's password isn't recognized by the server.

Similar Messages

Suddenly can't send mail with Comcast.

Just thought I'd add my experience to the chorus. Use Mail on a G4 PB running latest version of Tiger with Comcast as ISP. Few days ago kept getting the message that port 25 timed out. I questioned Comcast, and got a standard reply to try port 587, which I did, and which works. I can now send mail through port 587.
Question though: Is this a Comcast problem, or an Apple Mail problem. It seems like it cannot be a coincidence that "can't send mail" seems to be a hot topic all of a sudden, and that it involves various ISP's and platforms. I haven't heard the word "virus" mentioned.

In my mind, it's a silly attempt by ISPs to limit/cut off SPAM, not that that is a silly idea in and of itself, but changing the Port number isn't going to last very long, add to that not notifying Users/Paying customers before hand is negligent if not criminal!
The Spammers probably knew and adjusted to the change before the first Customer figured it out.

Suddenly can't send mail, can't receive.

Hi, recently I'm suddenly unable to receive email. I'm able to send however.
I set up the mail account 3 months ago and it's been working fine up until now, and I haven't changed any of the Mail Preference settings.
I keep getting this error message:
"The server refused to allow a connection on port 143"
I'm able to check mail directly on the mail server on Firefox,so it's not a server issue-the Mail application just doesn't work.

I am also having the same problem as of 1 day ago. I can send but not receive mail, but I can retrieve my mail through the Apple server site. I recently installed Leopard. Any thoughts?

Can't send mail with server -- upgrade OS?

I have a new MB, so have been setting things up. In the course of all this, I realized, what with checking settings, etc., that I can easily send mail from the new laptop, which is running whatever the latest OS is -- I think that's 15.5.5, but I have nearly constant difficulties with Mail on my desktop, which is running 15.5.2. I keep getting -- but not always -- messages saying mail can't be sent using the selected server; do I want to try another server or try later, or what. But on the laptop -- I don't get that at all.
I did a search on the Apple site and its recommendation? Upgrade the OS. Now, I can certainly do that, though I always hold my breath for fear something will go wrong and I'll break something that wasn't broken, so to speak.
Is anyone else having this issue? Did upgrading the OS stop it? I probably will have to, because I really do need the Mail program to work as it should. I'm getting ready to move to it from Entourage, but I can't if I can't send mail.

I suddenly started having the can't send mail problem yesterday, and I'm on 10.5.5, so upgrading the OS is not a fix. I followed all the directions here: http://support.apple.com/kb/TS1307?viewlocale=en_US
and that did not work. But it might, if quitting is done at the right time....
I don't know what fixed it, and I'm not sure if it will remain fixed (last night I fixed it on my own, only to find when I started up this morning that it wasn't working again), but today I followed the advice from another discussion to delete the outgoing server (in prefs/accounts/outgoing pulldown menu) and make a new one... make sure to delete all mail that is pending (anything in outbox save as draft and delete)... and to quit. In other words - follow the instructions on the support page or some of the other discussions, but quit before trying to send again. The other thing I did was do a software upgrade - there was something for airport and a security fix that I installed. Whether it was doing just the right stuff in just the right order or if it was the software installs that moved things along, I can't say. By the looks of it, this seems to be a long time issue for Apple Mail, though I've been using it for years without issue.

I can't send mail

I am suddenly having trouble sending mail. I've checked my settings through ATT, they are correct and used their connection assistant which comes up as a green light. I'm receiving mail but just can't send it. They suggest delting the account online, but then I would lose everything.
I have one main account and 3 sub-accounts, same problem with all of them. I have also run disc repair and the iMail troubleshooter and tried re-installing mail, but my iMac won't let me.
I have an iMac bought in 2007 with intel, running Snow Leopard and 3 Gigs RAM.

I have an error that says it can't connect to port 537 TSL because it's an ssl. I have ssl selected. It happens with replyies as well as new messages.
This is a copy of the connection doctor detail:
WROTE Nov 28 06:45:44.705 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0e4470 -- thread:0x119c16e50
PASS *********
READ Nov 28 06:45:44.780 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0e3240 -- thread:0x101112930
-ERR [AUTH] invalid user/password
READ Nov 28 06:45:44.862 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cd8770 -- thread:0x11825eca0
+OK maildrop ready, 185 messages (6846918 octets) (19255228)
READ Nov 28 06:45:44.884 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0de7d0 -- thread:0x119d305f0
+OK maildrop ready, 222 messages (8064631 octets) (8515549)
WROTE Nov 28 06:45:44.889 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cd8770 -- thread:0x11825eca0
QUIT
WROTE Nov 28 06:45:44.915 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0de7d0 -- thread:0x119d305f0
QUIT
READ Nov 28 06:45:44.937 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cc7800 -- thread:0x11820cdb0
+OK maildrop ready, 0 messages (0 octets) (0)
WROTE Nov 28 06:45:44.994 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cc7800 -- thread:0x11820cdb0
QUIT
READ Nov 28 06:45:45.008 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cd8770 -- thread:0x11825eca0
+OK server signing off.
READ Nov 28 06:45:45.012 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0de7d0 -- thread:0x119d305f0
+OK server signing off.
READ Nov 28 06:45:45.066 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c8c090 -- thread:0x119c7c350
+OK maildrop ready, 113 messages (6040458 octets) (6252716)
READ Nov 28 06:45:45.082 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0e4470 -- thread:0x119c16e50
+OK maildrop ready, 3 messages (180007 octets) (184308)
WROTE Nov 28 06:45:45.096 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c8c090 -- thread:0x119c7c350
QUIT
READ Nov 28 06:45:45.114 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cc7800 -- thread:0x11820cdb0
+OK server signing off.
WROTE Nov 28 06:45:45.120 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0e4470 -- thread:0x119c16e50
QUIT
READ Nov 28 06:45:45.265 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0e4470 -- thread:0x119c16e50
+OK server signing off.
READ Nov 28 06:45:45.272 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c8c090 -- thread:0x119c7c350
+OK server signing off.
CONNECTED Nov 28 06:46:13.175 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x119c9c310 -- thread:0x11b0bd330
READ Nov 28 06:46:13.541 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x119c9c310 -- thread:0x11b0bd330
220 smtp111.sbc.mail.mud.yahoo.com ESMTP
CONNECTED Nov 28 06:46:43.661 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x119c70800 -- thread:0x11b0bd330
READ Nov 28 06:46:44.033 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x119c70800 -- thread:0x11b0bd330
220 smtp107.sbc.mail.mud.yahoo.com ESMTP
WROTE Nov 28 06:46:44.057 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x119c70800 -- thread:0x11b0bd330
HELO [192.168.1.8]
READ Nov 28 06:46:44.142 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x119c70800 -- thread:0x11b0bd330
250 smtp107.sbc.mail.mud.yahoo.com
CONNECTED Nov 28 06:46:44.300 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:587 -- socket:0x119c70800 -- thread:0x11b0bd330
CONNECTED Nov 28 06:47:14.515 [kCFStreamSocketSecurityLevelNone] -- host:outbound.att.net -- port:587 -- socket:0x119c70800 -- thread:0x11b0bd330
READ Nov 28 06:47:14.594 [kCFStreamSocketSecurityLevelNone] -- host:outbound.att.net -- port:587 -- socket:0x119c70800 -- thread:0x11b0bd330
220 smtp115.sbc.mail.gq1.yahoo.com ESMTP
WROTE Nov 28 06:47:14.619 [kCFStreamSocketSecurityLevelNone] -- host:outbound.att.net -- port:587 -- socket:0x119c70800 -- thread:0x11b0bd330
HELO [192.168.1.8]
READ Nov 28 06:47:14.698 [kCFStreamSocketSecurityLevelNone] -- host:outbound.att.net -- port:587 -- socket:0x119c70800 -- thread:0x11b0bd330
250 smtp115.sbc.mail.gq1.yahoo.com
CONNECTED Nov 28 06:47:14.806 [kCFStreamSocketSecurityLevelNone] -- host:outbound.att.net -- port:587 -- socket:0x119c34ad0 -- thread:0x11b0bd330
READ Nov 28 06:47:14.884 [kCFStreamSocketSecurityLevelNone] -- host:outbound.att.net -- port:587 -- socket:0x119c34ad0 -- thread:0x11b0bd330
220 smtp101.sbc.mail.gq1.yahoo.com ESMTP
WROTE Nov 28 06:47:14.910 [kCFStreamSocketSecurityLevelNone] -- host:outbound.att.net -- port:587 -- socket:0x119c34ad0 -- thread:0x11b0bd330
HELO [192.168.1.8]
READ Nov 28 06:47:14.989 [kCFStreamSocketSecurityLevelNone] -- host:outbound.att.net -- port:587 -- socket:0x119c34ad0 -- thread:0x11b0bd330
250 smtp101.sbc.mail.gq1.yahoo.com
CONNECTED Nov 28 06:48:05.279 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119f89cc0 -- thread:0x119ff8a60
CONNECTED Nov 28 06:48:05.306 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cb4530 -- thread:0x119c08380
CONNECTED Nov 28 06:48:05.309 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c48a10 -- thread:0x118250ae0
CONNECTED Nov 28 06:48:05.311 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119b9ce70 -- thread:0x119b3e590
CONNECTED Nov 28 06:48:05.312 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cf22f0 -- thread:0x119c82150
CONNECTED Nov 28 06:48:05.314 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x119ff5a20 -- thread:0x119d564f0
CONNECTED Nov 28 06:48:05.314 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c7efb0 -- thread:0x119c91330
CONNECTED Nov 28 06:48:05.316 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0b8180 -- thread:0x11c412260
CONNECTED Nov 28 06:48:05.318 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0bd480 -- thread:0x114559d20
READ Nov 28 06:48:05.336 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119f89cc0 -- thread:0x119ff8a60
220 fed1rmimpo210 cox ESMTP server ready
CONNECTED Nov 28 06:48:05.339 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119b639a0 -- thread:0x119c4a8c0
CONNECTED Nov 28 06:48:05.421 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x119cd20b0 -- thread:0x11b0b7600
CONNECTED Nov 28 06:48:05.423 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x1182f61e0 -- thread:0x1151e7b60
CONNECTED Nov 28 06:48:05.441 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0b9f40 -- thread:0x11b098a70
READ Nov 28 06:48:05.531 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119b639a0 -- thread:0x119c4a8c0
220 fed1rmimpo306 cox ESMTP server ready
READ Nov 28 06:48:05.685 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x119ff5a20 -- thread:0x119d564f0
220 smtp112.sbc.mail.gq1.yahoo.com ESMTP
READ Nov 28 06:48:05.787 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x119cd20b0 -- thread:0x11b0b7600
220 smtp105.sbc.mail.mud.yahoo.com ESMTP
READ Nov 28 06:48:05.800 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x1182f61e0 -- thread:0x1151e7b60
220 smtp106.sbc.mail.mud.yahoo.com ESMTP
READ Nov 28 06:48:05.810 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0b9f40 -- thread:0x11b098a70
220 smtp107.sbc.mail.mud.yahoo.com ESMTP
READ Nov 28 06:48:05.846 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0bd480 -- thread:0x114559d20
+OK hello from popgate 2.48.1 on pop120.sbc.mail.sp2.yahoo.com
READ Nov 28 06:48:05.853 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c7efb0 -- thread:0x119c91330
+OK hello from popgate 2.48.1 on pop116.sbc.mail.sp2.yahoo.com
READ Nov 28 06:48:05.857 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119b9ce70 -- thread:0x119b3e590
+OK hello from popgate 2.48.1 on pop128.sbc.mail.sp2.yahoo.com
READ Nov 28 06:48:05.862 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cf22f0 -- thread:0x119c82150
+OK hello from popgate 2.48.1 on pop130.sbc.mail.sp2.yahoo.com
READ Nov 28 06:48:05.868 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cb4530 -- thread:0x119c08380
+OK hello from popgate 2.48.1 on pop129.sbc.mail.sp2.yahoo.com
READ Nov 28 06:48:05.871 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c48a10 -- thread:0x118250ae0
+OK hello from popgate 2.48.1 on pop127.sbc.mail.sp2.yahoo.com
READ Nov 28 06:48:05.876 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0b8180 -- thread:0x11c412260
+OK hello from popgate 2.48.1 on pop118.sbc.mail.sp2.yahoo.com
WROTE Nov 28 06:48:05.881 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0bd480 -- thread:0x114559d20
CAPA
WROTE Nov 28 06:48:05.906 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c7efb0 -- thread:0x119c91330
CAPA
WROTE Nov 28 06:48:05.930 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119b9ce70 -- thread:0x119b3e590
CAPA
WROTE Nov 28 06:48:05.955 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cf22f0 -- thread:0x119c82150
CAPA
WROTE Nov 28 06:48:05.978 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cb4530 -- thread:0x119c08380
CAPA
WROTE Nov 28 06:48:06.003 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c48a10 -- thread:0x118250ae0
CAPA
WROTE Nov 28 06:48:06.028 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0b8180 -- thread:0x11c412260
CAPA
READ Nov 28 06:48:06.053 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0bd480 -- thread:0x114559d20
+OK CAPA list follows
EXPIRE NEVER
IMPLEMENTATION popgate 2.48.1
PIPELINING
RESP-CODES
TOP
UIDL
USER
READ Nov 28 06:48:06.079 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c7efb0 -- thread:0x119c91330
+OK CAPA list follows
EXPIRE NEVER
IMPLEMENTATION popgate 2.48.1
PIPELINING
RESP-CODES
TOP
UIDL
USER
READ Nov 28 06:48:06.105 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119b9ce70 -- thread:0x119b3e590
+OK CAPA list follows
EXPIRE NEVER
IMPLEMENTATION popgate 2.48.1
PIPELINING
RESP-CODES
TOP
UIDL
USER
READ Nov 28 06:48:06.130 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cf22f0 -- thread:0x119c82150
+OK CAPA list follows
EXPIRE NEVER
IMPLEMENTATION popgate 2.48.1
PIPELINING
RESP-CODES
TOP
UIDL
USER
READ Nov 28 06:48:06.153 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cb4530 -- thread:0x119c08380
+OK CAPA list follows
EXPIRE NEVER
IMPLEMENTATION popgate 2.48.1
PIPELINING
RESP-CODES
TOP
UIDL
USER
READ Nov 28 06:48:06.176 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c48a10 -- thread:0x118250ae0
+OK CAPA list follows
EXPIRE NEVER
IMPLEMENTATION popgate 2.48.1
PIPELINING
RESP-CODES
TOP
UIDL
USER
READ Nov 28 06:48:06.199 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0b8180 -- thread:0x11c412260
+OK CAPA list follows
EXPIRE NEVER
IMPLEMENTATION popgate 2.48.1
PIPELINING
RESP-CODES
TOP
UIDL
USER
WROTE Nov 28 06:48:06.224 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0bd480 -- thread:0x114559d20
USER [email protected]
WROTE Nov 28 06:48:06.246 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c7efb0 -- thread:0x119c91330
USER [email protected]
WROTE Nov 28 06:48:06.271 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119b9ce70 -- thread:0x119b3e590
USER [email protected]
WROTE Nov 28 06:48:06.295 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cf22f0 -- thread:0x119c82150
USER [email protected]
WROTE Nov 28 06:48:06.320 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cb4530 -- thread:0x119c08380
USER [email protected]
WROTE Nov 28 06:48:06.345 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c48a10 -- thread:0x118250ae0
USER [email protected]
WROTE Nov 28 06:48:06.368 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0b8180 -- thread:0x11c412260
USER [email protected]
READ Nov 28 06:48:06.392 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0bd480 -- thread:0x114559d20
+OK password required.
READ Nov 28 06:48:06.417 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c7efb0 -- thread:0x119c91330
+OK password required.
READ Nov 28 06:48:06.442 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119b9ce70 -- thread:0x119b3e590
+OK password required.
READ Nov 28 06:48:06.467 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cf22f0 -- thread:0x119c82150
+OK password required.
READ Nov 28 06:48:06.493 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cb4530 -- thread:0x119c08380
+OK password required.
READ Nov 28 06:48:06.518 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c48a10 -- thread:0x118250ae0
+OK password required.
READ Nov 28 06:48:06.544 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0b8180 -- thread:0x11c412260
+OK password required.
WROTE Nov 28 06:48:06.570 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0bd480 -- thread:0x114559d20
PASS *********
WROTE Nov 28 06:48:06.595 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c7efb0 -- thread:0x119c91330
PASS ******
WROTE Nov 28 06:48:06.623 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119b9ce70 -- thread:0x119b3e590
PASS ************
WROTE Nov 28 06:48:06.647 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cf22f0 -- thread:0x119c82150
PASS **********
WROTE Nov 28 06:48:06.674 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cb4530 -- thread:0x119c08380
PASS *********
WROTE Nov 28 06:48:06.700 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c48a10 -- thread:0x118250ae0
PASS *********
WROTE Nov 28 06:48:06.726 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0b8180 -- thread:0x11c412260
PASS **********
READ Nov 28 06:48:06.842 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119b9ce70 -- thread:0x119b3e590
+OK maildrop ready, 222 messages (8064631 octets) (8515549)
READ Nov 28 06:48:06.911 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0b8180 -- thread:0x11c412260
-ERR [AUTH] invalid user/password
WROTE Nov 28 06:48:06.935 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119b9ce70 -- thread:0x119b3e590
QUIT
READ Nov 28 06:48:06.963 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0bd480 -- thread:0x114559d20
+OK maildrop ready, 113 messages (6040458 octets) (6252716)
READ Nov 28 06:48:06.985 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c48a10 -- thread:0x118250ae0
+OK maildrop ready, 3 messages (180007 octets) (184308)
READ Nov 28 06:48:07.001 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cf22f0 -- thread:0x119c82150
+OK maildrop ready, 0 messages (0 octets) (0)
WROTE Nov 28 06:48:07.006 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0bd480 -- thread:0x114559d20
QUIT
WROTE Nov 28 06:48:07.033 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c48a10 -- thread:0x118250ae0
QUIT
READ Nov 28 06:48:07.036 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119b9ce70 -- thread:0x119b3e590
+OK server signing off.
READ Nov 28 06:48:07.045 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c7efb0 -- thread:0x119c91330
+OK maildrop ready, 64 messages (3207299 octets) (3759629)
WROTE Nov 28 06:48:07.055 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cf22f0 -- thread:0x119c82150
QUIT
READ Nov 28 06:48:07.087 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cb4530 -- thread:0x119c08380
+OK maildrop ready, 185 messages (6846918 octets) (19255228)
WROTE Nov 28 06:48:07.152 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c7efb0 -- thread:0x119c91330
QUIT
READ Nov 28 06:48:07.152 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c48a10 -- thread:0x118250ae0
+OK server signing off.
READ Nov 28 06:48:07.153 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x11b0bd480 -- thread:0x114559d20
+OK server signing off.
READ Nov 28 06:48:07.175 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119cf22f0 -- thread:0x119c82150
+OK server signing off.
WROTE Nov 28 06:48:07.202 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cb4530 -- thread:0x119c08380
QUIT
READ Nov 28 06:48:07.303 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:pop.att.yahoo.com -- port:995 -- socket:0x119c7efb0 -- thread:0x119c91330
+OK server signing off.
READ Nov 28 06:48:07.361 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:inbound.att.net -- port:995 -- socket:0x119cb4530 -- thread:0x119c08380
+OK server signing off.
WROTE Nov 28 06:48:35.514 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119f89cc0 -- thread:0x119ff8a60
EHLO [192.168.1.8]
READ Nov 28 06:48:35.574 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119f89cc0 -- thread:0x119ff8a60
250-fed1rmimpo210 hello [67.124.28.79], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN CRAM-MD5
250-SIZE 28672000
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 OK
WROTE Nov 28 06:48:35.601 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119f89cc0 -- thread:0x119ff8a60
STARTTLS
WROTE Nov 28 06:48:35.635 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119b639a0 -- thread:0x119c4a8c0
EHLO [192.168.1.8]
READ Nov 28 06:48:35.667 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119f89cc0 -- thread:0x119ff8a60
220 2.0.0 Ready to start TLS
READ Nov 28 06:48:35.704 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119b639a0 -- thread:0x119c4a8c0
250-fed1rmimpo306 hello [67.124.28.79], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN CRAM-MD5
250-SIZE 28672000
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 OK
WROTE Nov 28 06:48:35.731 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119b639a0 -- thread:0x119c4a8c0
STARTTLS
READ Nov 28 06:48:35.790 [kCFStreamSocketSecurityLevelNone] -- host:smtp.west.cox.net -- port:587 -- socket:0x119b639a0 -- thread:0x119c4a8c0
220 2.0.0 Ready to start TLS
CONNECTED Nov 28 06:48:35.812 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x11b0e9a60 -- thread:0x119d564f0
WROTE Nov 28 06:48:35.926 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.west.cox.net -- port:587 -- socket:0x119f89cc0 -- thread:0x119ff8a60
EHLO [192.168.1.8]
CONNECTED Nov 28 06:48:35.937 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x1182de150 -- thread:0x11b0b7600
CONNECTED Nov 28 06:48:35.938 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0f6210 -- thread:0x1151e7b60
CONNECTED Nov 28 06:48:35.957 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0d3800 -- thread:0x11b098a70
READ Nov 28 06:48:35.986 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.west.cox.net -- port:587 -- socket:0x119f89cc0 -- thread:0x119ff8a60
250-fed1rmimpo210 hello [67.124.28.79], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN CRAM-MD5
250-SIZE 28672000
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 OK
WROTE Nov 28 06:48:36.041 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.west.cox.net -- port:587 -- socket:0x119f89cc0 -- thread:0x119ff8a60
AUTH PLAIN ****************************
WROTE Nov 28 06:48:36.058 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.west.cox.net -- port:587 -- socket:0x119b639a0 -- thread:0x119c4a8c0
EHLO [192.168.1.8]
READ Nov 28 06:48:36.109 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.west.cox.net -- port:587 -- socket:0x119f89cc0 -- thread:0x119ff8a60
535 5.7.0 ...authentication rejected
READ Nov 28 06:48:36.123 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.west.cox.net -- port:587 -- socket:0x119b639a0 -- thread:0x119c4a8c0
250-fed1rmimpo306 hello [67.124.28.79], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN CRAM-MD5
250-SIZE 28672000
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 OK
WROTE Nov 28 06:48:36.158 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.west.cox.net -- port:587 -- socket:0x119b639a0 -- thread:0x119c4a8c0
AUTH PLAIN (*** 32 bytes hidden ***)
READ Nov 28 06:48:36.219 [kCFStreamSocketSecurityLevelTLSv1SSLv3] -- host:smtp.west.cox.net -- port:587 -- socket:0x119b639a0 -- thread:0x119c4a8c0
535 5.7.0 ...authentication rejected
READ Nov 28 06:48:36.248 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x11b0e9a60 -- thread:0x119d564f0
220 smtp110.sbc.mail.gq1.yahoo.com ESMTP
WROTE Nov 28 06:48:36.272 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x11b0e9a60 -- thread:0x119d564f0
HELO [192.168.1.8]
READ Nov 28 06:48:36.303 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x1182de150 -- thread:0x11b0b7600
220 smtp110.sbc.mail.mud.yahoo.com ESMTP
READ Nov 28 06:48:36.310 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0f6210 -- thread:0x1151e7b60
220 smtp111.sbc.mail.mud.yahoo.com ESMTP
READ Nov 28 06:48:36.326 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0d3800 -- thread:0x11b098a70
220 smtp112.sbc.mail.mud.yahoo.com ESMTP
WROTE Nov 28 06:48:36.327 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x1182de150 -- thread:0x11b0b7600
HELO [192.168.1.8]
WROTE Nov 28 06:48:36.352 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0f6210 -- thread:0x1151e7b60
HELO [192.168.1.8]
READ Nov 28 06:48:36.367 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x11b0e9a60 -- thread:0x119d564f0
250 smtp110.sbc.mail.gq1.yahoo.com
WROTE Nov 28 06:48:36.376 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0d3800 -- thread:0x11b098a70
HELO [192.168.1.8]
READ Nov 28 06:48:36.412 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x1182de150 -- thread:0x11b0b7600
250 smtp110.sbc.mail.mud.yahoo.com
READ Nov 28 06:48:36.437 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0f6210 -- thread:0x1151e7b60
250 smtp111.sbc.mail.mud.yahoo.com
WROTE Nov 28 06:48:36.453 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:outbound.att.net -- port:465 -- socket:0x11b0e9a60 -- thread:0x119d564f0
QUIT
READ Nov 28 06:48:36.478 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0d3800 -- thread:0x11b098a70
250 smtp112.sbc.mail.mud.yahoo.com
WROTE Nov 28 06:48:36.504 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x1182de150 -- thread:0x11b0b7600
QUIT
WROTE Nov 28 06:48:36.528 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0f6210 -- thread:0x1151e7b60
QUIT
WROTE Nov 28 06:48:36.580 [kCFStreamSocketSecurityLevelNegotiatedSSL] -- host:smtp.att.yahoo.com -- port:465 -- socket:0x11b0d3800 -- thread:0x11b098a70
QUIT

Can´t send mail on any account

Hi,
Suddenly all of my accounts can´t send mail...
it pops up a window saying mail can´t use this smtp, and it doesn´t matter what I choose for selected server, nothing works.
And if I change the outgoing mail server settings in preferences it does not change in the pop up.
I did not change anything.
I have tried to start new account but nothing works.

Gunz,
For your .mac account, if you are using the smtp.mac.com as the Outgoing Server, change the Port to be Port 587, and test. Although you are using many different venues, more and more ISPs are blocking Port 25 for all but their own SMTP. Are the other accounts unrelated to your ISP? If so, their SMTP may need to be presented either on Port 587, or still another.
If you are having a problem with the SMTP provided by your ISP, then a change in policy may have been accompanied by a new name for their SMTP, or a new Authentication protocol.
More info, please, but first test with Port 587 and the smtp.mac.com.
Ernie

All of a sudden I cannot send mail but I still receive it. Help?

All of a sudden I cannot send mail although I still receive. Anyone have an answer to this?

Do you get an error message?
You can go back into the mail account settings and scroll to the outgoing mail server and see if you can enter a password, same one as your incoming mail server.

Can't send mail with IMAP

Hi,
I have two different IMAP accounts, and I can't send mail with either of them. I receive it just fine, but can't send. One of them just switched to ESMTP (I'm not entirely sure what that means), and said that many mail programs are not yet compatible with it. I know that both accounts can send, as I can send from them on the web.
I have tried switching from port 25 to port 587, with no luck. Regardless of what I do, the program displays a window saying, "Sending the message content to the server failed." I haven't been able to send for a little over a week now. Any help would be greatly appreciated.
Thanks

Tonight I have been suddenly unable to send e-mail from my mac.com address.
The problem is the same whether I try to send from my G4 laptop running OS 10.4, or my eMac running OS 10.3.9 , or from .mac web mail.
The alert I am receiving says: "The sender address [email protected] was rejected by the server."
I am using the SMTP outgoing mail server, not POP.
I can still receive e-mail with no difficulty.
I have changed no settings.
What's up?

Can receive but can't send mail via BT Yahoo SMTP server port 995

Suddenly I can't send mail from my BT/Yahoo account but can still receive mail. The message that i get is that it was rejected by the server. I have not changed the server - it is still SMTP via port 995, using SSL. Help!! Why should this have ocurred out of the blue and what do I do?

Hi Dancing Brave,
Thanks for visiting Apple Support Communities.
I recommend starting with the steps in this article if you are not able to send mail:
OS X Mail: Troubleshooting sending and receiving email messages
http://support.apple.com/kb/ts3276
Best,
Jeremy

Can't send mail - error "HELO/EHLO"

Running !0.2.8 with Mail 1.2.5
Using broad band connection via tiscali.co.uk
Receiving mail, but suddenly can't send any - with error message
"HELO/EHLO with my domain name. You are not me."
Have checked all network settings and all are o.k.
Can anyone help please?

It is my site mentioned above as an explanation of the error (hence my arrival here - saw the thread in my web stats)
Let me explain whats happening in the hope of shedding some light on the issue.
When you send out e-mail, the following procedure happens:
1. You create the mail, add recipients/subject etc and press send.
2. Your mac connects to your configured SMTP server
3. The server will ask your computer for its name
4. Your computer returns a string to the server - known as an EHLO/HELO usually this would be the name your computer is set to (for example: mymac.local)
5. The server checks the name that was sent, if it is a FQDN (e.g. server.company.com) it will check the DNS records to ensure the host is valid, then checks its access rules and either allows your computer to send the rest of the e-mail or sends a deny message and kicks you off
Your computer is failing one of the EHLO/HELO checks, the reason for this is that your email client is returning tiscali.co.uk or localhost when the server is asking it for its name.
It is possible that the name of your mac is the issue, it could be a bug, or you may even be using a tiscali proxy server to connect.
What is the name of your mac?
Are you using a tiscali proxy server?
I'm on a pc at the moment but when I get a chance I will look at the strings that Mail returns to my server from my Mac as it could possibly be a bug.

Is there a fix for "can't send mail?"

I just spent 4+ hours on this forum and worked through all suggestions I could find - still can't send mail. It happened yesterday afternoon, from one moment to the next - suddenly all my three POP accounts are offline and there was nothing I could do about it. I checked with Entourage, same thing there as well, can't send mail.
I have no idea if this is connected with the problem in many posts about the "can't send mail" issue or not, but at least on the surface it looks like it is.
Any help is appreciated! Thank you.

Yes, there are complaint sites online where I've read hundreds of complaints that trickle in one by one on different dates.
Take a look at this post, and the comments below it:
http://www.lockergnome.com/usrbingeek/2007/04/12/comcast-blocking-port-25/
This is going to be an ongoing problem for different users, one at a time.
DSL users in my area are going through a similar issue with their CenturyTel email accounts. Over the last two years they have added a new smtp server and some people were transferred immediately to it, and others got added month by month (some were on smtp.centurytel.net while others are on smtpauth.centurytel.net). Then a couple of months ago, they started requiring login and password to the smtp server, but not for all users. I get a few calls a month for the next batch. Centurytel has gone with a 3rd party email hosting company so that they don't have to deal with it.
I'm trying to set up all clients with the latest changes, but they don't always work in advance of the changes. It's hit and miss. CenturyTel has said that they have posted notices on their help site, but who goes there?
Maybe they are just trying to manage their tech support load during changes?
Message was edited by: dechamp

Can't send mail since 10.4.6 update

Since updating my OS to 10.4.6 I can't send mail. I can receive mail and I can browse online. But mail will not go out. I've verified all the Outgoing Mail Server info SEVERAL times and have had no luck. I've enabled Entourage to handle mail instead of MacMail and it won't work either. Totally stumped.
Same thing has happened on my iBook G4 laptop by the way. I'm convinced that the update has something to do with this.

INTERNET CONNECTION LOST
so... since the 10.4.6 update once my computers fall asleep the connection to my wireless router is lost. (mail seems to be working ok, when i have an internet connection...)
I have tried multiple things to fix this. Thus far the only solution seems to be resetting the router to use connect back to the internet. Once this is done the internet connection works fine, until lost or the computers go to sleep. When i wake the computer i have to do it all over again... and on top of it the post link is missing on all the pages!!! so i am replying here.
So this time I have rebooted to my external drive with the previous version (10.4.5) to see if indeed it is the 10.4.6 update that seems to have hosed this connection somehow.
HELP please, this is terrible annoying. Is anyone else experiencing this?
thank you.
PowerBook G4 and PowerPC dual G5 (10.4.6 both) Mac OS X (10.4.6)

Can't send mail on iOS 5 devices with iCloud

A long time ago I signed up for a .Mac trial to use that address with iChat. The trial expired, and, as expected, the address continued to work with iChat, though it no longer functioned as an email address. It then came to be my Apple ID. Now, having set that Apple ID up for use with iCloud, my iOS devicess are having trouble sending, and only sending email from my iCloud address. The reason is this: I logged into <username>@mac.com for iCloud (as that's my Apple ID), and everything set up right except the mail address that iOS Mail thinks I have. It thinks the mail address for the iCloud account is <username>@mac.com. When I send mail to <username>@me.com, my iOS devices get it just fine, but when I try to send mail back, it tries to send it from the @mac.com address, and therefore fails as that is not a valid email address.
I've tried to go into the settings and change the email address that it uses for iCLoud, but with no luck. I see a place to change it, but it is grayed out and won't let me select it and bring up a keyboard to change it.
Is there any way to tell it that it assumed the wrong email address for my iCloud? Or is there no way to send iCloud email from my iOS devices?
Thanks in advance!
P.S. I can send mail via iCloud from the web app and from Apple Mail (OS X Lion), but not from iOS devices because of this glitch. I can also send mail from iOS devices using other email accounts (Gmail, Yahoo).

I found a work around that works. Got to Settings...Icloud....account......advanced....outgoing mail server.....
Add an "other" server.
Host Name p01-smtp.mail.me.com
Put in your me.com email address as username and your Apple ID password
SSL is on
Authentication is password
Server port 587
This worked for me.....I will use this until the bug is fixed. (you may need to use p02, p03 etc) Don't make this server your primary. Leave it in "on" status in the other category.
Good luck

Can't send mail... after 4 months of using it

I'm stumped... help me out please.
When i send a mail out, this message pops up, "Error : This Message could not be delivered and will remain in your Outbox until it can be delivered. Sending the message content to the server failed."
So it's still in my mailbox. But then, it shows up in my gmail account and on my blackberry as a sent mail, but the receiver never gets it. Also, i can still send mail from both my blackberry and gmail.com... just not from Apple Mail.
What's going on?

Sometimes an ISP provider blocks one of your incoming
Mail ports and "won't notify you". ( Why? probably it's their protection software )
In my case Comcast blocked my Port 25 and my Outgoing kept bouncing.
Incoming was fine.
Make sure when you change your Port to 587,
You also check "ON" the Secure Sockets Layer box right underneath,
Then change Authentication: to Password
Then enter your name and password
and click OK.
The reps at most of the providers
are useless and won't tell you
the second part of the solution.
It took me 2 days and 4 reps
at Comcast to find this out
and 10 hours of trying to
clean my Mac...
which they will always
blame.
Best of Luck, Tom

Receiving mail, but can't send mail with attachments?

Hello,
I can't send mails anymore, I have been able to send some without any attachments (i.e. reply doesn't work as it automatically attaches the original text). This started 3 days ago. Also, my mail doesn't seem to recognize powerpoint and word docs., but I a know the people who have send me such files do not have VISTA. When I choose "open with" then it works. So I have 2 problems, one being moe urgent then the other.
1) can't send mail with attachments
2) .doc (word), .pps (powerpoint)attachments are not always recognized.
thank you all!!!

Try going into Settings > Mail, Contacts, Calendars > select the account > account name , tap on SMTP (under the 'Outgoing Mail Server' heading) and then tap on your Primary Server and try entering your email account and password and see if it then works

Suddenly can't send mail

Similar Messages

Maybe you are looking for