incoming_mail missing configuration
Similar to service_desk #2255 (closed), incoming_mail is missing configuration that prevents it from being processed on GitLab.com.
See https://docs.gitlab.com/ee/administration/incoming_email.html#configuration-examples for how this is configured in omnibus.
example configuration in the GitLab.com Staging environment:
## Reply by email
# Allow users to comment on issues and merge requests by replying to notification emails.
# For documentation on how to set this up, see https://docs.gitlab.com/ee/administration/reply_by_email.html
incoming_email:
enabled: true
# The email address including the `%{key}` placeholder that will be replaced to reference the item being replied to.
# The placeholder can be omitted but if present, it must appear in the "user" part of the address (before the `@`).
address: "incoming-staging+%{key}@gitlab.com"
# Email account username
# With third party providers, this is usually the full email address.
# With self-hosted email servers, this is usually the user part of the email address.
user: "incoming-staging@gitlab.com"
# Email account password
password: "***"
# IMAP server host
host: "imap.gmail.com"
# IMAP server port
port: 993
# Whether the IMAP server uses SSL
ssl: true
# Whether the IMAP server uses StartTLS
start_tls: false
# The mailbox where incoming mail will end up. Usually "inbox".
mailbox: "inbox"
# The IDLE command timeout.
idle_timeout: 10
# file path of internal `mail_room` JSON logs
log_path: /var/log/gitlab/mailroom/mail_room_json.log
# Whether to expunge (permanently remove) messages from the mailbox when they are deleted after delivery
expunge_deleted: