Update dependencies: nginx, redis, imagemagick (#475)
[discourse_docker.git] / samples / mail-receiver.yml
1 ## this is the incoming mail receiver container template
2 ##
3 ## After making changes to this file, you MUST rebuild
4 ## /var/discourse/launcher rebuild mail-receiver
5 ##
6 ## BE *VERY* CAREFUL WHEN EDITING!
7 ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
8 ## visit http://www.yamllint.com/ to validate this file as needed
9
10 base_image: discourse/mail-receiver:release
11 update_pups: false
12
13 expose:
14 - "25:25" # SMTP
15
16 env:
17 LANG: en_US.UTF-8
18
19 ## Where e-mail to your forum should be sent. In general, it's perfectly fine
20 ## to use the same domain as the forum itself here.
21 MAIL_DOMAIN: discourse.example.com
22 # uncomment these (and the volume below!) to support TLS
23 # POSTCONF_smtpd_tls_key_file: /letsencrypt/discourse.example.com/prop.ltcmp.net.key
24 # POSTCONF_smtpd_tls_cert_file: /letsencrypt/discourse.example.com/fullchain.cer
25 # POSTCONF_smtpd_tls_security_level: may
26
27
28 ## The URL of the mail processing endpoint of your Discourse forum.
29 ## This is simply your forum's base URL, with `/admin/email/handle_mail`
30 ## appended. Be careful if you're running a subfolder setup -- in that case,
31 ## the URL needs to have the subfolder included!
32 DISCOURSE_MAIL_ENDPOINT: 'http://discourse.example.com/admin/email/handle_mail'
33
34 ## The master API key of your Discourse forum. You can get this from
35 ## the "API" tab of your admin panel.
36 DISCOURSE_API_KEY: abcdefghijklmnop
37
38 ## The username to use for processing incoming e-mail. Unless you have
39 ## renamed the `system` user, you should leave this as-is.
40 DISCOURSE_API_USERNAME: system
41
42 volumes:
43 - volume:
44 host: /var/discourse/shared/mail-receiver/postfix-spool
45 guest: /var/spool/postfix
46 # uncomment to support TLS
47 # - volume:
48 # host: /var/discourse/shared/standalone/letsencrypt
49 # guest: /letsencrypt
50
51