[ubbman]

Mail.app works perfectly, except that when I attempt to send a message (from any server), it simply doesn't do anything. It doesn't even attempt to send the message. After this, the program continues to function, but it won't allow me to quit, and I have to force quit it. I've tried several different mail servers, several different combinations of mail servers, deleting all my mailboxes, deleting the preference files, etc. etc. Nothing works.

Anyone had this before? Would appreciate any help. Thank you.

[besson3c]

Does it do this from another user account on that computer?

[JKT]

What server port are you using? Is it port 25 and if so, does your ISP block that port? If they do, then try changing it to port 587.

[ubbman]

I'm using port 465 and SSL--the exact same settings I use for Thunderbird, which works perfectly. As for using another user account, I haven't yet tried that.

Thanks for the suggestions so far.

[ubbman]

Bumping to see if anyone has any ideas before I give up on this.

Thanks!

[Zarqawi's Eye]

Sorry, no ideas here. The old OS X users here know mail.app as mail.crap

[Chuckit]

Originally Posted by Zarqawi's Eye 

Sorry, no ideas here. The old OS X users here know mail.app as mail.crap

I've been using OS X since 10.1. Mail has always treated me well. What client do you recommend?

[analogika]

What happens in the Activity window when you try to send mail? (Apple-0 or look under the Windows menu)

[Zarqawi's Eye]

Originally Posted by Chuckit 

I've been using OS X since 10.1. Mail has always treated me well. What client do you recommend?

Entourage works well, and is robust and stable.

[ubbman]

Originally Posted by analogika 

What happens in the Activity window when you try to send mail? (Apple-0 or look under the Windows menu)

Absolutely nothing.

[Uncle Skeleton]

Is anything printed to Console, or is any crash log updated when this happens (the first time after mail.app is launched)?

[ubbman]

Originally Posted by Uncle Skeleton 

Is anything printed to Console, or is any crash log updated when this happens (the first time after mail.app is launched)?

Yes!

After attempting to send the message, though nothing happens in Mail itself, this is what came up in the console:

2007-01-28 14:14:00.038 Mail[718] *** -[MessageWriter setEncodingHint:]: selector not recognized [self = 0xd91c610]
2007-01-28 14:14:00.039 Mail[718] Exception raised during monitored invocation of _synchronouslyAppendMessageToOutboxWithContents:la stDraftID:, exception: *** -[MessageWriter setEncodingHint:]: selector not recognized [self = 0xd91c610]


And when attempting to quit after the message failed to send:

2007-01-28 14:14:16.978 Mail[718] *** -[MessageWriter setEncodingHint:]: selector not recognized [self = 0xd929680]
2007-01-28 14:14:16.978 Mail[718] Exception raised during monitored invocation of _synchronouslySaveMessageWithContentsreviousDraf tID:, exception: *** -[MessageWriter setEncodingHint:]: selector not recognized [self = 0xd929680]


Make any sense?

Thanks.

[philm]

As mentioned above, what happens when you login as another user on the same computer?

[Uncle Skeleton]

That's got to be a bug in Mail.app. Have you called Apple support?

[ewiser]

This can happen if your ISP only allows their outgoing mail sever to be used.
If you are trying to set up an email address that is not your ISP. Keep your incoming sever the new email address. In your outgoing sever use the ISP email sever.
I had this problem before.

[ubbman]

What ultimately worked was simply replacing 10.4.8 Mail with 10.4.6 Mail. Not sure what the hell happened.

Thanks a bunch to all those that helped. Appreciate it.