I have multiple websites running on my server: domain1.com and domain2.com
The problem is now that when I sent an email via ASP.NET from `domain2.com`, that in this email source I see (notice `domain1`):
Received: from mail.domain1.com (h2134215.myisp.com. [81.112.2.12)
Received: from h2134215 ([81.112.2.12]) by domain1.com with MailEnable ESMTPA; Sat, 21 Jun 2021 22:17:29 +0200
Message-ID: <D9221D4FF6F74EC3877CC9368DDDAB94.MAI@domain1.com>
I'm using Mail Enable to send emails via ASP.NET like so:
Dim mailObj As New SmtpClient
mailObj.Host = localhost
I also tried:
Dim mailObj As New SmtpClient
mailObj.Host = "smtp.domain2.com"
Dim basicAuthenticationInfo As New System.Net.NetworkCredential("info@domain2.com", "mypassword")
mailObj.UseDefaultCredentials = False
mailObj.Credentials = basicAuthenticationInfo
In both cases my emails are sent.
Looking at my SMTP settings in MailEnable
[General] tab
Local domain name: domain1.com
Default mail domain name: mail.domain1.com
This is causing my emails to be rejected by some mailservers as spam.
How can I configure Mail Enable to use the correct email headers that match the domain from which I'm sending, `domain2` in this case?
Mail Enable email headers when sending emails via ASP.NET
-
- Site Admin
- Posts: 9738
- Joined: Mon Mar 22, 2004 4:44 am
- Location: Melbourne, Victoria, Australia
Re: Mail Enable email headers when sending emails via ASP.NET
Hi,
You will need to upgrade to the Enterprise version so that you can create postoffice IP bindings. This will allow you to bind postoffices/domains to specific IP address when sending outbound messages.
https://www.mailenable.com/documentation/10.0/Enterprise/Localhost_-_General.html
You will need to upgrade to the Enterprise version so that you can create postoffice IP bindings. This will allow you to bind postoffices/domains to specific IP address when sending outbound messages.
https://www.mailenable.com/documentation/10.0/Enterprise/Localhost_-_General.html
Regards,
Ian Margarone
MailEnable Support
Ian Margarone
MailEnable Support
Re: Mail Enable email headers when sending emails via ASP.NET
Hi Ian,
Thanks
A few follow-up questions before I consider upgrading:
1. Is this issue I describe really a potential cause for my emails to end up in spam? I Googled, but could not find this spam marking issue specifically, maybe you as an email expert know?
2. I use the standard version but it all runs on the same server (same IP address), but with different domains. I still need the Enterprise version? This can't be done with Professional?
3. I see this on the link you provided "The postoffice can have its own SSL certificate.". I have one master SSL certificate with many domains, I can reuse that master certificate for each individual postoffice?
Thanks again!
Thanks
A few follow-up questions before I consider upgrading:
1. Is this issue I describe really a potential cause for my emails to end up in spam? I Googled, but could not find this spam marking issue specifically, maybe you as an email expert know?
2. I use the standard version but it all runs on the same server (same IP address), but with different domains. I still need the Enterprise version? This can't be done with Professional?
3. I see this on the link you provided "The postoffice can have its own SSL certificate.". I have one master SSL certificate with many domains, I can reuse that master certificate for each individual postoffice?
Thanks again!
Re: Mail Enable email headers when sending emails via ASP.NET
*friendly bump*
-
- Site Admin
- Posts: 9738
- Joined: Mon Mar 22, 2004 4:44 am
- Location: Melbourne, Victoria, Australia
Re: Mail Enable email headers when sending emails via ASP.NET
Hi,
If your messages are ending up on the remote servers recipient junk email folder then the first step is to review the following article and ensure you have implemented DKIM, SPF and a valid PTR record for your domains.
https://www.mailenable.com/kb/content/article.asp?ID=ME020241
If your messages are ending up on the remote servers recipient junk email folder then the first step is to review the following article and ensure you have implemented DKIM, SPF and a valid PTR record for your domains.
https://www.mailenable.com/kb/content/article.asp?ID=ME020241
Regards,
Ian Margarone
MailEnable Support
Ian Margarone
MailEnable Support