Re: webmail and email from command line
On Wed, Aug 14, 2019 at 4:24 PM loredana wrote: > > Greetings, > > I posted the following message to debian-accessibility and I post it > again as suggested. My mistake. I can't cope with this threading hijacking. As I said in my first post, I do have a serious problem I am trying to solve. I will browse the mailing list for a while, just in case somebody out there wants to help and I will be back (to debian-accessibility) once I find a working solution. For the time being, I need to give to my mailbox a well deserved break. Thanks again to those who helped. Bye, Loredana "A chi piu' sa, piu' perder tempo spiace" - Dante Alighieri
Re: webmail and email from command line
On Fri, Aug 16, 2019 at 12:51 PM Jude DaShiell wrote: > Running using 2fa may be possible with non-browser apps if your security > records indicate you ran with what google considers an untrusted app and > google has it listed. You can generate an app-specific password for the > non-browser app and will need to save it. Then you modify your > non-browser app settings on local machine and key in that app-specific > password in place of the other password you used earlier. This has been > documented for mutt as being possible and may work for other non-browser > apps too. You'll need to give google a mobile number for account > recovery and the like too. Yes, that should work too (see the first mail in this thread). But ... what stopped me and made me think is: what if I prefer to have access to "my" mail without giving up a mobile or not so mobile telephone number? I am happier if this is made possible for everybody who prefer so via a free application. Not sure gmailieer is going to work, not until I try it. Bu it looks promising. Cheers, Loredana
Re: webmail and email from command line
First of all, I wish to thank all of you who shared their experience. Be reassured I am taking any constructive suggestion into serious account and exploring more. Then: On Fri, Aug 16, 2019 at 2:03 AM Celejar wrote: > > On Wed, 14 Aug 2019 16:24:49 +000 > loredana wrote: > > secure applications, this is likely not to be a viable solution (it > > seems that google is going to forbit less secure application access > > starting November first of this year and it is already a pain to use > > it now). > > What is your source for Google's plans, and how is it already a pain? I am following the google development on this issue, but I got the date from the mu4e mailing list. I'l post the link, if I can find it again (remember, I am almost blind and even replying to email is, at the moment, really slow and difficult). > have been using getmail and sylpheed with several Google mail accounts > for years, and it seemed pretty straightforward - just set the "allow > less secure apps" option, and then configure POP3 / SMTP normally. In the email that started this thread, I tried to make clear that this is something happening "now". I use the internet for crossing oceans quickly since bitnet and I remember whet google was born as google."org". I am myself a long term gmail user and this is why I carefully look after main changes. The way email clients will authenticate to gmail is drfinitely one of them and is going to affect us for sure. I may be able to be more responsive once I find a good way of avoiding webmail. Meanwhile, here is the best I could find toward a possible solution that may help avoid the OAUTH2 authorization issue by complying with it. You need debian buster as a minimum, then look at the gmailieer package. It seems to be oauth2 enabled and therefore be able to access gmail and possibly other mail providers. I still have to test it. If you try it, be careful because it requires notmuch and notmuch is in the less secure apps list, so you have to allow less secure apps first, I guess, and hopefully be able to set it off/on as you like again (if you can, this will probably get a feeling about the pain ...). gmailieer is GPLv3+ and in debian. IMHO this these are two good things. The debian package page: https://packages.debian.org/search?keywords=gmailieer It seems that mbsync (isink) is on itw long way to become OAUTH2 enableb, too, as possibly other applications. It is a matter of timen and the free software community will catch up, as usual. I don't think the authentication issue is going to affect webmail users for a while. Loredana
Re: webmail and email from command line
On Wed, Aug 14, 2019 at 3:00 PM wrote: > [...] > Note that what Google calls there "less secure applications" is just > marketing mumbo-jumbo to nudge users off their non-browser clients. I know. But knowing it, and perhaps blaiming it, is not a solution. > Is changing mail provider an option for you? Yes, not an easy one, 'though. Image writing to all your contacts, human and automatic ones, and convince them to write to a new email address. Moreover, is this going to be a solution? Which provider would you suggest? Cheers, Loredana > > Cheers > -- tomás
webmail and email from command line
Greetings, I posted the following message to debian-accessibility and I post it again suggested. Briefly, I am a "long term" debian user (since debian potato) and I am almost but not completely blind. This happened recently, so I am still adapting to the new situation. Please keep this in mind, as it is the primary problem for us. I find increasily difficult and error prone to read/send email via a browser and would like to either use emacs (preferred, now that it talks, thanks to speechd-el) or the command line. 'Though I managed to send mail to my gmail account by allowing less secure applications, this is likely not to be a viable solution (it seems that google is going to forbit less secure application access starting November first of this year and it is already a pain to use it now). Two factor authentication may well be the only solution for desktop users in a couple of months time. Your Institution willl have somebody solving this issue for you, but at home normal users who prefer to avoid using a browser for email are on their own. Once the authentication issue is solved, then any client (not only a browser) should be able to read/send mail, making life for me and possibly other visually impaired people easier. Here is what I plan to do: * use mbsync to fetch mail locally * use any tool to read/edit mail locally (I will use emacs and mu4e, but at this point any editor and mail agent than can work with mail locally should be just fine) * configure exim to deal with gmail authentication to read and send mail via smtp gmail server frpm localhost. Is this a reasonable approach? Any comment or suggestion? Any other way of dealing with email locally, without a browser, and to use the network only for reading/sending mail with an imap/smtp server acceptable authorization? BTW, swacks is in debian and it is a very nice tool to test smtp connections from the command line: swaks --tls --auth --to @gmail.com --server smtp.gmail.com Be careful with spoken passwords .. Loredana
