Menu
▾
▴
fetchmail-users — User questions and discussion
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(16) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(2) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(8) |
Aug
(21) |
Sep
(17) |
Oct
(35) |
Nov
(39) |
Dec
(55) |
| 2006 |
Jan
(70) |
Feb
(11) |
Mar
(55) |
Apr
(27) |
May
(73) |
Jun
(47) |
Jul
(63) |
Aug
(27) |
Sep
(52) |
Oct
(39) |
Nov
(87) |
Dec
(15) |
| 2007 |
Jan
(23) |
Feb
(46) |
Mar
(108) |
Apr
(63) |
May
(54) |
Jun
(34) |
Jul
(29) |
Aug
(103) |
Sep
(46) |
Oct
(69) |
Nov
(29) |
Dec
(17) |
| 2008 |
Jan
(45) |
Feb
(32) |
Mar
(25) |
Apr
(17) |
May
(39) |
Jun
(20) |
Jul
(64) |
Aug
(31) |
Sep
(38) |
Oct
(20) |
Nov
(42) |
Dec
(50) |
| 2009 |
Jan
(10) |
Feb
(38) |
Mar
(3) |
Apr
(29) |
May
(41) |
Jun
(31) |
Jul
(21) |
Aug
(53) |
Sep
(49) |
Oct
(26) |
Nov
(28) |
Dec
(15) |
| 2010 |
Jan
(83) |
Feb
(38) |
Mar
(33) |
Apr
(44) |
May
(9) |
Jun
(16) |
Jul
(35) |
Aug
(38) |
Sep
(11) |
Oct
(35) |
Nov
(68) |
Dec
(19) |
| 2011 |
Jan
(16) |
Feb
(69) |
Mar
(42) |
Apr
(54) |
May
(56) |
Jun
(29) |
Jul
|
Aug
(65) |
Sep
(3) |
Oct
(39) |
Nov
(33) |
Dec
(4) |
| 2012 |
Jan
(31) |
Feb
(21) |
Mar
(26) |
Apr
(13) |
May
(38) |
Jun
(39) |
Jul
(14) |
Aug
(31) |
Sep
(8) |
Oct
(32) |
Nov
(12) |
Dec
(16) |
| 2013 |
Jan
(40) |
Feb
(22) |
Mar
(21) |
Apr
(15) |
May
(13) |
Jun
(9) |
Jul
(34) |
Aug
(10) |
Sep
(10) |
Oct
|
Nov
(7) |
Dec
(1) |
| 2014 |
Jan
(25) |
Feb
(9) |
Mar
(8) |
Apr
(12) |
May
(7) |
Jun
|
Jul
(7) |
Aug
(4) |
Sep
(27) |
Oct
(25) |
Nov
(18) |
Dec
(3) |
| 2015 |
Jan
(18) |
Feb
(13) |
Mar
(4) |
Apr
(19) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(7) |
Sep
(6) |
Oct
(4) |
Nov
(19) |
Dec
(6) |
| 2016 |
Jan
|
Feb
(8) |
Mar
(14) |
Apr
|
May
(11) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
(10) |
Oct
|
Nov
(11) |
Dec
(17) |
| 2017 |
Jan
(17) |
Feb
(35) |
Mar
|
Apr
(4) |
May
(8) |
Jun
(2) |
Jul
(16) |
Aug
|
Sep
(5) |
Oct
(11) |
Nov
(15) |
Dec
(10) |
| 2018 |
Jan
|
Feb
(3) |
Mar
|
Apr
(3) |
May
(2) |
Jun
(8) |
Jul
|
Aug
(10) |
Sep
(17) |
Oct
(15) |
Nov
(12) |
Dec
(10) |
| 2019 |
Jan
(4) |
Feb
(14) |
Mar
(33) |
Apr
(17) |
May
(7) |
Jun
(6) |
Jul
(2) |
Aug
(4) |
Sep
(22) |
Oct
(13) |
Nov
|
Dec
|
| 2020 |
Jan
(36) |
Feb
(19) |
Mar
(31) |
Apr
(2) |
May
(22) |
Jun
(7) |
Jul
(25) |
Aug
(9) |
Sep
(17) |
Oct
(52) |
Nov
(13) |
Dec
(9) |
| 2021 |
Jan
(23) |
Feb
(13) |
Mar
(9) |
Apr
(15) |
May
(3) |
Jun
(7) |
Jul
(4) |
Aug
(23) |
Sep
(3) |
Oct
(8) |
Nov
(28) |
Dec
(9) |
| 2022 |
Jan
(38) |
Feb
(2) |
Mar
(56) |
Apr
(24) |
May
(29) |
Jun
(22) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(13) |
Nov
(2) |
Dec
|
| 2023 |
Jan
(6) |
Feb
(1) |
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
(21) |
Aug
(5) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2024 |
Jan
(15) |
Feb
(4) |
Mar
|
Apr
(4) |
May
(11) |
Jun
(9) |
Jul
(1) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(1) |
Dec
(1) |
| 2025 |
Jan
(7) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
(10) |
Jul
|
Aug
(1) |
Sep
(12) |
Oct
(11) |
Nov
|
Dec
|
|
From: Gene H. <ghe...@wd...> - 2014-11-11 06:09:29
|
Greetings; Using a fetchmail thats only a couple months old, built from your tarball, I just had to set, from a restart on the command line giving it the --bad-header accept option in order to clear and retrieve an obviously C&C message from a bot controller, or something similar. The header really was bad: From gene Tue Nov 11 00:37:56 2014 Return-Path: <ad...@bh...> Delivered-To: ghe...@wd... Received: from mail.wdtv.com [66.118.69.84] by coyote.coyote.den with POP3 (fetchmail-6.3.26) for <gene@localhost> (single-drop); Tue, 11 Nov 2014 00:37:56 -0500 (EST) Received: (qmail 9141 invoked by uid 508); 23 Oct 2014 14:44:53 -0400 Received: from empireland.net (74.208.106.93) by mail.wdtv.com with AES256-SHA encrypted SMTP; 23 Oct 2014 14:44:53 -0400 Received: from nx ([218.109.100.99]) (authenticated user ad...@bh...) by empireland.net (Kerio Connect 7.1.2); Thu, 23 Oct 2014 12:42:33 -0600 X-procmail: user=gene »ú·¿»·¾³·¨¹æ Message-ID: <201...@bh...> From: =?utf-8?B?6ZW/5a2Z5aWz5aOr?= <ad...@bh...> To: <hua...@hu...> Subject: =?utf-8?B?56Gu6K6k5Ye977yb6ZW/5a2Z5aWz5aOr?= Date: Fri, 24 Oct 2014 02:42:28 +0800 MIME-Version: 1.0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 X-mailer: Aqzn 9 Followed by about 23.5kb of what looked to be base64 encoded crap. Image,virus, c&c, I have no clue. Does anything in that look familiar to you folks? I haven't cleaned it up. Thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS |
|
From: Matthias A. <mat...@gm...> - 2014-11-03 20:16:53
|
Am 03.11.2014 um 11:31 schrieb Ian Balchin: > Matthias, hello, > > see below > > On Sun, Nov 02, 2014 at 11:47:46PM +0100, Matthias Andree wrote: >> Ian, >> >> can you get the logs of a run similar to: >> >> fetchmail --nosyslog --nodetach -vvv -d600 >> >> That should show something. Note that if running as root it will grab >> /usr/local/etc/fetchmailrc, all other users will look at >> $HOME/.fetchmailrc. We should then see where it hangs. >> > Starting afresh this morning and having made sure that all was as should be, having set for fetchmail user with fetchmailrc in /usr/local/etc > As you can see with a system start fetchmail daemon is running from 11:27:54 > But by the time i make a timestamp with an imap disconnect at 11:52:33 it has not yet made a pop3 call to receive mail. > > > Nov 3 10:52:52 hestia fetchmail[907]: terminated with signal 15 > Nov 3 11:26:57 hestia dovecot: dovecot: Killed with signal 15 (by pid=1020 uid=0 code=kill) > Nov 3 11:26:57 hestia fetchmail[774]: terminated with signal 15 > Nov 3 11:26:57 hestia postfix/postfix-script[1057]: stopping the Postfix mail system > Nov 3 11:26:57 hestia postfix/master[758]: terminating on signal 15 > Nov 3 11:27:53 hestia postfix/postfix-script[748]: starting the Postfix mail system > Nov 3 11:27:53 hestia postfix/master[750]: daemon started -- version 2.11.1, configuration /usr/local/etc/postfix > Nov 3 11:27:54 hestia fetchmail[766]: starting fetchmail 6.3.26 daemon > Nov 3 11:27:54 hestia dovecot: Dovecot v1.2.17 starting up > Nov 3 11:27:54 hestia dovecot: auth(default): passwd-file /usr/local/etc/passwd.dovecot: Read 1 users > Nov 3 11:27:54 hestia dovecot: auth-worker(default): passwd-file /usr/local/etc/passwd.dovecot: Read 1 users > Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=861 > Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=860 > Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=864 > Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=863 > Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=859 > Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=862 > Nov 3 11:28:53 hestia dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=192.168.0.21 rip=192.168.0.15 lport=143 rport=49092 resp=<hidden> > Nov 3 11:28:53 hestia dovecot: auth(default): passwd-file(nignog,192.168.0.15): lookup: user=inksi file=/usr/local/etc/passwd.dovecot > Nov 3 11:28:53 hestia dovecot: auth(default): client out: OK 1 user=nignog > Nov 3 11:28:53 hestia dovecot: auth(default): master in: REQUEST 1 862 1 > Nov 3 11:28:53 hestia dovecot: auth-worker(default): passwd(nignog,192.168.0.15): lookup > Nov 3 11:28:53 hestia dovecot: auth(default): master out: USER 1 inksi system_groups_user=nignog uid=1001 gid=1001 home=/home/nignog > Nov 3 11:28:53 hestia dovecot: imap-login: Login: user=<nignog>, method=PLAIN, rip=192.168.0.15, lip=192.168.0.21 > Nov 3 11:28:54 hestia dovecot: auth(default): new auth connection: pid=866 > Nov 3 11:52:33 hestia dovecot: IMAP(nignog): Disconnected: Logged out bytes=2377/16968 > > If I run it as su it is woken up but that is all apart from the standard notice 'running as root strongly discouraged'. > then: > > root@hestia:/usr/home/nignog # fetchmail --nosyslog --nodetach -vvv -d600 > fetchmail: WARNING: Running as root is discouraged. > Scratch list of UIDs: <empty> > fetchmail: no mailservers have been specified. ****** is this line a clue? ***** > root@hestia:/usr/home/nignog # That line is definitely a clue, but not the right one. That only means there is no global configuration, which is fine. Note that the FreeBSD port/pkg's /usr/local/etc/rc.d/fetchmail file reads some variables from /etc/rc.conf and its siblings - check the former for the supported variables, and their defaults. Check, in particular, for the fetchmail_users variable, and the rc.d/fetchmail file's comments under "Per-user daemon". Mind the spelling - fetchmail_user and fetchmail_users have the innocuous s at the end (or not) but make a huge difference... Setting the fetchmail_users variable in /etc/rc.conf (you will likely have to add it) to the login should help a fair deal getting the daemon to run as the right user, and grab the right configuration. > so then the only option is to repeat the command as a user > > $ fetchmail --nosyslog --nodetach -vvv -d600 > Old UID list from pop3.gormless.co.za: <empty> > Old UID list from pop3.gormless.co.za: <empty> > Old UID list from pop3.gormless.co.za: <empty> > Old UID list from pop3.gormless.co.za: <empty> > Scratch list of UIDs: <empty> > fetchmail: starting fetchmail 6.3.26 daemon > fetchmail: 6.3.26 querying pop3.gormless.co.za (protocol POP3) at Mon Nov 3 12:13:43 2014: poll started > Trying to connect to 41.78.28.41/110...connected. > fetchmail: POP3< +OK Dovecot ready. > fetchmail: POP3> CAPA > fetchmail: POP3< +OK > fetchmail: POP3< CAPA > fetchmail: POP3< TOP > fetchmail: POP3< UIDL > fetchmail: POP3< RESP-CODES So then it logs in properly... |
|
From: Ian B. <an...@fa...> - 2014-11-03 19:19:22
|
O Mon, Nov 03, 2014 at 06:39:28AM -0500, Jerry wrote: > On Mon, 3 Nov 2014 12:31:35 +0200, Ian Balchin stated: > > > Matthias, hello, > > > > see below > > > > On Sun, Nov 02, 2014 at 11:47:46PM +0100, Matthias Andree wrote: > > > Ian, > > > > > > can you get the logs of a run similar to: > > > > > > fetchmail --nosyslog --nodetach -vvv -d600 > > > > > > That should show something. Note that if running as root it will grab > > > /usr/local/etc/fetchmailrc, all other users will look at > > > $HOME/.fetchmailrc. We should then see where it hangs. > > > > > Starting afresh this morning and having made sure that all was as should > > be, having set for fetchmail user with fetchmailrc in /usr/local/etc As you > > can see with a system start fetchmail daemon is running from 11:27:54 But > > by the time i make a timestamp with an imap disconnect at 11:52:33 it has > > not yet made a pop3 call to receive mail. > > > > > > Nov 3 10:52:52 hestia fetchmail[907]: terminated with signal 15 > > Nov 3 11:26:57 hestia dovecot: dovecot: Killed with signal 15 (by pid=1020 > > uid=0 code=kill) Nov 3 11:26:57 hestia fetchmail[774]: terminated with > > signal 15 Nov 3 11:26:57 hestia postfix/postfix-script[1057]: stopping the > > Postfix mail system Nov 3 11:26:57 hestia postfix/master[758]: terminating > > on signal 15 Nov 3 11:27:53 hestia postfix/postfix-script[748]: starting > > the Postfix mail system Nov 3 11:27:53 hestia postfix/master[750]: daemon > > started -- version 2.11.1, configuration /usr/local/etc/postfix Nov 3 > > 11:27:54 hestia fetchmail[766]: starting fetchmail 6.3.26 daemon Nov 3 > > 11:27:54 hestia dovecot: Dovecot v1.2.17 starting up Nov 3 11:27:54 hestia > > dovecot: auth(default): passwd-file /usr/local/etc/passwd.dovecot: Read 1 > > users Nov 3 11:27:54 hestia dovecot: auth-worker(default): > > passwd-file /usr/local/etc/passwd.dovecot: Read 1 users Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=861 Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=860 Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=864 Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=863 Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=859 Nov 3 11:27:55 > > hestia dovecot: auth(default): new auth connection: pid=862 Nov 3 11:28:53 > > hestia dovecot: auth(default): client in: AUTH 1 PLAIN > > service=imap lip=192.168.0.21 rip=192.168.0.15 > > lport=143 rport=49092 resp=<hidden> Nov 3 11:28:53 hestia > > dovecot: auth(default): passwd-file(nignog,192.168.0.15): lookup: > > user=inksi file=/usr/local/etc/passwd.dovecot Nov 3 11:28:53 hestia > > dovecot: auth(default): client out: OK 1 user=nignog Nov 3 > > 11:28:53 hestia dovecot: auth(default): master in: REQUEST 1 > > 862 1 Nov 3 11:28:53 hestia dovecot: auth-worker(default): > > passwd(nignog,192.168.0.15): lookup Nov 3 11:28:53 hestia dovecot: > > auth(default): master out: USER 1 inksi > > system_groups_user=nignog uid=1001 gid=1001 > > home=/home/nignog Nov 3 11:28:53 hestia dovecot: imap-login: Login: > > user=<nignog>, method=PLAIN, rip=192.168.0.15, lip=192.168.0.21 Nov 3 > > 11:28:54 hestia dovecot: auth(default): new auth connection: pid=866 Nov 3 > > 11:52:33 hestia dovecot: IMAP(nignog): Disconnected: Logged out > > bytes=2377/16968 > > > > If I run it as su it is woken up but that is all apart from the standard > > notice 'running as root strongly discouraged'. then: > > > > root@hestia:/usr/home/nignog # fetchmail --nosyslog --nodetach -vvv -d600 > > fetchmail: WARNING: Running as root is discouraged. > > Scratch list of UIDs: <empty> > > fetchmail: no mailservers have been specified. ****** is this line a > > clue? ***** root@hestia:/usr/home/nignog # > > > > > > so then the only option is to repeat the command as a user > > > > $ fetchmail --nosyslog --nodetach -vvv -d600 > > Old UID list from pop3.gormless.co.za: <empty> > > Old UID list from pop3.gormless.co.za: <empty> > > Old UID list from pop3.gormless.co.za: <empty> > > Old UID list from pop3.gormless.co.za: <empty> > > Scratch list of UIDs: <empty> > > fetchmail: starting fetchmail 6.3.26 daemon > > fetchmail: 6.3.26 querying pop3.gormless.co.za (protocol POP3) at Mon Nov > > 3 12:13:43 2014: poll started Trying to connect to > > 41.78.28.41/110...connected. fetchmail: POP3< +OK Dovecot ready. > > fetchmail: POP3> CAPA > > fetchmail: POP3< +OK > > fetchmail: POP3< CAPA > > fetchmail: POP3< TOP > > fetchmail: POP3< UIDL > > fetchmail: POP3< RESP-CODES > > fetchmail: POP3< PIPELINING > > fetchmail: POP3< AUTH-RESP-CODE > > fetchmail: POP3< STLS > > fetchmail: POP3< USER > > fetchmail: POP3< SASL CRAM-MD5 PLAIN LOGIN > > fetchmail: POP3< . > > fetchmail: POP3> AUTH CRAM-MD5 > > fetchmail: POP3< + PDkxNDkyMTkxNzI3NDk3NjcuMTQxNTAwOTYyNEBlbWFpbC1wcm94eXg+ > > fetchmail: decoded as <9149219172749767.1415009624@email-proxyx> > > fetchmail: POP3> > > aHlwYXRpYUBmYWJsZXMuY28uemEgOWU5YzVmZWFmNzRiY2I5MjRhYzY2NzkzOGM5YWVjMGQ= > > fetchmail: POP3< +OK Logged in. fetchmail: selecting or re-polling default > > folder fetchmail: POP3> STAT > > fetchmail: POP3< +OK 0 0 > > fetchmail: No mail for nignog@mydomain at pop3.gormless.co.za > > fetchmail: POP3> QUIT > > fetchmail: POP3< +OK Logging out. > > > > and it runs happily thereafter for multiple pops every 10 mins. > > > > Can you see anything there? > > Back only tonight. > > > > Ian > > 1) You have me confused here. Is this what your "fetchmailrc" entry looks > like: > > -rwx------ 1 fetchmail fetchmail 4.7K 2014-10-31 07:25:43 EDT fetchmailrc yes (but 1k) > > 2) cd to the /usr/local/etc directory and run as root: > > service fetchmail stop > > At that point fetchmail should be shut down. If not, post the error message. stopped. not to be seen in top. no error messages > > 3) Now still as root, enter: service fetchmail start > > If any error messages are displayed, show them here. > started. seen in top > 4) now, still as root, enter: service fetchmail awaken > > Post any error messages. root@hestia:/var/log # service fetchmail awaken Forcing fetchmail to check mailbox(es)... root@hestia:/var/log # the view from maillog: Nov 3 16:05:39 hestia fetchmail[766]: terminated with signal 15 Nov 3 16:08:50 hestia fetchmail[1342]: starting fetchmail 6.3.26 daemon Nov 3 16:10:30 hestia fetchmail[1342]: awakened by User defined signal 1 > > 5) If you want, and have not done so all ready, create a log file. cd > to /var/log and enter: touch "fetchmail.log" sans quotations and then change > the ownership and permissions. done > > chown fetchmail:fetchmail /var/log/fetchmail.log > chmod 0666 /var/log/fetchmail.log done > > In your "/usr/local/etc/fetchmailrc" file, enter the following: > > set logfile "/var/log/fetchmail.log" > set postmaster "postmaster" > set bouncemail > set no spambounce > set softbounce > set properties "" done > > You may need to change some of them; however, leave the logfile entry as is. > > Now, you will have to restart fetchmail for this to take effect. Again, as > root, service fetchmail restart done > > Post any error messages. none no apparent immediate connection either > > Good luck! didn't get any of that either first time around. from fetchmail.log fetchmail: starting fetchmail 6.3.26 daemon no timestamp :( - but after the best part of an hour that is all there is. Well, no mail to be collected, so .... I send an email to be picked up in case fetchmail was working secretly in the background root@hestia:/var/log # service fetchmail awaken Forcing fetchmail to check mailbox(es)... root@hestia:/var/log # tail -f -n 50 /var/log/fetchmail.log fetchmail: starting fetchmail 6.3.26 daemon fetchmail: 1 message for nignog@mydomain at pop3.imaginet.co.za (1261 octets). fetchmail: reading message nignog@myd...@po...:1 of 1 (1261 octets) flushed another email and another awaken fetchmail: awakened by User defined signal 1 fetchmail: 1 message for nignog@mydomain at pop3.imaginet.co.za (1284 octets). fetchmail: reading message nignog@myd...@po...:1 of 1 (1284 octets) flushed So fetchmail does check immediately after 'awaken' I suspected that fetchmail does check within the polling time but if there is nothing to fetch then it does not log this explicitly tailing fetchmail.log for a while shows no activity. So I sent another email, and within the cycle period it fetched this - repeatedly and reliably it seems. So I need to increase the verbosity, and add a time stamp, else revert to maillog. Is this possible? I see nothing in man pages or FAQ. Thank you for your patience. I will be back. Ian > > -- > Jerry > > ------------------------------------------------------------------------------ > _______________________________________________ > Fetchmail-users mailing list > Fet...@li... > https://lists.sourceforge.net/lists/listinfo/fetchmail-users |
|
From: Jerry <je...@se...> - 2014-11-03 11:39:36
|
On Mon, 3 Nov 2014 12:31:35 +0200, Ian Balchin stated: > Matthias, hello, > > see below > > On Sun, Nov 02, 2014 at 11:47:46PM +0100, Matthias Andree wrote: > > Ian, > > > > can you get the logs of a run similar to: > > > > fetchmail --nosyslog --nodetach -vvv -d600 > > > > That should show something. Note that if running as root it will grab > > /usr/local/etc/fetchmailrc, all other users will look at > > $HOME/.fetchmailrc. We should then see where it hangs. > > > Starting afresh this morning and having made sure that all was as should > be, having set for fetchmail user with fetchmailrc in /usr/local/etc As you > can see with a system start fetchmail daemon is running from 11:27:54 But > by the time i make a timestamp with an imap disconnect at 11:52:33 it has > not yet made a pop3 call to receive mail. > > > Nov 3 10:52:52 hestia fetchmail[907]: terminated with signal 15 > Nov 3 11:26:57 hestia dovecot: dovecot: Killed with signal 15 (by pid=1020 > uid=0 code=kill) Nov 3 11:26:57 hestia fetchmail[774]: terminated with > signal 15 Nov 3 11:26:57 hestia postfix/postfix-script[1057]: stopping the > Postfix mail system Nov 3 11:26:57 hestia postfix/master[758]: terminating > on signal 15 Nov 3 11:27:53 hestia postfix/postfix-script[748]: starting > the Postfix mail system Nov 3 11:27:53 hestia postfix/master[750]: daemon > started -- version 2.11.1, configuration /usr/local/etc/postfix Nov 3 > 11:27:54 hestia fetchmail[766]: starting fetchmail 6.3.26 daemon Nov 3 > 11:27:54 hestia dovecot: Dovecot v1.2.17 starting up Nov 3 11:27:54 hestia > dovecot: auth(default): passwd-file /usr/local/etc/passwd.dovecot: Read 1 > users Nov 3 11:27:54 hestia dovecot: auth-worker(default): > passwd-file /usr/local/etc/passwd.dovecot: Read 1 users Nov 3 11:27:55 > hestia dovecot: auth(default): new auth connection: pid=861 Nov 3 11:27:55 > hestia dovecot: auth(default): new auth connection: pid=860 Nov 3 11:27:55 > hestia dovecot: auth(default): new auth connection: pid=864 Nov 3 11:27:55 > hestia dovecot: auth(default): new auth connection: pid=863 Nov 3 11:27:55 > hestia dovecot: auth(default): new auth connection: pid=859 Nov 3 11:27:55 > hestia dovecot: auth(default): new auth connection: pid=862 Nov 3 11:28:53 > hestia dovecot: auth(default): client in: AUTH 1 PLAIN > service=imap lip=192.168.0.21 rip=192.168.0.15 > lport=143 rport=49092 resp=<hidden> Nov 3 11:28:53 hestia > dovecot: auth(default): passwd-file(nignog,192.168.0.15): lookup: > user=inksi file=/usr/local/etc/passwd.dovecot Nov 3 11:28:53 hestia > dovecot: auth(default): client out: OK 1 user=nignog Nov 3 > 11:28:53 hestia dovecot: auth(default): master in: REQUEST 1 > 862 1 Nov 3 11:28:53 hestia dovecot: auth-worker(default): > passwd(nignog,192.168.0.15): lookup Nov 3 11:28:53 hestia dovecot: > auth(default): master out: USER 1 inksi > system_groups_user=nignog uid=1001 gid=1001 > home=/home/nignog Nov 3 11:28:53 hestia dovecot: imap-login: Login: > user=<nignog>, method=PLAIN, rip=192.168.0.15, lip=192.168.0.21 Nov 3 > 11:28:54 hestia dovecot: auth(default): new auth connection: pid=866 Nov 3 > 11:52:33 hestia dovecot: IMAP(nignog): Disconnected: Logged out > bytes=2377/16968 > > If I run it as su it is woken up but that is all apart from the standard > notice 'running as root strongly discouraged'. then: > > root@hestia:/usr/home/nignog # fetchmail --nosyslog --nodetach -vvv -d600 > fetchmail: WARNING: Running as root is discouraged. > Scratch list of UIDs: <empty> > fetchmail: no mailservers have been specified. ****** is this line a > clue? ***** root@hestia:/usr/home/nignog # > > > so then the only option is to repeat the command as a user > > $ fetchmail --nosyslog --nodetach -vvv -d600 > Old UID list from pop3.gormless.co.za: <empty> > Old UID list from pop3.gormless.co.za: <empty> > Old UID list from pop3.gormless.co.za: <empty> > Old UID list from pop3.gormless.co.za: <empty> > Scratch list of UIDs: <empty> > fetchmail: starting fetchmail 6.3.26 daemon > fetchmail: 6.3.26 querying pop3.gormless.co.za (protocol POP3) at Mon Nov > 3 12:13:43 2014: poll started Trying to connect to > 41.78.28.41/110...connected. fetchmail: POP3< +OK Dovecot ready. > fetchmail: POP3> CAPA > fetchmail: POP3< +OK > fetchmail: POP3< CAPA > fetchmail: POP3< TOP > fetchmail: POP3< UIDL > fetchmail: POP3< RESP-CODES > fetchmail: POP3< PIPELINING > fetchmail: POP3< AUTH-RESP-CODE > fetchmail: POP3< STLS > fetchmail: POP3< USER > fetchmail: POP3< SASL CRAM-MD5 PLAIN LOGIN > fetchmail: POP3< . > fetchmail: POP3> AUTH CRAM-MD5 > fetchmail: POP3< + PDkxNDkyMTkxNzI3NDk3NjcuMTQxNTAwOTYyNEBlbWFpbC1wcm94eXg+ > fetchmail: decoded as <9149219172749767.1415009624@email-proxyx> > fetchmail: POP3> > aHlwYXRpYUBmYWJsZXMuY28uemEgOWU5YzVmZWFmNzRiY2I5MjRhYzY2NzkzOGM5YWVjMGQ= > fetchmail: POP3< +OK Logged in. fetchmail: selecting or re-polling default > folder fetchmail: POP3> STAT > fetchmail: POP3< +OK 0 0 > fetchmail: No mail for nignog@mydomain at pop3.gormless.co.za > fetchmail: POP3> QUIT > fetchmail: POP3< +OK Logging out. > > and it runs happily thereafter for multiple pops every 10 mins. > > Can you see anything there? > Back only tonight. > > Ian 1) You have me confused here. Is this what your "fetchmailrc" entry looks like: -rwx------ 1 fetchmail fetchmail 4.7K 2014-10-31 07:25:43 EDT fetchmailrc 2) cd to the /usr/local/etc directory and run as root: service fetchmail stop At that point fetchmail should be shut down. If not, post the error message. 3) Now still as root, enter: service fetchmail start If any error messages are displayed, show them here. 4) now, still as root, enter: service fetchmail awaken Post any error messages. 5) If you want, and have not done so all ready, create a log file. cd to /var/log and enter: touch "fetchmail.log" sans quotations and then change the ownership and permissions. chown fetchmail:fetchmail /var/log/fetchmail.log chmod 0666 /var/log/fetchmail.log In your "/usr/local/etc/fetchmailrc" file, enter the following: set logfile "/var/log/fetchmail.log" set postmaster "postmaster" set bouncemail set no spambounce set softbounce set properties "" You may need to change some of them; however, leave the logfile entry as is. Now, you will have to restart fetchmail for this to take effect. Again, as root, service fetchmail restart Post any error messages. Good luck! -- Jerry |
|
From: Ian B. <an...@fa...> - 2014-11-03 10:31:22
|
Matthias, hello, see below On Sun, Nov 02, 2014 at 11:47:46PM +0100, Matthias Andree wrote: > Ian, > > can you get the logs of a run similar to: > > fetchmail --nosyslog --nodetach -vvv -d600 > > That should show something. Note that if running as root it will grab > /usr/local/etc/fetchmailrc, all other users will look at > $HOME/.fetchmailrc. We should then see where it hangs. > Starting afresh this morning and having made sure that all was as should be, having set for fetchmail user with fetchmailrc in /usr/local/etc As you can see with a system start fetchmail daemon is running from 11:27:54 But by the time i make a timestamp with an imap disconnect at 11:52:33 it has not yet made a pop3 call to receive mail. Nov 3 10:52:52 hestia fetchmail[907]: terminated with signal 15 Nov 3 11:26:57 hestia dovecot: dovecot: Killed with signal 15 (by pid=1020 uid=0 code=kill) Nov 3 11:26:57 hestia fetchmail[774]: terminated with signal 15 Nov 3 11:26:57 hestia postfix/postfix-script[1057]: stopping the Postfix mail system Nov 3 11:26:57 hestia postfix/master[758]: terminating on signal 15 Nov 3 11:27:53 hestia postfix/postfix-script[748]: starting the Postfix mail system Nov 3 11:27:53 hestia postfix/master[750]: daemon started -- version 2.11.1, configuration /usr/local/etc/postfix Nov 3 11:27:54 hestia fetchmail[766]: starting fetchmail 6.3.26 daemon Nov 3 11:27:54 hestia dovecot: Dovecot v1.2.17 starting up Nov 3 11:27:54 hestia dovecot: auth(default): passwd-file /usr/local/etc/passwd.dovecot: Read 1 users Nov 3 11:27:54 hestia dovecot: auth-worker(default): passwd-file /usr/local/etc/passwd.dovecot: Read 1 users Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=861 Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=860 Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=864 Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=863 Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=859 Nov 3 11:27:55 hestia dovecot: auth(default): new auth connection: pid=862 Nov 3 11:28:53 hestia dovecot: auth(default): client in: AUTH 1 PLAIN service=imap lip=192.168.0.21 rip=192.168.0.15 lport=143 rport=49092 resp=<hidden> Nov 3 11:28:53 hestia dovecot: auth(default): passwd-file(nignog,192.168.0.15): lookup: user=inksi file=/usr/local/etc/passwd.dovecot Nov 3 11:28:53 hestia dovecot: auth(default): client out: OK 1 user=nignog Nov 3 11:28:53 hestia dovecot: auth(default): master in: REQUEST 1 862 1 Nov 3 11:28:53 hestia dovecot: auth-worker(default): passwd(nignog,192.168.0.15): lookup Nov 3 11:28:53 hestia dovecot: auth(default): master out: USER 1 inksi system_groups_user=nignog uid=1001 gid=1001 home=/home/nignog Nov 3 11:28:53 hestia dovecot: imap-login: Login: user=<nignog>, method=PLAIN, rip=192.168.0.15, lip=192.168.0.21 Nov 3 11:28:54 hestia dovecot: auth(default): new auth connection: pid=866 Nov 3 11:52:33 hestia dovecot: IMAP(nignog): Disconnected: Logged out bytes=2377/16968 If I run it as su it is woken up but that is all apart from the standard notice 'running as root strongly discouraged'. then: root@hestia:/usr/home/nignog # fetchmail --nosyslog --nodetach -vvv -d600 fetchmail: WARNING: Running as root is discouraged. Scratch list of UIDs: <empty> fetchmail: no mailservers have been specified. ****** is this line a clue? ***** root@hestia:/usr/home/nignog # so then the only option is to repeat the command as a user $ fetchmail --nosyslog --nodetach -vvv -d600 Old UID list from pop3.gormless.co.za: <empty> Old UID list from pop3.gormless.co.za: <empty> Old UID list from pop3.gormless.co.za: <empty> Old UID list from pop3.gormless.co.za: <empty> Scratch list of UIDs: <empty> fetchmail: starting fetchmail 6.3.26 daemon fetchmail: 6.3.26 querying pop3.gormless.co.za (protocol POP3) at Mon Nov 3 12:13:43 2014: poll started Trying to connect to 41.78.28.41/110...connected. fetchmail: POP3< +OK Dovecot ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< AUTH-RESP-CODE fetchmail: POP3< STLS fetchmail: POP3< USER fetchmail: POP3< SASL CRAM-MD5 PLAIN LOGIN fetchmail: POP3< . fetchmail: POP3> AUTH CRAM-MD5 fetchmail: POP3< + PDkxNDkyMTkxNzI3NDk3NjcuMTQxNTAwOTYyNEBlbWFpbC1wcm94eXg+ fetchmail: decoded as <9149219172749767.1415009624@email-proxyx> fetchmail: POP3> aHlwYXRpYUBmYWJsZXMuY28uemEgOWU5YzVmZWFmNzRiY2I5MjRhYzY2NzkzOGM5YWVjMGQ= fetchmail: POP3< +OK Logged in. fetchmail: selecting or re-polling default folder fetchmail: POP3> STAT fetchmail: POP3< +OK 0 0 fetchmail: No mail for nignog@mydomain at pop3.gormless.co.za fetchmail: POP3> QUIT fetchmail: POP3< +OK Logging out. and it runs happily thereafter for multiple pops every 10 mins. Can you see anything there? Back only tonight. Ian > ------------------------------------------------------------------------------ > _______________________________________________ > Fetchmail-users mailing list > Fet...@li... > https://lists.sourceforge.net/lists/listinfo/fetchmail-users |
|
From: Matthias A. <mat...@gm...> - 2014-11-02 22:47:55
|
Ian, can you get the logs of a run similar to: fetchmail --nosyslog --nodetach -vvv -d600 That should show something. Note that if running as root it will grab /usr/local/etc/fetchmailrc, all other users will look at $HOME/.fetchmailrc. We should then see where it hangs. |
|
From: Ian B. <an...@fa...> - 2014-11-02 19:40:35
|
Jerry, hi,
thanks for reply. comments below.
On Sun, Nov 02, 2014 at 11:30:56AM -0500, Jerry wrote:
> On Sun, 2 Nov 2014 17:29:42 +0200, Ian Balchin stated:
>
> > > > On new FreeBSD server (my first ever) I have the fetchmail daemon
> > > > running but although showing in the maillog it does not actually run.
> > > > It never wakes up and fetches any mail.
> > > >
> > > > The output from it run as 'fetchmail -V -v --nodetach --nosyslog' is
> > > > pasted below
> > > >
> > > > The last line in maillog is:
> > > >
> > > > Nov 2 14:21:00 myserver fetchmail[4581]: starting fetchmail 6.3.26
> > > > daemon
> > > >
> > > > and there we sit.
> > > >
> > > > If run as 'fetchmail -vvv --nodetach --nosyslog' it works fine.
> > > >
> > > > I copied fetchmailrc out from /usr/local/etc to my home directory and
> > > > renamed it .fetchmailrc and then edited accordingly. User = me, group =
> > > > fetchmail. I added me to the fetchmail group with no change in
> > > > operation.
>
> 1) Do you have:
>
> ## Start Fetchmail
> fetchmail_enable="YES"
no, I didn't have that but I do now.
I picked it up for other installed packages, ie postifx, usually in the output at end of install, but did not see for fetchmail
Perhaps I was not looking carefully enough although seeing fetchmail as to be started by a user I never thought to add it in.
My understanding of bsd internals minimal at this stage.
But to be sure I have added that in as suggested.
>
> in the /etc/rc.conf file?
>
> 2) Are you the ohny user of this PC?
> a) If so, then why move the fetchmail configuration file?
yes, only because that was how it was before in a years-old ubuntu server. Not saying that is right, but it worked like that.
>
> 3) Did you read and follow the following portion of the
> "/usr/local/etc/rc.d/fetchmail" file?
Nope, but I have now.
>
> # There are two variants:
> #
ok, this is what I need
> # * Single system-wide fetchmail daemon:
> # - It is run as user `fetchmail_user' (default: fetchmail)
there is a user 'fetchmail'
> # Note: The directory /var/run/fetchmail must be writable for
> # 'fetchmail_user'.
this is so. owner and group 'fetchmail' and permissions 755 I think
> # - All configuration is contained in one global file
> # 'fetchmail_config' (default: /usr/local/etc/fetchmailrc)
> # that must be owned by 'fetchmail_user' (mode 700)
this is so, the config file is back where it should be as 'fetchmailrc' with correct perms of 700
> # - The fetchmail daemon awakes to fetch mail every
> # 'fetchmail_polling_interval' seconds (default: 900).
still, this does not occur.
in a nutshell, the daemon ignores the time setting
even if I kill the daemon and restart $ fetchmail -d 600 we get no polling, either immediately or after the 600 and it should do it immediately I think.
MAYBE I should reinstall as a pkg rather than as a port? Why did you ask that as the first question?
I'll save that for tomorrow at this point.
thanks for your time
Ian
> #
I figure this is for a situation where dozens of people want to connect and get their own mail from outside
> # * Per-user daemon
> # - Users for which a fetchmail daemon is to be started must be
> # listed in 'fetchmail_users', e.g. fetchmail_users="user1 user2"
> # The 'fetchmail_user' (sic!) variable is ignored in this
> # configuration variant.
> # - The config files for the individual users must be located at
> # ${fetchmail_home_prefix}/${user}/${fetchmail_config_name}. The
> # default for 'fetchmail_home_prefix' is "/home", and that for
> # 'fetchmail_config_name' is ".fetchmailrc".
> # - Note that "${fetchmail_home_prefix}/${user}" must be writable
> # for ${user} since it is used to store the per-user PID files!
> # - There are user-specific versions of 'fetchmail_config' and
> # 'fetchmail_polling_interval' that can be used to override the
> # defaults, i.e. for the user 'user1' there are variables
> # 'fetchmail_user1_config' and 'fetchmail_user1_polling_interval'
> # - All commands (e.g. start, stop, awaken (see below)) can be either
> # passed to all instances of the daemon (if /usr/local/etc/rc.d/fetchmail)
> # is run as root), or just to the instance belonging to the respective
> # user.
> #
>
> --
> Jerry
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Fetchmail-users mailing list
> Fet...@li...
> https://lists.sourceforge.net/lists/listinfo/fetchmail-users
|
|
From: Jerry <je...@se...> - 2014-11-02 16:37:09
|
On Sun, 2 Nov 2014 17:29:42 +0200, Ian Balchin stated:
> > > On new FreeBSD server (my first ever) I have the fetchmail daemon
> > > running but although showing in the maillog it does not actually run.
> > > It never wakes up and fetches any mail.
> > >
> > > The output from it run as 'fetchmail -V -v --nodetach --nosyslog' is
> > > pasted below
> > >
> > > The last line in maillog is:
> > >
> > > Nov 2 14:21:00 myserver fetchmail[4581]: starting fetchmail 6.3.26
> > > daemon
> > >
> > > and there we sit.
> > >
> > > If run as 'fetchmail -vvv --nodetach --nosyslog' it works fine.
> > >
> > > I copied fetchmailrc out from /usr/local/etc to my home directory and
> > > renamed it .fetchmailrc and then edited accordingly. User = me, group =
> > > fetchmail. I added me to the fetchmail group with no change in
> > > operation.
1) Do you have:
## Start Fetchmail
fetchmail_enable="YES"
in the /etc/rc.conf file?
2) Are you the ohny user of this PC?
a) If so, then why move the fetchmail configuration file?
3) Did you read and follow the following portion of the
"/usr/local/etc/rc.d/fetchmail" file?
# There are two variants:
#
# * Single system-wide fetchmail daemon:
# - It is run as user `fetchmail_user' (default: fetchmail)
# Note: The directory /var/run/fetchmail must be writable for
# 'fetchmail_user'.
# - All configuration is contained in one global file
# 'fetchmail_config' (default: /usr/local/etc/fetchmailrc)
# that must be owned by 'fetchmail_user' (mode 700)
# - The fetchmail daemon awakes to fetch mail every
# 'fetchmail_polling_interval' seconds (default: 900).
#
# * Per-user daemon
# - Users for which a fetchmail daemon is to be started must be
# listed in 'fetchmail_users', e.g. fetchmail_users="user1 user2"
# The 'fetchmail_user' (sic!) variable is ignored in this
# configuration variant.
# - The config files for the individual users must be located at
# ${fetchmail_home_prefix}/${user}/${fetchmail_config_name}. The
# default for 'fetchmail_home_prefix' is "/home", and that for
# 'fetchmail_config_name' is ".fetchmailrc".
# - Note that "${fetchmail_home_prefix}/${user}" must be writable
# for ${user} since it is used to store the per-user PID files!
# - There are user-specific versions of 'fetchmail_config' and
# 'fetchmail_polling_interval' that can be used to override the
# defaults, i.e. for the user 'user1' there are variables
# 'fetchmail_user1_config' and 'fetchmail_user1_polling_interval'
# - All commands (e.g. start, stop, awaken (see below)) can be either
# passed to all instances of the daemon (if /usr/local/etc/rc.d/fetchmail)
# is run as root), or just to the instance belonging to the respective
# user.
#
--
Jerry
|
|
From: Ian B. <an...@fa...> - 2014-11-02 15:29:32
|
Jerry, hi, see lower down On Sun, Nov 02, 2014 at 10:03:49AM -0500, Jerry wrote: > On Sun, 2 Nov 2014 15:40:39 +0200, Ian Balchin stated: > > > Hi, > > > > I have fetchmail running on other machines with no issues. > > > > On new FreeBSD server (my first ever) I have the fetchmail daemon running > > but although showing in the maillog it does not actually run. It never > > wakes up and fetches any mail. > > > > The output from it run as 'fetchmail -V -v --nodetach --nosyslog' is pasted > > below > > > > The last line in maillog is: > > > > Nov 2 14:21:00 myserver fetchmail[4581]: starting fetchmail 6.3.26 daemon > > > > and there we sit. > > > > If run as 'fetchmail -vvv --nodetach --nosyslog' it works fine. > > > > I copied fetchmailrc out from /usr/local/etc to my home directory and > > renamed it .fetchmailrc and then edited accordingly. User = me, group = > > fetchmail. I added me to the fetchmail group with no change in operation. > > > > Am using Postfix. > > > > ------------------------------ > > # i have edited out my domain, my isp, my passwd so hope that hasn't > > fouled it up below > > > > This is fetchmail release 6.3.26+GSS+RPA+SDPS+SSL+OPIE+NLS. > > > > Copyright (C) 2002, 2003 Eric S. Raymond > > Copyright (C) 2004 Matthias Andree, Eric S. Raymond, > > Robert M. Funk, Graham Wilson > > Copyright (C) 2005 - 2012 Sunil Shetye > > Copyright (C) 2005 - 2013 Matthias Andree > > Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you > > are welcome to redistribute it under certain conditions. For details, > > please see the file COPYING in the source or documentation directory. > > This product includes software developed by the OpenSSL Project > > for use in the OpenSSL Toolkit. (http://www.openssl.org/) > > > > Fallback MDA: (none) > > FreeBSD hestia.mydomain 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Fri > > Jan 17 01:46:25 UTC 2014 > > ro...@sn...:/usr/obj/usr/src/sys/GENERIC i386 Taking options > > from command line and /home/nignog/.fetchmailrc Poll interval is 600 > > seconds Idfile is /home/inksi/.fetchids Fetchmail will forward misaddressed > > multidrop messages to inksi. Fetchmail will direct error mail to the sender. > > Fetchmail will treat permanent errors as temporary (keep messages). > > Options for retrieving from nignog@myd...@po...: > > True name of server is pop3.gormless.com > > This host will be queried when no host is specified. > > Password = "uncrackable". > > Protocol is POP3 (using default port). > > All available authentication methods will be tried. > > SSL protocol: ssl23. > > Server nonresponse timeout is 300 seconds (default). > > Default mailbox selected. > > All messages will be retrieved (--all on). > > Fetched messages will not be kept on the server (--keep off). > > Old messages will not be flushed before message retrieval (--flush off). > > Oversized messages will not be flushed before message retrieval > > (--limitflush off). Rewrite of server-local addresses is enabled > > (--norewrite off). Carriage-return stripping is disabled (stripcr off). > > Carriage-return forcing is disabled (forcecr off). > > Interpretation of Content-Transfer-Encoding is enabled (pass8bits off). > > MIME decoding is disabled (mimedecode off). > > Idle after poll is disabled (idle off). > > Nonempty Status lines will be kept (dropstatus off) > > Delivered-To lines will be kept (dropdelivered off) > > No received-message limit (--fetchlimit 0). > > Fetch message size limit is 100 (--fetchsizelimit 100). > > Do binary search of UIDs during 3 out of 4 polls (--fastuidl 4). > > No SMTP message batch limit (--batchlimit 0). > > No forced expunges (--expunge 0). > > Messages will be SMTP-forwarded to: localhost (defaultt) > > Spam-blocking disabled > > No pre-connection command. > > No post-connection command. > > Single-drop mode: 1 local name recognized. > > nignog > > No interface requirement specified. > > No monitor interface specified. > > No plugin command specified. > > No plugout command specified. > > No UIDs saved from this host. > > No poll trace information will be added to the Received header. > > Messages with bad headers will be rejected. > > > > ------------------------ > > > > I am in violation of all multipdrop recommendations but haven't got that > > far yet. > > > > thanks for any pointers (any additional info supplied on request). > > Ian > > How was "fetchmail" installed; ie, from the FreeBSD ports system or did you > download and install it from source? I installed from the ports system, (twice, I deinstalled and tried to see if I could install as user but not possible). Ian > > -- > Jerry > > ------------------------------------------------------------------------------ > _______________________________________________ > Fetchmail-users mailing list > Fet...@li... > https://lists.sourceforge.net/lists/listinfo/fetchmail-users |
|
From: Jerry <je...@se...> - 2014-11-02 15:03:57
|
On Sun, 2 Nov 2014 15:40:39 +0200, Ian Balchin stated: > Hi, > > I have fetchmail running on other machines with no issues. > > On new FreeBSD server (my first ever) I have the fetchmail daemon running > but although showing in the maillog it does not actually run. It never > wakes up and fetches any mail. > > The output from it run as 'fetchmail -V -v --nodetach --nosyslog' is pasted > below > > The last line in maillog is: > > Nov 2 14:21:00 myserver fetchmail[4581]: starting fetchmail 6.3.26 daemon > > and there we sit. > > If run as 'fetchmail -vvv --nodetach --nosyslog' it works fine. > > I copied fetchmailrc out from /usr/local/etc to my home directory and > renamed it .fetchmailrc and then edited accordingly. User = me, group = > fetchmail. I added me to the fetchmail group with no change in operation. > > Am using Postfix. > > ------------------------------ > # i have edited out my domain, my isp, my passwd so hope that hasn't > fouled it up below > > This is fetchmail release 6.3.26+GSS+RPA+SDPS+SSL+OPIE+NLS. > > Copyright (C) 2002, 2003 Eric S. Raymond > Copyright (C) 2004 Matthias Andree, Eric S. Raymond, > Robert M. Funk, Graham Wilson > Copyright (C) 2005 - 2012 Sunil Shetye > Copyright (C) 2005 - 2013 Matthias Andree > Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you > are welcome to redistribute it under certain conditions. For details, > please see the file COPYING in the source or documentation directory. > This product includes software developed by the OpenSSL Project > for use in the OpenSSL Toolkit. (http://www.openssl.org/) > > Fallback MDA: (none) > FreeBSD hestia.mydomain 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Fri > Jan 17 01:46:25 UTC 2014 > ro...@sn...:/usr/obj/usr/src/sys/GENERIC i386 Taking options > from command line and /home/nignog/.fetchmailrc Poll interval is 600 > seconds Idfile is /home/inksi/.fetchids Fetchmail will forward misaddressed > multidrop messages to inksi. Fetchmail will direct error mail to the sender. > Fetchmail will treat permanent errors as temporary (keep messages). > Options for retrieving from nignog@myd...@po...: > True name of server is pop3.gormless.com > This host will be queried when no host is specified. > Password = "uncrackable". > Protocol is POP3 (using default port). > All available authentication methods will be tried. > SSL protocol: ssl23. > Server nonresponse timeout is 300 seconds (default). > Default mailbox selected. > All messages will be retrieved (--all on). > Fetched messages will not be kept on the server (--keep off). > Old messages will not be flushed before message retrieval (--flush off). > Oversized messages will not be flushed before message retrieval > (--limitflush off). Rewrite of server-local addresses is enabled > (--norewrite off). Carriage-return stripping is disabled (stripcr off). > Carriage-return forcing is disabled (forcecr off). > Interpretation of Content-Transfer-Encoding is enabled (pass8bits off). > MIME decoding is disabled (mimedecode off). > Idle after poll is disabled (idle off). > Nonempty Status lines will be kept (dropstatus off) > Delivered-To lines will be kept (dropdelivered off) > No received-message limit (--fetchlimit 0). > Fetch message size limit is 100 (--fetchsizelimit 100). > Do binary search of UIDs during 3 out of 4 polls (--fastuidl 4). > No SMTP message batch limit (--batchlimit 0). > No forced expunges (--expunge 0). > Messages will be SMTP-forwarded to: localhost (defaultt) > Spam-blocking disabled > No pre-connection command. > No post-connection command. > Single-drop mode: 1 local name recognized. > nignog > No interface requirement specified. > No monitor interface specified. > No plugin command specified. > No plugout command specified. > No UIDs saved from this host. > No poll trace information will be added to the Received header. > Messages with bad headers will be rejected. > > ------------------------ > > I am in violation of all multipdrop recommendations but haven't got that > far yet. > > thanks for any pointers (any additional info supplied on request). > Ian How was "fetchmail" installed; ie, from the FreeBSD ports system or did you download and install it from source? -- Jerry |
|
From: Ian B. <an...@fa...> - 2014-11-02 13:40:23
|
Hi,
I have fetchmail running on other machines with no issues.
On new FreeBSD server (my first ever) I have the fetchmail daemon running but although showing in the maillog it does not actually run.
It never wakes up and fetches any mail.
The output from it run as 'fetchmail -V -v --nodetach --nosyslog' is pasted below
The last line in maillog is:
Nov 2 14:21:00 myserver fetchmail[4581]: starting fetchmail 6.3.26 daemon
and there we sit.
If run as 'fetchmail -vvv --nodetach --nosyslog' it works fine.
I copied fetchmailrc out from /usr/local/etc to my home directory and renamed it .fetchmailrc and then edited accordingly.
User = me, group = fetchmail. I added me to the fetchmail group with no change in operation.
Am using Postfix.
------------------------------
# i have edited out my domain, my isp, my passwd so hope that hasn't fouled it up below
This is fetchmail release 6.3.26+GSS+RPA+SDPS+SSL+OPIE+NLS.
Copyright (C) 2002, 2003 Eric S. Raymond
Copyright (C) 2004 Matthias Andree, Eric S. Raymond,
Robert M. Funk, Graham Wilson
Copyright (C) 2005 - 2012 Sunil Shetye
Copyright (C) 2005 - 2013 Matthias Andree
Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you
are welcome to redistribute it under certain conditions. For details,
please see the file COPYING in the source or documentation directory.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)
Fallback MDA: (none)
FreeBSD hestia.mydomain 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Fri Jan 17 01:46:25 UTC 2014 ro...@sn...:/usr/obj/usr/src/sys/GENERIC i386
Taking options from command line and /home/nignog/.fetchmailrc
Poll interval is 600 seconds
Idfile is /home/inksi/.fetchids
Fetchmail will forward misaddressed multidrop messages to inksi.
Fetchmail will direct error mail to the sender.
Fetchmail will treat permanent errors as temporary (keep messages).
Options for retrieving from nignog@myd...@po...:
True name of server is pop3.gormless.com
This host will be queried when no host is specified.
Password = "uncrackable".
Protocol is POP3 (using default port).
All available authentication methods will be tried.
SSL protocol: ssl23.
Server nonresponse timeout is 300 seconds (default).
Default mailbox selected.
All messages will be retrieved (--all on).
Fetched messages will not be kept on the server (--keep off).
Old messages will not be flushed before message retrieval (--flush off).
Oversized messages will not be flushed before message retrieval (--limitflush off).
Rewrite of server-local addresses is enabled (--norewrite off).
Carriage-return stripping is disabled (stripcr off).
Carriage-return forcing is disabled (forcecr off).
Interpretation of Content-Transfer-Encoding is enabled (pass8bits off).
MIME decoding is disabled (mimedecode off).
Idle after poll is disabled (idle off).
Nonempty Status lines will be kept (dropstatus off)
Delivered-To lines will be kept (dropdelivered off)
No received-message limit (--fetchlimit 0).
Fetch message size limit is 100 (--fetchsizelimit 100).
Do binary search of UIDs during 3 out of 4 polls (--fastuidl 4).
No SMTP message batch limit (--batchlimit 0).
No forced expunges (--expunge 0).
Messages will be SMTP-forwarded to: localhost (defaultt)
Spam-blocking disabled
No pre-connection command.
No post-connection command.
Single-drop mode: 1 local name recognized.
nignog
No interface requirement specified.
No monitor interface specified.
No plugin command specified.
No plugout command specified.
No UIDs saved from this host.
No poll trace information will be added to the Received header.
Messages with bad headers will be rejected.
------------------------
I am in violation of all multipdrop recommendations but haven't got that far yet.
thanks for any pointers (any additional info supplied on request).
Ian
|
|
From: Matthias A. <mat...@gm...> - 2014-10-25 19:20:50
|
Am 25.10.2014 um 20:27 schrieb Peter Pentchev: > On Sat, Oct 25, 2014 at 06:18:11PM +0200, Matthias Andree wrote: >> Am 25.10.2014 um 16:43 schrieb Carlos E. R.: >> >>> In my system, installing "standalone" maildrop (which is not available in >>> the standard repositories, but in server:mail) requires installing >>> something more that I do not want: >>> >>> Telcontar:~ # zypper --no-refresh in maildrop >>> Loading repository data... >>> Reading installed packages... >>> Resolving package dependencies... >>> >>> The following 3 NEW packages are going to be installed: >>> courier-authlib courier-imap maildrop >> >> If maildrop requires courier-imap then the packaging is broken. Contact >> the packager or file a bug report and, since it's SUSE, hope someone >> reads it and deals with it. courier-authlib should suffice as requisite >> package. Also check if courier-imap is only "recommended" or required. > > It's possible that the situation is similar, although maybe reversed, to > the one in Debian. There are actually two maildrop packages in Debian - > the one named "maildrop" is the standalone MDA, and the one named > "courier-maildrop" is the version that is much more closely integrated > with the rest of the Courier MTA suite. I'm not very familiar with the > SuSE packaging system, so I cannot really check right now, but Carlos, > is it possible that there are two packages there, too? I check the openSUSE repos once again. The trick to avoid courier-imap is installing maildrop-maildirutils before installing maildrop. Alternatively, enabling the entire server:mail repository might work, too, but will also exchange postfix, amavis, bogofilter, getmail and related other packages... # zypper ar http://download.opensuse.org/repositories/server:/mail/openSUSE_13.1/server:mail.repo # zypper in maildrop-maildirutils maildrop should do the trick. This is more intrusive, however. |
|
From: Carlos E. R. <car...@op...> - 2014-10-25 19:19:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-10-25 18:18, Matthias Andree wrote: > Am 25.10.2014 um 16:43 schrieb Carlos E. R.: > package. Also check if courier-imap is only "recommended" or > required. You are right, it is a recommendation. >> And I'm not prepared to install courier-imap as I'm afraid would >> cause problems with the already running dovecot (imap). > > Only if you actually launch it at boot-time. There is a way to > defeat that, but I'm not familiar with the systemd bloat. I am, but it is one thing more to do ;-) >> I had a look at maildrop.html and maildropfilter.html. It appears >> a powerful but complex tool. The language is described (it's a >> man page, so it's man's style), but there are no examples that I >> could find. > > Check the maildropex manual page or HTML file, there are examples > in the other manuals, too. Ah, that one I had not seen, thanks. (not may examples, though). >> But yes, I would like a _generic_, fully mantained, procmail >> thing or replacement. > > I have not found the need to try and convert procmail weighted > scoring stuff, but everything else I ever used (and I had > multi-hundred line procmailrc files once upon a time) could be > transferred to maildrop. Not weighted scoring, but "simple" filtering. Many folders and formail calls. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRL96AACgkQtTMYHG2NR9WrVACfXpbhBY5AS2e/c3qZlDrOQuJT L1gAn1Fzt8Q8z3KYN+hjif3Mn8iCLukE =4KQe -----END PGP SIGNATURE----- |
|
From: Matthias A. <mat...@gm...> - 2014-10-25 16:18:20
|
Am 25.10.2014 um 16:43 schrieb Carlos E. R.: > In my system, installing "standalone" maildrop (which is not available in > the standard repositories, but in server:mail) requires installing > something more that I do not want: > > Telcontar:~ # zypper --no-refresh in maildrop > Loading repository data... > Reading installed packages... > Resolving package dependencies... > > The following 3 NEW packages are going to be installed: > courier-authlib courier-imap maildrop If maildrop requires courier-imap then the packaging is broken. Contact the packager or file a bug report and, since it's SUSE, hope someone reads it and deals with it. courier-authlib should suffice as requisite package. Also check if courier-imap is only "recommended" or required. > And I'm not prepared to install courier-imap as I'm afraid would cause > problems with the already running dovecot (imap). Only if you actually launch it at boot-time. There is a way to defeat that, but I'm not familiar with the systemd bloat. > I had a look at maildrop.html and maildropfilter.html. It appears a > powerful but complex tool. The language is described (it's a man page, so > it's man's style), but there are no examples that I could find. Check the maildropex manual page or HTML file, there are examples in the other manuals, too. > But yes, I would like a _generic_, fully mantained, procmail thing or > replacement. I have not found the need to try and convert procmail weighted scoring stuff, but everything else I ever used (and I had multi-hundred line procmailrc files once upon a time) could be transferred to maildrop. |
|
From: Carlos E. R. <car...@op...> - 2014-10-25 14:44:09
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2014-10-17 at 16:08 -0400, Gene Heskett wrote: > On Friday 17 October 2014 12:13:45 Matthias Andree did opine >> Personally I prefer maildrop, http://www.courier-mta.org/maildrop.html > > And this is a currently well supported filtering MTA that can do what > procmail is doing now? I'll go look at it, thanks. In my system, installing "standalone" maildrop (which is not available in the standard repositories, but in server:mail) requires installing something more that I do not want: Telcontar:~ # zypper --no-refresh in maildrop Loading repository data... Reading installed packages... Resolving package dependencies... The following 3 NEW packages are going to be installed: courier-authlib courier-imap maildrop And I'm not prepared to install courier-imap as I'm afraid would cause problems with the already running dovecot (imap). I had a look at maildrop.html and maildropfilter.html. It appears a powerful but complex tool. The language is described (it's a man page, so it's man's style), but there are no examples that I could find. Translating my 1500 lines of procmail would be daunting, so I prefer not to even try. If I had to, I would look at a specific tool for dovecot instead. One of the things about procmail is that it does not matter if I use dovecot or plain folders. Yes, it has some caveats. If a recipe is broken, email can be dropped in the next, unrelated, folder. But I know how to cope with that... I have not yet lost a single email. Yet :-) But yes, I would like a _generic_, fully mantained, procmail thing or replacement. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRLtyoACgkQtTMYHG2NR9XWRgCgmDT0O6r9U9Meoy/yzFrY34vu eLYAn3ce1kc2b8KaS5WvgGWkQXsQTYEn =dzkQ -----END PGP SIGNATURE----- |
|
From: Matthias A. <mat...@gm...> - 2014-10-20 07:30:57
|
Am 17.10.2014 um 22:41 schrieb Carlos E. R.: > It simply has not needed updates. I would not call it "unmaintained", > but "mature". Millions of systems use it. Eat more dung, millions of flies cannot all be wrong. It is not as if the majority of these "millions" of systems made a deliberate decision, it just shipped with many of those by default (some even as a required component of the base install), before we had better alternatives. > In the changelog of my distribution, I see its recent maintenance > updates, some coming from other distributions. Meaning upstream is dead, no-one bothers to fork/revive it, and the distro version bug sets fall asunder. The list archive no longer exists, several links on procmail.org go to domains that are no longer, and procmail never added clear comments on error handling to its manual pages, you'd have to grab those from someone else. If you just go by procmailex you'll find that you missed error handling once the disk fills up or goes read-only or similar. If that's a temporary condition, you'll see mail delivery gets erratic. Fixing that is possible, but it at least doubles the number of your .procmailrc recipes and clutters the file. |
|
From: Matthias A. <mat...@gm...> - 2014-10-20 07:20:24
|
Am 17.10.2014 um 22:08 schrieb Gene Heskett: > With my current config, there are only 3 places it puts an incoming mail. Yes. But unless you code error handling yourself with one :0e recipe that adds error handling after *each* delivering recipe, procmail will happily try a later file if it cannot write to one listed earlier. As though your original recipe hadn't been there. http://www.dovecot.org/list/dovecot/2007-August/024910.html https://docs.kde.org/stable/en/kdepim/kmail/faq.html#idp13808496 >> Personally I prefer maildrop, http://www.courier-mta.org/maildrop.html > > And this is a currently well supported filtering MTA that can do what > procmail is doing now? I'll go look at it, thanks. It's got a syntax I find easier to read and can do more or less what procmail can do, and it is being maintained. |
|
From: Carlos E. R. <car...@op...> - 2014-10-17 20:41:59
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-10-17 10:30, Gene Heskett wrote: > On Friday 17 October 2014 03:55:32 Matthias Andree did opine And > Gene did reply: >> Note that I advise against using procmail. It has been >> unmaintained for more than a decade and has design flaws that >> cause apparent mail "loss" (which are not loss but in fact a >> fallback behaviour that causes procmail to _misfile_ mail in >> error situations, and - albeit possible - are hard to overcome by >> procmail recipes). >> > Humm, since I have been using procmail for about a decade now, and > am aware of its unsupported status simply because there have been > no updates in several years, and it hasn't made any mistakes that I > have become aware of, what do you suggest as its most painfree > replacement? It simply has not needed updates. I would not call it "unmaintained", but "mature". Millions of systems use it. In the changelog of my distribution, I see its recent maintenance updates, some coming from other distributions. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRBfwkACgkQtTMYHG2NR9WyFgCfQvnvFRJC4f/E/fbzuShxRS6q aIQAnikt/tH1hiJwbGKCwMmquOThg6/0 =C7Rt -----END PGP SIGNATURE----- |
|
From: Gene H. <ghe...@wd...> - 2014-10-17 20:08:24
|
On Friday 17 October 2014 12:13:45 Matthias Andree did opine And Gene did reply: > Am 17.10.2014 um 10:30 schrieb Gene Heskett: > > Humm, since I have been using procmail for about a decade now, and am > > aware of its unsupported status simply because there have been no > > updates in several years, and it hasn't made any mistakes that I > > have become aware of, what do you suggest as its most painfree > > replacement? > > Would you notice if single messages ended up in the wrong folder - > especially if you do not know that messages have been file in some > other place where you do not expect it to be? > With my current config, there are only 3 places it puts an incoming mail. If SA goes off, it goes on thru to my /var/spool/mail/gene mailfile. If its from a niece, that goes to a separate mailfile. If its a clamav detected viri it gets put in a third viri file. All other sorting is done by kmail itself as it gets a dbus signal to go and get any newly arrived mail in my mailfile or in the nieces mailfile. Thats also owned by me, and kmail sorts that to a maildir holding her messages. Some specific recipes also send crap to /dev/null. Might be 100 of those. > Personally I prefer maildrop, http://www.courier-mta.org/maildrop.html And this is a currently well supported filtering MTA that can do what procmail is doing now? I'll go look at it, thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS |
|
From: Carlos E. R. <car...@op...> - 2014-10-17 16:58:53
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-10-17 16:31, Jerry wrote: > On Fri, 17 Oct 2014 13:49:17 +0200, Carlos E. R. stated: > I have a rather complex and fully functional set of sieve filters > in place. I have no intention of using Procmail. I just wanted to > by pass having mail delivered to Postfix first; however, it is not > an absolute necessity. Then don't change it :-) I think you get more flexibility and reliability with postfix in the loop. Even simplicity. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRBSrgACgkQtTMYHG2NR9WE+wCgjDSMW9I3RIzYZgahUhr0ldOJ og0An1XlU+9gnKmavABThXMWZQI4iY0B =QkuY -----END PGP SIGNATURE----- |
|
From: Matthias A. <mat...@gm...> - 2014-10-17 16:20:50
|
Am 17.10.2014 um 16:31 schrieb Jerry: > On Fri, 17 Oct 2014 13:49:17 +0200, Carlos E. R. stated: > >> On 2014-10-17 13:04, Jerry wrote: >>> I am attempting to get fetchmail to work with dovecot-lda. >>> >>> Presently, mail is delivered to dovecot-lda via Postfix. The user:group is >>> "vmail". No matter how I attempt to configure the mda in fetchmail, I >>> receive error 75 messages and a warning about the uid not matching. That is because fetchmail will not run it as user "vmail". Please show your fetchmail settings and logging, per <http://www.fetchmail.info/fetchmail-FAQ.html#G3> [...] > I have a rather complex and fully functional set of sieve filters in place. I > have no intention of using Procmail. I just wanted to by pass having mail > delivered to Postfix first; however, it is not an absolute necessity. Then why change the setup? Have you tried reading the dovecot manual on its options, or did you just copy some random configuration? |
|
From: Matthias A. <mat...@gm...> - 2014-10-17 16:13:56
|
Am 17.10.2014 um 10:30 schrieb Gene Heskett: > Humm, since I have been using procmail for about a decade now, and am > aware of its unsupported status simply because there have been no updates > in several years, and it hasn't made any mistakes that I have become aware > of, what do you suggest as its most painfree replacement? Would you notice if single messages ended up in the wrong folder - especially if you do not know that messages have been file in some other place where you do not expect it to be? Personally I prefer maildrop, http://www.courier-mta.org/maildrop.html |
|
From: Jerry <je...@se...> - 2014-10-17 14:31:20
|
On Fri, 17 Oct 2014 13:49:17 +0200, Carlos E. R. stated: > On 2014-10-17 13:04, Jerry wrote: > > I am attempting to get fetchmail to work with dovecot-lda. > > > > Presently, mail is delivered to dovecot-lda via Postfix. The user:group is > > "vmail". No matter how I attempt to configure the mda in fetchmail, I > > receive error 75 messages and a warning about the uid not matching. > > > > Does anyone have a working dovecot-lda with fetchmail config example that > > I can view? > > I have postfix -> procmail -> dovecot-lda. > You could try fetchmail -> procmail -> dovecot-lda. > > > My procmail rules are like this: > > DELIVER = "/usr/lib/dovecot/dovecot-lda" > > ... > > :0f > * ^List-Id:.*<fetchmail-users.lists.sourceforge.net> > | $FORMAIL -bfi 'Reply-To: "fetchmail-users mailing list" > <fet...@li...>' :0 aw: > $HOME/Mail/.D-locks/vsf-sf_lists.lock | $DELIVER -m _Lists/vsf-sf_lists I have a rather complex and fully functional set of sieve filters in place. I have no intention of using Procmail. I just wanted to by pass having mail delivered to Postfix first; however, it is not an absolute necessity. -- Jerry |
|
From: Carlos E. R. <car...@op...> - 2014-10-17 11:49:38
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-10-17 13:04, Jerry wrote: > I am attempting to get fetchmail to work with dovecot-lda. > > Presently, mail is delivered to dovecot-lda via Postfix. The user:group is > "vmail". No matter how I attempt to configure the mda in fetchmail, I receive > error 75 messages and a warning about the uid not matching. > > Does anyone have a working dovecot-lda with fetchmail config example that I > can view? I have postfix -> procmail -> dovecot-lda. You could try fetchmail -> procmail -> dovecot-lda. My procmail rules are like this: DELIVER = "/usr/lib/dovecot/dovecot-lda" ... :0f * ^List-Id:.*<fetchmail-users.lists.sourceforge.net> | $FORMAIL -bfi 'Reply-To: "fetchmail-users mailing list" <fet...@li...>' :0 aw: $HOME/Mail/.D-locks/vsf-sf_lists.lock | $DELIVER -m _Lists/vsf-sf_lists - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRBAjwACgkQtTMYHG2NR9XCfACgjKoGKk81DpowXp1RfCj2cbWm +5IAnicKNvndhP68U+g/sqJGzmKcV2Gk =pkiY -----END PGP SIGNATURE----- |
|
From: Jerry <je...@se...> - 2014-10-17 11:05:01
|
I am attempting to get fetchmail to work with dovecot-lda. Presently, mail is delivered to dovecot-lda via Postfix. The user:group is "vmail". No matter how I attempt to configure the mda in fetchmail, I receive error 75 messages and a warning about the uid not matching. Does anyone have a working dovecot-lda with fetchmail config example that I can view? Thanks! -- Jerry |
18 messages has been excluded from this view by a project administrator.
