This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revisionBoth sides next revision |
| users:email [2020/06/29 22:52] – jesse | users:email [2020/06/29 22:58] – jesse |
|---|
| |
| Sieve runs to filter email. There is one rule always run before any user filters which moves email flagged as spam to the 'Junk' folder, if you so desire it's possible to add another custom rule to move it back. You can add/manage custom rules using the ManageSieve protocol which is supported by some clients and the waffle.tech webmail. | Sieve runs to filter email. There is one rule always run before any user filters which moves email flagged as spam to the 'Junk' folder, if you so desire it's possible to add another custom rule to move it back. You can add/manage custom rules using the ManageSieve protocol which is supported by some clients and the waffle.tech webmail. |
| | |
| | ===== Security ===== |
| | |
| | Outgoing email is validated by SPF, DKIM, and DMARC to encourage successful delivery. In some cases the headers of email you send may be returned to the waffle.tech administrator if the recipient's mail system judges it to be spam, this is to enable investigation of any compromise. |
| | |
| | The MTA will opportunistically use TLS for any outgoing email if the receiving MTA supports it. Additionally, the MTA is configured with a list of "known secure" recipient domains and will refuse non-TLS delivery to these domains. This list includes all of the major email providers you can think of. Contact the administrator if you would like a domain you correspond with and know to support TLS to be added to this list. As always, do not trust en-route encryption of emails because there are several ways for it to fail and for your email to end up being transferred in plaintext. |