Emails do not reach their recipient - email

I have migrated my managed site by cPanel to another server that is also managed by cPanel, the problem I am having is that I try to send an email from my new host with one of my accounts and the mail never reaches its destination.
The problem occurs when within the body of the message I include images or urls of my site, for example:
If I include a <a href='https://example.com/register'>url</a> tag the mail never reaches its destination, also if I include something like <img src='https://mywebsite.com/images/logo.png'> these emails never reach their destination, but if I remove these labels the email reaches the destination without problems.
It should be noted that before the migration the mail service worked without problems.
Any suggestions or solutions to this problem?

Related

Magento doesn't deliver email to interal domain

I have this problem: let's say that my site is www.mysite.com; everytime cronjob sends mail to external domains, emails are correctly delivered.
But any email that contains #mysite.com, which is my domain, isn't.
I think that magento is trying somehow to deliver email to itself, but our email server is outside on a web hoster (aruba).
I've tried to modify "MX Entry Maintenance" into cPanel, and set that to "Remote", but nothing changed... I don't even know if that's the correct procedure.
How can I fix this? Where do I have to setup this configuration? Inside magento or inside the hoster ?

Google Apps email using wrong FROM address when sent from CFMAIL

Okay, so this is a really weird issue that's really just confusing the crap out of me...
I have a number ColdFusion sites running on the same dedicated server and have been noticing some really strange issues with mail sent from some sites using the <cfmail> tag.
Here is an example of a mail tag being used with a form on one of the websites:
<cfmail to="#cfmail.clientEmail#" from="#form.email# <#form.email#>" replyto="#form.email#" server="#cfmail.server#" username="#cfmail.username#" password="#cfmail.password#" subject="Request for info - #form.propertyName#" type="HTML" port="#cfmail.port#" useSSL="#cfmail.useSSL#">
(All of the cfmail scoped vars are being set in the Application file)
I do it this way so that the individual sites are not all using the in-house mail server, and instead use their own Google Apps account (DNS is set up properly).
Form submits, email sends, email is delivered...no problem, right?
Well...that's when things get funky.
Notice the FROM looks like this in the code:
from="#form.email# <#form.email#>
When delivered, it looks like this:
FROM : bob#someaddress.com <info#somerandomdomain.com>
When it SHOULD look like this:
FROM : bob#someaddress.com <bob#someaddress.com>
So, I checked - and re-checked the code. Everything is correct. Then, I checked the ColdFusion mail spooler...the text file generated there before the email actually leaves the server is CORRECT.
This leads me to believe that something is happening after the actual data reaches the google servers - somehow the email addresses are getting swapped out.
If it's any help, the mixed up from addresses are always email addresses that were set up a long time ago and then closed/abandoned for other sites I host on the same server.
And, another bit of funkyness to add...
This is happening to the TO addresses in some cases as well. Meaning, emails sent from different sites on the same server (using different Google Apps accounts and credentials) are ending up in the correct inbox AND other, unrelated, sites inboxes as well.
I've determined that the emails are correct as they leave the building on their way to Google (via the ColdFusion mail spooler) - but things seem to go all wonky after that.
Does anyone have any advice on this? The solution I've decided on for now is to move the clients to new mail providers...but this is not an ideal solution because of all the hassle involved in migrating their email over.

Website is not sending emails to email add on MS Exhange

Having problems with setting up my website to use MS Exchange to send emails. I dont want to use the hosts email system.
The MS Exhange has been set up, with email addresses created.
My webpages are using Persits.MailSender which the host supports.
Do i need to change MX records? A records?
Sorry, im not clued up with network side of things, any help would be appreciated
When i email direct, the email address on the exchange picks up the emails. BUT if i email through the website, it goes to the annoying webmail the host is provinding, and not to the exchange
I find this strange, the same email address receiving emails at different places!
Im using ASP, and I have a website set up, which has been sending emails for the last 12 months, the host has messed up (again) somewhere, but doesnt know what is wrong (as usual)
There are no errors, the email always gets sent.... but to the wrong place.
I would look into actually trapping and knowing your errors. That way you can see precisely why it fails and have something to work with. As it stands, your question isn't really answerable. No language nor framework is provided. We don't know if the mail server is confirmed to be working or accessible outside your netowrk; we don't know how your are referencing it or if you are passing user credentials; we don't know what error you're getting...
At this point, you're not debugging, you're just sort of swinging in the dark. Find the point of failure and then research that data point to get a solution. Debug, catch errors, log, step through your code. All good ideas.
Ok i figured it out, I deleted the mail domain on the host as that was the first place the website looks to send an email. Once the mail domain was deleted the emails were sent to the external hosted mailserver MS Exchange email address. Yay!

Sending an email from one server to another using same domain name

Just rebuilt a companies website, updated their A records to point to it's new server location but kept their email function as was.
Sending from the server works fine, and they receive mail from elsewhere fine but now when trying to send forms as emails to their existing addresses they never arrive.
For example trying to send an email (more specifically a Drupal Webform) from domain.com from Server 1 to email#domain.com on Server 2.
I've tried adjusting the send address from Server 1 which doesn't change anything. I think their IT person said something about receiving email at an exchange (Microsoft?) but I'm not savy this area at all.
Any ideas about this? I guess something is stopping it before it gets delivered (no spam) and the domains are conflicting, had a Google about but it's one of those where I'm not quite sure how to phrase the question. Thanks
SOLVED! In my CPanel I just needed to change my MX Entry to Remote Mail
Server Exchanger

Email aliasing with qmail

I'm trying to set up email domain aliasing in qmail (I'm on a Plesk server). What should happen is that emails sent to user#myalias.com get sent to user#realdomain.com (regardless of what user is). I would like this to happen without having to set up redirects and mess around with that sort of thing.
I've followed the details on this forum post with limited success. I only made changes to the qmail config as all other config is already there and correct as the myalias.com domain is set up through Plesk ...
modify /var/qmail/control/virtualdomains
add myalias.com:60 ("60" corresponds to the integer of the realdomain.com that is in the same file)
restart qmail service
Logs are showing that qmail accepts the incoming email to #myalias.com and then routes it to #realdomain.com. The email then goes missing and is never actually delivered.
Any thoughts on where/how I could dig deeper to figure out what's happening to the email?
Thanks.
Just following up on this older question of mine. It is all working well now. I had the NOC check the server and they corrected it for me. Had something to do with remotehosts file.
Does the logfile of realdomain.com show that it is even accepting or seeing the incoming redirects?
Try redirecting the email to another domain. If they end up at the other domain, then the problem lies with the domain you're trying to really send it to.
If they don't appear there at all, then it goes back to how they're being redirected and you can focus on that part.