From: Keith <kil...@gm...> - 2017-11-13 08:01:02
|
I would like to use Fetchmail to receive all emails sent to my ISP that uses IMAP. The problem is that I use a mobile device to regularly read my ISP email. When Fetchmail goes to retrieve my email it sees the messages as seen and won't download them. There is one command that will fetch all email on the server, but I want to keep my email on the ISP server after downloading it with fetchmail. Is there a command that will retrieve the email that has not been downloaded by fetchmail even though it has been seen by my mobile email device? |
From: Volker W. <po...@vo...> - 2017-11-13 08:26:35
|
Am Montag, 13. November 2017, 00:00:49 CET schrieb Keith: > I would like to use Fetchmail to receive all emails sent to my ISP that > uses IMAP. The problem is that I use a mobile device to regularly read > my ISP email. When Fetchmail goes to retrieve my email it sees the > messages as seen and won't download them. There is one command that will > fetch all email on the server, but I want to keep my email on the ISP > server after downloading it with fetchmail. > > > Is there a command that will retrieve the email that has not been > downloaded by fetchmail even though it has been seen by my mobile email > device? Yes, use the "fetchall" keyword in your fetchmailrc. See the fetchmail man page. Volker |
From: Matthias A. <mat...@gm...> - 2017-11-14 23:42:23
|
Am 13.11.2017 um 09:09 schrieb Volker Wysk: > Am Montag, 13. November 2017, 00:00:49 CET schrieb Keith: >> I would like to use Fetchmail to receive all emails sent to my ISP that >> uses IMAP. The problem is that I use a mobile device to regularly read >> my ISP email. When Fetchmail goes to retrieve my email it sees the >> messages as seen and won't download them. There is one command that will >> fetch all email on the server, but I want to keep my email on the ISP >> server after downloading it with fetchmail. >> >> >> Is there a command that will retrieve the email that has not been >> downloaded by fetchmail even though it has been seen by my mobile email >> device? > Yes, use the "fetchall" keyword in your fetchmailrc. See the fetchmail man page. That does not combine with the desired --keep option. Unfortunately, fetchmail 6.3.26 cannot currently work decently in this situation because it lacks UID + UIDVALIDITY support. There were past contributions to add UID support but without UIDVALIDITY; so they were worthless. Such code still needs to be written I'm afraid. |
From: <kj...@o2...> - 2017-12-03 19:30:50
|
Matthias Andree <mat...@gm...> writes: [...] > > Unfortunately, fetchmail 6.3.26 cannot currently work decently in this > situation because it lacks UID + UIDVALIDITY support. There were past > contributions to add UID support but without UIDVALIDITY; so they were > worthless. Such code still needs to be written I'm afraid. > I am interested in writing IMAP UID code, and below my thoughts: - we have to deal with uidvalidity - we have to deal with folders (each imap folder have its own uidvalidity/uid list) - uid.c code has a lot of quirks to manage lot of strange thigs with pop-uids (spaces and @-sings in names and uids - yes?) - imap uids are far simpler (they are integers, even sorted IIRC) - so (despite I hate to duplicate code) it is worth consider having imap uids next to pop3 uids, not modify uid.c? It is my 3¢, what do you think? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ Ogólny sens [helpa z W98] jest poprawny. Pod warunkiem, że z góry wiadomo co autor miał na myśli. -- Marcin Wieczorek na p.c.o.a. |
From: <kj...@o2...> - 2017-12-11 06:54:16
|
kj...@o2... (Kamil Jońca) writes: > Matthias Andree <mat...@gm...> writes: > > [...] >> >> Unfortunately, fetchmail 6.3.26 cannot currently work decently in this >> situation because it lacks UID + UIDVALIDITY support. There were past >> contributions to add UID support but without UIDVALIDITY; so they were >> worthless. Such code still needs to be written I'm afraid. >> > I am interested in writing IMAP UID code, and below my thoughts: > [...] It is my initial patch to have uid/uidvalidity support. - it uses its own file to keep uid data for imap (~/.fetchids-imap) - code for read / write imap uid lists was shamelessly plagiarized and then changed. - I have no idea how to deal with IMAP2 - it looks, that this protocol have no UID concept - I worked with debian's fetchmail-6.3.26 varsion as a base - it was only rougly tested, especially there were no testing with -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html If someone had told me I would be Pope one day, I would have studied harder. -- Pope John Paul I |
From: <kj...@o2...> - 2017-12-11 18:00:00
|
kj...@o2... (Kamil Jońca) writes: > kj...@o2... (Kamil Jońca) writes: > >> Matthias Andree <mat...@gm...> writes: >> >> [...] >>> >>> Unfortunately, fetchmail 6.3.26 cannot currently work decently in this >>> situation because it lacks UID + UIDVALIDITY support. There were past >>> contributions to add UID support but without UIDVALIDITY; so they were >>> worthless. Such code still needs to be written I'm afraid. >>> >> I am interested in writing IMAP UID code, and below my thoughts: >> [...] > > It is my initial patch to have uid/uidvalidity support. > - it uses its own file to keep uid data for imap (~/.fetchids-imap) > - code for read / write imap uid lists was shamelessly plagiarized and > then changed. > - I have no idea how to deal with IMAP2 - it looks, that this protocol > have no UID concept > - I worked with debian's fetchmail-6.3.26 varsion as a base > - it was only rougly tested, especially there were no testing with Attachement has been deleted. My patch is at https://drive.google.com/open?id=1UkPJEnvhOfKpJigTCKPpJBcR3ZBSugzM (it also have correction for "INBOX" mailbox) KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html Jak ktoś ma pecha, to złamie ząb podczas seksu oralnego (S.Sokół) |
From: Matthias A. <mat...@gm...> - 2017-12-11 23:03:07
|
Am 11.12.2017 um 18:59 schrieb Kamil Jońca: > kj...@o2... (Kamil Jońca) writes: > >> kj...@o2... (Kamil Jońca) writes: >> >>> Matthias Andree <mat...@gm...> writes: >>> >>> [...] >>>> Unfortunately, fetchmail 6.3.26 cannot currently work decently in this >>>> situation because it lacks UID + UIDVALIDITY support. There were past >>>> contributions to add UID support but without UIDVALIDITY; so they were >>>> worthless. Such code still needs to be written I'm afraid. >>>> >>> I am interested in writing IMAP UID code, and below my thoughts: >>> [...] >> It is my initial patch to have uid/uidvalidity support. >> - it uses its own file to keep uid data for imap (~/.fetchids-imap) >> - code for read / write imap uid lists was shamelessly plagiarized and >> then changed. >> - I have no idea how to deal with IMAP2 - it looks, that this protocol >> have no UID concept >> - I worked with debian's fetchmail-6.3.26 varsion as a base >> - it was only rougly tested, especially there were no testing with > Attachement has been deleted. My patch is at > https://drive.google.com/open?id=1UkPJEnvhOfKpJigTCKPpJBcR3ZBSugzM > (it also have correction for "INBOX" mailbox) > KJ > Hello Kamil, thanks for taking the initiative. I've been meaning to respond earlier, but real live has interfered, and unfortunately I wasn't able to tell you in time that this should either be against the "master" branch (if intrusive) or the "legacy_64" branch (if just an extension isolated well from the rest) because 6.3.26 is basically a dead end, and I have merged a patch by Rainer Weikusat to switch the slow (O(n^2)) POP3 UID list handling to something faster. OTOH as long as IMAP UIDs are integers, and continuous runs can be compressed (for C++ I think Boost has a library) those POP3 UIDs have a different requirement set. That said, I think it looks good as a proof of concept and with a few touch-ups, and someone - possibly me - contributing a better IMAP response parser that we can avoid matching empiric fixed strings, which might break when some freemailer develops a different dialect of IMAP4r1, and make the code more robust and portable. I am not asking you to fix the IMAP parser though. So, if you want to play with things and are happy to use Git, I propose that you clone out from https://gitlab.com/fetchmail/fetchmail and create a new kj-imap-uids branch there branching off RELEASE_6-3-26, and then rebase onto either legacy_64 or master. The interface changes you are doing might make me wonder about "master" which is open to more intrusive changes than legacy_64 which cannot break interfaces without very good reasons, but legacy_64 seems to be OK since the changes seem reasonable from skimming the patch quickly. Regards, Matthias |
From: Hylton C. (ZR1HPC) <hy...@co...> - 2017-12-12 16:27:48
|
Hi Keith, On 13/11/2017 10:00, Keith wrote: > I would like to use Fetchmail to receive all emails sent to my ISP that > uses IMAP. The problem is that I use a mobile device to regularly read > my ISP email. When Fetchmail goes to retrieve my email it sees the > messages as seen and won't download them. There is one command that will > fetch all email on the server, but I want to keep my email on the ISP > server after downloading it with fetchmail. Sounds like you need POP but to leave the emails on the server. This would reduce the bandwidth required to only the new messages. I mention this as I route all my ISP mail for my domain through a Gmail account. I have a dovecot IMAP server at home, using uidl for what it is worth without UIDVALIDITY. Once the mails have been downloaded from the Inbox they are archived in GMail, allowing me to always have a backup, albeit not marked as unread. Perhaps you could do something similar as GMail is great for SPAM filtering. I use fetchmail to POP all the email from my GMail inbox, both seen and new, into my local IMAP mailserver. From here I can use any device I care to access the mailbox over my local network i.e. sync device early morning and use web access for what comes during day, if needed/before next sync. > > Is there a command that will retrieve the email that has not been > downloaded by fetchmail even though it has been seen by my mobile email > device? > > > > > ------------------------------------------------------------------------------ > 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 > |
From: <kj...@o2...> - 2017-12-13 03:04:49
|
Matthias Andree <mat...@gm...> writes: > Hello Kamil, > > thanks for taking the initiative. I've been meaning to respond earlier, > but real live has interfered, and unfortunately I wasn't able to tell > you in time that this should either be against the "master" branch (if > intrusive) or the "legacy_64" branch (if just an extension isolated well > from the rest) because 6.3.26 is basically a dead end, and I have merged Yes, but this version is currently in Debian, and I wanted to use something I can revert quickly. :) > > So, if you want to play with things and are happy to use Git, I propose > that you clone out from https://gitlab.com/fetchmail/fetchmail and > create a new kj-imap-uids branch there branching off RELEASE_6-3-26, and (I cannot push to gitlab - I am not sure if I make everything properly) At https://drive.google.com/file/d/1KanPVHBXLhTbkCFlaXSySEys4pdlmlF-/view?usp=sharing are patch made against master branch, and also there is some corrections: 1. uid file is not hardcoded now, but its name is derived from uidfile with "-imap" suffix 2. functions which read/write imap uids have better debug 3. sanity checks when remove "\n" from data lines KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html Password: |
From: Matthias A. <mat...@gm...> - 2017-12-13 08:31:29
|
Am 13.12.2017 um 04:04 schrieb Kamil Jońca: > > (I cannot push to gitlab - I am not sure if I make everything properly) Hi Kamil, You cannot push into my repository - with most Git repositories, the model is: you fork/branch/clone your own repository from mine, push into your own and then send me a so-called "pull request" telling me to merge. > At > https://drive.google.com/file/d/1KanPVHBXLhTbkCFlaXSySEys4pdlmlF-/view?usp=sharing > > are patch made against master branch, and also there is some > corrections: > 1. uid file is not hardcoded now, but its name is derived from uidfile > with "-imap" suffix > 2. functions which read/write imap uids have better debug > 3. sanity checks when remove "\n" from data lines Dziękuję! I hope to evaluate this over the week-end. |