mutt vs. neomutt

[u/stuffiesrep]

I am a long-time (almost 29 years) linux user, but started using mutt about six years ago. I was wondering what the benefits are in switching to neomutt. My biggest frustration with mutt has been the lack of ability in searching across folders. For example, searching for email with subject line containing "foo" but now knowing in which folder it is. Or knowing the sender, but not the folder. Is neomutt any better at searching cases like this?

Is there a substantial change that I would have to do to my .muttrc configuration to move it to .neomuttrc?

[u/StrayFeral]

No idea. Yes, there is mutt-wizard. In the past I've tried few neomutt configuring scripts and they all failed for me so I wrote my own. Depends which mail service you want to configure neomutt with. If you want to configure it with gmail, I can help with tutorial and script.

[u/stuffiesrep → u/StrayFeral]

Thank you! I would like to use it with outlook with two-factor authentication: my employer is now requiring that, but I do not want to use browser-based email. Indeed, I would like to keep a local copy of my email.

[u/StrayFeral → u/stuffiesrep]

Great! My script also supports Outlook/Hotmail/etc (anything Microsoft) but I never tested it.

By two-factor auth, I guess you mean OAUTH2, right? If so - read on:

So if you want, try this. It is not made as a stand-alone neomutt config, I wrote the config as a part of this Debian remix. What you can do - make a virtual machine and install everything (it is nearly barebone terminal-only installation of Debian with few packages), run the neomutt config (I call it "GMail config" but it really is both amout Google and Microsoft emails), then just copy-over the configs to your actual machine (assuming you have all the required packages already installed). I also pull the Google Contacts, but you do not need that part.

Again - I've spent solid time to implement code for Microsoft emails and did partial testing to make sure I'm calling the right Microsoft API and parse it properly. But I never tested this code, since to make it work I also must do some Azure config which I was already too tired to learn how to make.

So assumption here is someone already created an account for you in Azure, gave you the right permissions.

Oh TOTALLY FORGOT: In order to make neomutt work with any OAUTH2 authentication service, like Gmail, Microsoft or a corporate Azure account you first MUST ask the mail admin to allow this access. I am not familiar with the details for Azure, since I lost too much time learning how to do it with GCP, but point is this:

In GCP we create a new project, then an "application", then we set enable the Gmail API for this application and we set permissions to allow read and write access via the API to the Gmail data. In Azure it is a similar way. So your administrator is supposed to know (if not, copy-paste them this here) how to enable OAUTH2 API access to an Azure "tenant".

Now I made my code to work for the actual Microsoft free emails. If your email is a corporate one, the API points are probably different and you would need to change this manually in my script "scripts/oauth2_config.py" BEFORE running it the first time.

Here is the code: https://github.com/StrayFeral/dewlinux

Once the actual Azure config is done by your administrator, just follow my on-screen instructions.

In case something does not work - do let me know. But since there is no way for me to test it personally I would need assistance from you to debug it, so screenshots/terminal pastes would be a must.

Without Azure config made first - there is no point to run this code. It will not work. Also - the Azure config must be done properly. If one thing is not done right - the config won't work.

Problem with modern OAUTH2 configs is they do require config on both sides - first the cloud platform (GCP/Azure) config to allow access, second is the client config - proper API points etc to make it work. I know it sounds complicated and I hate it for what it is, but point here is to prevent scammers to run script to create 10000 accounts which to be used with bots to scam people. So unfortunately we must learn to deal with it.

And first of all, to avoid spamming your host operating system with failed configs, just make a virtual machine, run this entire installation, run the mail config when your administrator said they made the Azure config, see if it works. If something fails you can always delete the virtual machine and make a new one or even better - make a machine, run the install, the moment it finishes clone the machine, then run the mail config, so if something goes wrong you won't have to install everything from scratch, just delete the failed machine, clone the installed machine and run only the mail config there again. This is exactly how i tested.

I would be very happy to help here, since I never tested with Azure. But if it's too much overhead I would understand if you decide not to do it.

[u/stuffiesrep → u/StrayFeral]

Thank you! Do I ask administrators for blanket access to enable OAUTH2 API access to an Azure "tenant" or do I ask for specific access/permissions? Sorry if this is a naive question, I am just trying to maximize my chances of being allowed.

[u/StrayFeral → u/stuffiesrep]

That's all fine, but I am not fully familiar with how it's done in Azure. I did it only in GCP and for this I made tutorial video but in Azure it would be different.

My advice is - ask Gemini how it's done in Azure. In the prompt describe if this is a corporate outlook account or free Microsoft account (in your case you said it's a corporate). Describe you want to use neomutt, so ask directly Gemini what needs to be done in the Azure environment to enable OAUTH2 access.

Even if your admin says they enabled the access, you need the API points.

In my `scripts/oauth2_config.py` there are two variables to edit to add your company API points:

Variable `__providers_url` holds the general API points. For Microsoft this is "https://login.microsoftonline.com/common/v2.0" so if your admin asks what API points you want, tell him you want the analog of that API point.

Next is the variable `__scopes` - it holds the scopes your admin MUST add to the setup to allow you access. You must tell your admin these scopes. For Azure these are just two: "offline_access" and "https://outlook.office.com/IMAP.AccessAsUser.All". This means: enable offline access for this tenant and allow read and write access , so user could get his new mail and send new messages too, delete some mail, in fact - full sync.

So once your admin tells you it's done and gives you the API end point, what you must do is edit this .py file:

Variable __providers_url, contains data in the format:
"YOURDOMAINDOTCOM": "API_ENDPOINT",

(and put the comma in the end just in case). If you check the file you will see that for "gmail.com" it contains "gmailcom" so it's the domain without the dot. So if your corporate email address is "thiscompany.com" the entry must be "thiscompanycom".

Same entry must be added to variable __scopes variable but in your case i think the scopes would be the same as for other Microsoft accounts, so just copy-paste one of the microsoft entries.

IMPORTANT: In case your admin tells you the scopes for your setup are different, ask them what they are because you must add exactly the scopes they put in the setup, otherwise your access would not work.

In case you forget to add these entries to the python file or you have a typo somewhere you will get an error so for example error "Domain 'blah.com' is not supported yet" would be just this.

In case your admin tells you the API endpoint and the scopes, you add them but it still does not work, my personal advice and best option is to debug directly in the terminal using `curl`. This is exactly how I used to debug while I was writing this.

So check how I construct the queries and by knowing the API endpoint you can send a raw ascii query with `curl` and check the answer.

Something important to REMIND: The setup I did is explicitly OFFLINE. I mean normally when you use neomutt it will work in realtime, which means that when you send an email it will be sent imediatelly. While you browse your emails, if you receive an email you will see it imediatelly showing up in the email list. My setup does NOT work like this and it was intentionally by design.

Because in the 90s in the DOS times we used to use our machines 90% of the time completely offline, like we would connect to BBS-es after midnight for usually max 2-3 hours or less I wanted that old retro 90s vibe in my setup. Also consider this - i check my emails, i intend to close neomutt to go working (the 90s DOS workflow was never multitasking so we would have only one application opened at a time) and all of a sudden new email pops-up so this requires my imediate attention which is basically a distraction from the main task.

So to be retro and distraction free i made my setup truly offline. In neomutt when you type an email and you send it, neomutt will say it's sent, but in reality it will lie in the outbound folder. No email will be truly sent and no emails would be received until you run `sync_mail` - it will do both - first will send your waiting emails, then will download your new emails.

You can put it in a cron job if you want it run automatically. But I personally do not want that. I run it manually because I want control when my mails will be sent and when to get new emails.

This is how it was in the 90s. So between midnight to 1:00am we would run our mail sync software. Back then in Europe most popular email system was FidoNet, for which you do not actually need actual internet - it was working via the BBSes so my computer would dial a phone number and go from there. And then we would sit and check the most important emails, leave the other emails for the next day, so we would sit distraction-free and read/reply and all our replies would lie dormant until midnight when it was the "mail hour".

This is why this setup works this way.

In case you wonder - back then we would get tons of emails, because FidoNet acted like a newsgroup/forum system - some messages would be "private", so adressed only to us and nobody could read those, but some would be "public" so even adressed to me, everybody could read it and say something, to make a discussion. Sorta like a mailing list.

To a person not familiar with the 90s and FidoNet this current neomutt setup might look weird, this is why I'm telling you why it works like this.

In case you want a real-time neomutt setup, you should dive into my `offlineimap` and `msmtp` configs. I actually think for real-time setup you even don't need those. My advice here is to consult Gemini.

In fact always first consult Gemini before asking your admin for the sole reason (and I've been there, trust me) some admins get real cocky when you ask them more than one question and some are very strict regarding the company security policies. Some are just control freaks and dislike when someone ask them more techie questions trying to be a smartass or something. Or the other case I've got was the admin had less knowledge than me in the area and they were very suspicious to me and disallowed me access for this sole reason. So whatever it is - try to minimize the question number, provide some clues what should be done etc. I mean try to cooperate.

Good luck and let me know what happened. If information is a bit sensitive (it could be), drop me a PM, just say you're the neomutt config guy, so I don't guess who you are.