Closed (fixed)
Project:
Email Verify
Version:
7.x-2.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
10 Oct 2015 at 01:53 UTC
Updated:
29 Nov 2016 at 02:54 UTC
Jump to comment: Most recent
Comments
Comment #2
2phaComment #3
oadaeh commentedSorry for not responding to this earlier.
There is not, but it should be simple enough to add it.
There shouldn't be any, since many other systems and websites make similar checks.
Yes, I suppose it could, though it's probably not likely, but it really depends on how careful/paranoid/ignorant/incompetent/choose-your-adjective the administrator of the mail server is.
Please note that the referenced error message:
is rather vague and will be challenging to pin down, especially when followed with
which says "may," and implies "may not" and "may be related to something else entirely."
So, addressing those two specific things mentioned, first
should not be related to this module, since there is no actual content included with the test (unless that is considered "content with spam-like characteristics"):
The second one:
would not be related at all to this module, but to the IP address of the server the site is hosted on and the IP address and domain name for the From address, which is defined as:
and located on the Site information configuration page at /admin/config/system/site-information.
You will need to research this yourself, and that may be best started on Microsft's policy page, here: https://mail.live.com/mail/policies.aspx, especially at the Reputation Management section, although there are certainly numerous resources on the Internet to help.
Comment #4
fonant commentedI can confirm, from having run my own public "email address validator" (now taken down to restore my server's reputation), that Microsoft servers will block any server that performs multiple "will this address accept mail?" tests using SMTP without actually sending a message.
This makes sense, as spammers would find a list of valid email addresses at a given domain extremely valuable.
Testing for an existing MX record is perfectly safe, but talking to the MX server to just test whether an email address accepts mail can indeed result in a block on your server's IP.
Comment #5
2phaThanks guys for the follow up on this.
I have since taken the website down that was implementing this module.
After researching and trying to find the cause (a few months ago now), I do believe it was this module that was causing the problem. I only have 2 other websites on the same ip (Linode) and did not have a problem before implementing this module.
This seems to be backed up by what fonant has said.
Comment #6
oadaeh commentedI created #2827654: Provide a way for an admin to specify which tests to run to deal with the idea of selecting which tests to run when verifying.