From: Joel Reicher <joel.reicher@gmail.com>
To: David Masterson <dsmasterson@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Gnus IMAP Qs: catch-up vs delete vs expire & "gnus-expire" tag ?
Date: Sat, 14 Dec 2024 23:04:23 +1100 [thread overview]
Message-ID: <86pllulbco.fsf@gmail.com> (raw)
In-Reply-To: <CAD8J8ntgf3kQh+CgAfWG4NOosyw40OpC+sfj9+p3fKK=OnUHdQ@mail.gmail.com> (David Masterson's message of "Sat, 14 Dec 2024 00:43:49 -0800")
David Masterson <dsmasterson@gmail.com> writes:
> I have a number of questions...
>
> I've been trying to set up my mailing list environment using
> Gnus with IMAP/SMTP via zohomail.com. I can read gnu.org
> mailing lists via IMAP fine.
>
> 1. SMTP thru zohomail.com to gnu.org gets bounced as
> "Undeliverable" due to a "550 - bad domain" error. Zoho support
> says the email looks fine. I've been trying to get an answer
> from sysadmin@fsf.org (email sent from my gmail account) for
> several days, but no reply. Anyone seen anything like this?
If you think Gnus/Message is responsible (i.e. sending with some
other client is fine), then a faulty From: address is all I can
think it might be.
> 2. Due to limited space in a free account on zohomail.com, I
> want to clean up old mail on both my system and the server. I
> assumed the way to do that was (mostly) by "catchup", but that
> just marks all the mails in the summary buffer as read. How do
> you delete old email?
There are a few ways, but you might want to start by reading
(info "(gnus) Expiring Mail")
You don't have to use expiry - the important part is what is done
when Gnus actions the expiry, and this can be done without the
expiry process - but personally I quite like it because setting
marks is fast, and the actual deletion (server command) is done in
bulk. It feels a lot like commit vs push in git to me.
> 3. I thought 'expire' was the way to delete, but the manual
> implies that expired email can be deleted by Gnus at some future
> time. How is that controlled?
That's covered by the info page above. I use nnmail-expiry-wait
immediate.
> 4. I found that the expired email wound up being tagged with
> "gnus-expire" on the IMAP server. Is there an assumption that
> the IMAP server will delete emails tagged with "gnus-expire"?
> If so, how does that work?
No. Expiry is actioned by Gnus. If you want to skip it completely
(which I do at the moment in certain situations) you can do B DEL.
> 5. Is this documented in the Gnus manual? At least the
> assumptions of how the IMAP server should work around "deleting
> emails".
I think you will find there's no working around; it's just that
Gnus tries to unify the news and mail experience as sensibly as
possible, which is a little nontrivial since deletion doesn't
really exist for news. This is also not specific to IMAP.
A (possibly unnecessary) word of warning: the IMAP expunge
operation has nothing to do with any of this, but it's easy to
think it does.
Cheers,
- Joel
next prev parent reply other threads:[~2024-12-14 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 8:43 Gnus IMAP Qs: catch-up vs delete vs expire & "gnus-expire" tag ? David Masterson
2024-12-14 12:04 ` Joel Reicher [this message]
2024-12-17 4:24 ` David Masterson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86pllulbco.fsf@gmail.com \
--to=joel.reicher@gmail.com \
--cc=dsmasterson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).