You can be happy for me, also. I'm just reading this forum after almost two years of having to use Cox Communication's SMTP server to send my from my account through Mail.app (MacOSX 10.4.4). Now messages sent from my TCH account get a Reply-to for that account because they go through the TCH mail server. Yay! No more Reply-to field.
When I first setup mail for our TotalChoiceHosting accounts the instructions in cPanel stated that the POP3/IMAP4 outgoing server is tempenazarene.org (that's the church's domain name) with the standard port (I use IMAP, other accounts at church use POP3). The SMTP (outgoing) setup used tempenazarene.org on port 25. Of course, on both I used my login name (<accountname>+tempenazarene.org) and password.
Along came all the PC worms and virii with their own little SMTP engines and Cox blocked all outgoing SMTP on port 25 and told us to use their SMTP server. Ok, it worked but now all mail from my church account now appeared to come from my Cox account and replies would come back to my Cox account. Not what I wanted but I lived with it. Other providers tell you to try port 587 for SMTP. Doesn't work for TCH mail servers.
Just today I switched the outgoing (SMTP) mail server name to mail.tempenazarene.org, the port to 26, SSL authentication on (don't want my password going in the clear), my account name and password and it went through!
I promise I'll visit more often if TCH promises they'll put explicit instructions about the alternate port 26 in the Configuring Mail Client section. A field under manual settings such as Supported SMTP Ports or just a sentence that says "If your internet service provider blocks SMTP port 25 please try 26." Or maybe just "We miis you at the forums. To find out why port 25 doesn't work for you come talk to us." It would be nice to allow the use of now-becoming-more-standard-for-client-to-server-SMTP-connections port 587.
Thanks to TCH support!