Suddenly cannot send email through any SMTP server

I don't think the Combo Update is likely to help with this problem. But you can read about it, and download it from the link below. It can be installed OVER the existing OSX, even if already the same version is installed. See:

http://www.apple.com/support/downloads/macosx1048comboupdateppc.html

for the one applicable to PPC Macs, such as your G5. Note that it is 149 MB in size.

Are you prevented from choosing the YahooBB SMTP as the Outgoing Server for your other accounts? If so, there is more than an IP block. If not, then the use of the YahooBB SMTP with another domain From address will not be noticed by your recipients.

Ernie

In each other account, have you selected the YahooBB SMTP as Outgoing Server? This selection must be made in each account -- Mail Preferences/Accounts/Account Information and click on the arrows. The YahooBB SMTP will already be listed as an available choice, so choose it. Do this for each account.

If it works, great! If not, then I think more than the IP address is being used to block sending.

Ernie

So, after composing with another address in the From field, when you then send the From address is changed to that of your YahooBB account? Is this so, as seen in your Sent mailbox?

I would like to see the full headers of such a message, intended to be sent from another address. My email address can be found by clicking on my name to the left of this post, and looking in the bio line of my Profile. Send me a test message, and when I receive it, I will examine the Long Headers.

Ernie

I don't if this would help:

I have just migrated from a PowerBook to a PowerMac Pro. Both are wireless connected to internet, boths Mail account have the same settings, and still I can send and receive mail on the PowerBook, and just receive on the PowerMac.
When I try to send a mail, the message is "The sender adress xxxxx@wxs was rejected by the server".
Both have the last OS updates.

This seems to imply that the problem is on the PowerMac, but where?

Soory for polluting your thead: after x controls, I found that a wrong typed letter in the setting was the culprit.....
Shame omn me 😟

This has been a very helpful mail-trail. Had the same problem suddenly appear on my Intel iMAC. Tried the usual. Then used the Port 587 information. And bingo.

Intel-based iMAC Mac OS X (10.4.8) On Windows-based network; D-LINK router

Hi,

Hope I'm not side-tracking people here but I've discovered a link between e-mails not sending and having my website address in my signature.

After reseting my POP accounts, if I include my website address in my signature (which is hosted by the same SMPTE server that I receive my mail through) then the e-mail won't send. It looks like it has been sent but it doesn't get through.

As soon as I remover the website address from the signature, the e-mails get through. Even if I slightly misspell the address, it will get through. But as soon as I put the web address back in the signature, anywhere in the signature, the mails don't get through..... very strange!

Same problem here ..... since 2 days!!!!!
I gues this is a server problem, because the iMap function of my mobile device has the same problem!!!!
APPLE: please solve this problem NOW!!!!!

The best wishes

Bernhard

how exactly do you run the 10.4.8 Combo Updater??

I am having the same issues - cannot send

I had this problem about a month ago. I got lucky when I spotted and error message that showed up one time when I was trying unsuccessfully to send a message. I think my ISP's mail server got me mixed up with its administrators system since I only got the message once and it was something that should be directed to the system console. All my symptoms were just as many have described here. First the bottom line. As suspected, my ISP was blocking my outgoing mail based on my IP with no interference to incoming mail. The error message I got was "tarpitting 4.0 is active for IP 25.435. **.*". My IP was in the 169. **.***.** range, so nothing should have been affecting me, but it was. After some research I wound up looking through a users forum for Merak mail servers. It sounded like they are having some real issues with some of their versions and upgrades. The mail server is where the tarpitting happens. So I called my ISP and asked what mail server they were using. Sure enough it was Merak and they had just recently installed an update. After some discussion of my specific problem and several suggestions and denials; magically everything started working again just fine within the hour. Since I did nothing between our discussion and the magic, I would bet that something was done with the mail server. Maybe a reboot, clearing the tarpit list, advice from Merak, or something done on their end.

I had my ( long time stable) router blamed, my computer, and operator error. It is possible that anywhere along the transmission path that packet headers could be getting corrupted, but that stacking, unstacking, and restacking happens at a very fundamental level and would affect a lot more than just outgoing mail. Consequently, I don't think Apple can be blamed for all these problems.

Perhaps your problem is different, but most sound very familiar with what happened to me. I hope this helps and good luck! As Red Green says " I'm pullin for ya, we're all in this together."

I can't no longer send email after a software upgrade for 10.4.8.

It's DEFINITELY the OSX since my other Windows XP boxes still function well w/o any changes to outlook.

Incoming emails are fine. But outgoing are not.

That's a fascinating insight! Thanks for sharing it. My problem may be with Clamav corruption and constant crashing on incoming, but that's for another thread! What you've revealed, though, may be a contributory factor, or at least a masking one. My company's server has just gone through a horrendous transition. I'm not sure if Merak was involved, but I'll sure alert them to the issue. It's been fascinating to read this thread. Positively riveting! I don't understand very much beyond my router (or even this side of things, to tell you the truth), but you can see the human dilemma being engaged and ultimately sorted out, or resolved, or worked around in the dialogue above. Thanks so much! My learning curve has just been stretched! : )

Mac Mini 1.83 Superdrive, PB 12", iMac SE Slot G4 Mac OS X (10.4.9)

Yikes! This has to be the 'most read post' I can recall. That said, and looking at other most recent posts, it becomes clear many Mail users are having the same, nearly-identical problems.

I just spent the last week going through most of the same steps as the original posters, steedvix600 and Toby Brown, plus fixing permissions, running Disk Warrior and Drive Genius many times.

With growing anticipation, I kept reading to see if SOMEONE would come up with a solution! If I recall, a few people did solve their problems, but their problem did not seem to be exactly like [mine] ours.

In one of those "DUH" moments, I looked at the Tiger Install disc laying here, and loaded it in the drive. Next I just RE-INSTALLED Mail 2.1 over the existing Mail app.

Yes! I works!

And just now I noticed I had let MacOSX.4.9 [accidentally] get itself installed. Many other discussion groups have reported nasty consequences after installing that puppy.

I suspect updates of OS or, perhaps, certain apps, simply corrupt some of the Apple programs. I wonder if re-installing just those applications experiencing problems would provide a solution for many other readers caught up in this jam?