fetchmail-users — User questions and discussion

Re: [Fetchmail-users] is it possible to use fetchmail with OAuth2 tokens?

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

 Hi,
I am very grateful to you for pointing this out to me. I have downloaded the master branch and will compile and try out. But before that, would you or anyone else know of an example .fetchmailrc  for how to modify the lines to accommodate this support? How do the lines change to use the token?

Many thanks again!



    On Wednesday, February 27, 2019, 5:44:20 PM CST, Matthias Andree <mat...@gm...> wrote:  
 
 Am 27.02.19 um 07:14 schrieb Globe Trotter via Fetchmail-users:
> but I was hoping (and wondering how) to continue to use fetchmail. I found this webpage: Setting Up OAUTH2 Support for Fetchmail and Postfix but I am having trouble figuring out how to specify tokens. We do not have password two-factor authentication.

There is contributed OAuth2 support in the "master" branch in Git, see
https://gitlab.com/fetchmail/fetchmail/commits/master/contrib/README - I
haven't tested it. Feedback solicited.




_______________________________________________
Fetchmail-users mailing list
Fet...@li...
https://lists.sourceforge.net/lists/listinfo/fetchmail-users
  

Re: [Fetchmail-users] is it possible to use fetchmail with OAuth2 tokens?

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

Am 27.02.19 um 07:14 schrieb Globe Trotter via Fetchmail-users:
> but I was hoping (and wondering how) to continue to use fetchmail. I found this webpage: Setting Up OAUTH2 Support for Fetchmail and Postfix but I am having trouble figuring out how to specify tokens. We do not have password two-factor authentication.

There is contributed OAuth2 support in the "master" branch in Git, see
https://gitlab.com/fetchmail/fetchmail/commits/master/contrib/README - I
haven't tested it. Feedback solicited.

Re: [Fetchmail-users] 517 Syntax error ??

[Peter P. <ro...@ri...>]

On Wed, Feb 27, 2019 at 10:37:30PM +0100, mario chiari wrote:
> On Tue, 2019-02-26 at 16:37 +0000, Ralph Corderoy wrote:
> > Hi Mario,
> > 
> > > > 
> 
> do you see anything? maybe the very last line below? thanks mario 
> 
> 
> [vmail@fedora-pc]$  env LC_ALL=C fetchmail -V -v --nodetach --nosyslog
> This is fetchmail release 6.3.26+GSS+RPA+NTLM+SDPS+SSL-SSLv2+HESIOD+NLS+KRB5.
[snip]

Could you also run and post the output of the second command that
Ralf quoted from the documentation, please?

  env LC_ALL=C fetchmail -vvv  --nodetach --nosyslog

G'luck,
Peter

-- 
Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} pp...@st...
PGP key:        http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13

Re: [Fetchmail-users] 517 Syntax error ??

[mario c. <ml...@ma...>]

On Tue, 2019-02-26 at 16:37 +0000, Ralph Corderoy wrote:
> Hi Mario,
> 
> > > 

do you see anything? maybe the very last line below? thanks mario 


[vmail@fedora-pc]$  env LC_ALL=C fetchmail -V -v --nodetach --nosyslog
This is fetchmail release 6.3.26+GSS+RPA+NTLM+SDPS+SSL-SSLv2+HESIOD+NLS+KRB5.

Copyright (C) 2002, 2003 Eric S. Raymond
Copyright (C) 2004 Matthias Andree, Eric S. Raymond,
                   Robert M. Funk, Graham Wilson
Copyright (C) 2005 - 2012 Sunil Shetye
Copyright (C) 2005 - 2013 Matthias Andree
Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you
are welcome to redistribute it under certain conditions. For details,
please see the file COPYING in the source or documentation directory.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)

Fallback MDA: (none)
Linux fedora-pc 4.19.12-301.fc29.x86_64 #1 SMP Mon Dec 24 01:58:57 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
The nodetach option is in effect, ignoring logfile option.
Taking options from command line and /----/.fetchmailrc
Poll interval is 600 seconds
Idfile is /----/.fetchids
Fetchmail will forward misaddressed multidrop messages to vmail.
Fetchmail will direct error mail to the sender.
Fetchmail will treat permanent errors as temporary (keep messages).
Options for retrieving from my...@my...@pop3.mydomain.net:
  True name of server is pop3.mydomain.net.
  This host will be queried when no host is specified.
  Password = "********".
  Protocol is POP3 (using service 110).
  All available authentication methods will be tried.
  Server nonresponse timeout is 300 seconds (default).
  Default mailbox selected.
  Only new messages will be retrieved (--all off).
  Fetched messages will not be kept on the server (--keep off).
  Old messages will not be flushed before message retrieval (--flush off).
  Oversized messages will not be flushed before message retrieval (--limitflush
off).
  Rewrite of server-local addresses is enabled (--norewrite off).
  Carriage-return stripping is enabled (stripcr on).
  Carriage-return forcing is disabled (forcecr off).
  Interpretation of Content-Transfer-Encoding is enabled (pass8bits off).
  MIME decoding is disabled (mimedecode off).
  Idle after poll is disabled (idle off).
  Nonempty Status lines will be kept (dropstatus off)
  Delivered-To lines will be kept (dropdelivered off)
  No received-message limit (--fetchlimit 0).
  Fetch message size limit is 100 (--fetchsizelimit 100).
  Do binary search of UIDs during 3 out of 4 polls (--fastuidl 4).
  No SMTP message batch limit (--batchlimit 0).
  No forced expunges (--expunge 0).
  Messages will be delivered with "/usr/lib/courier/bin/sendmail  -i -f %F --
%T".
  Spam-blocking disabled
  No pre-connection command.
  No post-connection command.
  Single-drop mode: 1 local name recognized.
	my...@my...
  No interface requirement specified.
  No monitor interface specified.
  No plugin command specified.
  No plugout command specified.
  No UIDs saved from this host.
  No poll trace information will be added to the Received header.
  Messages with bad headers will be rejected.
----

Re: [Fetchmail-users] is it possible to use fetchmail with OAuth2 tokens?

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

 

> I asked about oauth2 support on 2015. <https://sourceforge.net/p/fetchmail/mailman/fetchmail-users/?viewmonth=201511>

Thank you, Carlos. I am sorry that I did not understand this thread at all. It seems to veer off talking about IMAP vs POP3 (I prefer POP3) but it is not at all clear to me that fetchmail can handle tokens The thread seems to suggest that fetchmail does not support OAuth2, but that contradicts what I found on the web: Setting Up OAUTH2 Support for Fetchmail and Postfix.


| 
| 
|  | 
Setting Up OAUTH2 Support for Fetchmail and Postfix


 |

 |

 |


So, can fetchmail handle OAuth2 tokens? If so, is there any example? That would be very helpful. I am trying to fetch mails from a POP3 exchange server.
Thanks again for any further advice and best wishes!!

  

Re: [Fetchmail-users] is it possible to use fetchmail with OAuth2 tokens?

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

On 27/02/2019 07.14, Globe Trotter via Fetchmail-users wrote:
> Hello,
> Our workplace has decided to move to multi-factor authentication using a Google Authenticator. I am the sole linux user, with unfortunately not much support. I know that evolution works and I found some help here: Evolution Mail (Linux Users) | Department of Statistics

I asked about oauth2 support on 2015.

<https://sourceforge.net/p/fetchmail/mailman/fetchmail-users/?viewmonth=201511>

-- 
Cheers / Saludos,

		Carlos E. R.
		(from 15.0 x86_64 at Telcontar)

[Fetchmail-users] is it possible to use fetchmail with OAuth2 tokens?

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

Hello,
Our workplace has decided to move to multi-factor authentication using a Google Authenticator. I am the sole linux user, with unfortunately not much support. I know that evolution works and I found some help here: Evolution Mail (Linux Users) | Department of Statistics

| 
| 
| 
|  |  |

 |

 |
| 
|  | 
Evolution Mail (Linux Users) | Department of Statistics

The Evolution Mail client supports Office 365 through the evolution-ews plugin, starting in evolution-ews v3.27....
 |

 |

 |




but I was hoping (and wondering how) to continue to use fetchmail. I found this webpage: Setting Up OAUTH2 Support for Fetchmail and Postfix but I am having trouble figuring out how to specify tokens. We do not have password two-factor authentication.


| 
| 
|  | 
Setting Up OAUTH2 Support for Fetchmail and Postfix


 |

 |

 |


Any suggestions as to what could be done? Thanks in advance for any help! 

Re: [Fetchmail-users] 517 Syntax error ??

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

On Tuesday 26 February 2019 11:06:14 mario chiari wrote:

> On Tue, 2019-02-26 at 05:59 -0500, Gene Heskett wrote:
> > On Tuesday 26 February 2019 04:57:25 mario chiari wrote:
> > > Hi
> > >
> > > I get this error message:
> > >
> > > fetchmail: reading message my...@my...@pop3.mydomain.net:1
> > > of 40 (1552 octets) (log message incomplete)
> > > fetchmail: MDA returned nonzero status 67
> > > fetchmail:  not flushed
> > > 517 Syntax error.
> > >
> > > Most often the culprit seems to be a return receipt message, o a
> > > failed delivery message.
>
> ...
>
> > This might be the result of fetchmail being wrongfully denied the
> > ability to delete a mail successfully pulled from the pop3 server.
>
> Gene, thanks for yout reply.
>
> No,  return receipt and failed delivery msgs are not pulled from the
> pop3 server. (I see them only if I check at my provider's webmail)
>
> m.
Well, I was just throwing it out there to see if it stuck to the wall. 
I'll offer that was my best shot, so I'll go back to lurking.  Thats an 
error I've  not seem in 2 decades of using fetchmail.

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] 517 Syntax error ??

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

Hi Mario,

> > I get the impression it's more a complaint from the party that fetchmail
> > is passing the email to;  the Mail Delivery Agent.
>
> How do I check if it so? 

The command below should show what conversation causes the error:
fetching the email upstream, or delivering it downstream.

> > Have you seen http://www.fetchmail.info/fetchmail-FAQ.html#G3
> > that gives details of how to report a problem?
>
> I just checked it (thanks and sorry I did not do before)
> Now I get:

Thanks.  Now we need verbose output from an attempt to fetch that
problem email.  Sorry, should have said this before.  A better
reference is this part of the fetchmail(1) man page.

   SUPPORT, TROUBLESHOOTING
       For troubleshooting, tracing and debugging, you need to increase
       fetchmail's verbosity to actually see what happens. To do that, please
       run both of the two following commands, adding all of the options you'd
       normally use.

              env LC_ALL=C fetchmail -V -v --nodetach --nosyslog

              (This command line prints in English how fetchmail understands
              your configuration.)

              env LC_ALL=C fetchmail -vvv  --nodetach --nosyslog

              (This command line actually runs fetchmail with verbose English
              output.)

       Also see item #G3 in fetchmail's FAQ ⟨http://fetchmail.berlios.de/
       fetchmail-FAQ.html#G3⟩

       You can omit the LC_ALL=C part above if you want output in the local
       language (if supported). However if you are posting to mailing lists,
       please leave it in. The maintainers do not necessarily understand your
       language, please use English.

-- 
Cheers, Ralph.

Re: [Fetchmail-users] 517 Syntax error ??

[mario c. <ml...@ma...>]

On Tue, 2019-02-26 at 11:11 +0000, Ralph Corderoy wrote:
> Hi Mario,
> 
> Gene wrote:
> > > fetchmail: reading message my...@my...@pop3.mydomain.net:1 of
> > > 40 (1552 octets) (log message incomplete)
> > > fetchmail: MDA returned nonzero status 67
> > > fetchmail:  not flushed
> > > 517 Syntax error.
> > 
> > This might be the result of fetchmail being wrongfully denied the
> > ability to delete a mail successfully pulled from the pop3 server.
> 
> I get the impression it's more a complaint from the party that fetchmail
> is passing the email to;  the Mail Delivery Agent.

How do I check if it so? 

> 
> Have you seen http://www.fetchmail.info/fetchmail-FAQ.html#G3
> that gives details of how to report a problem?
I just checked it (thanks and sorry I did not do before)

Now I get:

[----]$ env LC_ALL=C fetchmail -V
This is fetchmail release 6.3.26+GSS+RPA+NTLM+SDPS+SSL-SSLv2+HESIOD+NLS+KRB5.

Copyright (C) 2002, 2003 Eric S. Raymond
Copyright (C) 2004 Matthias Andree, Eric S. Raymond,
                   Robert M. Funk, Graham Wilson
Copyright (C) 2005 - 2012 Sunil Shetye
Copyright (C) 2005 - 2013 Matthias Andree
Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you
are welcome to redistribute it under certain conditions. For details,
please see the file COPYING in the source or documentation directory.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)

Fallback MDA: (none)
Linux fedora-pc 4.19.12-301.fc29.x86_64 #1 SMP Mon Dec 24 01:58:57 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Taking options from command line and /***/***/.fetchmailrc
Poll interval is 600 seconds
Logfile is /***/***/logs/fetchmail.log
Idfile is /***/***/.fetchids
Fetchmail will forward misaddressed multidrop messages to vmail.
Options for retrieving from ***@mydomain.net@pop3.mydomain.net:
  True name of server is pop3.mydomain.net.
  Protocol is POP3 (using service 110).
  All available authentication methods will be tried.
  Server nonresponse timeout is 300 seconds (default).
  Default mailbox selected.
  Only new messages will be retrieved (--all off).
  Fetched messages will not be kept on the server (--keep off).
  Old messages will not be flushed before message retrieval (--flush off).
  Oversized messages will not be flushed before message retrieval (--limitflush
off).
  Rewrite of server-local addresses is enabled (--norewrite off).
  Carriage-return stripping is enabled (stripcr on).
  Carriage-return forcing is disabled (forcecr off).
  Interpretation of Content-Transfer-Encoding is enabled (pass8bits off).
  MIME decoding is disabled (mimedecode off).
  Idle after poll is disabled (idle off).
  Nonempty Status lines will be kept (dropstatus off)
  Delivered-To lines will be kept (dropdelivered off)
  Fetch message size limit is 100 (--fetchsizelimit 100).
  Do binary search of UIDs during 3 out of 4 polls (--fastuidl 4).
  Messages will be delivered with "/usr/lib/courier/bin/sendmail  -i -f %F --
%T".
  Single-drop mode: 1 local name recognized.
  No UIDs saved from this host.

Re: [Fetchmail-users] 517 Syntax error ??

[mario c. <ml...@ma...>]

On Tue, 2019-02-26 at 05:59 -0500, Gene Heskett wrote:
> On Tuesday 26 February 2019 04:57:25 mario chiari wrote:
> 
> > Hi
> > 
> > I get this error message:
> > 
> > fetchmail: reading message my...@my...@pop3.mydomain.net:1 of
> > 40 (1552 octets) (log message incomplete)
> > fetchmail: MDA returned nonzero status 67
> > fetchmail:  not flushed
> > 517 Syntax error.
> > 
> > Most often the culprit seems to be a return receipt message, o a
> > failed delivery message.
> > 
> > 
...
> This might be the result of fetchmail being wrongfully denied the ability 
> to delete a mail successfully pulled from the pop3 server.

Gene, thanks for yout reply.

No,  return receipt and failed delivery msgs are not pulled from the pop3
server. (I see them only if I check at my provider's webmail)

m. 

Re: [Fetchmail-users] 517 Syntax error ??

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

Hi Mario,

Gene wrote:
> > fetchmail: reading message my...@my...@pop3.mydomain.net:1 of
> > 40 (1552 octets) (log message incomplete)
> > fetchmail: MDA returned nonzero status 67
> > fetchmail:  not flushed
> > 517 Syntax error.
>
> This might be the result of fetchmail being wrongfully denied the
> ability to delete a mail successfully pulled from the pop3 server.

I get the impression it's more a complaint from the party that fetchmail
is passing the email to;  the Mail Delivery Agent.

Have you seen http://www.fetchmail.info/fetchmail-FAQ.html#G3
that gives details of how to report a problem?

-- 
Cheers, Ralph.

Re: [Fetchmail-users] 517 Syntax error ??

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

On Tuesday 26 February 2019 04:57:25 mario chiari wrote:

> Hi
>
> I get this error message:
>
> fetchmail: reading message my...@my...@pop3.mydomain.net:1 of
> 40 (1552 octets) (log message incomplete)
> fetchmail: MDA returned nonzero status 67
> fetchmail:  not flushed
> 517 Syntax error.
>
> Most often the culprit seems to be a return receipt message, o a
> failed delivery message.
>
> I have a very basic know-how about fetchmail, but I would like to fix
> this issue.
>
> Thanks
> Regards
> mario

This might be the result of fetchmail being wrongfully denied the ability 
to delete a mail successfully pulled from the pop3 server. Because so 
many customers use imap and a web based email agent, many ISP's have 
denied fetchmail that deletion ability.  My ISP uses dovecot to serve 
both customers from the same server. Mine has made that failure silent 
somehow, so I have to log into the server daily and use firefox to clean 
out my mailbox as I don't use imap. I keep my own email corpus, pushing 
nearly 20 years old now.

I use the latest fetchmail 6.3.26 with a patch to include a timestamp in 
the log line, against their server, and they have it configured to 
accept the "flush" command but ignore it. So fetchmail is not aware of 
the failure. It has its own old mail record keeping.  IMO thats the best 
option for the ISP who must serve both protocols since imap users expect 
their mail server to have everything they've ever received.

This also exposes, if they get hacked, all the most private details of 
your online banking activities, etc, etc, and allows the ISP who would 
monetize their spam delivery by sending you crap you may have shown an 
interest in. My mail is IMNSHO, none of their business, hence I log in 
and clean it out a couple times a day.

A phone call to your ISP's tech staff might be beneficial if thats the 
cause but email is flowing anyway. They may not be aware they are giving 
fetchmail a minor tummy ache with their method of protecting their imap 
using customers.
>
>
> _______________________________________________
> Fetchmail-users mailing list
> Fet...@li...
> https://lists.sourceforge.net/lists/listinfo/fetchmail-users


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>

[Fetchmail-users] 517 Syntax error ??

[mario c. <ml...@ma...>]

Hi

I get this error message:

fetchmail: reading message my...@my...@pop3.mydomain.net:1 of 40 (1552
octets) (log message incomplete)
fetchmail: MDA returned nonzero status 67
fetchmail:  not flushed
517 Syntax error.

Most often the culprit seems to be a return receipt message, o a failed delivery
message.  

I have a very basic know-how about fetchmail, but I would like to fix this
issue.

Thanks
Regards
mario 

Re: [Fetchmail-users] Unicode (remote) mailbox names

[ಚಿರಾಗ್ ನ. <chi...@gm...>]

On 02/01/19 11:18, Matthias Andree wrote:
> Am 02.01.19 um 04:31 schrieb ಚಿರಾಗ್ ನಟರಾಜ್:
> > Hey all,
> >
> > So I am bilingual and speak both Kannada and English fluently. I decided to switch my Google account over to Kannada just for fun and realized that it broke my fetchmail setup. After some investigation, I found out that the remote mailbox name had changed from "[Gmail]/All Mail" to "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್". However, changing the name in my .fetchmailrc didn't fix the issue. The exact output I got when running fetchmail in verbose mode is given here:
> >
> > --------
> > fetchmail: starting fetchmail 6.4.0.beta4 daemon
> > fetchmail: 6.4.0.beta4 querying imap.gmail.com (protocol IMAP) at : poll started
> > Trying to connect to 209.85.201.109/993...connected.
> > fetchmail: Loaded OpenSSL library 0x1010101f newer than headers 0x1010008f, trying to continue.
> > fetchmail: Server certificate:
> > fetchmail: Issuer Organization: Google Trust Services
> > fetchmail: Issuer CommonName: Google Internet Authority G3
> > fetchmail: Subject CommonName: imap.gmail.com
> > fetchmail: Subject Alternative Name: imap.gmail.com
> > fetchmail: imap.gmail.com key fingerprint: 0F:BD:6E:EF:72:5F:46:75:CE:06:CF:5C:8C:3B:D2:AB
> > fetchmail: SSL/TLS: using protocol TLSv1.2, cipher ECDHE-RSA-CHACHA20-POLY1305, 256/256 secret/processed bits
> > fetchmail: IMAP< * OK Gimap ready for requests from 64.20.43.202 c23mb659673737qtq
> > fetchmail: IMAP> A0001 CAPABILITY
> > fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH
> > fetchmail: IMAP< A0001 OK Thats all she wrote! c23mb659673737qtq
> > fetchmail: IMAP> A0002 LOGIN "chiraag.nataraj" *
> > fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH UTF8=ACCEPT LIST-EXTENDED LIST-STATUS LITERAL- SPECIAL-USE APPENDLIMIT=35651584
> > fetchmail: IMAP< A0002 OK chi...@gm... authenticated (Success)
> > fetchmail: IMAP> A0003 SELECT "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್"
> > fetchmail: IMAP< A0003 BAD Could not parse command
> > fetchmail: mailbox selection failed
> > fetchmail: IMAP> A0004 LOGOUT
> > fetchmail: IMAP< * BYE LOGOUT Requested
> > fetchmail: IMAP< A0004 OK 73 good day (Success)
> > fetchmail: client/server synchronization error while fetching from chi...@im...
> > fetchmail: 6.4.0.beta4 querying imap.gmail.com (protocol IMAP) at : poll completed
> > fetchmail: Query status=7 (ERROR)
> > --------
> >
> > The configuration I am using is given here:
> >
> > --------
> > set postmaster "chiraag"
> > set bouncemail
> > set no spambounce
> > set softbounce
> > set properties ""
> > poll imap.gmail.com with proto IMAP
> >        user 'chiraag.nataraj' there with password 'supersecretpassword' is 'chiraag' here
> >        options keep ssl sslproto "TLS1+" mda "getmail_maildir $HOME/Mail/Gmail/"
> >   folder "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್"
> > --------
> >
> > Am I missing something or does fetchmail not (currently) support Unicode mailbox names?
> >
> Hello Chiraag,
> 
> you are right, fetchmail does not currently transcode mailbox names to
> the modified UTF-7 format that IMAP requires for mailbox names per
> RFC3501 chapter 5.1.3, <https://tools.ietf.org/html/rfc3501#page-19>
> 
> Does it work if you specify
> 
> folder "[Gmail]/&DI4MsgzNDLIMvg- &DK4MxwyyDM0-"
> 
> ? (I hope my gnome-terminal and Thunderbird and clipboard haven't messed
> up my copy and paste and that I haven't made a mistake translating the
> mailbox name to modified UTF-7)
> 
> Regards,
> 
> -- 
> Matthias Andree
>
Hi Matthias,

Thank you so much, the solution worked beautifully and my fetchmail is (once again) downloading my emails!

Sincerely,

Chiraag
-- 
ಚಿರಾಗ್ ನಟರಾಜ್
Graduate Student at Brown University
Email: chi...@gm...
Phone: 610-350-6329
Website: http://chiraag.nataraj.us

Re: [Fetchmail-users] Unicode (remote) mailbox names

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

Am 02.01.19 um 04:31 schrieb ಚಿರಾಗ್ ನಟರಾಜ್:
> Hey all,
>
> So I am bilingual and speak both Kannada and English fluently. I decided to switch my Google account over to Kannada just for fun and realized that it broke my fetchmail setup. After some investigation, I found out that the remote mailbox name had changed from "[Gmail]/All Mail" to "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್". However, changing the name in my .fetchmailrc didn't fix the issue. The exact output I got when running fetchmail in verbose mode is given here:
>
> --------
> fetchmail: starting fetchmail 6.4.0.beta4 daemon
> fetchmail: 6.4.0.beta4 querying imap.gmail.com (protocol IMAP) at : poll started
> Trying to connect to 209.85.201.109/993...connected.
> fetchmail: Loaded OpenSSL library 0x1010101f newer than headers 0x1010008f, trying to continue.
> fetchmail: Server certificate:
> fetchmail: Issuer Organization: Google Trust Services
> fetchmail: Issuer CommonName: Google Internet Authority G3
> fetchmail: Subject CommonName: imap.gmail.com
> fetchmail: Subject Alternative Name: imap.gmail.com
> fetchmail: imap.gmail.com key fingerprint: 0F:BD:6E:EF:72:5F:46:75:CE:06:CF:5C:8C:3B:D2:AB
> fetchmail: SSL/TLS: using protocol TLSv1.2, cipher ECDHE-RSA-CHACHA20-POLY1305, 256/256 secret/processed bits
> fetchmail: IMAP< * OK Gimap ready for requests from 64.20.43.202 c23mb659673737qtq
> fetchmail: IMAP> A0001 CAPABILITY
> fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH
> fetchmail: IMAP< A0001 OK Thats all she wrote! c23mb659673737qtq
> fetchmail: IMAP> A0002 LOGIN "chiraag.nataraj" *
> fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH UTF8=ACCEPT LIST-EXTENDED LIST-STATUS LITERAL- SPECIAL-USE APPENDLIMIT=35651584
> fetchmail: IMAP< A0002 OK chi...@gm... authenticated (Success)
> fetchmail: IMAP> A0003 SELECT "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್"
> fetchmail: IMAP< A0003 BAD Could not parse command
> fetchmail: mailbox selection failed
> fetchmail: IMAP> A0004 LOGOUT
> fetchmail: IMAP< * BYE LOGOUT Requested
> fetchmail: IMAP< A0004 OK 73 good day (Success)
> fetchmail: client/server synchronization error while fetching from chi...@im...
> fetchmail: 6.4.0.beta4 querying imap.gmail.com (protocol IMAP) at : poll completed
> fetchmail: Query status=7 (ERROR)
> --------
>
> The configuration I am using is given here:
>
> --------
> set postmaster "chiraag"
> set bouncemail
> set no spambounce
> set softbounce
> set properties ""
> poll imap.gmail.com with proto IMAP
>        user 'chiraag.nataraj' there with password 'supersecretpassword' is 'chiraag' here
>        options keep ssl sslproto "TLS1+" mda "getmail_maildir $HOME/Mail/Gmail/"
>   folder "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್"
> --------
>
> Am I missing something or does fetchmail not (currently) support Unicode mailbox names?
>
Hello Chiraag,

you are right, fetchmail does not currently transcode mailbox names to
the modified UTF-7 format that IMAP requires for mailbox names per
RFC3501 chapter 5.1.3, <https://tools.ietf.org/html/rfc3501#page-19>

Does it work if you specify

folder "[Gmail]/&DI4MsgzNDLIMvg- &DK4MxwyyDM0-"

? (I hope my gnome-terminal and Thunderbird and clipboard haven't messed
up my copy and paste and that I haven't made a mistake translating the
mailbox name to modified UTF-7)

Regards,

-- 
Matthias Andree

Re: [Fetchmail-users] Unicode (remote) mailbox names

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

Hi Chiraag,

> So I am bilingual and speak both Kannada and English fluently.

I hadn't heard of Kannada before.  For others on the list like me: it's
one of the `scheduled languages of India', with over 40 million native
speakers.

> fetchmail: IMAP> A0003 SELECT "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್"
> fetchmail: IMAP< A0003 BAD Could not parse command
...
>   folder "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್"

Have you a missing `"' to end the `folder's parameter?
fetchmail(1)'s description of `Run Control Syntax' suggests it could be
an unquoted string without any `"' at all.

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

[Fetchmail-users] Unicode (remote) mailbox names

[ಚಿರಾಗ್ ನ. <chi...@gm...>]

Hey all,

So I am bilingual and speak both Kannada and English fluently. I decided to switch my Google account over to Kannada just for fun and realized that it broke my fetchmail setup. After some investigation, I found out that the remote mailbox name had changed from "[Gmail]/All Mail" to "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್". However, changing the name in my .fetchmailrc didn't fix the issue. The exact output I got when running fetchmail in verbose mode is given here:

--------
fetchmail: starting fetchmail 6.4.0.beta4 daemon
fetchmail: 6.4.0.beta4 querying imap.gmail.com (protocol IMAP) at : poll started
Trying to connect to 209.85.201.109/993...connected.
fetchmail: Loaded OpenSSL library 0x1010101f newer than headers 0x1010008f, trying to continue.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Google Trust Services
fetchmail: Issuer CommonName: Google Internet Authority G3
fetchmail: Subject CommonName: imap.gmail.com
fetchmail: Subject Alternative Name: imap.gmail.com
fetchmail: imap.gmail.com key fingerprint: 0F:BD:6E:EF:72:5F:46:75:CE:06:CF:5C:8C:3B:D2:AB
fetchmail: SSL/TLS: using protocol TLSv1.2, cipher ECDHE-RSA-CHACHA20-POLY1305, 256/256 secret/processed bits
fetchmail: IMAP< * OK Gimap ready for requests from 64.20.43.202 c23mb659673737qtq
fetchmail: IMAP> A0001 CAPABILITY
fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH
fetchmail: IMAP< A0001 OK Thats all she wrote! c23mb659673737qtq
fetchmail: IMAP> A0002 LOGIN "chiraag.nataraj" *
fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH UTF8=ACCEPT LIST-EXTENDED LIST-STATUS LITERAL- SPECIAL-USE APPENDLIMIT=35651584
fetchmail: IMAP< A0002 OK chi...@gm... authenticated (Success)
fetchmail: IMAP> A0003 SELECT "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್"
fetchmail: IMAP< A0003 BAD Could not parse command
fetchmail: mailbox selection failed
fetchmail: IMAP> A0004 LOGOUT
fetchmail: IMAP< * BYE LOGOUT Requested
fetchmail: IMAP< A0004 OK 73 good day (Success)
fetchmail: client/server synchronization error while fetching from chi...@im...
fetchmail: 6.4.0.beta4 querying imap.gmail.com (protocol IMAP) at : poll completed
fetchmail: Query status=7 (ERROR)
--------

The configuration I am using is given here:

--------
set postmaster "chiraag"
set bouncemail
set no spambounce
set softbounce
set properties ""
poll imap.gmail.com with proto IMAP
       user 'chiraag.nataraj' there with password 'supersecretpassword' is 'chiraag' here
       options keep ssl sslproto "TLS1+" mda "getmail_maildir $HOME/Mail/Gmail/"
  folder "[Gmail]/ಎಲ್ಲಾ ಮೇಲ್"
--------

Am I missing something or does fetchmail not (currently) support Unicode mailbox names?

Thanks in advance!

- Chiraag
-- 
ಚಿರಾಗ್ ನಟರಾಜ್
Graduate Student at Brown University
Email: chi...@gm...
Phone: 610-350-6329
Website: http://chiraag.nataraj.us

Re: [Fetchmail-users] Fetchmail without passwords in plaintext file?

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

Am 12.12.18 um 14:07 schrieb Bjoern Voigt:
> Gene Heskett wrote:
>> While I realize there is a need for encrypted passwd's in the more densly
>> populated and/or industrial areas where business critical information 
>> might be sought by the shadier types, that need has not reached out here 
>> in the puckerbrush. Yet... I am not aware of any pop3 server in this 
>> moderately rural area, ever asking us to use encrypted passwds. Not 
>> saying there aren't such isp's but I've not encountered any yet.  What 
>> I'm saying is that forcing it on us, would force us to find another 
>> fetchmail like agent. In fact, they've not even forced us to longer 
>> passwds yet. I'd druther they did, to at least 20 alpha/numeric chars 
>> but too many winders users think 12345 or 54321Boom is good enough.
>> And they are the majority by far. I'm an island of all linux stuff here.
> Gene, I do not think, that Fetchmail will force us to store passwords
> encrypted. But I think, Fetchmail should ofter at least one working
> interface to an encrypted password store or password manager. And I
> think, the Fetchmail documentation should recommend to store passwords
> encrypted.


Björn,

you may want to get fetchmail's master branch from Git or possibly the
7.0.0-alpha6 tarball (*) and let us know what you think of either
passwordeval and/or PWMD support.

(*) currently at <http://krusty.dt.e-technik.tu-dortmund.de/~ma/fetchmail/>

HTH

Matthias

Re: [Fetchmail-users] Fetchmail without passwords in plaintext file?

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

On Wednesday 12 December 2018 11:37:44 Peter Pentchev wrote:
[...]
> I think you're talking at cross purposes. 

Entirely possible Peter.

> I believe that Bjoern and 
> Matthias are discussing whether the password should be stored in
> the ~/.fetchmailrc file in plain text, so that anybody with access to
> the user's account would be able to look at the file and see it, or
> whether fetchmail should ask another program to provide it with
> the password only when it is needed.

Access to the users machine tightens that up considerably. Stuff the 
public can look at is my web page but its in a sandbox no-one has 
splashed out of yet in much of a decade, and I am the only breathing 
user. I can become the other 3 "users" at will if they need attention, 
but these 6 or 7 machines are all mine, and all behind dd-wrt in my 
router. Which, other than the NAT from the registered ipv4 address for 
my 192.168.xx.xx web pages has not been penetrated in close to 20 years.

> Gene, you seem to be talking about whether the password, once
> fetchmail has obtained it somehow, should be sent over the network in
> plaintext; I believe that this is usually handled by instructing
> fetchmail to negotiate a TLS/SSL connection with the mail server.  If
> there are any ISPs that do not provide this option to their users in
> 2018, that's... troubling.

That of coarse is happening, out of my sight, and it is being sent 
encrypted, but its stored in the clear here. If we had a dubiously named 
utility to dcrypt it from a locally secure encryption, reencoding it for 
fetchmails use only when needed I'm sure that would be acceptable, 
particularly if the memory it used to do it was scrubbed before giving 
it back. That would be about as secure as I can imagine. And at the same 
time not a huge time sink to do it, specially if working from an SSD.
 
> G'luck,
> Peter

Take care Peter.

-- 
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] Fetchmail without passwords in plaintext file?

[Peter P. <ro...@ri...>]

On Wed, Dec 12, 2018 at 11:17:12AM -0500, Gene Heskett wrote:
> On Wednesday 12 December 2018 08:07:05 Bjoern Voigt wrote:
> 
> > Matthias Andree wrote:
> > > Regarding plaintext password storage, you don't have to, but
> > > fetchmail had originally been written for end-user consumption and
> > > not high-grade datacenter use.
> >
> > Yes, you know the historical requirements for Fetchmail. But how you
> > think now about unencrypted passwords in Fetchmail?
> >
> > I think, that datacenters are much more secured than mobile devices
> > (e.g. laptops) of average Linux users. Also SOHO servers, NAS devices
> > are often not secured very good.
> >
> > Of course, long-term Linux users (I also started 1996) may still
> > think, that unencrypted passwords in a file with -rw-------
> > permissions are "safe enough". In fact this is somehow true for
> > multi-user computers in secure locations where normal users have no
> > root rights and where the root users are trustworthy.
> >
> > But do we still have to discuss about unencrypted passwords at the end
> > of 2018? Auditors could laugh at us.
> >
> They may do worse than that, but its the mail server admins at your ISP 
> which will have to push for it to gain any real traction.  Welcome to 
> the facts of life. :)
> 
> Besides, in transit, its still clear text to those that want to spoof it, 
> all they have to do is copy it in passing so there will be no difference 
> in the security level until the isp's server sends the encryption std 
> the client is to use today, and rotates it frequently. Daily might be 
> reasonable, hourly would tend to load up the server with 10000 accounts. 
> Even that, to a determined hacker is only a minor problem and we all 
> know it.

I think you're talking at cross purposes.  I believe that Bjoern and
Matthias are discussing whether the password should be stored in
the ~/.fetchmailrc file in plain text, so that anybody with access to
the user's account would be able to look at the file and see it, or
whether fetchmail should ask another program to provide it with
the password only when it is needed.

Gene, you seem to be talking about whether the password, once fetchmail
has obtained it somehow, should be sent over the network in plaintext;
I believe that this is usually handled by instructing fetchmail to
negotiate a TLS/SSL connection with the mail server.  If there are any
ISPs that do not provide this option to their users in 2018, that's...
troubling.

G'luck,
Peter

-- 
Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} pp...@st...
PGP key:        http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13

Re: [Fetchmail-users] Fetchmail without passwords in plaintext file?

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

On Wednesday 12 December 2018 08:07:05 Bjoern Voigt wrote:

> Matthias Andree wrote:
> > Regarding plaintext password storage, you don't have to, but
> > fetchmail had originally been written for end-user consumption and
> > not high-grade datacenter use.
>
> Yes, you know the historical requirements for Fetchmail. But how you
> think now about unencrypted passwords in Fetchmail?
>
> I think, that datacenters are much more secured than mobile devices
> (e.g. laptops) of average Linux users. Also SOHO servers, NAS devices
> are often not secured very good.
>
> Of course, long-term Linux users (I also started 1996) may still
> think, that unencrypted passwords in a file with -rw-------
> permissions are "safe enough". In fact this is somehow true for
> multi-user computers in secure locations where normal users have no
> root rights and where the root users are trustworthy.
>
> But do we still have to discuss about unencrypted passwords at the end
> of 2018? Auditors could laugh at us.
>
They may do worse than that, but its the mail server admins at your ISP 
which will have to push for it to gain any real traction.  Welcome to 
the facts of life. :)

Besides, in transit, its still clear text to those that want to spoof it, 
all they have to do is copy it in passing so there will be no difference 
in the security level until the isp's server sends the encryption std 
the client is to use today, and rotates it frequently. Daily might be 
reasonable, hourly would tend to load up the server with 10000 accounts. 
Even that, to a determined hacker is only a minor problem and we all 
know it.

[...]

Take care Björn

-- 
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] Fetchmail without passwords in plaintext file?

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

On Wednesday 12 December 2018 08:07:23 Bjoern Voigt wrote:

> Gene Heskett wrote:
> > While I realize there is a need for encrypted passwd's in the more
> > densly populated and/or industrial areas where business critical
> > information might be sought by the shadier types, that need has not
> > reached out here in the puckerbrush. Yet... I am not aware of any
> > pop3 server in this moderately rural area, ever asking us to use
> > encrypted passwds. Not saying there aren't such isp's but I've not
> > encountered any yet.  What I'm saying is that forcing it on us,
> > would force us to find another fetchmail like agent. In fact,
> > they've not even forced us to longer passwds yet. I'd druther they
> > did, to at least 20 alpha/numeric chars but too many winders users
> > think 12345 or 54321Boom is good enough. And they are the majority
> > by far. I'm an island of all linux stuff here.
>
> Gene, I do not think, that Fetchmail will force us to store passwords
> encrypted. But I think, Fetchmail should ofter at least one working
> interface to an encrypted password store or password manager. And I
> think, the Fetchmail documentation should recommend to store passwords
> encrypted.
>
That I cannot argue with. Optional is best, and the user should be able 
to make it so from the instructions in the man page. Complete enough 
he/she won't have to pester the list to do it. And it wouldn't hurt to 
arrange a cleartext version hidden someplace preferably NOT on the 
machines drives. Here, a post-it note on the wall would be fine if you 
could find one that would stick till the rapture. Seems like the glue is 
getting weaker over the last couple decades...
> Greetings,
> Björn



-- 
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>

[Fetchmail-users] Fetchmail without passwords in plaintext file?

[Bjoern V. <bj...@ar...>]

Matthias Andree wrote:
> Regarding plaintext password storage, you don't have to, but fetchmail
> had originally been written for end-user consumption and not high-grade
> datacenter use.

Yes, you know the historical requirements for Fetchmail. But how you
think now about unencrypted passwords in Fetchmail?

I think, that datacenters are much more secured than mobile devices
(e.g. laptops) of average Linux users. Also SOHO servers, NAS devices
are often not secured very good.

Of course, long-term Linux users (I also started 1996) may still think,
that unencrypted passwords in a file with -rw------- permissions are
"safe enough". In fact this is somehow true for multi-user computers in
secure locations where normal users have no root rights and where the
root users are trustworthy.

But do we still have to discuss about unencrypted passwords at the end
of 2018? Auditors could laugh at us.

> If I need to manually (through Git downloads) integrate a merge request
> (such as !1 or !11 or others), possibly rebasing it to linearize
> history, I cannot properly have Gitlab reflect that, you'll need to read
> the comments to see that I did in fact merge them - but not into the
> legacy_64 branch, (6.4 BETA) but instead into the master branch, where I
> take the 7.0 ALPHA snapshots from. So, that point rejected, but no
> offense taken.
>
> Feel free to check if there are relevant Gitlab bug/feature request
> tickets and otherwise write one to permit me to mark things as merged. I
> believe Gitorous, or some other Git hosting site, permitted that.

OK, thanks for the details. On openSUSE Tumbleweed (a rolling-release
distribution) I still have Fetchmail 6.3.26. When 7.0 will be up?

I can not do the tasks, at least not this year. If I would do this, I
will have to start from zero: Open a Gitlab account, explore the
functionality of Gitlab, start playing with PWMD and the Fetchmail
patches, ...

May be you can contact Ben Kibbey who wrote the patches? He would be
much faster.

Greetings,
Björn

Re: [Fetchmail-users] Fetchmail without passwords in plaintext file?

[Bjoern V. <bj...@ar...>]

Gene Heskett wrote:
> While I realize there is a need for encrypted passwd's in the more densly
> populated and/or industrial areas where business critical information 
> might be sought by the shadier types, that need has not reached out here 
> in the puckerbrush. Yet... I am not aware of any pop3 server in this 
> moderately rural area, ever asking us to use encrypted passwds. Not 
> saying there aren't such isp's but I've not encountered any yet.  What 
> I'm saying is that forcing it on us, would force us to find another 
> fetchmail like agent. In fact, they've not even forced us to longer 
> passwds yet. I'd druther they did, to at least 20 alpha/numeric chars 
> but too many winders users think 12345 or 54321Boom is good enough.
> And they are the majority by far. I'm an island of all linux stuff here.

Gene, I do not think, that Fetchmail will force us to store passwords
encrypted. But I think, Fetchmail should ofter at least one working
interface to an encrypted password store or password manager. And I
think, the Fetchmail documentation should recommend to store passwords
encrypted.

Greetings,
Björn