coop-cloud/discourse
coop-cloud
/
discourse
1
0
Fork 1
Code Issues 5 Pull Requests Projects Releases Wiki Activity

Work out (and document) how to set up direct-delivery incoming mail #3

New Issue
Open
opened 2023-04-09 18:35:10 +00:00 by 3wordchant · 0 comments
3wordchant commented 2023-04-09 18:35:10 +00:00
Owner
Copy Link

One of Discourse's killer features (imho) is its ability to act as a mailing list, allowing people to reply to posts by email, and start new discussions by emailing a specific address.

It's possible to set this up using POP3 with a dedicated inbox, but it's always felt neater to use "direct delivery mail" (set-up instructions, where a specially-configured Postfix server passes emails directly to Discourse using its API endpoints.

At Autonomic, we've previously used Web Architects' Ansible playbook to set this up directly on the host; presumably there's some nifty way of crowbaring it into Docker, and adding it to this recipe as a compose.incoming-email.yml or something.

One of Discourse's killer features (imho) is its ability to act as a mailing list, allowing people to reply to posts by email, and start new discussions by emailing a specific address. It's possible to set this up using POP3 with a dedicated inbox, but it's always felt neater to use "direct delivery mail" ([set-up instructions](https://meta.discourse.org/t/configure-direct-delivery-incoming-email-for-self-hosted-sites/49487), where a specially-configured Postfix server passes emails directly to Discourse using its API endpoints. At Autonomic, we've previously used [Web Architects' Ansible playbook](https://git.coop/webarch/discourse/-/blob/master/tasks/email.yml) to set this up directly on the host; presumably there's some nifty way of crowbaring it into Docker, and adding it to this recipe as a `compose.incoming-email.yml` or something.
3wordchant changed title from Work out (and document) how to set up incoming mail to Work out (and document) how to set up direct-delivery incoming mail 2023-04-09 18:35:24 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
cas_readme
0.6.3+3.1.2
0.6.2+3.1.1
0.6.1+3.1.1
0.6.0+3.1.1
0.5.0+3.0.6
0.4.1+3.0.6
0.4.0+3.0.1
0.3.1+2.8.9
0.3.0+2.8.9
0.2.1+2.8.9
0.2.0+2.8.1
0.1.0+2.7.7
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/discourse#3
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?