Problem with 'send as' from new gmail account

Savvy_Sue

For new starters at work I set up two email addresses: newperson.ourcharity@gmail.com, and then newperson@ourcharity.org.uk using 123-reg

Then I go into the gmail account and set it to send from the @ourcharity.org.uk address. This used to be really simple, but now involves setting an app specific password, using information supplied here.

This was all working fine until last week: I set up a new address, did the send as thing, and we keep getting this message:

Delivery to the following recipient failed permanently:

[EMAIL="jfarrand@gmail.com"]whoever@wherever[/EMAIL][EMAIL="jfarrand@gmail.com"].com[/EMAIL]

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the relay smtp.gmail.com by smtp.gmail.com. [64.233.163.109].

The error that the other server returned was:
535-5.7.8 Username and Password not accepted. Learn more at
535 5.7.8 http://support.google.com/mail/bin/answer.py?answer=14257 lf12sm6421433lac.38 - gsmtp
(SMTP AUTH failed with the remote server)

I've read the article they link to, it doesn't seem directly relevant but I've tried resetting the Google Apps password, and I've tried the Unlock Catchpa, that doesn't seem to help either.

BTW, this is only accessing gmail from a computer. We don't need mobile access to our emails, so no mobile devices or apps are involved.

Any suggestions, or has gmail just decided we can't do this any more?

grumpycrab

Do you get an SMTP server with 123-reg? First check it works (using 123 reg webmail) then try it as the SMTP server in the "send as thing"?

(123-reg SMTP info)

• Check that you have entered the correct outgoing mail server: smtp.123-reg.co.uk
• Ensure that the options for My server requires authentication and Use same settings as my incoming mail server are enabled.
• Use default outgoing smtp ports 25 or alternatively if port 25 is blocked please use port 587 or vice versa.
• Ensure that the option for SSL is switched off, if switched on please use port 465

Savvy_Sue

I'm not sure we do but I'll give that a whirl tomorrow.

When this problem first cropped up I spoke to 123-reg and established that we'd have to pay silly amounts per month to run our email through them, other than doing the straight forwarding (which I forgot to mention in my first post ...)

Savvy_Sue

Our external tech support chap arrived on Thursday (my day off) and says he's fixed it by switching two step verification back on - you have to have it on to set the App Specific Password, but I've switched it off after that.

In case anyone else was wondering ...