info:mail
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
info:mail [2015/01/26 11:05] – [For the administrator] hartmut | info:mail [2024/02/20 11:46] (current) – [Address Mapping] hartmut | ||
---|---|---|---|
Line 9: | Line 9: | ||
The domain of the incoming address must be one of the domains listed in '' | The domain of the incoming address must be one of the domains listed in '' | ||
- | After editing the file, run the following | + | If you changed the aliases, run |
+ | # postalias / | ||
+ | After editing the '' | ||
# postmap / | # postmap / | ||
+ | |||
+ | After that, | ||
# postfix reload | # postfix reload | ||
Line 26: | Line 30: | ||
Important: sieve scripts will only work when formatted with DOS-type CRLF linebreaks. The above extension takes care of that. | Important: sieve scripts will only work when formatted with DOS-type CRLF linebreaks. The above extension takes care of that. | ||
+ | |||
+ | If you set up a new user, do not forget that dovecot looks for a .dovecot.sieve script in that user's home directory (which may be also a symlink to an include script in a sieve folder). | ||
For specific information about managing sieve on antiguru.de look at [[moritz: | For specific information about managing sieve on antiguru.de look at [[moritz: | ||
Line 36: | Line 42: | ||
Drawback: on clients that can't be configured otherwise, answering mails received that way will result in the answers carrying your IMAP inbox address as sender. | Drawback: on clients that can't be configured otherwise, answering mails received that way will result in the answers carrying your IMAP inbox address as sender. | ||
+ | |||
+ | ===User Agents=== | ||
+ | Icedove/ | ||
+ | |||
+ | Take care when creating new folders: If you don't create them as subfolders to the mailbox root, but instead as subfolders to INBOX, it may happen that you end up with an INBOX folder on the server, containing nothing but the aforementioned subfolder. This is because in this here setup, the INBOX is no folder, but only exists virtually. So: never create subfolders to INBOX, and you won't run into difficulties (like clients not even seeing these folders). | ||
+ | |||
+ | When it comes to **mobile user agents**, the picture changes: The stock email app for Android Lollipop, called ' | ||
+ | |||
+ | There are a lot of mail user agents or clients for Android, but most of them are either still a whole lot more ugly than GMail, or do not offer more functionality, | ||
+ | |||
+ | By 'doing its job' I mean: the email client should at least take note of mails appearing in subfolders, and possibly offer a unified inbox, a virtual folder where all unread mail is presented in a bundle. It should not pester you with advertisements and, if to be paid, at least be free to try out. | ||
+ | |||
+ | After testing dozens of email clients, I can conclude that I found only one that matched these criteria, and even to some extent surpassed them. It is called Aquamail[[https:// | ||
+ | |||
+ | So far, testing Aquamail has shown very positive results. I'll keep you updated. | ||
==== TLDR; ==== | ==== TLDR; ==== | ||
Line 79: | Line 100: | ||
To fine-tune the setup, there are some things to be taken into account: | To fine-tune the setup, there are some things to be taken into account: | ||
- | * spam scores: In / | + | * spam scores: In / |
- | * spam from the inboxes polled by fetchmail will be silently deleted when the score of $sa_kill_level_deflt (now 20) is reached. You might want to review the logs for some time to look for false-positives being discarded. | + | * spam from the inboxes polled by fetchmail will be silently deleted when the score of sa_kill_level_deflt (now 20) is reached. You might want to review the logs for some time to look for false-positives being discarded. |
* on the server, the rewriting of the subject lines of messages considered spam has been disabled. This makes it easier to deal with false positives. Just move them out of the spam folder. | * on the server, the rewriting of the subject lines of messages considered spam has been disabled. This makes it easier to deal with false positives. Just move them out of the spam folder. | ||
* learning: do not delete true spam messages. After collecting lots of them, they should be used to train the spam filter. | * learning: do not delete true spam messages. After collecting lots of them, they should be used to train the spam filter. | ||
+ | * Ports: now, all clients submitting messages on port 465 (smtps) are considered local. Check if this is a valid assumption. If not, modify the system to accept these submissions on port 587 (submission). See below. | ||
==== Setup details | ==== Setup details |
info/mail.1422270326.txt.gz · Last modified: 2015/01/26 11:05 by hartmut