Configuring Service Desk
-
@girish
Sad me, I blew it away about 5 minutes ago - I am seeing it now though!
Now, I'm not sure what to plug in to the config section:
Is address
git@apps.thedoodleproject.net
and user/password my credentials or did a service account of sorts get created or ?@doodlemania2 Did you create a mailbox named
git@
already ? After you have done that, I would first test if incoming email integration works is general. For example, create a test project and see if you can mail in issues. You can then enable service desk in that project and you can mail in service desk requests as well. This should all work out of the box.You need the "custom address" for Service Desk only if you don't want "git@" for the Service Desk but something else like "helpme@" or something. For the latter case, you have to create a mailbox named "helpme@" and then put the password of that mailbox into the configuration.
-
@doodlemania2 Did you create a mailbox named
git@
already ? After you have done that, I would first test if incoming email integration works is general. For example, create a test project and see if you can mail in issues. You can then enable service desk in that project and you can mail in service desk requests as well. This should all work out of the box.You need the "custom address" for Service Desk only if you don't want "git@" for the Service Desk but something else like "helpme@" or something. For the latter case, you have to create a mailbox named "helpme@" and then put the password of that mailbox into the configuration.
@girish Got it! Now that I read the instructions more clearly, it makes sense.
Now - when I send a message to my "private" issue repo (git+derek-test1-2-dmpv512f9bq1v22fe7mehyc4x-issue@mydomain.com) it lands in my catch all address bucket and not in Gitlab.
Do I need to unconfigured catch-all?
-
@girish Got it! Now that I read the instructions more clearly, it makes sense.
Now - when I send a message to my "private" issue repo (git+derek-test1-2-dmpv512f9bq1v22fe7mehyc4x-issue@mydomain.com) it lands in my catch all address bucket and not in Gitlab.
Do I need to unconfigured catch-all?
-
@doodlemania2 can you see if the mail room service is running by
supervisorctl status
in the Web terminal ? Also, can you check if there are any errors in the logs? -
@girish
That could be the situation! Let me try to bounce it and try again. -
@girish - looks like the service bounces:
-
@doodlemania2 From the Web Terminal, does
telnet mail 9393
work? If not, can you check if the mail server is running in Services? Maybe give it a restart and see if it helps? -
@girish yep sure does!
@doodlemania2 there is that thing about /home/git not being writable - didn't know if that was related to the email address being git@ (shrug)
-
@doodlemania2 there is that thing about /home/git not being writable - didn't know if that was related to the email address being git@ (shrug)
-
@doodlemania2 just to double check, did you create a mailbox named
git@
in Email -> Domain -> Mailboxes ? This is not created automatically. -
@girish doink - THAT did it!