Detailed explanation of the instance where GITLAB email does not send Tencent enterprise email

Don’t talk nonsense, just give me the idea

After gitlab is redeployed, new users will not send activation emails. The configuration is as follows:

gitlab_rails['smtp_enable']=truegitlab_rails['smtp_address']="smtp.exmail.qq.com"gitlab_rails['smtp_port']=465gitlab_rails['smtp_user_name']="name@domain.com"gitlab_rails['smtp_password']="pass"gitlab_rails['smtp_domain']="doamin.com"gitlab_rails['smtp_authentication']="login"gitlab_rails['smtp_enable_starttls_auto']=truegitlab_rails['smtp_tls']=truegitlab_rails['gitlab_email_from']="name@domain.com"

First confirm that the configuration is OK. Secondly, check the log production.log

log and no error message is given. Then just activate the ultimate move

sudo gitlab-rails console production

irb(main):001:0> ActionMailer::Base.delivery_method=> :smtp

Make sure the method is smtp. If it is wrong, the configuration is written wrong or it is not loaded correctly

irb(main):002:0> ActionMailer::Base.smtp_settings=> {:address=>"localhost", :port=>25, :domain=>"localhost.localdomain", :user_name=>nil, :password=>nil, :authentication=>nil, :enable_starttls_auto=>true}`

Make sure the configuration is what we want

irb(main):003:0> Notify.test_email('youremail@email.com', 'Hello World', 'This is a test message').deliver_now

Send a test email, detailed errors will be printed

TX returns a 553 error and a link address

At this time the truth is revealed, using a third-party client to log in to the QQ mailbox requires an authorization code instead of the password

The above is the detailed content of Detailed explanation of the instance where GITLAB email does not send Tencent enterprise email. For more information, please follow other related articles on the PHP Chinese website!