info:mail
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
info:mail [2015/01/26 11:44] – [Mail aggregation aka unified inbox] hartmut | info:mail [2015/01/26 12:06] – [For the administrator] hartmut | ||
---|---|---|---|
Line 39: | Line 39: | ||
==== TLDR; ==== | ==== TLDR; ==== | ||
- | Now that the system wide setup is working, it is simple to add a service that is polling an external inbox into your user's IMAP inbox here. Just create a file called .fetchmailrc in your user directory and adjust the permissions so that fetchmail is going to accept them. | + | Now that the system wide setup is working, it is simple to add a service that is polling an external inbox into your user's IMAP inbox here. Just create a file called .fetchmailrc in your user directory and adjust the |
+ | permissions so that fetchmail is going to accept them. | ||
+ | < | ||
+ | $ touch ~/ | ||
+ | $ chmod 0600 / | ||
+ | </ | ||
+ | Then, edit this file to match your credentials for the inbox you want to poll: | ||
+ | < | ||
+ | #log to system log - enable after verifying your setup | ||
+ | #set syslog | ||
+ | poll pop.gmx.net protocol pop3: | ||
+ | | ||
+ | # use secure connection relying on CA certificates | ||
+ | ssl | ||
+ | # do not delete from server (for testing) | ||
+ | keep | ||
+ | # get all messages, not just the ones that arrived after the last poll (use this after commenting out keep) | ||
+ | #fetchall | ||
+ | </ | ||
+ | Now, run fetchmail verbosely: | ||
+ | $ fetchmail -v | ||
+ | and check the output. If all is well, change the .fetchmailrc to delete messages from the remote inbox and log to system log, and add it to your crontab, so that it will be executed regularly by the system. | ||
+ | |||
+ | |||
+ | $ crontab -e | ||
+ | | ||
+ | Add a line like this to your crontab: | ||
+ | < | ||
+ | */5 * * * * / | ||
+ | </ | ||
+ | (this will poll every 5 minutes). Then, save and exit the editor. Now, the fetchmail job will run unattended as set in the crontab. | ||
+ | |||
+ | Once this works, one could filter mail using the sieve method described above. | ||
+ | |||
+ | |||
+ | ==== For the administrator ==== | ||
+ | |||
+ | To fine-tune the setup, there are some things to be taken into account: | ||
+ | * 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. | ||
+ | * 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. | ||
==== Setup details | ==== Setup details |
info/mail.txt · Last modified: 2024/02/20 12:46 by hartmut