7/2/2023 0 Comments Incoming mail![]() In order for everyone else on the Internet to know where to deliver mail, you must create an MX record for your forum. If so, all is well, and you can go on to then next step. The last line printed should look rather a lot like this: Aug 31 04:14:31 postfix/master: daemon started - version 3.1.1, configuration /etc/postfix To check everything’s OK, take a peek in the logs. Now, do an initial build of the container, and fire it up!. Use Ctrl-X to exit (say “Yes” to “Do you want to save changes?”, or all your work will be for nothing). If you’re not sure what your favourite text editor is, try nano: nano containers/mail-receiver.yml If you use the default mail endpoint ( /admin/email/handle_mail), we suggest using the receive_email API key scope to provide an extra layer of security. (If you are an advanced user and know that you are using nginx outside your container, see below for additional configuration for external nginx.) Since every site is unique, open containers/mail-receiver.yml in your preferred text editor and change the MAIL_DOMAIN, DISCOURSE_MAIL_ENDPOINT, and DISCOURSE_API_KEY variables to suit your site. Now, go to your /var/discourse directory and create a new mail-receiver.yml container definition from the sample conveniently provided: cd /var/discourse So, start off by logging into your Discourse server, and becoming root via sudo: ssh -i There’s no need for a separate droplet just to handle mail – the whole container only takes about 5MB of memory! We’re going to get the mail-receiver container up and running on the server that’s already running your Discourse instance. Any self-hosted Discourse forum using our supported installation process can make use of this procedure to get easy, smooth-flowing incoming e-mail. It supports all e-mail processes: handling bounces, replies, and new topic creation. This procedure creates a new container on your Discourse server, alongside the typical app container, which receives e-mail and forwards it into Discourse for processing. This howto is all about getting that hawtness into your forum. There are no delays in delivery – no more waiting for the next polling run to see new posts appear!.You have more control over the e-mail addresses that people use to send posts and.No need to deal with gmail or another provider’s foibles.In addition, you can use Discourse to handle e-mail for a group, such as an e-mail-based support channel (which is how Discourse’ own e-mail support is handled).ĭelivering e-mail directly into your Discourse forum, rather than setting up POP3 polling, has a number of benefits: Letting people post new topics, or send PMs, via e-mail has similar benefits to engagement.Allowing people to reply to posts via e-mail can significantly improve engagement, as people can reply straight away from their mail client, even if they’re not able to visit the forum at that moment.Receiving e-mail bounces allows you to disable sending to non-existent addresses. Repeatedly sending e-mails that bounce will get your e-mails flagged as spam. ![]()
0 Comments
Leave a Reply. |