fetchmail-users — User questions and discussion

[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

-- 

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

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

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

-- 
ACCEL Services, Inc.| Specialists in Gravity, Magnetics |  (713)993-0671 ph.
                     |   and Integrated Interpretation   |  (713)993-0608 fax
448 W. 19th St. #325|            Since 1992             |  (713)306-5794 cell
  Houston, TX, 77008 |          Chuck Campbell           | cam...@ac...
                     |  President & Senior Geoscientist  |

      "Integration means more than having all the maps at the same scale!"

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

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

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

[Fetchmail-users] message size error in fetchmail

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

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: Trying to connect to <ip redacted>/110...connected.
fetchmail: POP3< +OK <mail server redacted>
fetchmail: POP3> CAPA
fetchmail: POP3< -ERR authorization first
fetchmail: authorization first
fetchmail: Repoll immediately on <redacted>
fetchmail: Trying to connect to <ip redacted>/110...connected.
fetchmail: POP3< +OK <mail server redacted>
fetchmail: POP3> USER <user redacted>
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 98 20135316
fetchmail: POP3> UIDL
fetchmail: POP3< +OK
fetchmail: POP3< 1 1508958447.17539.atl4mail14,S=6598
fetchmail: 1 is unseen
fetchmail: POP3< 2 1508958525.17093.atl4mail02pod6,S=5029
fetchmail: 2 is unseen
fetchmail: POP3< 3 1508958823.2521.atl4mail11pod6,S=5280
fetchmail: 3 is unseen
.
.
.
<snip 89 similar messages>
.
.
.
fetchmail: POP3< 93 1509302243.10963.atl4mail07pod6,S=4081
fetchmail: POP3< 94 1509303055.10074.atl4mail01pod6,S=7151
fetchmail: POP3< 95 1509303846.17811.atl4mail10pod6,S=4293
fetchmail: POP3< 96 1509304525.15874.atl4mail06pod6,S=4388
fetchmail: POP3< 97 1509305188.8931.atl4mail20,S=92771
fetchmail: 97 is unseen
fetchmail: POP3< 98 1509305379.4421.atl4mail18,S=6710
fetchmail: POP3< .
fetchmail: 98 messages (5 seen) for <email addr redacted> at <mail server redacted> (20135316 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 6677
fetchmail: POP3> RETR 1
fetchmail: POP3< +OK
fetchmail: reading message <email addr redacted>:1 of 98 (6677 octets)Trying to connect to 127.0.0.1/25...connected.
fetchmail: SMTP< 220 <host redacted> ESMTP Sendmail 8.14.4/8.14.4; Sun, 29 Oct 2017 14:36:05 -0500
fetchmail: SMTP> EHLO <host redacted>
fetchmail: SMTP< 250-<host redacted> Hello localhost [127.0.0.1], pleased to meet you
fetchmail: SMTP< 250-ENHANCEDSTATUSCODES
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250-8BITMIME
fetchmail: SMTP< 250-SIZE
fetchmail: SMTP< 250-DSN
fetchmail: SMTP< 250-ETRN
fetchmail: SMTP< 250-AUTH GSSAPI DIGEST-MD5 CRAM-MD5
fetchmail: SMTP< 250-STARTTLS
fetchmail: SMTP< 250-DELIVERBY
fetchmail: SMTP< 250 HELP
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
.
.
.
<snipped remaining comparable errors for remaining email messages>

This repeats for all the unseen messages, and I get no emails.
Here is the .fetchmailrc:

# Configuration created Fri May 26 16:39:05 2000 by fetchmailconf
#
set logfile fetchmail.log
set postmaster "xxxxxxxx"
set bouncemail
set properties ""
set daemon 300
#
#
poll <redacted>.com with proto POP3 and options no dns uidl
        user "<redacted>" there with password "xxxxxxxx" is <redacted> here options no rewrite fetchall pass8bits warnings 3600
antispam 571 550 501 554

thanks,
-chuck

-- 

Re: [Fetchmail-users] set sha1 fingerprint checking correctly on fetchmail

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

> But I guess I should ask for a md5 fingerprint?

You can ask them for it if you want to verify it
with their admins out of band.

> Not sure if this will work, since gmx.com appear to have changed their fingerprint.

No, they changed out their cert.
You're computing the fingerprint of their cert.

cat /etc/passwd | more
cat /etc/passwd | md5
openssl s_client -connect pop.gmx.com:995 < /dev/null | openssl x509
-noout -fingerprint -md5
Sortof like that.

Put that fingerprint in fetchmailrc and it'll "work".
Then... search: TLS certificate tutorial

> http://pyropus.ca/software/getmail/configuration.html

Seems word "fingerprint" is in there now so
try them both to learn and compare what they
can do today.

Re: [Fetchmail-users] set sha1 fingerprint checking correctly on fetchmail

[Globe T. <its...@ya...>]

 Thanks!
>This simply means put the MD5 in fetchmailrc instead of the SHA1... downgrading (linguistic lol) to lesser strength hash function. Technically both MD5 and SHA1 are now both broken via published full collision attacks. You can search for that.

Not sure if this will work, since gmx.com appear to have changed their fingerprint. But I guess I should ask for a md5 fingerprint?

> Would moving to getmail solve this issue?

> No. Last I checked getmail, fdm, etc did not offer enough options to properly handle config of CA and/or fingerprint checking, or even support them at all. Please make another
current check for your own use case to be sure.
I see. I do not have enough technical knowledge in this field to say if the following is enough:
http://pyropus.ca/software/getmail/configuration.html#retriever-ssl-extra
Thanks again!


   

   

Re: [Fetchmail-users] set sha1 fingerprint checking correctly on fetchmail

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

On Tue, Oct 3, 2017 at 4:37 PM, Globe Trotter via Fetchmail-users
<fet...@li...> wrote:
> I run Fedora 26 which has fetchmail at 6.3.26. How do I downgrade

This simply means put the MD5 in fetchmailrc instead of the
SHA1... downgrading (linguistic lol) to lesser strength hash function.
Technically both MD5 and SHA1 are now both broken via
published full collision attacks. You can search for that.

Stay with the latest release since old releases are unsupported.

> or better still, make fetchmail 7.x "an actual thing"?

Write code. Work on tickets, roadmap, or draft user
facing stuff. Or solicit / talk volunteers or current devs.

> Would moving to getmail solve this issue?

No. Last I checked getmail, fdm, etc did not offer enough
options to properly handle config of CA and/or fingerprint
checking, or even support them at all. Please make another
current check for your own use case to be sure.

Re: [Fetchmail-users] set sha1 fingerprint checking correctly on fetchmail

[Globe T. <its...@ya...>]

Thanks!


> That's because the world's defaults have moved to sha1 or better,
(an understanding demonstrated in your example command line above),
while all branches of fetchmail still use only the long ago
broken and deprecated MD5 in its configuration.
> Downgrade to the broken MD5 representation,
or make fetchmail 7.x an actual thing.
The latter being the much preferred outcome :)

I run Fedora 26 which has fetchmail at 6.3.26. How do I downgrade, or better still, make fetchmail 7.x "an actual thing"?
Would moving to getmail solve this issue? Thanks!

------------------------------------------------------------------------------
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] set sha1 fingerprint checking correctly on fetchmail

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

On Tue, Oct 3, 2017 at 10:09 AM, Globe Trotter via Fetchmail-users
<fet...@li...> wrote:
> $openssl s_client -connect pop.gmx.com:995 | openssl x509 -in /dev/stdin -sha1 -noout -fingerprint
> SHA1 Fingerprint=4D:69:52:FB:5F:18:34:5E:02:E2:7D:B5:95:B8:BD:3E:E1:8F:FD:F8

> fetchmail: 6.3.26 querying pop.gmx.com (protocol POP3) at Mon 02 Oct 2017 11:24:50 PM CDT: poll started
> fetchmail: pop.gmx.com key fingerprint: 6F:3E:88:EF:14:35:2C:69:7A:22:03:C8:2B:90:B3:8C
> fetchmail: pop.gmx.com fingerprints do not match!

That's because the world's defaults have moved to sha1 or better,
(an understanding demonstrated in your example command line above),
while all branches of fetchmail still use only the long ago
broken and deprecated MD5 in its configuration.

Downgrade to the broken MD5 representation,
or make fetchmail 7.x an actual thing.
The latter being the much preferred outcome :)

[Fetchmail-users] set sha1 fingerprint checking correctly on fetchmail

[Globe T. <its...@ya...>]

Hi, 

My mail service provider gmx.com recently appears to have changed their fingerprint to SHA1 (I am guessing) as a result of which my fetchmail has stopped working.
Here is the fingerprint I get:
$openssl s_client -connect pop.gmx.com:995 | openssl x509 -in /dev/stdin -sha1 -noout -fingerprint
depth=2 C = US, O = GeoTrust Inc., CN = GeoTrust Global CA
verify return:1
depth=1 C = US, O = GeoTrust Inc., CN = GeoTrust SSL CA - G3
verify return:1
depth=0 C = DE, ST = Rhineland-Palatinate, L = Montabaur, O = 1&1 Mail & Media GmbH, CN = pop.gmx.com
verify return:1
SHA1 Fingerprint=4D:69:52:FB:5F:18:34:5E:02:E2:7D:B5:95:B8:BD:3E:E1:8F:FD:F8



So, I set the following in my .fetchmailrc

sslfingerprint "4D:69:52:FB:5F:18:34:5E:02:E2:7D:B5:95:B8:BD:3E:E1:8F:FD:F8"

but I get the following:
$fetchmail -cv
fetchmail: --check mode enabled, not fetching mail
fetchmail: 6.3.26 querying pop.gmx.com (protocol POP3) at Mon 02 Oct 2017 11:24:50 PM CDT: poll started
Trying to connect to 212.227.17.171/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: GeoTrust Inc.
fetchmail: Issuer CommonName: GeoTrust SSL CA - G3
fetchmail: Subject CommonName: pop.gmx.com
fetchmail: Subject Alternative Name: pop.gmx.com
fetchmail: pop.gmx.com key fingerprint: 6F:3E:88:EF:14:35:2C:69:7A:22:03:C8:2B:90:B3:8C
fetchmail: pop.gmx.com fingerprints do not match!
fetchmail: OpenSSL reported: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
fetchmail: SSL connection failed.
fetchmail: socket error while fetching from gt...@gm...@pop.gmx.com
fetchmail: 6.3.26 querying pop.gmx.com (protocol POP3) at Mon 02 Oct 2017 11:24:50 PM CDT: poll completed

The fingerprint is quite different from the fingerprint that is reported (and included in my .fetchmailrc). 

What am I doing wrong?
Many thanks for any help!

           Try the new Yahoo Mail 

Re: [Fetchmail-users] oddball, but probably viral ISP emil server configuration

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

On 2017-09-15 02:13, Gene Heskett wrote:
> On Thursday 14 September 2017 15:06:58 Matthias Andree wrote:


>> Code to copy messages to trash (not all 
>> IMAP servers can actually /move/) hasn't been written for fetchmail.
>> The proper answer is to find a ISP with clueful staff...
>>
>> Sorry.
>>
> But I am out in the semi-rural and wilder brush of north central WV, they 
> are the local cable company, scattered about WV, VA, PA & possibly the 
> Carolina's. The alternative is Frontier.net, running on what was 
> Verizons 50 yo copper, none of which is buried deep enough to clear your 
> weed eater or lawnmower.  Except for this, it generally  Just Works(TM).
> 
> Thank you for checking instead of ignoring me.

But you do not need to have your ISP also provide mail. It is usual, but
not necessary.


I have a problem with mine: on one account, the inbox suddenly becomes
empty, till a new mail gets there, and all emails appear back on the
inbox. They say that Thunderbird makes several simultaneous connections
and then the index at the server corrupts. Configure Thunderbird to make
only one connection to the imap server (!).

It also happens with fetchmail.


Some ISPs have curious ideas about how email works.


-- 
Cheers / Saludos,

		Carlos E. R.
		(from 42.2 x86_64 "Malachite" at Telcontar)

Re: [Fetchmail-users] oddball, but probably viral ISP emil server configuration

[Brian B. <br...@pi...>]

On 15/09/17 10:13, Gene Heskett wrote:
> On Thursday 14 September 2017 15:06:58 Matthias Andree wrote:
> 
>> Am 14.09.2017 um 10:49 schrieb Gene Heskett:
>>> Greetings all;
>>>
>>> My ISP is running an imap/pop3 combined email server, but they,
>>> because its shared with imap users, have disabled fetchmails ability
>>> to delete the successfully pulled message. I have had somewhat
>>> heated discussions with the tech people, but they are convinced its
>>> the only way they can make imap work from any customers machines.
>>
>> Which is nonsense.
>>
>>> They also do not, when logged into the webmail, actually delete the
>>> mails selected for deletion, but silently move them, maximum of 100
>>> at a time, to the trash folder, and it does not show a message count
>>> until you select it, and discover nearly 30,000 old emails sitting
>>> in there. That folder can be one click cleared, except this whole
>>> procedure just cost me an hour and a half to do the moves, and then
>>> the folder clearing.
>>>
>>> Is there some way I can make fetchmail automatically, not dele, that
>>> is ignored, but move to the trash, each message as its successfully
>>> downloaded?
>>
>> Unfortunately there isn't.
> 
> I suspected as much.
> 
>> Code to copy messages to trash (not all
>> IMAP servers can actually /move/) hasn't been written for fetchmail.
>> The proper answer is to find a ISP with clueful staff...
>>
>> Sorry.
>>
> But I am out in the semi-rural and wilder brush of north central WV, they
> are the local cable company, scattered about WV, VA, PA & possibly the
> Carolina's. The alternative is Frontier.net, running on what was
> Verizons 50 yo copper, none of which is buried deep enough to clear your
> weed eater or lawnmower.  Except for this, it generally  Just Works(TM).
> 
> Thank you for checking instead of ignoring me.
> 
> Cheers, Gene Heskett

Sorry to pick up this thread late, Gene.

I don't see any reason why you should be using the email service from 
your ISP. In general, that is a very bad idea because it means you are 
adding another layer of "stickiness" to any possible future move to a 
different ISP. There are many free or fee email providers, and some will 
allow you to personalise your mail domain name. Many also provide pop3 
and imap support which actually works as intended.

My region of Australia was recently converted to a new broadband 
infrastructure, but many of my friends (who hadn't taken the advice 
above) were effectively obliged to stick with the same ISP on the new 
network because their contacts all had the isp-domain email address 
embedded in their address books.

I advise you to switch your email provider soon, and set up your new 
email infrastructure in parallel to the old "mess". Take time to ask 
your contacts to start using the new address(es) and watch the reduction 
in flow via the old addresses. If you are ever offered a competitive 
broadband service, you will be ready to take advantage quickly.

Sympathies! Good luck,

Brian

Re: [Fetchmail-users] oddball, but probably viral ISP emil server configuration

[Gene H. <ghe...@sh...>]

On Thursday 14 September 2017 15:06:58 Matthias Andree wrote:

> Am 14.09.2017 um 10:49 schrieb Gene Heskett:
> > Greetings all;
> >
> > My ISP is running an imap/pop3 combined email server, but they,
> > because its shared with imap users, have disabled fetchmails ability
> > to delete the successfully pulled message. I have had somewhat
> > heated discussions with the tech people, but they are convinced its
> > the only way they can make imap work from any customers machines.
>
> Which is nonsense.
>
> > They also do not, when logged into the webmail, actually delete the
> > mails selected for deletion, but silently move them, maximum of 100
> > at a time, to the trash folder, and it does not show a message count
> > until you select it, and discover nearly 30,000 old emails sitting
> > in there. That folder can be one click cleared, except this whole
> > procedure just cost me an hour and a half to do the moves, and then
> > the folder clearing.
> >
> > Is there some way I can make fetchmail automatically, not dele, that
> > is ignored, but move to the trash, each message as its successfully
> > downloaded?
>
> Unfortunately there isn't.

I suspected as much.

> Code to copy messages to trash (not all 
> IMAP servers can actually /move/) hasn't been written for fetchmail.
> The proper answer is to find a ISP with clueful staff...
>
> Sorry.
>
But I am out in the semi-rural and wilder brush of north central WV, they 
are the local cable company, scattered about WV, VA, PA & possibly the 
Carolina's. The alternative is Frontier.net, running on what was 
Verizons 50 yo copper, none of which is buried deep enough to clear your 
weed eater or lawnmower.  Except for this, it generally  Just Works(TM).

Thank you for checking instead of ignoring me.

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>

Re: [Fetchmail-users] oddball, but probably viral ISP emil server configuration

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

Am 14.09.2017 um 10:49 schrieb Gene Heskett:
> Greetings all;
>
> My ISP is running an imap/pop3 combined email server, but they, because 
> its shared with imap users, have disabled fetchmails ability to delete 
> the successfully pulled message. I have had somewhat heated discussions 
> with the tech people, but they are convinced its the only way they can 
> make imap work from any customers machines.

Which is nonsense.

> They also do not, when logged into the webmail, actually delete the mails 
> selected for deletion, but silently move them, maximum of 100 at a time, 
> to the trash folder, and it does not show a message count until you 
> select it, and discover nearly 30,000 old emails sitting in there. That 
> folder can be one click cleared, except this whole procedure just cost 
> me an hour and a half to do the moves, and then the folder clearing.
>
> Is there some way I can make fetchmail automatically, not dele, that is 
> ignored, but move to the trash, each message as its successfully 
> downloaded?
Unfortunately there isn't. Code to copy messages to trash (not all IMAP
servers can actually /move/) hasn't been written for fetchmail.
The proper answer is to find a ISP with clueful staff...

Sorry.

[Fetchmail-users] oddball, but probably viral ISP emil server configuration

[Gene H. <ghe...@sh...>]

Greetings all;

My ISP is running an imap/pop3 combined email server, but they, because 
its shared with imap users, have disabled fetchmails ability to delete 
the successfully pulled message. I have had somewhat heated discussions 
with the tech people, but they are convinced its the only way they can 
make imap work from any customers machines.

They also do not, when logged into the webmail, actually delete the mails 
selected for deletion, but silently move them, maximum of 100 at a time, 
to the trash folder, and it does not show a message count until you 
select it, and discover nearly 30,000 old emails sitting in there. That 
folder can be one click cleared, except this whole procedure just cost 
me an hour and a half to do the moves, and then the folder clearing.

Is there some way I can make fetchmail automatically, not dele, that is 
ignored, but move to the trash, each message as its successfully 
downloaded?

That would greatly simplify my email maintenance chores, in addition to 
reducing my exposure to the National Snooping Agency.

Thanks people.

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>

Re: [Fetchmail-users] I see a lot of "client/server synchronization error while fetching from..."

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

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



On Monday, 2017-07-31 at 22:38 +0200, Matthias Andree wrote:

> Am 28.07.2017 um 19:29 schrieb Carlos E. R.:
>>
>> I rather suspect the ISP. They have been doing things.
>>
>> Another error I see is that now and then ALL email disappears from the
>> Thunderbird inbox, me doing nothing. Suddenly, the inbox is empty. If I
>> run fetchmail it also finds nothing.
>>
>> So I send an email to that account, the mail appears after a minute, and
>> suddenly, the rest of the inbox reappears, perhaps 300 mails.
>
> Eww. That does not look very trustworthy. There be bugs, and dragons.

Indeed!

Well, the sync error has cleared, but the disappearing act not.

That server has worked well for several years, but...

- -- 
Cheers,
        Carlos E. R.
        (from 42.2 x86_64 "Malachite" at Telcontar)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAll/tEUACgkQtTMYHG2NR9WT1QCfYsxjIUkBOY/CvHp7UDLsabyg
FcgAoI8NITG2Ir5alyvZF8qPsShiGVqX
=A8Ee
-----END PGP SIGNATURE-----

Re: [Fetchmail-users] I see a lot of "client/server synchronization error while fetching from..."

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

Am 28.07.2017 um 19:29 schrieb Carlos E. R.:
>
> I rather suspect the ISP. They have been doing things.
>
> Another error I see is that now and then ALL email disappears from the
> Thunderbird inbox, me doing nothing. Suddenly, the inbox is empty. If I
> run fetchmail it also finds nothing.
>
> So I send an email to that account, the mail appears after a minute, and
> suddenly, the rest of the inbox reappears, perhaps 300 mails.

Eww. That does not look very trustworthy. There be bugs, and dragons.

Re: [Fetchmail-users] I see a lot of "client/server synchronization error while fetching from..."

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

On 2017-07-28 19:13, Matthias Andree wrote:
> Am 28.07.2017 um 03:12 schrieb Carlos E. R.:
>>
>>
>> Config is:
>>
>> poll imap.telefonica.net with proto imap timeout 20, and tracepolls
>>         user USERNAME, with password PASSWORD, is cer here, and
>> fetchall, expunge 20,  folders Inbox, Spam, Junk
>>
>>
>>
>>
>> The log goes thus:
>>
...

>> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -  SMTP>. (EOM)
>> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< *
>> BYE Logging out
>> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP<
>> A0067 OK Logout completed.
>> <2.3> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - - 
>> client/server synchronization error while fetching from
>> ...@imap.telefonica.net
>> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  6.3.26
>> querying imap.telefonica.net (protocol IMAP) at 2017-07-28T02:30:08
>> CEST: poll completed
>> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  Query
>> status=7 (ERROR)
>>
>> I have to run fetchmail several times in order to fetch it all,
>> because it aborts at each error.
>>
>> Can I do something?
> 
> Hi Carlos,
> 
> is there anything accessing the mailboxes at the same time, for instance
> another e-mail client (thunderbird, kmail, evolution) that is also
> deleting messages?

There is Thunderbird, of course, but it is not deleting messages. I have
had Th and fetchmail running this way for many years with the same
accounts, and never a problem.


> Fetchmail is downloading and marking 20 messages as deleted, issues
> "EXPUNGE" and the server reports 21 or more messages expunged, which
> confuses fetchmail (meaning: nobody has written code to deal with
> something else accessing the mailbox at the same time).
> 
> If you are 100% sure fetchmail is the only client accessing the server
> at the same time, then file a report to the server's operators,
> otherwise, the workaround would be to not make fetchmail delete messages
> so it doesn't expunge either.

Only fetchmail should be doing expunges. Thunderbird is running but
doing nothing at those times (I run fetchmail manually), so I just watch
the mail count go down on all mail accounts till it gets to zero.

> 
> The relevant source code comment is:
> 
>>    /* if there is a mismatch between the number of mails which should
>>      * have been expunged and the number of mails actually expunged,
>>      * another email client may be deleting mails. Quit here,
>>      * otherwise fetchmail gets out-of-sync with the imap server,
>>      * reports the wrong size to the SMTP server on MAIL FROM: and
>>      * triggers a "message ... was not the expected length" error on
>>      * every subsequent mail */
>>     if (deletions > 0 && deletions != actual_deletions)
>>     {
>>         report(stderr,
>>                 GT_("mail expunge mismatch (%d actual != %d expected)\n"),
>>                 actual_deletions, deletions);
>>         deletions = 0;
>>         return(PS_ERROR);
>>     }

Thanks.


I rather suspect the ISP. They have been doing things.

Another error I see is that now and then ALL email disappears from the
Thunderbird inbox, me doing nothing. Suddenly, the inbox is empty. If I
run fetchmail it also finds nothing.

So I send an email to that account, the mail appears after a minute, and
suddenly, the rest of the inbox reappears, perhaps 300 mails.

-- 
Cheers / Saludos,

		Carlos E. R.
		(from 42.2 x86_64 "Malachite" at Telcontar)

Re: [Fetchmail-users] I see a lot of "client/server synchronization error while fetching from..."

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

Am 28.07.2017 um 03:12 schrieb Carlos E. R.:
>
>
> Config is:
>
> poll imap.telefonica.net with proto imap timeout 20, and tracepolls
>         user USERNAME, with password PASSWORD, is cer here, and
> fetchall, expunge 20,  folders Inbox, Spam, Junk
>
>
>
>
> The log goes thus:
>
> ...
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP>
> A0064 FETCH 20 BODY.PEEK[TEXT]
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 20
> FETCH (BODY[TEXT] {275}
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -   (275 body
> octets) (log message incomplete)
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< )
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP<
> A0064 OK Fetch completed.
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  SMTP>. (EOM)
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  SMTP< 250
> 2.0.0 Ok: queued as 85D5A188139
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -   flushed
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP>
> A0065 STORE 20 +FLAGS (\Seen \Deleted)
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 20
> FETCH (FLAGS (\Deleted \Seen NonJunk))
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP<
> A0065 OK Store completed.
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP>
> A0066 EXPUNGE
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 87
> EXPUNGE
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 20
> EXPUNGE
> [...]
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 1
> EXPUNGE
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP<
> A0066 OK Expunge completed.
> <2.3> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  mail
> expunge mismatch (21 actual != 20 expected)
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP>
> A0067 LOGOUT
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< *
> BYE Logging out
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP<
> A0067 OK Logout completed.
> <2.3> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - - 
> client/server synchronization error while fetching from
> ...@imap.telefonica.net
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  6.3.26
> querying imap.telefonica.net (protocol IMAP) at 2017-07-28T02:48:45
> CEST: poll completed
> <2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  Query
> status=7 (ERROR)
>
>
> Looking at previous instances:
>
> ...
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  IMAP< * 12
> FETCH (RFC822.HEADER {6969}
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  reading
> message ...@gma...@gm...:12 of 89 (6969 header
> octets) (log message incomplete)
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP> MAIL
> FROM:<opensuse-factory+bounces-78582-...=gma...@op...>
> BODY=7BIT SIZE=8786
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP< 250
> 2.1.0 Ok
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP> RCPT
> TO:<cer@localhost>
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP< 250
> 2.1.5 Ok
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP> DATA
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP< 354
> End data with <CR><LF>.<CR><LF>
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  IMAP< )
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  IMAP<
> A0039 OK Success
> <2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  IMAP>
> A0040 FETCH 12 BODY.PEEK[TEXT]
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< *
> 106 EXPUNGE
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 20
> EXPUNGE
> [..]
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 1
> EXPUNGE
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP<
> A0066 OK Expunge completed.
> <2.3> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  mail
> expunge mismatch (21 actual != 20 expected)
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP>
> A0067 LOGOUT
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -  IMAP< * 12
> FETCH (BODY[TEXT] {1631}
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -   (1631
> body octets) (log message incomplete)
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -  IMAP< )
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -  IMAP<
> A0040 OK Success
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -  SMTP>. (EOM)
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< *
> BYE Logging out
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP<
> A0067 OK Logout completed.
> <2.3> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - - 
> client/server synchronization error while fetching from
> ...@imap.telefonica.net
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  6.3.26
> querying imap.telefonica.net (protocol IMAP) at 2017-07-28T02:30:08
> CEST: poll completed
> <2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  Query
> status=7 (ERROR)
>
> I have to run fetchmail several times in order to fetch it all,
> because it aborts at each error.
>
> Can I do something?

Hi Carlos,

is there anything accessing the mailboxes at the same time, for instance
another e-mail client (thunderbird, kmail, evolution) that is also
deleting messages?
Fetchmail is downloading and marking 20 messages as deleted, issues
"EXPUNGE" and the server reports 21 or more messages expunged, which
confuses fetchmail (meaning: nobody has written code to deal with
something else accessing the mailbox at the same time).

If you are 100% sure fetchmail is the only client accessing the server
at the same time, then file a report to the server's operators,
otherwise, the workaround would be to not make fetchmail delete messages
so it doesn't expunge either.

The relevant source code comment is:

>    /* if there is a mismatch between the number of mails which should
>      * have been expunged and the number of mails actually expunged,
>      * another email client may be deleting mails. Quit here,
>      * otherwise fetchmail gets out-of-sync with the imap server,
>      * reports the wrong size to the SMTP server on MAIL FROM: and
>      * triggers a "message ... was not the expected length" error on
>      * every subsequent mail */
>     if (deletions > 0 && deletions != actual_deletions)
>     {
>         report(stderr,
>                 GT_("mail expunge mismatch (%d actual != %d expected)\n"),
>                 actual_deletions, deletions);
>         deletions = 0;
>         return(PS_ERROR);
>     }

[Fetchmail-users] I see a lot of "client/server synchronization error while fetching from..."

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



Config is:

poll imap.telefonica.net with proto imap timeout 20, and tracepolls
         user USERNAME, with password PASSWORD, is cer here, and fetchall, expunge 20,  folders Inbox, Spam, Junk




The log goes thus:

...
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP> A0064 FETCH 20 BODY.PEEK[TEXT]
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 20 FETCH (BODY[TEXT] {275}
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -   (275 body octets) (log message incomplete)
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< )
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< A0064 OK Fetch completed.
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  SMTP>. (EOM)
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  SMTP< 250 2.0.0 Ok: queued as 85D5A188139
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -   flushed
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP> A0065 STORE 20 +FLAGS (\Seen \Deleted)
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 20 FETCH (FLAGS (\Deleted \Seen NonJunk))
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< A0065 OK Store completed.
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP> A0066 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 87 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 20 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 19 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 18 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 17 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 16 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 15 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 14 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 13 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 12 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 11 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 10 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 9 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 8 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 7 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 6 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 5 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 4 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 3 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 2 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * 1 EXPUNGE
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< A0066 OK Expunge completed.
<2.3> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  mail expunge mismatch (21 actual != 20 expected)
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP> A0067 LOGOUT
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< * BYE Logging out
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  IMAP< A0067 OK Logout completed.
<2.3> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  client/server synchronization error while fetching from ...@imap.telefonica.net
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  6.3.26 querying imap.telefonica.net (protocol IMAP) at 2017-07-28T02:48:45 CEST: poll completed
<2.6> 2017-07-28 02:48:45 minas-tirith fetchmail 11858 - -  Query status=7 (ERROR)


Looking at previous instances:

...
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  IMAP< * 12 FETCH (RFC822.HEADER {6969}
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  reading message ...@gma...@gm...:12 of 89 (6969 header octets) (log message incomplete)
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP> MAIL FROM:<opensuse-factory+bounces-78582-...=gma...@op...> BODY=7BIT SIZE=8786
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP< 250 2.1.0 Ok
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP> RCPT TO:<cer@localhost>
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP< 250 2.1.5 Ok
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP> DATA
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  SMTP< 354 End data with <CR><LF>.<CR><LF>
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  IMAP< )
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  IMAP< A0039 OK Success
<2.6> 2017-07-28 02:30:07 minas-tirith fetchmail 10071 - -  IMAP> A0040 FETCH 12 BODY.PEEK[TEXT]
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 106 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 20 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 19 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 18 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 17 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 16 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 15 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 14 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 13 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 12 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 11 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 10 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 9 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 8 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 7 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 6 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 5 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 4 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 3 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 2 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * 1 EXPUNGE
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< A0066 OK Expunge completed.
<2.3> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  mail expunge mismatch (21 actual != 20 expected)
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP> A0067 LOGOUT
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -  IMAP< * 12 FETCH (BODY[TEXT] {1631}
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -   (1631 body octets) (log message incomplete)
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -  IMAP< )
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -  IMAP< A0040 OK Success
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10071 - -  SMTP>. (EOM)
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< * BYE Logging out
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  IMAP< A0067 OK Logout completed.
<2.3> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  client/server synchronization error while fetching from ...@imap.telefonica.net
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  6.3.26 querying imap.telefonica.net (protocol IMAP) at 2017-07-28T02:30:08 CEST: poll completed
<2.6> 2017-07-28 02:30:08 minas-tirith fetchmail 10070 - -  Query status=7 (ERROR)



...
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31524 - -  SMTP< 250 2.0.0 Ok: queued as 2761E188974
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31524 - -   flushed
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31524 - -  IMAP> A0038 STORE 11 +FLAGS (\Seen \Deleted)
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -  IMAP< * 20 FETCH (BODY[TEXT] {1308}
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -   (1308 body octets) (log message incomplete)
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -  IMAP< )
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -  IMAP< A0064 OK Fetch completed.
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -  SMTP>. (EOM)
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -  SMTP< 250 2.0.0 Ok: queued as 7A2EE188975
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -   flushed
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -  IMAP> A0065 STORE 20 +FLAGS (\Seen \Deleted)
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -  IMAP< * 20 FETCH (FLAGS (\Deleted \Seen NonJunk))
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -  IMAP< A0065 OK Store completed.
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31525 - -  IMAP> A0066 EXPUNGE
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31524 - -  IMAP< * 11 FETCH (FLAGS (\Seen \Deleted))
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31524 - -  IMAP< A0038 OK Success
<2.6> 2017-07-27 15:56:06 minas-tirith fetchmail 31524 - -  IMAP> A0039 FETCH 12 RFC822.HEADER
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 100 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 99 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 20 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 19 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 18 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 17 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 16 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 15 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 14 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 13 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 12 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 11 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 10 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 9 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 8 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 7 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 6 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 5 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 4 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 3 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 2 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 1 EXPUNGE
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * 1 RECENT
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< A0066 OK Expunge completed.
<2.3> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  mail expunge mismatch (22 actual != 20 expected)
2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP> A0067 LOGOUT
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< * BYE Logging out
<2.6> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  IMAP< A0067 OK Logout completed.
<2.3> 2017-07-27 15:56:07 minas-tirith fetchmail 31525 - -  client/server synchronization error while fetching from ...@imap.telefonica.net


...
<2.6> 2017-07-26 15:38:51 minas-tirith fetchmail 10160 - -  SMTP< 354 End data with <CR><LF>.<CR><LF>
<2.6> 2017-07-26 15:38:51 minas-tirith fetchmail 10160 - -  IMAP< )
<2.6> 2017-07-26 15:38:51 minas-tirith fetchmail 10160 - -  IMAP< A0063 OK Fetch completed.
<2.6> 2017-07-26 15:38:51 minas-tirith fetchmail 10160 - -  IMAP> A0064 FETCH 20 BODY.PEEK[TEXT]
<2.6> 2017-07-26 15:38:51 minas-tirith fetchmail 10160 - -  IMAP< * 20 FETCH (BODY[TEXT] {326}
<2.6> 2017-07-26 15:38:51 minas-tirith fetchmail 10160 - -   (326 body octets) (log message incomplete)
<2.6> 2017-07-26 15:38:51 minas-tirith fetchmail 10160 - -  IMAP< )
<2.6> 2017-07-26 15:38:51 minas-tirith fetchmail 10160 - -  IMAP< A0064 OK Fetch completed.
<2.6> 2017-07-26 15:38:51 minas-tirith fetchmail 10160 - -  SMTP>. (EOM)
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  SMTP< 250 2.0.0 Ok: queued as AA79718554C
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -   flushed
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP> A0065 STORE 20 +FLAGS (\Seen \Deleted)
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 20 FETCH (FLAGS (\Deleted \Seen NonJunk))
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< A0065 OK Store completed.
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP> A0066 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 21 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 20 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 19 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 18 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 17 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 16 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 15 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 14 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 13 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 12 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 11 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 10 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 9 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 8 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 7 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 6 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 5 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 4 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 3 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 2 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 1 EXPUNGE
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * 1 RECENT
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< A0066 OK Expunge completed.
<2.3> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  mail expunge mismatch (21 actual != 20 expected)
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP> A0067 LOGOUT
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< * BYE Logging out
<2.6> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  IMAP< A0067 OK Logout completed.
<2.3> 2017-07-26 15:38:52 minas-tirith fetchmail 10160 - -  client/server synchronization error while fetching from ...@imap.telefonica.net




I have to run fetchmail several times in order to fetch it all, because 
it aborts at each error.

Can I do something?


- -- 
Cheers
        Carlos E. R.

        (from 42.2 x86_64 "Malachite" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAll6j2oACgkQja8UbcUWM1zqgQD/QrzBQbVu5NHJDLg5DOIU8BU3
lx3EoJSnjQZIQFCrv8kBAJVGE6qrSuPCMY/wFHktZVm+IYiqdnyHyzwfVdRr7v7F
=9nsY
-----END PGP SIGNATURE-----

Re: [Fetchmail-users] Downloading 'seen' email?

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

Am 11.07.2017 um 10:45 schrieb Hylton Conacher (ZR1HPC):
> 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,

0. POP3 doesn't really have a notion of "Seen" messages, it's rather
supporting a concept of "downloaded" messages. fetchmail tries to "peek"
at messages though so as not to mark messages Seen on the server's end.

1. Gmail is quirky. See
<http://www.fetchmail.info/fetchmail-FAQ.html#I9> unfortunately Google
changed the location of its help texts, currently
<https://support.google.com/mail/answer/7104828#downloadmultipleclients>
might do, look for "recent:" (add it to the mygmailaddress part in your
rcfile, i. e. as prefix to the user part:

user "recent:mygmailaddress" ...

2. check the logs if fetchmail is using "LAST" or "UIDL" to figure how
many messages are seen. You can force it to use UIDL by adding "uidl"
after the "pop3".

3. you may want to do ONE SINGLE run with the "--all" option. This
downloads "seen" mail. It does not mix with "keep" and "daemon" enabled
at the same time (obviously - it does not make sense, you would
re-download all copies of kept messages over and over).

HTH
Matthias