Password reset email not sending
 

Hi all. When users try to use the password reset function on my forum (3.7.2), they never receive the email. As admin, I do not have this problem, so I know email itself is functioning properly, but all other usergroups appear to.

Is there a setting I'm missing somewhere?

Is it possible that the people having problems all have gmail or something like that? Sometimes one of those services will block a server for spam or some reason like that.

Looks like that's the case. I'm on Gmail and it works fine, and it works for others on Gmail, but users who are on Hotmail and Yahoo can't receive the email. Knowing this helps, but at the same time it doesn't. I'm an experienced IT guy, but I do next to nothing with mail servers.

I've found instructions on how to get removed from Hotmail and Yahoo blacklists, but they're asking for information I'm not sure I have access to. Where would the outgoing mail logs be for the PHP mail system that VB uses?

EDIT: Might it be because the email address we use for the password reset message comes from an @gmail.com address when the actual server is @fasthosts.net.uk? Even Gmail pops up a phishing warning. Hotmail and Yahoo might just be blocking it outright. I'm not sure that's something that can be helped, though, because Fasthosts is the host, but the email address would still be @somethingelse.co.uk, and it would likely trigger the same filters.

I don't know much about it either. I don't know where the logs would be (or even if all outgoing mail is logged), but someone else might. I guess if you have vb configured for "SMTP Email" then there might be a log on whatever server the smtp is running on, otherwise I don't think there would be a log unless the php mail function keeps one.

It might be a good idea to talk to your host about it, maybe they have an alternate server you can use for outgoing mail.

Or maybe this will help: http://www.fasthosts.co.uk/knowledge...article_id=320

If you set "SMTP Email" to yes (under Email Options in the admin cp), then enter smtp.fasthosts.co.uk as the SMTP host.

Interesting.

If I use smtp.fasthosts.co.uk, I still get the phishing warning because of the email address listed as the sender, so it probably still wouldn't work (but we're not worse off than we were before). I'm still going to have someone test it, though.

If I use smtp.gmail.com with TLS/SSL and port 587 as per here, I get Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error." which is obviously less than helpful.

If I try the same but going to AdminCP > Settings > Options > Cookies and HTTP Header Options and turning off gzip, I get If I use TLS/SSL with port 465, it acts like it's going to send the email but I get nothing (which is what Hotmail and Yahoo users see).

I missed your edit above - I really don't know if the email mismatch would cause hotmail to reject it or not.

I think the "Failed to enable crypto" message might mean that php on your server isn't configured to allow encrypted connections (as it says in the comment for that option, openssl has to be compiled in to php).

Yeah, and given my host, the chance that I'd get that request done is exceedingly small. I'd really love to move everything for a number of reasons, this being but one, but I just can't be bothered. My luck I'd just break the database and then...well, I guess I wouldn't have to worry about the forum anymore. :)

At any rate, I'm going to get someone on Hotmail to test using the smtp.fasthosts.co.uk setting, and if that doesn't work, I guess we'll have to manually deal with requests from affected users. There can't be that many folks with Hotmail and Yahoo accounts, can there? :(

--------------- Added [DATE]1378848962[/DATE] at [TIME]1378848962[/TIME] ---------------

This just got weird. One of the users who cannot get the password reset email DOES get the automated happy birthday email. Obviously, the latter is far from critical, but of course that's what goes through.

--------------- Added [DATE]1378861897[/DATE] at [TIME]1378861897[/TIME] ---------------

Enabled -f parameter. It worked. I ignored that because it says, "In all likelihood, your problem will not be caused by this setting." I hope that in future versions they've amended that.

Wow. I don't know what that does, but I'm glad you got it working.