Using SMTP's domain vs sending domain??

X

xRed

Member
Hi,

I am a bit confused. I have just added a sending domain since without it I was unable to add SMTP.

Here I have one sending domain and an SMTP which has its own domain, so when I am sending via this SMTP node which domain will be using in the emails which would be sent from this SMTP?

I will be adding many more SMTP's and if I use only one domain for tracking links etc for all the SMTPs then all will be blacklisted in one campaign only.

I want each sending node/SMTP to use its own respective domain when sending and for tracking instead of using same sending domain for all SMTP's

Can anyone please help me clarify this doubt and tell me what settings do I edit?

Thank you!
 
The domain that you chose while setting up the sending node (SMTP), that domain will be responsible to appear in email headers. So e.g if you want to add 50 SMTPs with all different domains. You'll need to add 50 Sending domains and then add 50 SMTPs and assign their respective domain. The domain that you set in Send-From while setting up Sending Node is responsible to send emails.
 
wasif said:
The domain that you chose while setting up the sending node (SMTP), that domain will be responsible to appear in email headers. So e.g if you want to add 50 SMTPs with all different domains. You'll need to add 50 Sending domains and then add 50 SMTPs and assign their respective domain. The domain that you set in Send-From while setting up Sending Node is responsible to send emails.
Click to expand...
Thanks thats what I thought, but this wasn't the case in mumara classic correct?

I simply used to add a SMTP and when sending campaign it automatically used to send from the selected SMTP domain, because AFAIK it wasn't mandatory to add a sending domain when configuring SMTP.
 
In Campaigns, we have made things more optimized to avoid mistakes done by clients while setting up campaigns. In Mumara Campaigns, you also have an option to fetch sender-info from Sending Nodes (SMTPs) while scheduling the broadcasts.
 
wasif said:
In Campaigns, we have made things more optimized to avoid mistakes done by clients while setting up campaigns. In Mumara Campaigns, you also have an option to fetch sender-info from Sending Nodes (SMTPs) while scheduling the broadcasts.
Click to expand...
The thing is I am having a LOT of hassle adding the same smtp domain as sender domain because I use a script to install SMTP and it requires me to use my own nameservers(ns1.mydomain.com) hence I am unable to add CNAME record(for sending domain verification) on the same domain because then DNS its not editable unless I use registrars DNS.

So either my SMTP will work or my domain gets verified in mumara but I can't have both which makes sending node useless for me.
Can't seem to find a solution for this.
 
I am still confused, you can explain in a bit more detail. I am not sure why you are adding the same domain again and again. You can just link a sending domain to as many sending nodes as you want.
 
wasif said:
I am still confused, you can explain in a bit more detail. I am not sure why you are adding the same domain again and again. You can just link a sending domain to as many sending nodes as you want.
Click to expand...
Sorry I am not good at explaining things but I'll try again haha.

Lets say I have one smtp server configured on "mydomain.com"

Here I am unable to verify "mydomain.com" in my mumara panel as I don't know how to add CNAME and TXT(DKIM) record because its nameservers are "ns1.mydomain.com" and "ns2.mydomain.com". Due to this I can't change DNS settings in my registrar cause I am using my own domain's nameservers. So is there a alternate way to add TXT and CNAME record (for domain verification)??



Another scenario that can avoid all this hassle altogether is, can I use a WHOLE other domain as sending domain that is different that my SMTP domain? Or will it just make my mails marks as spam?



Because unless I resolve this little issue I am not sure how useful mumara campaigns is for me(I have unsubscribed last week due to this only reason) and I am unable to afford to someone to look into this issue(this is a very small problem but since I have limited knowlegde in DNS field I am unable to solve it).
 
As you are using private nameservers so it means you are hosting the DNS inside your own server. So there are two suggestions

1- Use a control panel in your server e.g. cPanel or any other panel that comes up with the DNS Zone editor and allows you to insert custom DNS entries. If your server is a minimal installation then you have to be more technical and should know how to host custom DNS records inside it.

2- Shift your domain to a free or paid DNS provider e.g. CloudFlare or clouDNS etc and manage the DNS there.

And regarding your other question, what are you referring to the SMTP domain? Is it responsible to appear in Email headers or you are referring to the Reverse DNS and Forward DNS domains? It's suggested if your sending domain and the FDNS/RDNS domains are the same, unless you are using an ESP. However, you can keep your domains separate as well. But it's important that your FDNS and RDNS records (FQDN) should match each other.

Let me know if you understand!
 
wasif said:
As you are using private nameservers so it means you are hosting the DNS inside your own server. So there are two suggestions

1- Use a control panel in your server e.g. cPanel or any other panel that comes up with the DNS Zone editor and allows you to insert custom DNS entries. If your server is a minimal installation then you have to be more technical and should know how to host custom DNS records inside it.

2- Shift your domain to a free or paid DNS provider e.g. CloudFlare or clouDNS etc and manage the DNS there.

And regarding your other question, what are you referring to the SMTP domain? Is it responsible to appear in Email headers or you are referring to the Reverse DNS and Forward DNS domains? It's suggested if your sending domain and the FDNS/RDNS domains are the same, unless you are using an ESP. However, you can keep your domains separate as well. But it's important that your FDNS and RDNS records (FQDN) should match each other.

Let me know if you understand!
Click to expand...

Thanks for the answers :)

By smtp domain I simply meant the domain on which smtp is configured.


Right now I went with this solution of using whole another domain as sending domain which is different than the domain on which smtp is configured.
 
You must log in or register to reply here.
Back
Top