Changes between Version 12 and Version 13 of howto/SetupFetchmail
- Timestamp:
- Jun 14, 2014, 3:16:29 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
howto/SetupFetchmail
v12 v13 16 16 == Installation == 17 17 18 First set-up a mail storage and a [wikipedia:Mail_transfer_agent mail transfer agent] . See [wiki:howto/SetupDovecot Dovecot] and [wiki:howto/SetupPostfix Postfix] a possible set-up. Fetchmail will not work without and you can lo ose your mail if those components are not set-up properly.18 First set-up a mail storage and a [wikipedia:Mail_transfer_agent mail transfer agent] . See [wiki:howto/SetupDovecot Dovecot] and [wiki:howto/SetupPostfix Postfix] a possible set-up. Fetchmail will not work without and you can lose your mail if those components are not set-up properly. 19 19 20 20 === Z-Shell === … … 38 38 == Configuration == 39 39 40 Note: Do not use any of the attached files without checking / changing them with your favo urite text editor. You will need to {{{chmod +x}}} the attached files in order to execute them.40 Note: Do not use any of the attached files without checking / changing them with your favorite text editor. You will need to {{{chmod +x}}} the attached files in order to execute them. 41 41 42 42 === Step 1: ''create user'' === 43 43 44 Fetchmail does not need root or normal iser privileges to run so it is suggested to create an unprivileged user and group for daemon based fetchmail configurations. You can use the [attachment:Make_Fetchmail_User.command] to do so. This attached shell script also has instructions to view and un-do all the commands.44 Fetchmail does not need root or normal user privileges to run so it is suggested to create an unprivileged user and group for daemon based fetchmail configurations. You can use the [attachment:Make_Fetchmail_User.command] to do so. This attached shell script also has instructions to view and undo all the commands. 45 45 46 46 === Step 2: ''create directories'' === … … 48 48 Dovecot need two directories to work with - one to store the run status, one for the log files. You can use the [attachment:Make_Fetchmail_Directories.command] to create the directories. 49 49 50 Depending on which fetchmail (macports or OSX) is used you might want to change the path names to better reflect you system set-up.50 Depending on which fetchmail (macports or OSX) is used you might want to change the path names to better reflect you system set-up. 51 51 52 52 ''Note:'' … … 68 68 Fetchmail is started using {{{launchd}}} which is controlled by the attached [attachment:org.macports.fetchmail.plist]. 69 69 70 Depending on which fetchmail (macports or OSX) is used you might want to change the path names to better reflect you system setup.70 Depending on which fetchmail (macports or OSX) is used you might want to change the path names to better reflect you system setup. 71 71 72 72 The attached [attachment:Restart_Fetchmail.command] command will stop and restart fetchmail which forces a re-read of the configuration files and triggers an immediate mail collection - quite helpful while debugging the system. … … 80 80 '''Before using fetchmail you should collect all your mail by conventional means.''' 81 81 82 After starting fetchmail you should check if the start was succes full by checking the syslog:82 After starting fetchmail you should check if the start was successful by checking the syslog: 83 83 84 84 {{{ … … 91 91 }}} 92 92 93 Last you send yourself a mail and trigger a mail collection with [attachment:Restart_Fetchmail.command] and then check if the mail arrived okin your local mail storage.93 Last you send yourself a mail and trigger a mail collection with [attachment:Restart_Fetchmail.command] and then check if the mail arrived in your local mail storage. 94 94 95 95 == Optional Parts ==