mailoop
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| mailoop [2019/07/23 14:30] – [Alternative B (the advanced one)] ma | mailoop [2020/11/30 13:49] (current) – removed ma | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== OpenEMM Mailloop Configuration ===== | ||
| - | The mailloop service enables OpenEMM to process bounces (and autoresponder mails) which are received hours or even days later by email (asynchronous bounces). You need to define a dedicated __mailloop service domain name__ which is different from the __OpenEMM server hostname__ (set in / | ||
| - | \\ | ||
| - | For each new bounce filter created in the OpenEMM GUI, OpenEMM creates a new filter address based on the __mailloop service domain name__. The OpenEMM user should define a mail forwarding for the address(es) used as sender address in its mailings, to direct all incoming response to the filter address(es) for further processing by the mailloop service (see “Alternative A” below).\\ | ||
| - | \\ | ||
| - | In our example below the subdomain of the OpenEMM server hostname is **openemm** and the mailloop service subdomain name will be **mailloop**. The (abbreviated) DNS entry for domain.com should look like this: | ||
| - | < | ||
| - | IN A 0 < | ||
| - | openemm IN A 0 < | ||
| - | mailloop IN A 0 < | ||
| - | mailloop.domain.com. IN MX 10 openemm.domain.com. | ||
| - | </ | ||
| - | Replace expression <ip address> with the IP address of the OpenEMM server, which also runs the mailloop service.\\ | ||
| - | \\ | ||
| - | The 1st line assigns the IP address for domain.com and the 2nd line defines its regular hostname. The 3rd line defines the A record and the 4th line defines the MX record for the mailloop service domain name, meaning that host **openemm** accepts emails sent to host **mailloop**.\\ | ||
| - | \\ | ||
| - | Validate your setup by using a tool like dig or host, for example | ||
| - | < | ||
| - | # host -a domain.com | ||
| - | # host -a openemm.domain.com | ||
| - | # host -a mailloop.domain.com | ||
| - | </ | ||
| - | When you send emails and want to take advantage of the bounce management for asynchronous bounces, there are two possibilities for the format of the sender address: | ||
| - | |||
| - | ===== Alternative A (the most popular one) ===== | ||
| - | Use whatever sender address (or reply-to address) you like. Implement a forward mechanism in the email account of this sender/ | ||
| - | < | ||
| - | aml_1@mailloop.domain.com | ||
| - | </ | ||
| - | After processing the incoming mail, the bounce filter will forward the filtered response to a feedback address of your choice (different from the sender address, of course).\\ | ||
| - | \\ | ||
| - | The flow for responses to your mailings works like this: | ||
| - | < | ||
| - | recipient -> sender/ | ||
| - | </ | ||
| - | The advantage of this model is that you can choose any sender address you want, but you have to implement an external forward mechanism. | ||
| - | |||
| - | ===== Alternative B (the advanced one) ===== | ||
| - | Use a sender/ | ||
| - | \\ | ||
| - | In the GUI configuration for the bounce filter set field " | ||
| - | \\ | ||
| - | Finally, use field " | ||
| - | < | ||
| - | recipient -> sender address (news@mailloop.domain.com) -> feedback address | ||
| - | </ | ||
| - | The advantage of this alternative is, that no external forward mechanism is needed. | ||
mailoop.1563892204.txt.gz · Last modified: 2019/07/23 14:30 by ma
