I am trying to use phplist in a different server than the domain that I want to use it as a sender. Is is possible?
To clarify my question:
my phplist is installed in example.com
The domain that I want to use as sender is example1.com (in another
ip than phplist)
I would need some help on how I have to set up my dns settings in both servers.
(In phplist settings I use smtp credentials of info#example1.com)
Please let me know if I need to clarify something better.
It's perfectly acceptable for a domain to be associated with more than one server in various ways. You don't have to do anything special to send from a different domain, but it would be a very good idea to add the IPs to the SPF record for the domain you're sending from. For outbound you don't have to do anything in DNS - to deal with bounces you can use a return path in your sender domain rather than the from domain.
Hi you have ask a good question about adding a new domain to the phplist.
If you need to set up a new from emails using the domain example1.com, go to campaign setting, and add the new from email address in your case whatever#example1.com.
Also you need to add an spf record to the dns area of example1.com, to allows your IP addresses to send emails from domain example1.com.
you can use spf wizard to generate the spf reccord https://www.spfwizard.net/
wish that all you need.
Related
BLUF: Can I add a TXT record (SPF) for a PTR record with no other records for the domain in our DNS?
Sorry, I don't know how to put a good title to this. I've inherited a DNS server and in one of our zone files we have a mail subdomain defined for a customer of ours.
Zone file 103.102.101.in-addr.arpa.dns
74 IN PTR mail.example.com.
74 IN TXT "v=spf1 mx a ip4:101.102.103.74 ~all"
This client wants us to add an SPF record and as far as I know we have no other entries for this client in our DNS except for this one PTR record. I'm not really sure how this situation began as this was all set up before my arrival and no one else where I work has any technical background on this. I just don't want to waste their time and since I'm not sure how to ask this question concisely, Google search hasn't been very helpful so far.
Much appreciated for anyone that can chime in.
If you are routing the email for them then you know what the domain name is.
Using that, use the DNS query tools to find out where the domain name is hosted and let them know they have to contact the domain name hosting company and have the SPF entry added. At the same time they should inquire if the hosting name server has DKIM DNS keys. If they do, ask them to also assign the DKIM and DMARC keys so that the domain can also block spoofed spam and attachments. Spoofed emails have been one of the biggest entry points for hackers and network takeovers using ransomware. SPF and DKIM / DMARC together with a check policy on the mail server is the standard in defence against this. Also be sure to use TLS or SSL via the SMTP to encrypt the emails for further protection. You can get a 1 year SSL cert from any of the SSL cert registrars for the domain on the web. I find ZeroSSL has the best prices. You will have to get who ever resisted the domain to help in confirming the SSL when registering it or access to the domain DNS to add a TXT record key that is supplied by the SSL registrar. Its not complicated but is very strict and you cant do it without access to either the email address that originally registered the domain or access to the domain hosting servers DNS to add the supplied TXT key for the domain.
Good luck :)
Go here for the tools you need. https://dnschecker.org/all-tools.php
I am having some difficulty setting up my SendGrid account to connect to my DNS on Cloudflare and enable custom domain whitelisting for two domains.
My plan is to deploy emails from my Clickfunnels' Actionetics account. Currently, my integration into Clickfunnels is a success and I was able to receive an automated test e-mail (from my custom domain) to my personal email address. I understand that I should be able to send emails from any e-mail address I need (support#domain.com, hamid#domain.com, info#domain.com) without needing to physically needing to go through any setup process to get these emails up and running. Initially when I went through the SendGrid setup, I needed to add 3 CNAMES to my Cloudflare DNS. Everything successfully installed without any issues from Cloudflare. After speaking with Support, I was told that I might need to retry the whitelabel wizard with automatic security off. Going through this wizard should give 2 txt's and one MX (mail exchanger) record instead of 3 CNAMES.
"Automating security allows the system to redirect ISPs to SendGrid to check DNS records that follow strict security protocols and are custom to your account. Due to a character limit on TXT records, we are only able to create a custom SPF (sender policy framework) record for users with up to 11 IP addresses. This will not affect deliverability. You would have to go through the whitelabel process again."
If you have experience in this type of issue, please let me know what you think.
This is one method the I recommended.
“white-label the domains again but this time completing it with automatic security turned off. Going through this wizard should give 2 txt's and one MX record instead of 3 CNAMES.”
"Automating security allows the system to redirect ISPs to SendGrid to check DNS records that follow strict security protocols and are custom to your account.
Due to a character limit on TXT records, we are only able to create a custom SPF record for users with up to 11 IP addresses. This will not affect deliverability. You would have to go through the white-label process again."
Thanks, I hope you can resolve this.
I can't understand your question.
SPF is kind of TXT record, it can help receiver know email comes from right ip address.
Whitelabeled Domains help receiver know email really comes from the right server.
Sendgrid need a subdomain and two well-know subdomain to verify your identity.
I have domain name(exmple.com) and DNS. I want email at admin#exmple.com is forwarded to mymail#gmail.com. there is any way to forwarding using MX recoder in DNS. If it is possible tell me how to update MX record ?
Thanks
It is not possible. The MX record answers the question "To send an email to a given domain name, which host should I contact?". Since what you want to do involves the local parts of email addresses, it falls outside of the realm of DNS.
I have a website "example.com" with email user "anyname". I also have a domain name "other.com" with zone records pointing to "example.com". if I email "anyname#other.com" I get either a user not found or a relay not allowed message.
I have found no way to modify "other.com"s MX records to allow this.
I have also played with mod rewrite to no good effect.
A domain name that we have is using google mail as its backend, but its not hosted anywhere (no website). How can I, through the registrar interface (I'm using 1&1), redirect ppl who type in http://mail.example.com to http://mail.google.com/a/example.com ?
I can create a subdomain and set its DNS/CNAME, but what do I put where? Also, if I make this change will it affect the existing mail delivery (for which everything is running fine presently).
It turns out it wasn't that tough... and the instructions are part of Google itself:
Dashboard -> Service settings: Email -> General:Web address -> Change URL
https://www.google.com/a/cpanel/example.com/CustomUrl?s=mail
Changing CNAME record
To use the custom URL mail.example.com, you must change the CNAME record with your domain host.
Sign in to oneandone.
Navigate to your DNS Management page. The location and name
of this page will vary by host, but
can generally be found in Domain
Management or Advanced Settings.
Find the CNAME settings and enter the following as the CNAME value
or alias:
mail
Set the CNAME destination to the following address:
ghs.googlehosted.com
Save changes with your domain host and click "I've completed
these steps" below.
You cannot redirect to a path (such as /a/example.com) using only DNS. DNS CNAME records can make mail.example.com/foo effectively point to mail.google.com/foo, but something more sophisticated will require HTTP redirects. This means you need someone hosting your web page for this to work.
Sorry.
If your registrar offers an "HTTP Redirect" option, you can use that. Some registrars do. If you use this, they're effectively running a minimal web server for you. Note that this may break SSL when users access your page via https://example.com.
Mail delivery is via MX records, which won't be affected by changes to other types of record (so long as you don't interfere with the DNS records for the domain's mail servers).