... | ... | @@ -716,7 +716,33 @@ A working run will look something like this: |
|
|
{"severity":"INFO","time":"2022-08-29T20:15:57.744+00:00","context":{"email":"git@gitlab.torproject.org","name":"inbox"},"action":"Getting new messages","unread":{"count":0,"ids":[]},"to_be_delivered":{"count":0,"ids":[]}}0","context":{"email":"git@gitlab.torproject.org","name":"inbox"},"action":"Idling"}
|
|
|
```
|
|
|
|
|
|
Emails should be processed every minute or so.
|
|
|
Emails should be processed every minute or so. If they are not, the
|
|
|
`mailroom` process might be crashed, you can see if it's running with:
|
|
|
|
|
|
```
|
|
|
gitlabctl status mailroom
|
|
|
```
|
|
|
|
|
|
Example running properly:
|
|
|
|
|
|
```
|
|
|
root@gitlab-02:~# gitlab-ctl status mailroom
|
|
|
run: mailroom: (pid 3611591) 247s; run: log: (pid 2993172) 370149s
|
|
|
```
|
|
|
|
|
|
Example stopped:
|
|
|
|
|
|
```
|
|
|
root@gitlab-02:~# gitlab-ctl status mailroom
|
|
|
finish: mailroom: (pid 3603300) 5s; run: log: (pid 2993172) 369429s
|
|
|
```
|
|
|
|
|
|
Startup failures do *not* show up in the JSON log file, but instead in
|
|
|
another logfile, see:
|
|
|
|
|
|
```
|
|
|
tail -f /var/log/gitlab/mailroom/current
|
|
|
```
|
|
|
|
|
|
### Outgoing email
|
|
|
|
... | ... | |