UPCP Cron Email Not Forwarding?

Hello all,

We have a very weird issue!

We have all root emails being forwarded to an external email address ('Edit System Mail Preferences' all have the external email address set), however, even though we receive emails being forwarded there is one that does not...it simply goes to the local root@whm1.domain.com address....which obviously fails delivery.

Here's the failed email header:

Anyone seen this?

 

Thanks for the reply.

Forwarding to our own dedicated email server. We have full control over the server....the email is not getting there as the sub-domain stated is only the sub-domain for the WHM server.

This particular WHM server does not deal with mail, only web. All other root emails are forwarded correctly to the external mailbox. It's just the Cron job as outlined above.

We have a good few WHM servers setup in near the same manner and all emails are forwarded normally. However, for some reason the nightly WHM UPCP Cron job on this particular server is still going to local root@.

 

The sub-domain is the hostname.

I'll check the email logs, however I think this is to do with configuration before it gets to the email as the address is incorrect.... If it was specifically email related it would be at least trying to email to the correct address.

I'll take another look at the mail queue tomorrow morning and if it's still trying the wrong address I'll open that ticket.

Cheers

 

Thanks.

Had a look and it seems as though because the main domain which is part of the hostname isn't hosted on that WHM instance it is classing it as a local delivery....but weirdly we have other servers setup using WHM with a different sub-domain as the hostname and they are fine.

So, for instance, we have cloudwhm2.domain1.com as a hostname for one WHM VPS and all emails route to cloudwhm2@domain1.com...and they are all work. However, this particular WHM VPS which we are having this issue with is set up with similar config (whm1.domain.com as hostname and emails forwarding to whm1@domain.com) but doesn't work for the UPCP cron job email.

 

Yes, the hostname is 'whm1.domain.com'. Which is obviously a FQDN. This is so we can set the server IP address against that sub-domain.

 

Interesting. Going by the quote, we have got it right. It is a FQDN. It's also not used by anything else. However, we do add the hostname (whm1.domain.com) to our DNS with the main server IP address. I really can't see that being the issue...all other servers we have are FQDN with a DNS entry. It just wouldn't make sense not to add the entry...otherwise how would we add an SSL for whm1.domain.com if there was no DNS entry....something weird here.