Cameron Simpson wrote:
On 14Dec2018 11:40, Victor Sudakov wrote:
Kurt, once you've mentioned it. How do I create a maildir folder from
within mutt if my default $mbox_type is mbox?
When I want to create a new folder "foo", I tag some messages and save
them to =foo, mutt asks whether to create
Tim Chase wrote:
On 2018-12-13 22:05, Patrick Shanahan wrote:
mbox still serves my needs and has never failed me. why would I
want to invest time and effort to change to something (anything)
else? maildir does not "work better" as I can see.
Perhaps you're not putting strains on mbox that
On 12/13/18 10:05 PM, Patrick Shanahan wrote:
mbox still serves my needs and has never failed me. why would I want to
invest time and effort to change to something (anything) else? maildir
does not "work better" as I can see.
If mbox works for the way you use it, there's no need to change.
On Fri, Dec 14, 2018 at 07:37:28AM -0600, Tim Chase wrote:
> On 2018-12-13 22:05, Patrick Shanahan wrote:
> > mbox still serves my needs and has never failed me. why would I
> > want to invest time and effort to change to something (anything)
> > else? maildir does not "work better" as I can
On Thursday, December 13, 2018 at 17:56:51 -0600, Derek Martin wrote:
The majority of the community said nothing at all, which
suggests (as I suggested) that most people don't actually give
a $#@! about this, as well they shouldn't. I'll note that in
response to Kevin's query, two people (Ariis
On 2018-12-13 22:05, Patrick Shanahan wrote:
> mbox still serves my needs and has never failed me. why would I
> want to invest time and effort to change to something (anything)
> else? maildir does not "work better" as I can see.
Perhaps you're not putting strains on mbox that others have.
Derek Martin wrote:
[dd]
What we really need is some sort of a database back end anyway, so we
can have reasonable virtual folders. :)
I hope you are kidding. Microsoft Exchange went this way. I don't like
the result.
I don't necessarily mean
storing the message in the database... the
Ian Zimmerman wrote:
On 2018-12-14 11:27, Victor Sudakov wrote:
> DEFAULT=/path/to/maildir/ procmail /dev/null
>
> will work (but I try to avoid procmail for data-critical tasks).
May I ask why? procmail has been in my ~/.forward for two decades,
with lots of rules, and I've not seen any
On 13.12.18 13:05, Kurt Hackenberg wrote:
>
> You may want to preserve message attributes -- things like, this message has
> been read, this message has been replied to, this message has been flagged,
> this message has been assigned the keyword "blorgh". Mail delivery agents,
> including
Ian Zimmerman wrote:
On 2018-12-13 13:05, Kurt Hackenberg wrote:
Whether to use IMAP at all -- well, one reason to use IMAP, even if
you have direct access to the mail files, is so you can use any mail
reader, not just one. When various mail readers read and write files
directly, even file
On Fri, Dec 14, 2018 at 11:43:17AM +1100, Cameron Simpson wrote:
> On 13Dec2018 18:26, derek martin wrote:
> >Maildir + header caching improves the case for Maildir in some, but
> >not all, cases (and if mbox is also supported by header caching
> >now, that goes out the window, but I don't recall
On 2018-12-13, Derek Martin wrote:
> On Wed, Dec 12, 2018 at 01:18:04PM +1100, Erik Christiansen wrote:
>
>> Then the thoughts of the majority of the community bear
>> consideration, especially when based on reason.
>
> The majority of the community said nothing at all, which suggests (as
> I
I got cured of mbox when I had malware infect my spool file. There were
a few thousand messages I wanted to go through in that mbox but clamav
quarrantined the whole mbox file and I couldn't read the messages that
weren't infected and never learned which of the messages actually got
infected
On Tuesday, December 11, 2018 at 17:48:14 -0600, Derek Martin wrote:
On Tue, Dec 11, 2018 at 09:08:16PM +0100, Mihai T. Lazarescu wrote:
> >If a reply is sent to a message that has destination fields, it
> >is often desirable to send a copy of the reply to all of the
> >recipients
On Fri, Dec 14, 2018 at 03:20:57PM +0100, Mihai Lazarescu wrote:
> On Thursday, December 13, 2018 at 17:56:51 -0600, Derek Martin wrote:
>
> >The majority of the community said nothing at all, which
> >suggests (as I suggested) that most people don't actually give
> >a $#@! about this, as well
On 2018-12-14 11:27, Victor Sudakov wrote:
> > DEFAULT=/path/to/maildir/ procmail /dev/null
> >
> > will work (but I try to avoid procmail for data-critical tasks).
>
> May I ask why? procmail has been in my ~/.forward for two decades,
> with lots of rules, and I've not seen any problems from
On Fri, Dec 14, 2018 at 09:06:13AM -0800, Ian Zimmerman wrote:
> Yes, that's certainly a reason. Too bad; in my case I and the few other
> users all agree that email (a relatively slow and deliberate mode of
> communication on a modern scale) doesn't mix well with "on the road",
> unlike SMS.
On 2018-12-13 13:05, Kurt Hackenberg wrote:
> Whether to use IMAP at all -- well, one reason to use IMAP, even if
> you have direct access to the mail files, is so you can use any mail
> reader, not just one. When various mail readers read and write files
> directly, even file formats that are
On Thu, Dec 13, 2018 at 12:38:42PM -0500, Kurt Hackenberg wrote:
> On 12/13/18 11:15 AM, Victor Sudakov wrote:
>
> >Dan Ritter wrote:
> >>That doesn't happen in Maildir storage. Is it reasonable to
> >>switch from mbox to maildir?
> >
> >An interesting idea!
>
> In my opinion, it's always a good
On 2018-12-13 17:56, Derek Martin wrote:
> The majority of the community said nothing at all, which suggests (as
> I suggested) that most people don't actually give a $#@! about this,
> as well they shouldn't. I'll note that in response to Kevin's query,
> two people (Ariis and Christiansen)
On Thu, Dec 13, 2018 at 05:56:51PM -0600, Derek Martin wrote:
The majority of the community said nothing at all, which suggests (as
I suggested) that most people don't actually give a $#@! about this,
as well they shouldn't.
I'm pretty happy with the turnout. I've re-read the discussion and
21 matches
Mail list logo
