Not able to log in using google/launchpad account - confirmation email is not received

I have the same error, right now

Me too, the whole login/signup is broken!!

This is probably similar to or related to:
https://bugs.launchpad.net/openstack-community/+bug/1742568

Also possibly related, and could well be the cause:
https://bugs.launchpad.net/openstack-community/+bug/1723264

The IP is not listed in Spamhaus anymore. Can you please check if now the confirmation email is sent?

I just tried it with a gmail address, as well as with a address that is running on my own mailserver. I didn't receive the mail to the gmail account, but now I did receive the one to my own server. So it seems like something has changed since both didn't work when I posted this bug - however gmail still declines the mail (it's also not in the spam folder there).

Anyways, I've managed using openId for login before - I tried to ask two questions on ask.openstack since and both are declined because the spam filter thinks they are spam. (They certainly aren't though....)

@fungi I need your help to debug this because I have no access to the machine's logs

@baaoo I have approved a post held in moderation by user 'flusel' (mis-classification of spam is a different issue: open a separate issue please if you're not flusel)

The MTA logs indicate that Gmail is deferring/rejecting some messages, but Google is notoriously vague about why. Rejections from some other non-Google MTAs note that the server has become listed in the Mailspike blacklist, and per separate bug 1745512 I've put in a delisting request there. Some rejections also claim the server is covered by a Spamhaus PBL entry but their lookup form disagrees as of today at least (perhaps some MTAs are relying on very stale/cached results?).

Google and others require SPF/DKIM and all the modern shebang before they even start looking at incoming mail. Does the domain have all that? Also, there is IP reputation to keep in mind and since this server has come on and off RBLs, the reputation may be low.

The easiest solution is to hook this up to a mail delivering service like Mailgun and similar. Otherwise, maybe consider using mail.openstack.org which has higher reputation? The drawback is that people may start marking mail from ask.openstack.org as spam (instead of changing their preferences) and take mail.o.o's reputation down. Tradeoffs :(

Per the discussion in bug 1745512 this service is also not listed in the SPF record for openstack.org even though it is sending messages as <email address hidden> so could consider either using a valid @ask.openstack.org address (for which we could set up a corresponding MX record and mailbox somewhere), or get added to the SPF record. That SPF record ends in "?all" though, which per the specification should mean it just gets treated as if there were no SPF record when a sender doesn't match. Nonetheless, some receiving MTAs incorrectly treat ? (neutral) like ~ (softfail) or even - (fail) so it _may_ help.

Google however does not *require* SPF/DKIM before they start looking at incoming mail. We successfully send non-DKIM-signed messages from addresses whose domain part has no corresponding SPF record to @gmail.com addresses on a regular basis, so the answer is certainly somewhat more nuanced than that.

Since the Mailspike BL removal yesterday I'm seeing basically no rejections in the MTA log (other than for qq.com addresses). People who were previously having trouble with new account creation should try again and update here if the confirmation E-mails still don't make it through so we can dig deeper.

I have tried to create an account using launchpad using 4 different email addresses and unfortunately I haven't received an email on any of the addresses.

Assuming this is about the ask.openstack.org site, our provider apparently placed the netblock for this server's IPv4 address into the Spamhaus Policy Block List recently. I have filed for an exclusion which should take effect within the next hour. https://www.spamhaus.org/query/ip/23.253.72.95

This morning I was able to receive the confirmation email on a @hotmail address. However, I am still unable to receive confirmation emails on other domains with differently configured mail servers.

I highly suspect that ending the spf record with '?all' does not suffice for some mail servers. As it is deemed as 'neutral' and not an actual 'pass'. The headers in the email I received at the @hotmail address back this up:

Authentication-Results: spf=neutral (sender IP is 23.253.72.95)
smtp.mailfrom=openstack.org; hotmail.com; dkim=none (message not signed)
header.d=none;hotmail.com; dmarc=none action=none header.from=openstack.org;

This tool can also be used to further validate spf records: https://mxtoolbox.com/SuperTool.aspx?action=spf%3aopenstack.org&run=toolpage

In my personal experience having a 'pass' on the spf record has a big positive influence on the amount of email that gets successfully delivered.

I can confirm myself that having correct SPF/DMARC entries is KEY on assuring that your email does not endup ignored by most big email services around.

It would help significantly in debugging this if we could get actual mail delivery failure logs/records. We can look at the mail server on ask.openstack.org if you can provide a recipient email address and approximate time for the expected email. Can you get that information to us? Might also help to do this synchronously on IRC as well (freenode #openstack-infra) so that we can find answers to the next questions that pop up.

Robert: Please try again when you have time. The server hosting ask.openstack.org was rebuilt a little over 2 weeks ago (on May 20), and it wasn't noticed at the time that the IP address assigned for it was covered by a Spamhaus Policy Block List entry maintained by the service provider. An exception has been added to the PBL for this address now, and any providers checking against it should hopefully cease to see it listed as disallowed (very soon at least, if not already).

still having the same problem
I just tried with google and launchpad accounts, and still not getting a verification email

This time I'm unable to find the server on any obvious blacklists, but Gmail is rejecting the confirmation message addressed to you claiming "Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked."

Askbot confirmation messages are sent from the <email address hidden> address, so either adding it to your expected contacts list or creating a sender whitelist entry per https://support.google.com/a/answer/2364632 might help (I'm not a Gmail user and never have been, so this is merely what I was able to turn up with a Web search).

I just tried again on a email address managed by axc.nl and managed to receive the confirmation email for becoming a community member. Both the SPF record and DKIM tested out as valid so at least that has been improved.