Conversation
ljs@mastodonapp.uk

Lorenzo Stoakes

neomutt crashed so I have to wait for 22k+ headers to be read at 10 a second and lore is still broken so yeah.

Email development is fun...

4
0
0
kdave

kdave

Reply to @ljs@mastodonapp.uk
@ljs neomutt can be configured to store header cache, set header_cache=path
1
0
2
paulmckrcu

Paul E. McKenney

Reply to @ljs@mastodonapp.uk
@ljs I use fetchmail. Hey, I have the hair color for it!
0
0
3
mathieu@fosstodon.org

Mathieu

Reply to @ljs@mastodonapp.uk
Edited yesterday

@ljs isn't one of the selling point of neomutt to have kyoto cabinet as a cache backend and multithread support?! wtf
(regular mutt user here with slow as hell import :D)

2
0
0
ljs@mastodonapp.uk

Lorenzo Stoakes

Reply to @kdave

let me try that thanks!

1
0
0
ljs@mastodonapp.uk

Lorenzo Stoakes

Reply to @ljs@mastodonapp.uk

seems to work ohhhh

0
0
0
ljs@mastodonapp.uk

Lorenzo Stoakes

Reply to @mathieu@fosstodon.org

@mathieu yeah maybe I just didn't set the bloody config as per @kdave 's advice :)

0
0
0
monsieuricon

K. Ryabitsev-Prime 🍁

Reply to @ljs@mastodonapp.uk
@ljs I just banned 300 subnets that an aggressive crawler was using to hit us with a fake b4 user-agent. Hopefully, that improves things for you.
1
0
4
monsieuricon

K. Ryabitsev-Prime 🍁

Reply to @monsieuricon
@ljs unless, of course, you're on one of those 300 subnets. :)
1
0
2
liskin@genserver.social

Tomáš Janoušek

Reply to @mathieu@fosstodon.org
@mathieu @ljs I think both neomutt and regular mutt have header (and body!) cache. The only usecase I still have for neomutt is NNTP - obviously I don't subscribe to LKML so NNTP was how I accessed it back when there wasn't that other thing that gets it from public inbox or whatever.
0
0
0
ljs@mastodonapp.uk

Lorenzo Stoakes

Reply to @monsieuricon

@monsieuricon thanks! :)

I hope not ;)

I do need to figure out how to get lei to cache properly though, not sure if doing something wrong.

But now I figured out how to get neomutt to generally cache can use work mail as backup!

0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: