Jump to content

Recommended Posts

Posted

Didnt know where to ask this question in the forums and didnt want to issue a trouble ticket yet.

 

Just recently I noticed that messages sent to [myTCHaccount]@server94.totalchoicehosting.com stopped going through and are bounced back:

 

 

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

 

[myTCHaccount]@server94.totalchoicehosting.com

SMTP error from remote mailer after RCPT TO:<[myTCHaccount]@server94.totalchoicehosting.com>:

host server94.totalchoicehosting.com [72.9.224.178]:

550-elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65] is currently not

550-permitted to relay through this server. Perhaps you have not logged into

550-the pop/imap server in the last 30 minutes or do not have SMTP

550 Authentication turned on in your email client.

 

I also notice that the host's FQDN now is server94.tchmachines.com. Sending to the same account @server94.tchmachines.com works and lands in my postmaster mailbox like it always did. Was there a change that now requires the *.tchmachines.com domain to be used for this purpose, or should the totalchoicehosting.com domain be used but is somehow broken?

 

Thanks.

Posted

You really should be sending email to yourTCHaccount@yourTCHdomain.com to avoid any issues.

Posted
You really should be sending email to yourTCHaccount@yourTCHdomain.com to avoid any issues.

 

Thanks for the reply, Jim. The only reason I was using that machine servername was the way I had my external DNS setup. TCH's servers were the most preferred MX hosts, but in the event it fell through to my backup MX, I needed an external host to forward messages to. Unfortunately that caused a mail loop when the domains were left the same (ie: yourTCHaccount@yourTCHdomain.com). Using the myTCHaccount@server94.totalchoicehosting.com solved that problem until it 'broke' or was reconfigured.

 

No worries, I've managed to implement a cleaner solution anyway for now. But, if I wanted to, can myTCHaccount@serverXX.tchmachines.com be used as another method of reaching my hosting account?

 

Thanks!

Posted
Thanks for the reply, Jim. The only reason I was using that machine servername was the way I had my external DNS setup. TCH's servers were the most preferred MX hosts, but in the event it fell through to my backup MX, I needed an external host to forward messages to. Unfortunately that caused a mail loop when the domains were left the same (ie: yourTCHaccount@yourTCHdomain.com). Using the myTCHaccount@server94.totalchoicehosting.com solved that problem until it 'broke' or was reconfigured.

 

No worries, I've managed to implement a cleaner solution anyway for now. But, if I wanted to, can myTCHaccount@serverXX.tchmachines.com be used as another method of reaching my hosting account?

 

Thanks!

Hello,

 

The only way to use the server name for e-mail is if you use the default catchall account, this means using username@servername (username is the same username as your cPanel username) when it won't work is when you are trying to reach an additional e-mail account such as say mark@mydomain would work with mark@servername as the sever wouldn't know where to place the e-mail as there maybe more than one mark e-mail account on the server.

 

Forgot to add welcome to the forum, MaxHeadroom :)

Posted
Hello,

 

The only way to use the server name for e-mail is if you use the default catchall account, this means using username@servername (username is the same username as your cPanel username) when it won't work is when you are trying to reach an additional e-mail account such as say mark@mydomain would work with mark@servername as the sever wouldn't know where to place the e-mail as there maybe more than one mark e-mail account on the server.

 

Forgot to add welcome to the forum, MaxHeadroom :)

 

That's what I thought and have observed. When did the username@server94.totalchoicehosting.com change and require this function to be used as username@server94.tchmachines.com [notice the domain name]. That's what caused the bouncing which I was able to easily test and remedy.

 

Thanks for all the welcomes! Good to be here.

Posted

Hello,

 

Although I am not really sure when this functionality changed it looks like the hostname for the server was changed from server94.totalchoicehosting.com to server94.tchmachines.com which would mean if sending an e-mail to that server it would have to be sent to @server94.tchmachines.com in order for it to be fully processed.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...