Tag Info

New answers tagged

0

TL;DR: One of the two ISP's we are using blocks DNS requests from outside their network. DNS requests were occasionally coming from the other ISP's network... The fix: Implement a static route at the firewall for ISP DNS servers to use a specific interface, or use another service (like OpenDNS or Google DNS). The story: Well we found out what the problem ...


0

I'm not sure that your issue is resolved, but you have typed wrong MX weight for google MX records. yourdomain.com. 10800 IN MX 10 ASPMX.L.GOOGLE.com. yourdomain.com. 10800 IN MX 20 ALT1.ASPMX.L.GOOGLE.com. yourdomain.com. 10800 IN MX 30 ALT2.ASPMX.L.GOOGLE.com. yourdomain.com. 10800 IN MX 40 ASPMX2.GOOGLEMAIL.com. ...


1

First of all: Make sure, that "intra.contoso.com" is not in the Global Domain document of the domino server, otherwise it will be very hard to make the domino server send these mails out. Then create a Foreign SMTP- document for intra.contoso.com. Fill in like this: Internet Domain: intra.consoso.com Domain name: ExchangeDomain (Dummy Name, has to be ...


3

Not with an MX record, no. It's strictly inclusive. That sort of thing is typically done with an spf record. That DNS record is where you list what is allowed and not allowed to send mail.


1

Q: Is it possible to exclude certain addresses or wild card addresses using an MX record? A: No.


3

You are mixing up quite a lot of things here. The current email provider for the company only allows a single Office365 exchange account per subscription This is not how Office 365 licensing works. There are two options: 1. You subscribe to your licenses directly at Microsoft or office365.com. 2. You buy license subscriptions from Microsoft partners, ...


0

So I've just fixed this error by looking at my GoDaddy hosted domains (the ones that are not using CloudFlare) and adding some CNAME's and changing my MX records from what I posted in the question to: MX 300 0 smtp.asia.secureserver.net. MX 300 10 mailstore1.asia.secureserver.net. Basically I've just added ".asia" before "secureserver.net".


17

It would definitely create a problem if you were to point your MX records at CNAME records since it is against the standards. The clearest explanation is provided by RFC2181 ยง10.3: 10.3. MX and NS records The domain name used as the value of a NS resource record, or part of the value of a MX resource record must not be an alias. Not only is ...


0

Well, if I try to telnet mindspring.com:25, I am unable to connect, so I suspect that ServerHostname is a red herring. Clearly you are getting connected to a mail server, but it is requiring that you authenticate in order to use port 25. The 550 error you are getting is either because SMTP auth is turned on on the server you have connected to, or because ...


0

You don't specify your mail software but there are a number of options for this case. They can be combined. (I would recommend the first for all hosts not providing MX services. It should resolve your issue.) Configure the mail server to listen on the local host interface(s) (127.0.0.0, ::1) only. Configure the mail server to use a common server as a ...


1

What McAfee told you is definitely the recommended approach here. Spammers intentionally try direct connections for the exact reason you pointed out - they're trying to bypass perimeter defenses. The specifics depend on your environment, preferences, and details from McAfee. Here are some links to get you started: ...


1

My question is: Is there any added benefit of sending automated email from an email address with a subdomain? I don't think there are many technical reasons why a subdomain is required or necessarily better for deliverability of emails. That being said, having/using subdomains can sometimes make things easier for large organizations because: As ...


1

RFC2181 section 10.3 says you can't point your MX record to a CNAME: The domain name used as the value ... of a MX resource record must not be an alias.


10

The first MX means that the IP addresses in the MX record(s) for the domain you're actually attaching the SPF record to should be accepted as valid. The second one means that IP addresses in the MX record(s) for the domain mail.mydomain.com should be accepted as valid. If this SPF record is for the domain mail.mydomain.com, then the second one is redundant. ...



Top 50 recent answers are included