I clicked around a bit to see what was still out there,and I fear that this type of access to gratis webmail is going the way of the dodo.

Not really, just the death of one-step authentication. I've been looking at workarounds and took the bold step of just f***ing googling it, which revealed this reddit thread. The poster describes the workaround for Auth 2.0. 2-step auth has to be authorized, so you're ok if you have a phone number to give to google:

Log into gmail

Click the user icon in the top-right corner and select "Manage your Go
+ogle Account"

Go to the security page (from the list at the left)

[This is necessary for the next step, but will stop your scripts from 
+logging into smtp with your regular password. This is sort of the poi
+nt of no return. Make sure you are ready to go all the way and update
+ all of your email-sending scripts before continuing.] Enable two-ste
+p authentication.

Once two-step authentication is enabled, go back to the security page.
+ There should now be a new section called "App Passwords". Select it.
+ You will probably be asked to log in again.

Generate a new app password. I put in "Mail" under "select app" and "O
+ther" under "select device," but I don't think any of the information
+ you put it matters.

It will give you a 16-character app password which will be shown in ye
+llow.

Have your scripts use this password to log into smtp instead of your r
+egular password and everything should work. It will not prompt you fo
+r 2-step verification.

After doing this, my scripts seem to work. I did not have to make any 
+other changes to the code other than substituting the app password fo
+r the original one. Hopefully it helps you too.

[download]

Gmailpocalypse this is not....

In reply to Re^3: sending an email from my rpi to my droplet [gmail workaround] by Aldebaran
in thread getting SMTP capability working by Aldebaran

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.