Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.emacs.help > #60679 > unrolled thread

10, 15 yrs ago this newsgroup was *much* larger. What happened?

Back to article view | Back to gnu.emacs.help

Contents

  10, 15 yrs ago this newsgroup was *much* larger.  What happened? dkcombs@panix.com (dkcombs) - 2023-03-26 23:30 +0000
    Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Dan Espen <dan1espen@gmail.com> - 2023-03-26 21:26 -0400
      Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Richard Smith <null@void.com> - 2023-03-27 10:13 +0100
        Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? dkcombs@panix.com (dkcombs) - 2023-03-27 15:08 +0000
          Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Anssi Saari <as@sci.fi> - 2023-03-28 12:48 +0300
            Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? dkcombs@panix.com (dkcombs) - 2023-03-28 15:20 +0000
              Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Matto Fransen <mattof@sdf.org> - 2023-03-28 18:39 +0200
              Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Anssi Saari <as@sci.fi> - 2023-03-31 09:21 +0300
          Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Axel Reichert <mail@axel-reichert.de> - 2023-03-30 19:07 +0200
            Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Richard Smith <null@void.com> - 2023-03-31 19:36 +0100
        Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Matto Fransen <mattof@sdf.org> - 2023-03-28 12:09 +0200
          Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? USEnet <jvromans@squirrel.nl> - 2023-03-28 17:35 +0200
            Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Richard Smith <null@void.com> - 2023-03-29 09:04 +0100
      Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Javier <invalid@invalid.invalid> - 2023-04-02 01:44 +0000
        Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Dan Espen <dan1espen@gmail.com> - 2023-04-01 21:49 -0400
          Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Javier <invalid@invalid.invalid> - 2023-04-02 18:25 +0000
            Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Dan Espen <dan1espen@gmail.com> - 2023-04-02 15:35 -0400
              Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Javier <invalid@invalid.invalid> - 2023-04-02 21:54 +0000
                Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Dan Espen <dan1espen@gmail.com> - 2023-04-03 09:49 -0400
                  Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Javier <invalid@invalid.invalid> - 2023-04-03 15:18 +0000
                  Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? HASM <hasm@example.invalid> - 2023-04-03 13:36 -0700
                    Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Dan Espen <dan1espen@gmail.com> - 2023-04-03 19:42 -0400
                  Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-03 23:27 +0100
                    Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Dan Espen <dan1espen@gmail.com> - 2023-04-03 19:37 -0400
                      Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-04 02:31 +0100
                      Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? HASM <hasm@example.invalid> - 2023-04-04 09:59 -0700
                        Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-05 01:35 +0100
                          Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? HASM <hasm@example.invalid> - 2023-04-05 08:29 -0700
                            Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-05 21:43 +0100
                              Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Dan Espen <dan1espen@gmail.com> - 2023-04-05 21:45 -0400
                                Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? HASM <hasm@example.invalid> - 2023-04-06 06:17 -0700
                                  Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? USEnet <jvromans@squirrel.nl> - 2023-04-06 16:21 +0200
                                gmail imap setup Javier <invalid@invalid.invalid> - 2023-04-06 20:09 +0000
                              Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? HASM <hasm@example.invalid> - 2023-04-06 06:13 -0700
                                Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2023-04-06 17:20 +0100
                            Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Dan Espen <dan1espen@gmail.com> - 2023-04-05 21:50 -0400
        Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Dan Espen <dan1espen@gmail.com> - 2023-04-01 21:57 -0400
          Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? "Loris Bennett" <loris.bennett@fu-berlin.de> - 2023-04-03 08:26 +0200
    Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? "Szczezuja.space" <szczezuja@sdf.org> - 2023-03-30 17:06 +0000
      Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? Cecil Westerhof <Cecil@decebal.nl> - 2023-03-31 08:59 +0200
    Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? steve <sgonedes1977@gmail.com> - 2024-04-19 17:33 -0400
      Re: 10, 15 yrs ago this newsgroup was *much* larger.  What happened? HASM <hasm@example.invalid> - 2024-04-20 06:54 -0700
        Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Richard Owlett <rowlett@access.net> - 2024-06-12 10:10 -0500
          Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Julieta Shem <jshem@yaxenu.org> - 2024-06-12 20:24 -0300
            Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Richard Owlett <rowlett@access.net> - 2024-06-13 06:28 -0500
            Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Richard Smith <null@void.com> - 2024-07-03 13:20 +0100
          Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? steve g <sgonedes1977@gmail.com> - 2024-08-09 17:22 -0400
            Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? yeti <yeti@tilde.institute> - 2024-08-09 23:00 +0042
              Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Richard Owlett <rowlett@access.net> - 2024-08-10 06:54 -0500
                Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? steve g <sgonedes1977@gmail.com> - 2024-08-11 18:24 -0400
              Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? steve g <sgonedes1977@gmail.com> - 2024-08-11 18:19 -0400
            Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Rust Buckett <rust@fakedomain.nope> - 2025-02-06 21:40 -0500
              Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Richmond <dnomhcir@gmx.com> - 2025-02-07 14:20 +0000
                Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Salvador Mirzo <smirzo@example.com> - 2025-02-07 22:11 -0300
                  Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? "W. Greenhouse" <wgreenhouse@tilde.club> - 2025-02-10 16:20 +0000
                    Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Salvador Mirzo <smirzo@example.com> - 2025-02-11 22:18 -0300
                      Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? "W. Greenhouse" <wgreenhouse@tilde.club> - 2025-02-14 00:25 +0000
                        Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> - 2025-02-14 11:43 +0200
                          Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Salvador Mirzo <smirzo@example.com> - 2025-02-14 21:05 -0300
                          Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Rust Buckett <rust@fakedomain.nope> - 2025-04-01 21:34 -0400
                            Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Ethan Carter <ec1828@somewhere.edu> - 2025-04-05 04:01 -0300
                            Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? steve g <sgonedes1977@gmail.com> - 2026-03-31 16:35 -0400
                        Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Salvador Mirzo <smirzo@example.com> - 2025-02-14 21:04 -0300
              Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? steve g <sgonedes1977@gmail.com> - 2026-03-29 19:49 -0400
                Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Mekeor Melire <mekeor@posteo.de> - 2026-04-01 00:10 +0200
                  Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? steve g <sgonedes1977@gmail.com> - 2026-04-01 15:31 -0400
                    Re: 10, 15 yrs ago this newsgroup was *much* larger. What happened? Mekeor Melire <mekeor@posteo.de> - 2026-04-01 23:40 +0200

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

#60724

Dan Espen <dan1espen@gmail.com> writes:

> Well, that brings up another GNUS issue.
> Ever since GMAIL changed their IMAP support to require authentication I
> haven't been able to send email directly off my box.

My incoming mail comes through google, outgoing email goes through some
other (paid) gateway.

I used to do in and out through google, but when they changed a few
conditions on the free legacy workspace accounts I had to switch.

I don't use gnus for email thus I'm not sure, I use mh-e which, in my
case, uses postfix to send email out.  It was not too difficult to send
through google using OAUTH2.

Not that I have a @my_domain address on google, not sure whether @gmail
addresses are just as "easy".

-- HASM

[toc] | [prev] | [next] | [standalone]

#60727

HASM <hasm@example.invalid> writes:

> Dan Espen <dan1espen@gmail.com> writes:
>
>> Well, that brings up another GNUS issue.
>> Ever since GMAIL changed their IMAP support to require authentication I
>> haven't been able to send email directly off my box.
>
> My incoming mail comes through google, outgoing email goes through some
> other (paid) gateway.
>
> I used to do in and out through google, but when they changed a few
> conditions on the free legacy workspace accounts I had to switch.
>
> I don't use gnus for email thus I'm not sure, I use mh-e which, in my
> case, uses postfix to send email out.  It was not too difficult to send
> through google using OAUTH2.

I used MH-E for many years.  I think it uses the same underlying
mechanisms for sending mail that GNUS uses.

I'm not sure what OAUTH2 is or if it's sufficient to work with gmail now.
I know that my IMAP configuration stopped working.

-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]

#60725

Dan Espen <dan1espen@gmail.com> writes:

> Javier <invalid@invalid.invalid> writes:
>
>> Dan Espen <dan1espen@gmail.com> wrote:
>>> As you indicated, http://news.gmane.io says it's archive only.
>>> 
>>> If I can't post, I don't think I'll bother.
>>> I did put your info into my gnus.el in case I change my mind.
>>
>> It's a bit unconvenient, but not that bad.  The Followup to NNTP
>> is not going to work, but if you reply by email the generated subject
>> and references headers are valid.  You just need to send by email
>> changing the 'To:' header
>>
>> To: help-gnu-emacs@gnu.org
>>
>> Possibly it can be automated for that particular gmane.emacs.help
>> newsgroup in some of the gnus-*-hook variables.
>
> Well, that brings up another GNUS issue.
> Ever since GMAIL changed their IMAP support to require authentication I
> haven't been able to send email directly off my box.

Don't you use SMTP for sending?

-- 
Ben.

[toc] | [prev] | [next] | [standalone]

#60726

Ben Bacarisse <ben.usenet@bsb.me.uk> writes:

> Dan Espen <dan1espen@gmail.com> writes:
>
>> Javier <invalid@invalid.invalid> writes:
>>
>>> Dan Espen <dan1espen@gmail.com> wrote:
>>>> As you indicated, http://news.gmane.io says it's archive only.
>>>> 
>>>> If I can't post, I don't think I'll bother.
>>>> I did put your info into my gnus.el in case I change my mind.
>>>
>>> It's a bit unconvenient, but not that bad.  The Followup to NNTP
>>> is not going to work, but if you reply by email the generated subject
>>> and references headers are valid.  You just need to send by email
>>> changing the 'To:' header
>>>
>>> To: help-gnu-emacs@gnu.org
>>>
>>> Possibly it can be automated for that particular gmane.emacs.help
>>> newsgroup in some of the gnus-*-hook variables.
>>
>> Well, that brings up another GNUS issue.
>> Ever since GMAIL changed their IMAP support to require authentication I
>> haven't been able to send email directly off my box.
>
> Don't you use SMTP for sending?

I don't think SMTP is sufficient to send through Gmail.  I'm not an
expert on email.

I used to use IMAP for inbound and outbound email with GNUS.
A while back Google changed their IMAP interface to require
some kind of authorization that I have yet to figure out.
It looked like you had to go to Google to register your email app,
then generate some kind of key which lasts for a while then
you have to change it.

-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]

#60728

Dan Espen <dan1espen@gmail.com> writes:

> Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
>
>> Dan Espen <dan1espen@gmail.com> writes:
>>
>>> Javier <invalid@invalid.invalid> writes:
>>>
>>>> Dan Espen <dan1espen@gmail.com> wrote:
>>>>> As you indicated, http://news.gmane.io says it's archive only.
>>>>> 
>>>>> If I can't post, I don't think I'll bother.
>>>>> I did put your info into my gnus.el in case I change my mind.
>>>>
>>>> It's a bit unconvenient, but not that bad.  The Followup to NNTP
>>>> is not going to work, but if you reply by email the generated subject
>>>> and references headers are valid.  You just need to send by email
>>>> changing the 'To:' header
>>>>
>>>> To: help-gnu-emacs@gnu.org
>>>>
>>>> Possibly it can be automated for that particular gmane.emacs.help
>>>> newsgroup in some of the gnus-*-hook variables.
>>>
>>> Well, that brings up another GNUS issue.
>>> Ever since GMAIL changed their IMAP support to require authentication I
>>> haven't been able to send email directly off my box.
>>
>> Don't you use SMTP for sending?
>
> I don't think SMTP is sufficient to send through Gmail.  I'm not an
> expert on email.

That's how I do it.

> I used to use IMAP for inbound and outbound email with GNUS.
> A while back Google changed their IMAP interface to require
> some kind of authorization that I have yet to figure out.
> It looked like you had to go to Google to register your email app,
> then generate some kind of key which lasts for a while then
> you have to change it.

That will, most likely, also work.

-- 
Ben.

[toc] | [prev] | [next] | [standalone]

#60729

> I don't think SMTP is sufficient to send through Gmail.  I'm not an
> expert on email.

To get email from gmail I use getmail
  https://getmail6.org/
not that hard to setup.

To send email to gmail it's a lot more involved.
With postfix I a few entries are needed in main.cf.
Password needs to be entered in a postfix sasl password map.
The password map needs to be updated periodically, as the keys expired after some time (1 hour?).
I do this via cron and python Oauth2 based script.

-- HASM

[toc] | [prev] | [next] | [standalone]

#60730

HASM <hasm@example.invalid> writes:

>> I don't think SMTP is sufficient to send through Gmail.  I'm not an
>> expert on email.
>
> To get email from gmail I use getmail
>   https://getmail6.org/
> not that hard to setup.
>
> To send email to gmail it's a lot more involved.
> With postfix I a few entries are needed in main.cf.
> Password needs to be entered in a postfix sasl password map.

This is how I send mail.  Postfix chooses the account based on the
address in the mail being sent.  Since I use various email clients, this
simplifies them all.  Everything is sent via a local "sendmail"
compatible MTA.

> The password map needs to be updated periodically, as the keys expired
> after some time (1 hour?).  I do this via cron and python Oauth2 based
> script.

But I don't have to do this.

-- 
Ben.

[toc] | [prev] | [next] | [standalone]

#60732

ben> Postfix chooses the account based on the address in the mail being
ben> sent.

I do this too, but that's a different subject.  For me postfix not only
chooses an account to send "from" but also the relay to use with "to".

>> The password map needs to be updated periodically, as the keys expire

> But I don't have to do this.

Guess I have to update my setup.  As described, e.g. here:

  https://mmogilvi.users.sourceforge.net/software/oauthbearer.html

it seems that both fetchmail and postfix can now renew the oauth2 token,
but this wasn't the case when I implemented my solution. At the time it
was only possible by patching fetchmail (and maybe postfix), which I
didn't want to do and maintain.

-- HASM

[toc] | [prev] | [next] | [standalone]

#60733

HASM <hasm@example.invalid> writes:

> ben> Postfix chooses the account based on the address in the mail being
> ben> sent.
>
> I do this too, but that's a different subject.  For me postfix not only
> chooses an account to send "from" but also the relay to use with "to".

Of course.  I'm not sure what you thought I meant.   Once postfix has
the mail, it relays it based on the from header.

>>> The password map needs to be updated periodically, as the keys expire
>
>> But I don't have to do this.
>
> Guess I have to update my setup.  As described, e.g. here:
>
>   https://mmogilvi.users.sourceforge.net/software/oauthbearer.html

I don't do it that way.  I went the route described as step 1 in that
document:

  1. Configure your gmail (or equivalent) account to enable IMAP and/or
  POP access. If it will let you set up an "application password"
  instead of OAUTH2, that would generally be a whole lot simpler and
  arguably just as secure.

but for SMTP sending.

Thanks for the link.  One day I am sure I will be forced to do it the
hard way.

> it seems that both fetchmail and postfix can now renew the oauth2 token,
> but this wasn't the case when I implemented my solution. At the time it
> was only possible by patching fetchmail (and maybe postfix), which I
> didn't want to do and maintain.

When I did it, there was no oauth2 (as far as I can recall) and I've
used the same setup, unchanged, since then.

-- 
Ben.

[toc] | [prev] | [next] | [standalone]

#60734

Ben Bacarisse <ben.usenet@bsb.me.uk> writes:

> HASM <hasm@example.invalid> writes:
>
>> ben> Postfix chooses the account based on the address in the mail being
>> ben> sent.
>>
>> I do this too, but that's a different subject.  For me postfix not only
>> chooses an account to send "from" but also the relay to use with "to".
>
> Of course.  I'm not sure what you thought I meant.   Once postfix has
> the mail, it relays it based on the from header.
>
>>>> The password map needs to be updated periodically, as the keys expire
>>
>>> But I don't have to do this.
>>
>> Guess I have to update my setup.  As described, e.g. here:
>>
>>   https://mmogilvi.users.sourceforge.net/software/oauthbearer.html
>
> I don't do it that way.  I went the route described as step 1 in that
> document:
>
>   1. Configure your gmail (or equivalent) account to enable IMAP and/or
>   POP access. If it will let you set up an "application password"
>   instead of OAUTH2, that would generally be a whole lot simpler and
>   arguably just as secure.
>
> but for SMTP sending.
>
> Thanks for the link.  One day I am sure I will be forced to do it the
> hard way.
>
>> it seems that both fetchmail and postfix can now renew the oauth2 token,
>> but this wasn't the case when I implemented my solution. At the time it
>> was only possible by patching fetchmail (and maybe postfix), which I
>> didn't want to do and maintain.
>
> When I did it, there was no oauth2 (as far as I can recall) and I've
> used the same setup, unchanged, since then.

I don't see any "application password" option.


-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]

#60737

dan> I don't see any "application password" option.

See my reply to Ben, and this Google page

  https://support.google.com/accounts/answer/185833?hl=en#zippy=

Under Create & Use App Passwords, point 3, there are four cases that
restrict the use App Passwords.

 a. 2-Step Verification is not set up for your account.
 b. 2-Step Verification is only set up for security keys.
 c. Your account is through work, school, or other organization.
 d. You turned on Advanced Protection.

If you are restricted by a, b or d cases, you may be able to change it,
if by the c case, you're out of luck.

-- HASM

[toc] | [prev] | [next] | [standalone]

#60738

10, 15 yrs ago it was customary to change the article title when the topic
derailed...

[toc] | [prev] | [next] | [standalone]

#60740 — gmail imap setup

Dan Espen <dan1espen@gmail.com> wrote:
> 
> I don't see any "application password" option.

You need to go to https://myaccount.google.com

Enable 2 step verification in

https://myaccount.google.com/security?gar=1

and app passwords should appear at the bottom of this page.

https://myaccount.google.com/signinoptions/two-step-verification?gar=1

In any case, Google doesn't like app-passwords, and they might disable
them in favor of Oauth.  In my experienced bothering with Oauth2 is
too much hassle. At that point the best is to leave google completely
and go to something like protonmail.

Choosing "free as in beer" is never a good idea.

[toc] | [prev] | [next] | [standalone]

#60736

> I went the route described as step 1 in that document:
>
>   1. ... If it will let you set up an "application password" instead of OAUTH2

In Google's "Sign in with App Passwords" help page, they say:

 Under "Signing in to Google," select App Passwords.
 You may need to sign in.
 If you don’t have this option, it might be because:
   ...
   Your account is through work, school, or other organization.

and I fall under the "other organization", i.e. I don't have a
@gmail.com address, but a @mydomain.tl address, hosted on gmail.


> One day I am sure I will be forced to do it the hard way.

I was forced and it took me a while to do it back then.  Hopefully
Google warned with sufficient advance for me to figure one way out.

-- HASM

[toc] | [prev] | [next] | [standalone]

#60739

HASM <hasm@example.invalid> writes:

>> I went the route described as step 1 in that document:
>>
>>   1. ... If it will let you set up an "application password" instead of OAUTH2
>
> In Google's "Sign in with App Passwords" help page, they say:
>
>  Under "Signing in to Google," select App Passwords.
>  You may need to sign in.
>  If you don’t have this option, it might be because:
>    ...
>    Your account is through work, school, or other organization.
>
> and I fall under the "other organization", i.e. I don't have a
> @gmail.com address, but a @mydomain.tl address, hosted on gmail.

Ah, I see.

-- 
Ben.

[toc] | [prev] | [next] | [standalone]

#60735

HASM <hasm@example.invalid> writes:

> ben> Postfix chooses the account based on the address in the mail being
> ben> sent.
>
> I do this too, but that's a different subject.  For me postfix not only
> chooses an account to send "from" but also the relay to use with "to".
>
>>> The password map needs to be updated periodically, as the keys expire
>
>> But I don't have to do this.
>
> Guess I have to update my setup.  As described, e.g. here:
>
>   https://mmogilvi.users.sourceforge.net/software/oauthbearer.html
>
> it seems that both fetchmail and postfix can now renew the oauth2 token,
> but this wasn't the case when I implemented my solution. At the time it
> was only possible by patching fetchmail (and maybe postfix), which I
> didn't want to do and maintain.

Thanks for this, this looks like what I've been looking for.

I have a python biff type app using imaplib that tells me I have mail
and who it's from.
I think those instructions may be clear enough for me to get that
working too.


-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]

#60713

Javier <invalid@invalid.invalid> writes:

> Dan Espen <dan1espen@gmail.com> wrote:
>> 
>> I'm guessing the link from email to usenet is broken.  I was able to
>> access the mailing list and the mailing list has activity.
>> 
>
> I think the mailing list is still visible through NNTP, but only in
> the news.gmane.org server, and that needs registering.

According to this 2020 thread
https://lars.ingebrigtsen.no/2020/01/06/whatever-happened-to-news-gmane-org/
it's now
news.gmane.io

I didn't see instructions for how to set up GNUS though.

-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]

#60719

Dan Espen <dan1espen@gmail.com> writes:

> Javier <invalid@invalid.invalid> writes:
>
>> Dan Espen <dan1espen@gmail.com> wrote:
>>> 
>>> I'm guessing the link from email to usenet is broken.  I was able to
>>> access the mailing list and the mailing list has activity.
>>> 
>>
>> I think the mailing list is still visible through NNTP, but only in
>> the news.gmane.org server, and that needs registering.
>
> According to this 2020 thread
> https://lars.ingebrigtsen.no/2020/01/06/whatever-happened-to-news-gmane-org/
> it's now
> news.gmane.io
>
> I didn't see instructions for how to set up GNUS though.

I have the following:

    (setq gnus-select-method '(nntp "news.fu-berlin.de"))
    (setq gnus-secondary-select-methods
	  (quote
	   ((nnimap "main"
		    (nnir-search-engine imap)
		    (remove-prefix "nnimap")
		    (nnimap-address "mail.zedat.fu-berlin.de")
		    (nnimap-record-commands t)
		    (nnimap-inbox INBOX))
	    (nntp "gmane"
		  (nntp-address "news.gmane.io")
		  (remove-prefix nntp))
	    (nntp "fu_news"
		  (nntp-address "news.fu-berlin.de")
		  (remove-prefix nntp))
	    )))

Cheers,

Loris

-- 
This signature is currently under constuction.

[toc] | [prev] | [next] | [standalone]

#60704

On 2023-03-26, dkcombs <dkcombs@panix.com> wrote:
> Subject line says it all.  Has emacs usage gone down?

I am rather new in the emacs world (less than a year) and I see several
people around me (especially on Gophersphere and Geminispace) where it's
discussed emacs. So probably new users aren't that rare. My observations
may of course be unrepresentative. 

-- 
  .-=-. Szczezuja; on the small-net:
 (  S\ \ gemini://szczezuja.space/  -  gemlog & tinylog
  `--' / gopher://sdf.org:70/0/users/szczezuja/ - phlog

[toc] | [prev] | [next] | [standalone]

#60709

"Szczezuja.space" <szczezuja@sdf.org> writes:

> On 2023-03-26, dkcombs <dkcombs@panix.com> wrote:
>> Subject line says it all.  Has emacs usage gone down?
>
> I am rather new in the emacs world (less than a year) and I see several
> people around me (especially on Gophersphere and Geminispace) where it's
> discussed emacs. So probably new users aren't that rare. My observations
> may of course be unrepresentative. 

New users probably do not know that there is something like
newsgroups. :'-(

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

[toc] | [prev] | [next] | [standalone]

Page 2 of 4 — ← Prev page 1 [2] 3 4  Next page →

Back to top | Article view | gnu.emacs.help

csiph-web