New Users doesn't receive Email Confirmations on latest build but SMTP Ruby Test works

Hi Guys. I just installed on a local server Ubuntu 18x the EE latest Version of Gitlab. Configured over Weekend. Works so fare excellent, except new User Inivationen. Ruby Console output for Notify.test_email('andre.grueter@myDomain,ch', 'Message Subject', 'Message Body').deliver_now

works like charm and reach: Sent mail to andre.grueter@myDomain,ch (2095.9ms) Date: Sun, 06 Jan 2019 19:06:12 +0000 From: QuadCom Continous continous@myDomain.ch Reply-To: QuadCom Continous continous@myDomain.ch To: andre.grueter@myDomain.ch Message-ID: 5c3251a544584_23443feef5ddc600739f4@dev.mail Subject: Message Subject Mime-Version: 1.0 Content-Type: text/html; charset=UTF-8

But, any new created interal or external user never receive an Invitation E-Mail. Now lets grep some logs: Application.log:

January 06, 2019 15:25: Administrator created a new project "Administrator / pages-test" January 06, 2019 16:18: User "Adam Obuchowski" (adam.obuchowski@myDomain.ch) was created January 06, 2019 18:16: Administrator created a new project "Administrator / GitLab Docs" January 06, 2019 19:04: User "Andre Grueter" (andre.grueter@mydomain.ch) was created

So log and time stamp on Application Level is fine.

Production.log:(From Elastic) Completed 200 OK in 54ms (Views: 1.6ms | ActiveRecord: 0.0ms | Elasticsearch: 0.0ms) Sent mail to andre.grueter@MyDomain.ch (2095.9ms) [ActiveJob] [ActionMailer::DeliveryJob] [e551debd-74ae-462f-8e0f-4c1154c46235] Performing ActionMailer::DeliveryJob from Sidekiq(mailers) with arguments: "Notify", "new_user_email", "deliver_now", 8, "wZTNHEpFfSw6huMA9eLy" [ActiveJob] [ActionMailer::DeliveryJob] [e551debd-74ae-462f-8e0f-4c1154c46235] Sent mail to MyDomain.ch (44.9ms) [ActiveJob] [ActionMailer::DeliveryJob] [e551debd-74ae-462f-8e0f-4c1154c46235] Performed ActionMailer::DeliveryJob from Sidekiq(mailers) in 145.35ms

This Logs has been generated from Ruby Console over TestSMTP Command.

Now checking the mail logs on my kerio connect mailserver, and I see:

Hostname of sender is not equal from Ruby Confs of Gitlab: It takes as MailHost Sender "Hostname" and of course something also other struggles into it, is: default Root/Admin User has an e-mail address: admin@example.com

If you change it under /accounts/preferences it takes effect, but not for the "user profile" its self. So you need to change it there properply too, other wise you send out:

E-Mail SMTP Output: <admin@example.com>, Result: failed, Status: 5.3.0 Message was manually deleted from the queue, Remote-Host: 127.0.0.1, Msg-Id: <5c31213c5724e_38f73fca23c2400c848f@dev.mail>

and this lands on any mail queue or will get rejected. Means: the SMTP Configuration on Ruby Level doesn't take properly effect. Unless you alter your hostnames accordingly, to a dns name which is resolving.

@dev.mail>` --> dev is our hostname where Gitlab Omnibus runs. Its an ugly addon: .mail

A further aspect is, that if you change a user account main email address, it won't take effect unless you restart gitlab. I think it would be a good option to update your pages and mention, that for example on debian hosts, the hostname should be resolving over dns, since many mailfilter simply blocks a smtp sender which doesn't resolve.

-- I was looking around here, and it seems from time to time a raising issue... but I would be super happy to get an advise or hint, because continuation management without users makes not really fun :-)

Edited by Buzzy3