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
(5) |
Nov
|
Dec
|
From: Rob M. <rob...@gm...> - 2017-07-11 18:15:18
|
Use IMAP instead. POP assumes that only a single mail client is using the mailbox. IMAP is for when you're using multiple clients, and they should track the read status internally, not rely on the mailbox state. On Tue, Jul 11, 2017 at 9:54 AM Hylton Conacher (ZR1HPC) < hy...@co...> wrote: > I have been noticing that some email, although possibly read on Gmail > and marked as unread, is not downloading to a local mailserver. > > Looking at the log for the last retrieval I see the line of: > > ***Start*** > fetchmail: 155 messages (67 seen) for 72h...@gm... at > pop.gmail.com (15312088 octets). > ***End*** > > Looking through the log I see that the number of messages seen changes > yet never hits 0. > > My fetchmailrc is: > ***Start*** > > #set daemon 300 > #set syslog > #set postmaster "hylton" > set logfile /var/log/fetchmail.log > poll pop.gmail.com > protocol POP3 > > user "mygmailaddress" there with password "mypassword": is "hylton" here > keep ssl > #7mda "/usr/bin/procmail -d %T" > ***End*** > > Whilst there may be other errors in the above file, my main concern is > how to retrieve the 67 'seen' messages as they are not on the local > mailserver but are listed as unread on Gmail, and are sitting in the Inbox? > > Comments? > Hylton > P.S: If this has been covered previously, please direct me to the > archive location of messages for fetchmail so I can use its search > function and hopefully find the answer. > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Fetchmail-users mailing list > Fet...@li... > https://lists.sourceforge.net/lists/listinfo/fetchmail-users > -- Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |
From: Hylton C. (ZR1HPC) <hy...@co...> - 2017-07-11 17:01:30
|
Jerry, comments below. On 11/07/2017 12:20, Jerry wrote: > On Tue, 11 Jul 2017 10:45:37 +0200, Hylton Conacher (ZR1HPC) stated: > >> I have been noticing that some email, although possibly read on Gmail >> and marked as unread, is not downloading to a local mailserver. >> >> Looking at the log for the last retrieval I see the line of: >> >> ***Start*** >> fetchmail: 155 messages (67 seen) for 72h...@gm... at >> pop.gmail.com (15312088 octets). >> ***End*** >> >> Looking through the log I see that the number of messages seen changes >> yet never hits 0. >> >> My fetchmailrc is: >> ***Start*** >> >> #set daemon 300 >> #set syslog >> #set postmaster "hylton" >> set logfile /var/log/fetchmail.log >> poll pop.gmail.com >> protocol POP3 >> >> user "mygmailaddress" there with password "mypassword": is "hylton" >> here keep ssl >> #7mda "/usr/bin/procmail -d %T" >> ***End*** >> >> Whilst there may be other errors in the above file, my main concern is >> how to retrieve the 67 'seen' messages as they are not on the local >> mailserver but are listed as unread on Gmail, and are sitting in the >> Inbox? >> >> Comments? >> Hylton >> P.S: If this has been covered previously, please direct me to the >> archive location of messages for fetchmail so I can use its search >> function and hopefully find the answer. > > A quick and easy fix is simply to access the messages via a web > interface and mark them as "unread". They will then be downloaded the > next time fetchmail accesses the server. As I stated in my first sentence, whilst the messages may be read using the web interface or Gmail app on my phone or iPad, they are also marked as UNREAD using the same device immediately after I have read the email. For some reason, respite being marked as UNREAD and sitting in the Gmail Inbox, these items do not download into my local mailserver via POP3? Anyone have an idea as I too do not want to have to then download them using fetchmail. Regards Hylton |
From: Jerry <je...@se...> - 2017-07-11 16:46:27
|
On Tue, 11 Jul 2017 14:48:46 +0200, Carlos E. R. stated: >On 2017-07-11 14:20, Jerry wrote: >> On Tue, 11 Jul 2017 12:59:57 +0200, Carlos E. R. stated: >> >>> On 2017-07-11 12:20, Jerry wrote: >>>> On Tue, 11 Jul 2017 10:45:37 +0200, Hylton Conacher (ZR1HPC) >>>> stated: >>> >>>> A quick and easy fix is simply to access the messages via a web >>>> interface and mark them as "unread". They will then be downloaded >>>> the next time fetchmail accesses the server. >>> >>> Won't do. >>> >>> I also noticed that if I read a message on the phone, it later does >>> not download with fetchmail. I'm not fully sure, I'd have to >>> verify, but I suspect this is what happens. >>> >>> In that case, I can not go on the web everytime I use fetchmail. >> >> All you have to do is use the web interface on your phone to access >> "gmail", or whatever web based email client you are using. After you >> have read your message(s), mark them as "unread". It is really quite >> simple to do. > >Very inconvenient. Okay, this is so simply anyone could do it. I am assuming that this is a Gmail account. Other web-based mail works basically the same. 1) Create a new web-based account 2) In Gmail, under <SETTINGS> <FORWARDING and POP/IMAP> Enable: Forward a copy of incoming mail to <Your New Account> and "Keep Gmail's copy in the inbox" 3) Configure fetchmail to download mail from your new account. You can continue to read mail from your old account without screwing up everything. It doesn't get much simpler than that. -- Jerry |
From: Peter P. <ro...@ri...> - 2017-07-11 13:56:18
|
On Tue, Jul 11, 2017 at 08:20:55AM -0400, Jerry wrote: > On Tue, 11 Jul 2017 12:59:57 +0200, Carlos E. R. stated: > > >On 2017-07-11 12:20, Jerry wrote: > >> On Tue, 11 Jul 2017 10:45:37 +0200, Hylton Conacher (ZR1HPC) > >> stated: > > > > > >> > >> A quick and easy fix is simply to access the messages via a web > >> interface and mark them as "unread". They will then be downloaded the > >> next time fetchmail accesses the server. > > > >Won't do. > > > >I also noticed that if I read a message on the phone, it later does not > >download with fetchmail. I'm not fully sure, I'd have to verify, but I > >suspect this is what happens. > > > >In that case, I can not go on the web everytime I use fetchmail. > > All you have to do is use the web interface on your phone to access > "gmail", or whatever web based email client you are using. After you > have read your message(s), mark them as "unread". It is really quite > simple to do. Mm, you do realize that this would make it very difficult for the OP to actually keep track of which messages have been read and which have not, right? -- Peter Pentchev ro...@ri... ro...@Fr... pp...@st... PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 |
From: Carlos E. R. <rob...@te...> - 2017-07-11 12:49:12
|
On 2017-07-11 14:20, Jerry wrote: > On Tue, 11 Jul 2017 12:59:57 +0200, Carlos E. R. stated: > >> On 2017-07-11 12:20, Jerry wrote: >>> On Tue, 11 Jul 2017 10:45:37 +0200, Hylton Conacher (ZR1HPC) >>> stated: >> >> >>> >>> A quick and easy fix is simply to access the messages via a web >>> interface and mark them as "unread". They will then be downloaded the >>> next time fetchmail accesses the server. >> >> Won't do. >> >> I also noticed that if I read a message on the phone, it later does not >> download with fetchmail. I'm not fully sure, I'd have to verify, but I >> suspect this is what happens. >> >> In that case, I can not go on the web everytime I use fetchmail. > > All you have to do is use the web interface on your phone to access > "gmail", or whatever web based email client you are using. After you > have read your message(s), mark them as "unread". It is really quite > simple to do. Very inconvenient. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) |
From: Jerry <je...@se...> - 2017-07-11 12:21:06
|
On Tue, 11 Jul 2017 12:59:57 +0200, Carlos E. R. stated: >On 2017-07-11 12:20, Jerry wrote: >> On Tue, 11 Jul 2017 10:45:37 +0200, Hylton Conacher (ZR1HPC) >> stated: > > >> >> A quick and easy fix is simply to access the messages via a web >> interface and mark them as "unread". They will then be downloaded the >> next time fetchmail accesses the server. > >Won't do. > >I also noticed that if I read a message on the phone, it later does not >download with fetchmail. I'm not fully sure, I'd have to verify, but I >suspect this is what happens. > >In that case, I can not go on the web everytime I use fetchmail. All you have to do is use the web interface on your phone to access "gmail", or whatever web based email client you are using. After you have read your message(s), mark them as "unread". It is really quite simple to do. -- Jerry |
From: Carlos E. R. <rob...@te...> - 2017-07-11 11:00:08
|
On 2017-07-11 12:20, Jerry wrote: > On Tue, 11 Jul 2017 10:45:37 +0200, Hylton Conacher (ZR1HPC) stated: > > A quick and easy fix is simply to access the messages via a web > interface and mark them as "unread". They will then be downloaded the > next time fetchmail accesses the server. Won't do. I also noticed that if I read a message on the phone, it later does not download with fetchmail. I'm not fully sure, I'd have to verify, but I suspect this is what happens. In that case, I can not go on the web everytime I use fetchmail. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) |
From: Jerry <je...@se...> - 2017-07-11 10:46:49
|
On Tue, 11 Jul 2017 10:45:37 +0200, Hylton Conacher (ZR1HPC) stated: >I have been noticing that some email, although possibly read on Gmail >and marked as unread, is not downloading to a local mailserver. > >Looking at the log for the last retrieval I see the line of: > >***Start*** >fetchmail: 155 messages (67 seen) for 72h...@gm... at >pop.gmail.com (15312088 octets). >***End*** > >Looking through the log I see that the number of messages seen changes >yet never hits 0. > >My fetchmailrc is: >***Start*** > >#set daemon 300 >#set syslog >#set postmaster "hylton" >set logfile /var/log/fetchmail.log >poll pop.gmail.com >protocol POP3 > >user "mygmailaddress" there with password "mypassword": is "hylton" >here keep ssl >#7mda "/usr/bin/procmail -d %T" >***End*** > >Whilst there may be other errors in the above file, my main concern is >how to retrieve the 67 'seen' messages as they are not on the local >mailserver but are listed as unread on Gmail, and are sitting in the >Inbox? > >Comments? >Hylton >P.S: If this has been covered previously, please direct me to the >archive location of messages for fetchmail so I can use its search >function and hopefully find the answer. A quick and easy fix is simply to access the messages via a web interface and mark them as "unread". They will then be downloaded the next time fetchmail accesses the server. -- Jerry |
From: Hylton C. (ZR1HPC) <hy...@co...> - 2017-07-11 08:54:06
|
I have been noticing that some email, although possibly read on Gmail and marked as unread, is not downloading to a local mailserver. Looking at the log for the last retrieval I see the line of: ***Start*** fetchmail: 155 messages (67 seen) for 72h...@gm... at pop.gmail.com (15312088 octets). ***End*** Looking through the log I see that the number of messages seen changes yet never hits 0. My fetchmailrc is: ***Start*** #set daemon 300 #set syslog #set postmaster "hylton" set logfile /var/log/fetchmail.log poll pop.gmail.com protocol POP3 user "mygmailaddress" there with password "mypassword": is "hylton" here keep ssl #7mda "/usr/bin/procmail -d %T" ***End*** Whilst there may be other errors in the above file, my main concern is how to retrieve the 67 'seen' messages as they are not on the local mailserver but are listed as unread on Gmail, and are sitting in the Inbox? Comments? Hylton P.S: If this has been covered previously, please direct me to the archive location of messages for fetchmail so I can use its search function and hopefully find the answer. |
From: Eric W. <ewa...@gm...> - 2017-06-20 16:45:31
|
Hey All, I'm utilizing fetchmailrc with RT (request tracker), specifically with a program called rt-mailgate. Thats has worked great for years and years (around 10). Just in the last 2 months, we've been experiencing this new issue. Basically, some emails are retrieved by fetchmail, and some are not. If I delete any one of the un-retrieved emails, then the rest of the un-retrieved emails get retrieved and processed by fetchmail. Until then I get this in the error log: fetchmail: 1 message (1 seen) for us...@do... at mail.domain.com (2338 octets). I am using fetchmail version 6.3.26. Here is a list of the poll I use: poll mail.domain.com protocol pop3 username us...@do... password ************************************ mda "/usr/bin/perl /usr/bin/rt-mailgate --url https://localhost:3773 --queue RT_QUEUE --no-verify-ssl --action correspond" is host_server no rewrite no flush no idle ssl sslfingerprint "09:02:4B:F8:C4:DE:C8:9E:D1:BE:D4:98:F2:C5:9A:0D" sslcertpath /etc/ssl/certs fetchsizelimit 0 We've deduced that the issue is not happening with request tracker. This is the thread I started initially with Request Tracker: https://forum.bestpractical.com/t/rt-mailgate-fetchmail-quietly-rejects-email-for-unkown-reasons-maybe-unapproved-x-mdspf-result/31927 Let me know what I can try next to troubleshoot this issue. Thanks! Eric |
From: Carlos E. R. <rob...@te...> - 2017-06-04 11:17:05
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2017-05-19 at 20:55 +0200, Matthias Andree wrote: > Be sure that whatever runs your 50 fetchmail processes with the > individual configuration data: > > 1. also gives each process their own .fetchids file and .pid file > location, easiest done through the FETCHMAILHOME environment variable > (also see the env(1) manual page) which flips the whole set of > directories in one go; > > 2. you run fetchmail from an unprivileged user account, not root or toor > or similar. I went ahead and distributed my fetchmail run in two processes, but it can be easily expanded, manually. I created two directories: cer@Telcontar:~> ls -a .fetchmail_0* .fetchmail_01: . .. .fetchmailrc .fetchmailrc~ .fetchmail_02: . .. .fetchmailrc cer@Telcontar:~> Each directory contains one .fetchmailrc file with a part of the original .fetchmailrc, different on each file so the is no interference. In my case, one file polls gmail, which is particularly slow, and the other polls the rest. Then I created a script: +++...................... #!/bin/bash function bucle_N() { cd $HOME/.fetchmail_$1 echo "Launching fetchmail $1" FETCHMAILHOME=$HOME/.fetchmail_$1 fetchmail -v --fetchmailrc .fetchmailrc echo "Fetchmail $1 finished." } echo "Launching two fetchmail processes" date --iso-8601=seconds bucle_N 01 & bucle_N 02 & echo "Waiting for the two fetchmail processes to finish" wait echo "All fetchmails processes have finished." date --iso-8601=seconds mailq | grep Requests ......................++- Notice that it may not be worth it to download a lot of emails fast, if one is going to filter for spam using spamassassin, which is heavy and slow. - -- Cheers, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlkz7CUACgkQtTMYHG2NR9UDpQCfZybLgZ+gEXOxbBe1AuVig+vl +scAnAxg+q2X1iJdUHTpuqaaO1XMJy2t =K0M8 -----END PGP SIGNATURE----- |
From: Carlos E. R. <rob...@te...> - 2017-05-20 12:43:03
|
On 2017-05-20 12:46, grarpamp wrote: >> (You can however cheat and set the FETCHMAILHOME >> environment variable to overcome this setting, >> but in that case, it is your responsibility to make sure you >> aren't polling the same server with two processes >> at the same time.) > > Polling the same server with N processes at the same time is a > highly valid use case. I assume the issue is not polling the same account. Polling the same server should be no problem, except that fetchmail doesn't do it on its own. > There are various ways to do that today. > Having enhanced fetchmail config file semantics would help > streamline it. That would be nice :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) |
From: grarpamp <gra...@gm...> - 2017-05-20 10:46:47
|
> (You can however cheat and set the FETCHMAILHOME > environment variable to overcome this setting, > but in that case, it is your responsibility to make sure you > aren't polling the same server with two processes > at the same time.) Polling the same server with N processes at the same time is a highly valid use case. There are various ways to do that today. Having enhanced fetchmail config file semantics would help streamline it. Today if you're dealing with multiple accounts and servers in various parallel polling modes / timings, including say a daemon fetch and random check oneshots of the same account, you're almost guaranteed to need end up writing configs on the fly and forking off polling instances. Program instances will always be needed, but config writing or multiple configs shouldn't be needed for them, one config file and an address target should do. The list archives are unfortunately not in a usable format but there were some initial posts on this config stuff for 7.x a while back. |
From: Matthias A. <mat...@gm...> - 2017-05-19 18:55:47
|
Am 19.05.2017 um 08:24 schrieb Christopher Mudersbach: > Since we are processing the emails after they downloaded we have multiple poll processes running that initiate the above commands. If one of those poll processes is initiating the fetchmail command and another one is already running we get the following message: > > fetchmail: WARNING: Running as root is discouraged. > fetchmail: another foreground fetchmail is running at 28646. > > Is there any way we can run multiple fetchmail processes at the same time? See Carlos E.R.'s message and my followup for an approach to do that. Regarding the messages you see, you are changing two items at the same time and drawing the wrong conclusion from the warning. The warning above is because you've run fetchmail from a privileged account (root), not because you're running it twice. In the latter case you'd get different diagnostics. Be sure that whatever runs your 50 fetchmail processes with the individual configuration data: 1. also gives each process their own .fetchids file and .pid file location, easiest done through the FETCHMAILHOME environment variable (also see the env(1) manual page) which flips the whole set of directories in one go; 2. you run fetchmail from an unprivileged user account, not root or toor or similar. |
From: Matthias A. <mat...@gm...> - 2017-05-19 18:51:16
|
Am 19.05.2017 um 13:25 schrieb Carlos E. R.: > See the documentation: > Only one daemon process is permitted per user; in daemon mode, > fetchmail sets up a per-user lockfile to guar- > antee this. (You can however cheat and set the FETCHMAILHOME > environment variable to overcome this setting, > but in that case, it is your responsibility to make sure you > aren't polling the same server with two processes > at the same time.) > > I don't exactly know why not, as long as you don't poll the same > account. It should be able to poll two different accounts from the same > server, I think. Seconded. The documentation could be more precise and should read "polling the same account ... at the same time" instead of "polling the same server...", and FETCHMAILHOME is the way to go. The GNU "parallel" utility might then also be an easy way to launch a limited number of concurrent processes. Answering "Why not" is simple, with the documentation refinement shown above: It's useless and doesn't work right. Fetchmail isn't designed for itself running twice on the same mailbox and would not properly synchronize its data between its processes, so both processes might end up corrupting each other's state, or fetching mail in duplicate, or bump into server locks and be refused, or thereabouts. But that would not be Christopher's approach anyways, I presume. |
From: Matthias A. <mat...@gm...> - 2017-05-19 18:44:07
|
Am 19.05.2017 um 08:38 schrieb grarpamp: > IIRC, try specifying --pidfile $(mktemp blah.XXXXXXXXX) > > Of course pid files are foolish broken antique races, running > without them should be made possible, and daemon > monitors are better... but until then. This does not contribute to answering the originator's questions. |
From: Carlos E. R. <rob...@te...> - 2017-05-19 11:25:24
|
On 2017-05-19 08:24, Christopher Mudersbach wrote: > Hello, ... > Is there any way we can run multiple fetchmail processes at the same time? As a different user (fetch_01, fetch_02...) See the documentation: Only one daemon process is permitted per user; in daemon mode, fetchmail sets up a per-user lockfile to guar- antee this. (You can however cheat and set the FETCHMAILHOME environment variable to overcome this setting, but in that case, it is your responsibility to make sure you aren't polling the same server with two processes at the same time.) I don't exactly know why not, as long as you don't poll the same account. It should be able to poll two different accounts from the same server, I think. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) |
From: grarpamp <gra...@gm...> - 2017-05-19 06:39:40
|
IIRC, try specifying --pidfile $(mktemp blah.XXXXXXXXX) Of course pid files are foolish broken antique races, running without them should be made possible, and daemon monitors are better... but until then. |
From: Christopher M. <C.M...@da...> - 2017-05-19 06:24:39
|
Hello, we have the following problem: We are downloading emails from our mailserver through fetchmail. Right now we are downloading from 50 Mailboxes (via POP3) and have it setup that every mailbox has its own config file. For example: fetchmail -F -f /dokuweb/log/.fetchmailrc_0042 fetchmail -F -f /dokuweb/log/.fetchmailrc_einvoice_00D4 .fetchmailrc_0042 poll XXX.XXX.XXX.XXX protocol pop3 auth password user XXX password XXX is XXX poll XXX.XXX.XXX.XXXX protocol pop3 auth password user YYY password XXX is YYY .fetchmailrc_einvoice_00D4: poll XXX.XXX.XXX.XXX protocol pop3 auth password user XXX password XXX is XXX Since we are processing the emails after they downloaded we have multiple poll processes running that initiate the above commands. If one of those poll processes is initiating the fetchmail command and another one is already running we get the following message: fetchmail: WARNING: Running as root is discouraged. fetchmail: another foreground fetchmail is running at 28646. Is there any way we can run multiple fetchmail processes at the same time? Thank you very much. ________________________________ Amtsgericht Siegen HRB 4697 - Gesch?ftsf?hrer Sebastian Weber Das Web-basierte Archivierungs- und Informationsmanagementsystem http://www.datasec.de Oder per e-Mail / or send a mailto:co...@da... Diese elektronisch uebermittelte Post ist nur fuer den aufgefuehrten Empfaenger bestimmt. Im Falle einer irrtuemlichen Uebermittlung bitten wir um Ruecksendung an den Absender. Wir weisen darauf hin, dass diese Sendung einschliesslich aller Anlagen insbesondere Dateianlagen unser Eigentum ist und ohne unsere schriftliche Zustimmung weder abgeaendert, kopiert noch dritten Personen zugaenglich gemacht werden darf. This e-mail is private and confidential and should only be read by those to whom it is addressed. If you are not the intended recipient, please return this e-mail to the sender. We notify that any dissemination, distribution, copy, reproduction, modification or publication of this communication is strictly prohibited. This message is not intended to be relied upon by any person without subsequent written confirmation of its contents. |
From: Chris <cpo...@em...> - 2017-04-04 11:28:30
|
On Tue, 2017-04-04 at 09:45 +0200, Matthias Andree wrote: > Am 04.04.2017 um 04:42 schrieb Chris: > > > > I've been testing 17.04 Gnome in a VM and wanted to get Fetchmail > > setup. According to the config.log - https://pastebin.com/42B61zxE > > I > > don't have OpenSSL installed however this seems to show that it is: > > > > sudo apt list OpenSSL > > [sudo] password for chris: > > Listing... Done > > openssl/zesty,now 1.0.2g-1ubuntu11 amd64 [installed] > > > > My configure command is $ ./configure --with-ssl. > > > > Anyone with ideas? I may not reply immediately since I'll be out of > > town tomorrow through sometime Friday. > $ sudo apt install libssl-dev > > Thanks for the nudge Matthias and grarpamp, I should know by now that the dev packages need to be installed also. -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 06:25:15 up 1 day, 9:07, 1 user, load average: 2.35, 1.05, 0.46 Description: Ubuntu 16.04.2 LTS, kernel 4.4.0-71-generic |
From: Matthias A. <mat...@gm...> - 2017-04-04 07:45:42
|
Am 04.04.2017 um 04:42 schrieb Chris: > I've been testing 17.04 Gnome in a VM and wanted to get Fetchmail > setup. According to the config.log - https://pastebin.com/42B61zxE I > don't have OpenSSL installed however this seems to show that it is: > > sudo apt list OpenSSL > [sudo] password for chris: > Listing... Done > openssl/zesty,now 1.0.2g-1ubuntu11 amd64 [installed] > > My configure command is $ ./configure --with-ssl. > > Anyone with ideas? I may not reply immediately since I'll be out of > town tomorrow through sometime Friday. $ sudo apt install libssl-dev |
From: grarpamp <gra...@gm...> - 2017-04-04 02:58:23
|
On Mon, Apr 3, 2017 at 10:42 PM, Chris <cpo...@em...> wrote: > don't have OpenSSL installed however this seems to show that it is Most stuff based on debian, maybe even more linux's, do silly thing of userland and dev seperate, you have to also install "-dev" versions of the same package if you want to compile anything, maybe they try to save space for micro installs but it's silly major headache. With FreeBSD, and pretty much all BSD's, they're sane, once you add the package, you get everything you need, and the configure below just works. https://www.freebsd.org/ https://www.freebsd.org/ports/categories-grouped.html https://www.freebsd.org/cgi/ports.cgi?query=openssl&stype=name&sektion=all > My configure command is $ ./configure --with-ssl. |
From: Chris <cpo...@em...> - 2017-04-04 02:42:12
|
I've been testing 17.04 Gnome in a VM and wanted to get Fetchmail setup. According to the config.log - https://pastebin.com/42B61zxE I don't have OpenSSL installed however this seems to show that it is: sudo apt list OpenSSL [sudo] password for chris: Listing... Done openssl/zesty,now 1.0.2g-1ubuntu11 amd64 [installed] My configure command is $ ./configure --with-ssl. Anyone with ideas? I may not reply immediately since I'll be out of town tomorrow through sometime Friday. Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 20:53:13 up 23:35, 1 user, load average: 3.00, 4.05, 3.23 Description: Ubuntu 16.04.2 LTS, kernel 4.4.0-71-generic -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 21:41:33 up 1 day, 23 min, 1 user, load average: 0.26, 0.35, 0.51 Description: Ubuntu 16.04.2 LTS, kernel 4.4.0-71-generic |
From: grarpamp <gra...@gm...> - 2017-02-22 23:22:23
|
>>> Can anyone list services that require this? >> >> Gmail does, but can be disabled. Then it is not *required*. If people know of services actually starting to *refuse* AUTH=PLAIN LOGIN, then the various OAuth forms might be useful to look into. >> You can look at Thunderbird code to >> find out what they do. I don't remember what the dialogue said, though, >> it pops up rarely. I think it is done in javascript, maybe they have a >> document on it. > Guys, of course it is technically doable [... not gonna happen] I can't see any problem with fetchmail providing a shellout to the operations, users providing that, patches, whatever. Especially since I suspect it is not actually dependant on human brainpower interaction, but I'd have to look further to know that. Efforts there would also depend on prevalance and impact of any *required*'s that may exist as above. > Frontier If reading right, maybe frontier is farming as proxy out to yahoo as virtualhost, so try connecting with PLAIN LOGIN directly to yahoo's imap/pop/submission servers specifying whatever your "frontier mail" user@dom:pass is. Unless yahoo has firewalled off their virtual to only frontier's proxy, it should work and you can bypass frontier as middleman. Or try logging into 'frontier.yahoo.com' as they say, whatever that is. What you say 'expires in 2018' could be frontier generating that app specfic from yahoo on your behalf using your user:pass to do it until yahoo bans that. I've really not looked at this so don't read much in me yet. You probably don't want to put much dependancy on your ISP provided email, you could move residence where they do not exist, they could be bought, stop service, etc. Best is your own portable domain housed with email literally anywhere on the net for under $25 or so per yr. |
From: Hans C. <fo...@gm...> - 2017-02-22 20:26:49
|
On Wed, 22 Feb 2017, Matthias Andree wrote: > Find a switch in your account settings that will let you use some more > traditional authentication scheme directly, or find a switch they'll > perfidiously have mislabelled "allow insecure authentication methods" or > such in a similar scary wording (Google and Yahoo provide it and name it > so) and set it so you can log in with passwords. I can't find any switch like that. The Yahoo "Account Settings" link takes me to a Frontier specific page with very few options. BUT, there does appear to be another option.... > Alternatively, perhaps Frontier permit you to set application-specific > passwords for mail, which might work along the lines laid out in > <https://johnlane.ie/gmail-fetchmail-is-a-less-secure-app.html>. THIS ONE. Thank you for the suggestion and that link. When I originally saw the "App Password" option on the Frontier page, I thought it was somehow related to OAuth. In other words, I thought you had to obtain an "App Password" in order to use OAuth. But I guess that's not the case. The downside to this option (assuming I can get it to work) is it also appears to be a temporary solution. There's a note on the Frontier page where I request the "App Password" that says: ... this option is subject to expire in 2018. So, I guess that will help for now, but I'll still need to come up with an alternate solution eventually. And just to clarify. All I need to do from a fetchmail perspective is replace the current entry in my .fetchmailrc: ... user 'us...@fr...' there with password 'XXXXXXXXX' ... with the newly generated "App Password": ... user 'us...@fr...' there with password 'APP PASSWORD' ... |