mailoop
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| mailoop [2019/06/01 18:12] – [Alternative B (the advanced one)] ma | mailoop [2019/06/01 18:28] – ma | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== OpenEMM Mailloop Configuration ===== | ====== 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 | + | 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 |
| \\ | \\ | ||
| - | For each new bounce filter created in the OpenEMM GUI, OpenEMM creates a new filter address based on the mailloop | + | For each new bounce filter created in the OpenEMM GUI, OpenEMM creates a new filter address based on the __mailloop |
| \\ | \\ | ||
| 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 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: | ||
Page Tools
