fetchmail-users — User questions and discussion

Re: [Fetchmail-users] Using Fetchmail with IMAP

[Hylton C. (ZR1HPC) <hy...@co...>]

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
> 

Re: [Fetchmail-users] Using Fetchmail with IMAP

[Matthias A. <mat...@gm...>]

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

Re: [Fetchmail-users] Using Fetchmail with IMAP

[<kj...@o2...>]

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ół)

Re: [Fetchmail-users] Using Fetchmail with IMAP

[<kj...@o2...>]

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

Re: [Fetchmail-users] Gmail SSL cert problem

[Chris <cpo...@em...>]

On Tue, 2017-12-05 at 01:42 -0500, grarpamp wrote:
> Maybe you changed fetchmail config, [auto] updated
> or changed some OS bits or CA bundle, etc we
> don't know why. Maybe G2 / G3 cert lost.
> And google has been changing things too.
> 
> You can get google intermediates here
> https://pki.google.com/
> https://pki.goog/
> https://security.googleblog.com/
> 
> Or from URL's in the server cert
> openssl s_client -connect pop.gmail.com:pop3s < /dev/null
> openssl x509 -text -in <certfile>
> 
> Also consider fetchmail fingerprint / certfiles options
> to avoid some various types of attack.
> 
> Search these things to learn more as needed.
> 
Thank you, I finally got it to working again. I went into my certs on
Firefox and exported these:

GlobalSignCloudSSLCA-SHA256-G3.crt
GlobalSignDomainValidationCA-SHA256-G2.crt
GlobalSignECCRootCA-R4.crt
GlobalSignECCRootCA-R5.crt
GlobalSignExtendedValidationCA-SHA256-G2.crt
GlobalSignOrganizationValidationCA-SHA256-G2.crt
GlobalSignRootCA-R2.crt
GlobalSignRootCA-R3.crt
GoogleInternetAuthorityG2.crt
GoogleInternetAuthorityG3.crt

and ran c_rehash ~/certs/.certs. I doubt all of the above were really
needed to fix the issue and I probably should have done one at a time
until it was fixed.

Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
11:37:02 up 13 days, 38 min, 1 user, load average: 1.26, 1.24, 1.25
Description:	Ubuntu 16.04.3 LTS, kernel 4.10.0-40-generic

Re: [Fetchmail-users] Gmail SSL cert problem

[grarpamp <gra...@gm...>]

Maybe you changed fetchmail config, [auto] updated
or changed some OS bits or CA bundle, etc we
don't know why. Maybe G2 / G3 cert lost.
And google has been changing things too.

You can get google intermediates here
https://pki.google.com/
https://pki.goog/
https://security.googleblog.com/

Or from URL's in the server cert
openssl s_client -connect pop.gmail.com:pop3s < /dev/null
openssl x509 -text -in <certfile>

Also consider fetchmail fingerprint / certfiles options
to avoid some various types of attack.

Search these things to learn more as needed.

[Fetchmail-users] Gmail SSL cert problem

[Chris <cpo...@em...>]

Using Fetchmail to poll the Gmail pop server. It's been working great
until I noticed this today:

fetchmail: Server certificate verification error: unable to get local
issuer certificate
fetchmail: Broken certification chain at: /OU=GlobalSign Root CA -
R2/O=GlobalSign/CN=GlobalSign
fetchmail: This could mean that the server did not provide the
intermediate CA's certificate(s), which is nothing fetchmail could do
anything about.  For details, please see the README.SSL-SERVER document
that ships with fetchmail.
fetchmail: This could mean that the root CA's signing certificate is
not in the trusted CA certificate location, or that c_rehash needs to
be run on the certificate directory. For details, please see the
documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: OpenSSL reported: error:14090086:SSL
routines:ssl3_get_server_certificate:certificate verify failed
fetchmail: SSL connection failed.

As it says above, it's not a Fetchmail problem, I realize that. What I
need to do apparently is get hold of a new 'googlepop.pem certificate
which I've been googling for the past few hours and can't find it. Does
anyone have any idea where to locate a new certificate?

Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
19:37:52 up 12 days, 8:39, 1 user, load average: 1.47, 1.06, 0.79
Description:	Ubuntu 16.04.3 LTS, kernel 4.10.0-40-generic

Re: [Fetchmail-users] Using Fetchmail with IMAP

[<kj...@o2...>]

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.

Re: [Fetchmail-users] Fetchmail 6.3.26-6 Corrupting Group Address Headers.

[Ralph C. <ra...@in...>]

Hi Matthias,

> Please submit the .fetchmailrc, with passwords removed, off-list
> (directly to me).

The problem occurs without using .fetchmailrc.

    $ me=ra...@in...
    $ LC_ALL=C fetchmail -f /dev/null -p imap -l 31415 --ssl \
    >     -u $me --smtpname $me mail27.pair.com
    ...
    reading message ra...@in...@ruis.pair.com:3 of 4 (2104 header octets) (6 body octets) flushed
    ...
    $

That email had the problem.

Have you tried to re-create it yourself?  It's trivial to do AFAICS.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

Re: [Fetchmail-users] Fetchmail 6.3.26-6 Corrupting Group Address Headers.

[Matthias A. <mat...@gm...>]

Am 20.11.2017 um 17:10 schrieb Ralph Corderoy:
> Hi Matthias,
>
>> I need the configuration (including usernames but without passwords)
>> since that influences how rewriting happens and what code paths are
>> run, and the -vv verbose trace.
> Those two are attached.  I cut out the names of all the entries in
> ~/.fetchmailrc, and the UIDL lists, since they leak private information.
> If there's anything missing you need, let me know.

Please submit the .fetchmailrc, with passwords removed, off-list
(directly to me).
Since these are single-drop and the rewriting issue is unrelated to your
login names, feel free to remove usernames/login names as well, and you
can GnuPG encrypt to my 0xE412B156EFF3855A if you like.

Re: [Fetchmail-users] Fetchmail 6.3.26-6 Corrupting Group Address Headers.

[Ralph C. <ra...@in...>]

Hi Matthias,

> I need the configuration (including usernames but without passwords)
> since that influences how rewriting happens and what code paths are
> run, and the -vv verbose trace.

Those two are attached.  I cut out the names of all the entries in
~/.fetchmailrc, and the UIDL lists, since they leak private information.
If there's anything missing you need, let me know.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

Re: [Fetchmail-users] Fetchmail 6.3.26-6 Corrupting Group Address Headers.

[Ralph C. <ra...@in...>]

Hi Matthias,

> >     curl -sS ftp://lists.gnu.org/nmh-workers/2017-11 |
> >     sed -n '/Sat Nov 18 19:42:55 2017/,/^To:/p' |
> >     sed -n '$p'
>
> apparently that does not get me the message you are referring to, I am
> only getting this:
>
> > To: nmh...@no...

Sorry, it appears the pipeline is faulty as the archive grows.  This
works for me now.

    $ curl -sS ftp://lists.gnu.org/nmh-workers/2017-11 |
    > sed -n '/Sat Nov 18 19:42:55 2017/,/^$/p' |
    > grep '^To:'
    To: nmh-announce: ;, nmh...@no... 
    $

If you download that URL then you will find the start of the whole email
using that date as it's in the From_ line.

There are two addresses.  The first is a group address.  This is
commonly used in the form `undisclosed-recipients: ;'.  The second is a
normal, disclosed, recipient.  RFC 2822 makes very clear this is valid,
and has some handy examples to stress-test parsers.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

Re: [Fetchmail-users] Fetchmail 6.3.26-6 Corrupting Group Address Headers.

[Matthias A. <mat...@gm...>]

Am 20.11.2017 um 16:46 schrieb Ralph Corderoy:
> Hi Matthias,
>
>>> I used fetchmail 6.3.26-6
> ...
>>>     About to rewrite To: group-addr: ;, ra...@ex......
>>>     ...rewritten version is To: group-addr: ;@ruis.pair.com, ra...@ex....
>> Please file a proper report.
>> <http://www.fetchmail.info/fetchmail-FAQ.html#G3>
> No, sorry, you haven't made clear what's lacking and I've already spent
> too much time trying to find out how to report a bug;  that shouldn't be
> buried in the FAQ.
>
> It seems very likely from looking at fetchmail-6.3.26.tar.xz's
> rfc822.c's reply_hack() that this section kicks in erroneously.
>
> 	/*
> 	 * Not expanding on last non-WS == ';' deals with groupnames,
> 	 * an obscure misfeature described in sections
> 	 * 6.1, 6.2.6, and A.1.5 of the RFC822 standard.
> 	 */
> 	else if ((*from == ',' || HEADER_END(from))
> 		 && has_bare_name_part
> 		 && !has_host_part
> 		 && last_nws != ';')
> 	{
>     ...
> 	    *from++ = '@';
> 	    memcpy(from, host, hostlen);
> 	    from = p + hostlen + 1;
> 	    has_host_part = TRUE;
> 	}
>
> If there's useful data I can provide, let me know as fetchmail is
> currently corrupting modern, valid, emails that are in the wild;  not
> some exotic test case.
>
I need the configuration (including usernames but without passwords)
since that influences how rewriting happens and what code paths are run,
and the -vv verbose trace.
Please disregard the other message where I am asking for the message, I
have been able to extract the "offender" from the archive.

Re: [Fetchmail-users] Fetchmail 6.3.26-6 Corrupting Group Address Headers.

[Ralph C. <ra...@in...>]

Hi Matthias,

> > I used fetchmail 6.3.26-6
...
> >     About to rewrite To: group-addr: ;, ra...@ex......
> >     ...rewritten version is To: group-addr: ;@ruis.pair.com, ra...@ex....
>
> Please file a proper report.
> <http://www.fetchmail.info/fetchmail-FAQ.html#G3>

No, sorry, you haven't made clear what's lacking and I've already spent
too much time trying to find out how to report a bug;  that shouldn't be
buried in the FAQ.

It seems very likely from looking at fetchmail-6.3.26.tar.xz's
rfc822.c's reply_hack() that this section kicks in erroneously.

	/*
	 * Not expanding on last non-WS == ';' deals with groupnames,
	 * an obscure misfeature described in sections
	 * 6.1, 6.2.6, and A.1.5 of the RFC822 standard.
	 */
	else if ((*from == ',' || HEADER_END(from))
		 && has_bare_name_part
		 && !has_host_part
		 && last_nws != ';')
	{
    ...
	    *from++ = '@';
	    memcpy(from, host, hostlen);
	    from = p + hostlen + 1;
	    has_host_part = TRUE;
	}

If there's useful data I can provide, let me know as fetchmail is
currently corrupting modern, valid, emails that are in the wild;  not
some exotic test case.

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

Re: [Fetchmail-users] Fetchmail 6.3.26-6 Corrupting Group Address Headers.

[Matthias A. <mat...@gm...>]

> curl -sS ftp://lists.gnu.org/nmh-workers/2017-11 |
>     sed -n '/Sat Nov 18 19:42:55 2017/,/^To:/p' |
>     sed -n '$p'

Ralph,


apparently that does not get me the message you are referring to, I am
only getting this:

> To: nmh...@no...

which looks sane... please send me the "untransferable" header off-list
as an attachment (feel free to gzip it) along with the report.


Regards,

Matthias

Re: [Fetchmail-users] Fetchmail 6.3.26-6 Corrupting Group Address Headers.

[Matthias A. <mat...@gm...>]

Am 20.11.2017 um 14:37 schrieb Ralph Corderoy:
> Hi,
>
> I used fetchmail 6.3.26-6 on Arch Linux to fetch using IMAP an email
> that had a To header with two email addresses, the first a group
> address.  The mailing list archive has what was sent to list members.
>
>     $ curl -sS ftp://lists.gnu.org/nmh-workers/2017-11 |
>     > sed -n '/Sat Nov 18 19:42:55 2017/,/^To:/p' |
>     > sed -n '$p'
>     To: nmh-announce: ;, nmh...@no... 
>     $
>
> After fetchmail had passed it to my local Postfix, it had been
> corrupted.
>
>     To: nmh-announce: ;, ""@ruis.pair.com, nmh...@no...
>
> ruis.pair.com was the IMAP peer.
>
> I confirmed it was fetchmail and not Postfix at fault by arranging a
> test message to arrive at the peer, inspecting it by manually typing
> IMAP commands to show it wasn't corrupted, and then capturing
> fetchmail's verbose output on fetching it.
>
>     About to rewrite To: group-addr: ;, ra...@ex......
>     ...rewritten version is To: group-addr: ;@ruis.pair.com, ra...@ex....
>
> Please acknowledge the bug.  (I found it hard to see where bugs should
> be reported when I looked at fetchmail.info and elsewhere.)
>

Please file a proper report.

<http://www.fetchmail.info/fetchmail-FAQ.html#G3>

[Fetchmail-users] Fetchmail 6.3.26-6 Corrupting Group Address Headers.

[Ralph C. <ra...@in...>]

Hi,

I used fetchmail 6.3.26-6 on Arch Linux to fetch using IMAP an email
that had a To header with two email addresses, the first a group
address.  The mailing list archive has what was sent to list members.

    $ curl -sS ftp://lists.gnu.org/nmh-workers/2017-11 |
    > sed -n '/Sat Nov 18 19:42:55 2017/,/^To:/p' |
    > sed -n '$p'
    To: nmh-announce: ;, nmh...@no... 
    $

After fetchmail had passed it to my local Postfix, it had been
corrupted.

    To: nmh-announce: ;, ""@ruis.pair.com, nmh...@no...

ruis.pair.com was the IMAP peer.

I confirmed it was fetchmail and not Postfix at fault by arranging a
test message to arrive at the peer, inspecting it by manually typing
IMAP commands to show it wasn't corrupted, and then capturing
fetchmail's verbose output on fetching it.

    About to rewrite To: group-addr: ;, ra...@ex......
    ...rewritten version is To: group-addr: ;@ruis.pair.com, ra...@ex....

Please acknowledge the bug.  (I found it hard to see where bugs should
be reported when I looked at fetchmail.info and elsewhere.)

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy

Re: [Fetchmail-users] Can fetchmail print or log how many emails it fetched in a run?

[Carlos E. R. <rob...@te...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Friday, 2017-11-17 at 00:30 -0500, grarpamp wrote:

> Check the manpage enable verbose logging, you might be
> able to parse something out of that log, but whatever
> count and format you're looking for probably isn't there yet.
> You'd probably want to account for failures and completes
> too, both in remote server and local delivery.
> You could submit a simple local patch by checking return
> status of mda phase adding a counter / printf.
> Or parse it from log of your mda such as maildrop.

Verbose logging is already enabled, but I did not see anything easily 
suitable.

There are some lines like (pop3):

4 messages for LOGIN at SERVER

but that is not easy to grep for, so one like for each account.

This could be another:

IMAP< * 1509 EXISTS

or

IMAP< * OK [UNSEEN 3] First unseen.


But at the final point, nothing:

   6.3.26 querying imap.gmail.com (protocol IMAP) at 2017-11-15T00:13:47 CET: poll completed
   normal termination, status 0





- -- 
Cheers,
        Carlos E. R.
        (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAloO3JIACgkQtTMYHG2NR9Ub0QCeNtPw931w2BOmepjaMA72U4Ai
HKgAn1mEQ2Vng3V6KiM/aRhZZeaTKsjs
=hF56
-----END PGP SIGNATURE-----

Re: [Fetchmail-users] Can fetchmail print or log how many emails it fetched in a run?

[grarpamp <gra...@gm...>]

Check the manpage enable verbose logging, you might be
able to parse something out of that log, but whatever
count and format you're looking for probably isn't there yet.
You'd probably want to account for failures and completes
too, both in remote server and local delivery.
You could submit a simple local patch by checking return
status of mda phase adding a counter / printf.
Or parse it from log of your mda such as maildrop.

Re: [Fetchmail-users] Using Fetchmail with IMAP

[Matthias A. <mat...@gm...>]

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.

[Fetchmail-users] Can fetchmail print or log how many emails it fetched in a run?

[Carlos E. R. <rob...@te...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi,

I wonder if there is a way to know how many emails a fetchmail run
fetched? Better if per account. Perhaps printing it to the log, then
finding that entry. Or printing to the terminal where it runs, whatever.

- -- 
Cheers,
        Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAloLekEACgkQtTMYHG2NR9XDJACff2hnFlsUFyhqg7GUEq6FWhEb
g8QAnRzILQIUoAb9vThajm07o5C5JXLy
=lq3Z
-----END PGP SIGNATURE-----

Re: [Fetchmail-users] Using Fetchmail with IMAP

[Volker W. <po...@vo...>]

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

[Fetchmail-users] Using Fetchmail with IMAP

[Keith <kil...@gm...>]

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?

Re: [Fetchmail-users] message size error in fetchmail :SOLVED

[Matthias A. <mat...@gm...>]

Am 31.10.2017 um 18:42 schrieb Chuck Campbell:
> On 10/31/2017 11:58 AM, Chuck Campbell wrote:
>> I couldn't find a pre-built rpm for Centos 6 for any newer version.
>>
>> I built fetchmail-6.3.26 from sources, but must have done something
>> wrong, because it doesn't appear to do anything, and issues no info,
>> even when invoked with -vvvvv
>>
>> It appears as a running process, but I get no outputs at all. That is
>> an a different issue.
>>
>> I have a great deal of space available, but I'll have to remember how
>> to check available inodes. Curiously, using mpop with procmail, I can
>> get the mail just fine, so I have to believe there is no inode issue
>> (delivery to the same disk/ user).
>>
>> This may well be a sendmail (local) issue. I thought it was too much
>> work to replace it with qmail or postfix, until I know for sure it
>> isn't a fetchmail problem.
>>

At least CentOS/RHEL are more responsive distros, they should have fixed
security issues in 6.3.17 since, I hope they've also fixed
fetchmail-EN-2010-03 (a severe SASL auth bug).

> First, it turns out NOT to be a fetchmail problem, sorry for the
> noise. Now, in case anyone else comes looking for this, here is my
> solution:
>
> Thanks for the suggestion to look into the maillog. It turns out that
> opendkim was trying to create a temp file, and selinux was not
> allowing it. I tried to use audit2allow to build a module to fix this,
> but that failed. I ended up doing this:
>
> semanage permissive -a dkim_milter_t
>
> All is working again. If there is a better way, I'd be happy to hear it.

I'm not using DKIM locally; regarding choice of alternative MTAs I
consider qmail bitrotten beyond recognition, and it's "accept then
bounce" default policy of qmail-smtpd is unacceptable by today's
standards. I have very few Exim installations (notably I've run it for a
few years on a Windows laptop in Cygwin so I had local logs of outbound
mail), but I normally install Postfix, fetchmail just doesn't react all
too well to Postfix's smtpd_delay_reject feature, it expects instant
rejects...

Good that you've solved the issue.

Re: [Fetchmail-users] message size error in fetchmail :SOLVED

[Chuck C. <cam...@ac...>]

On 10/31/2017 11:58 AM, Chuck Campbell wrote:
> On 10/31/2017 11:26 AM, Matthias Andree wrote:
>> Am 31.10.2017 um 16:46 schrieb Chuck Campbell:
>>> Networksoliutions (my email provider) just changed some things, and
>>> fetchmail no longer works to pop my mail. I get message length errors.
>>> I don't know how to resolve this. This configuration had been working
>>> perfectly for years (date in .fetchmailrc is from 2000) until last week.
>>>
>>> I'm putting some segments of verbose logging here:
>>>
>>>
>>> fetchmail: starting fetchmail 6.3.17 daemon
>>> fetchmail: 6.3.17 querying <mail server redacted> (protocol POP3) at
>>> Sun 29 Oct 2017
>>> 02:36:05 PM CDT: poll started
>> [...]
>>> fetchmail: POP3> UIDL
>>> fetchmail: POP3< +OK
>>> fetchmail: POP3< 1 1508958447.17539.atl4mail14,S=6598
>>> fetchmail: 1 is unseen
>> [...]
>>> fetchmail: POP3> LIST 1
>>> fetchmail: POP3< +OK 1 6677
>>> fetchmail: POP3> RETR 1
>>> fetchmail: POP3< +OK
>> [...]
>>> fetchmail: forwarding to localhost
>>> fetchmail: SMTP> MAIL FROM:<cen...@ce...>  BODY=8BITMIME
>>> SIZE=6677
>>> fetchmail: SMTP< 250 2.1.0<cen...@ce...>... Sender ok
>>> fetchmail: SMTP> RCPT TO:<user redacted@localhost>
>>> fetchmail: SMTP< 250 2.1.5 <user redacted@localhost>... Recipient ok
>>> fetchmail: SMTP> DATA
>>> fetchmail: SMTP< 354 Enter mail, end with "." on a line by itself
>>> fetchmail: message <email addr redacted>:1 was not the expected length
>>> (6846 actual != 6677 expected)
>>> fetchmail: SMTP>. (EOM)
>>> fetchmail: SMTP< 451 4.7.0 resource unavailable
>>> fetchmail: SMTP error: 451 4.7.0 resource unavailable
>>> fetchmail: SMTP> RSET
>>> fetchmail: SMTP< 250 2.0.0 Reset state
>>> fetchmail:  not flushed [...]
>> Hi Chuck,
>>
>>
>> fetchmail 6.3.17 isn't anywhere near recent, but I don't think this is
>> related.
>>
>> It's been two decades that I pulled my last Sendmail server from
>> service, but what prevents delivery is not the size warning, but the
>> "451 4.7.0 resource unavailable". I don't know if sendmail complains
>> about the size mismatch (FreeBSD's sendmail 8.15 via sendmail -bs will
>> happily accept an oversized message), or if it's running out of disk
>> space or inodes in the /var or any your delivery partitions, normally
>> the size mismatch is only a warning.
>>
>> Carefully check your mail log if sendmail sends any more details to
>> syslog, and check the output of "df" and "df -i".
>>
>>
>> HTH
>>
>> Regards,
>>
>> Matthias
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>
> I couldn't find a pre-built rpm for Centos 6 for any newer version.
>
> I built fetchmail-6.3.26 from sources, but must have done something wrong, 
> because it doesn't appear to do anything, and issues no info, even when 
> invoked with -vvvvv
>
> It appears as a running process, but I get no outputs at all. That is an a 
> different issue.
>
> I have a great deal of space available, but I'll have to remember how to check 
> available inodes. Curiously, using mpop with procmail, I can get the mail just 
> fine, so I have to believe there is no inode issue (delivery to the same disk/ 
> user).
>
> This may well be a sendmail (local) issue. I thought it was too much work to 
> replace it with qmail or postfix, until I know for sure it isn't a fetchmail 
> problem.
>
> -chuck
>
First, it turns out NOT to be a fetchmail problem, sorry for the noise. Now, in 
case anyone else comes looking for this, here is my solution:

Thanks for the suggestion to look into the maillog. It turns out that opendkim 
was trying to create a temp file, and selinux was not allowing it. I tried to 
use audit2allow to build a module to fix this, but that failed. I ended up doing 
this:

semanage permissive -a dkim_milter_t

All is working again. If there is a better way, I'd be happy to hear it.

-chuck

--