Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Difference between nnmail- and gnus- variables?
Date: Wed, 04 Aug 2021 10:59:30 -0700	[thread overview]
Message-ID: <874kc55bwd.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m24kc57iaa.fsf@codeisgreat.org>

Pankaj Jangid <pankaj@codeisgreat.org> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>>>> In OO terms, nnmail.el can be thought of as an abstract parent class for
>>>> all backends belonging to the "store messages as files on disk" type of
>>>> server. It provides settings and functions that are used in common by
>>>> nnml, nnmbox, nnmaildir, etc.
>>>
>>> This clarifies a lot of things for me. Especially, it is now clear that
>>> this won’t work in my case. Because I am using IMAP.
>>
>> nnimap mostly uses nnmail for its splitting functions, and it looks like
>> its expiry settings as well -- that's pretty much it.
>
> Ok. I got a little confused by "store messages as file on disk". Since
> IMAP backend is like nntp because mails are mostly controlled by the
> server. I thought you are referring to the backends which manages emails
> themselves.

IMAP is a little odd just because it's kind of in between: the server
handles message storage, but the user "owns" the mail in the sense that
they're allowed to split, move, expire, etc. So some of the nnmail stuff
is relevant (splitting), but not most of it. A "real" nnmail backend is
one that ends up calling `nnmail-get-new-mail'.



  reply	other threads:[~2021-08-04 18:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 11:26 Pankaj Jangid
2021-08-03 17:21 ` Eric Abrahamsen
2021-08-03 17:59   ` Pankaj Jangid
2021-08-03 18:04     ` Eric Abrahamsen
2021-08-04  7:58       ` Pankaj Jangid
2021-08-04 17:59         ` Eric Abrahamsen [this message]
2021-08-05  6:05           ` Pankaj Jangid

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874kc55bwd.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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 NNTP newsgroup(s).