#neomutt

[daemonhxckergrrl]

cursed linux install idea: framebuffer-only !

'WM': tmux (holding the following)

Editor + Files: vim + nerdtree plugin

Img View: fim

Mail: neomutt

IRC: irssi

Browser: w3m-img

aka how to abuse the poor framebuffer xD

nb: i'm sure someone somewhere does this as an actual workflow

#daemon.md #linux #cursed computing #framebuffer console ONLY

[linuxshelltips]

#linux #Linux Command Line

[clacpybara]

inline images in neomutt

i use neomutt as my email client (imagine opening a browser to check your mail lol)

thing is: company requires all employees to send their mail with an image as the signature. most solutions online were quite complicated for people who don't know html (like me) so what you can do is

 - send yourself an email with the image as the signature

 - get the html from the mail (you can just open the <text/html> attachment in mutt)

 - cut the appropriate part, mine looks like this:

<br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><img src="https://your.image.url.goes.here" width="420" height="110"><br></div>

 - save it as a .html file

 - attach to every mail as inline, i.e. toggle disposition (just press ctrl-d)

you can set a macro for it, in my muttrc it is like this:

macro compose y ":exec attach-file<enter>/path/to/file.html<enter>:exec toggle-disposition<enter>:exec send-message<enter>"

if you have multiple accounts and want to disable this macro, put this in a hook or anything you use to change accounts:

macro compose y ":exec send-message<enter>"

#linux #email #mutt #neomutt #image

[fernand0]

#neomutt #mutt #correo #cliente

[dview]

Switching to Mutt

I’ve been wanting to try out a terminal based email client for a while now, but was always intimidated by the complexity of people’s elaborate setups and config files.

Well, yesterday I found out how to add a basic IMAP configuration for Mutt and installed NeoMutt.

I’m not using any fancy features at the moment, but simply being able to reply and compose emails in my favorite text editor (Vim/NeoVim) is such a joy.

Needless to say, I’m hooked! And I’m sure with time, my configuration file will grow and I’ll better perfect my Mutt skills. But honestly, if you’re familiar with Vim, it’s not as big as a learning curve as I expected.

I’ve been using Plain Text emails for a while now, so using a program and editor specifically designed for that format really makes for a smooth workflow.

#mutt #neomutt #vim #neovim

[theouterlinux]

Terminal Email Clients

Alpine: https://www.washington.edu/alpine/ Sup: https://github.com/sup-heliotrope/sup Mutt: http://www.mutt.org/ NeoMutt: https://www.neomutt.org/

#linux #command line #terminal #help #howto #tutorial #communication

[jmtapio]

For better or worse I'm a heavy email user, not least because so much of the traditional workflows in Debian are email based. I use a variety of email clients but my swiss-army knife is mutt, and has been since at least 2005, which is the earliest-dated comment in my mutt configuration files.

I've always used the mutt package as provided by Debian, which means in practice I have been actually been using neomutt since around 2016, when the Debian maintainers imported that patch-set into the mutt package. neomutt is an independent effort to coordinate development of mutt (or on top of mutt) as the upstream maintainer(s) were (for a time) largely dormant. It's meant to be a friendly project, in some cases incubating patches that people are still trying to submit to the upstream project.

Fast forward to 2017 and an upstream mutt maintainer complained that Debian is providing something called "mutt" that is actually "neomutt" and started making pseudo-legal threats. This could have been resolved in a number of ways (my proposal and plea are recorded in that bug), but the decision of the package maintainers was to switch the mutt package back to the mutt source and provide neomutt as a separate Debian package.

We now have a situation where

If you were using mutt in Debian from 2016 onwards, you were most likely using neomutt, and your configuration files are most likely tailored to neomutt. If/When you upgrade to the next stable Debian release, you will be moved to real-mutt and your configuration may break.

if you filed a bug against the mutt package, depending when you did and what version of Debian you were using, your bug might be assigned to the mutt source package, which is now real-mutt, but might actually relevant only to neomutt. Looking merely at the list of bugs against "mutt" is not enough to be sure it's a bug in mutt, or neomutt, or both.

real-mutt and neomutt have not yet co-existed in a Debian release, so you cannot evaluate both side-by-side without introducing packages from testing or unstable, which might mean a libc upgrade.

Lots of stuff, especially Debian devscripts, hard-code /usr/bin/mutt as a mailer. The neomutt package does not provide this binary, and it is not mediated by the alternatives system, so if you only install neomutt, you might have integration niggles to solve yourself.

For a short while, I attempted to adjust my configuration files so that they would work in both real-mutt and neomutt, but this proved too messy so I've given up. I did have them co-installed on my main mail-reading host, but I also found myself occasionally confused as to which I was actually running at a given moment, so I've decided to stick to neomutt everywhere going forward: which means neomutt on my main mail host, and the mutt package on my Debian-stable hosts, and I must remember to switch the packages over when I update them to Buster (the next stable release) in a month or two.

The other upshot of this is I've decided to declare "year zero" on my mutt configuration files, rather than try to adapt the mess of mixed mutt and neomutt configuration bits spread across a dozen files that have grown since (at least) 2005, I'm going to start from scratch and only import over something if I feel its absence in daily use.

via Planet Debian

#Reading

[tenderlystarstruckgentlemen]

New top story on Hacker News: Luke's mutt wizard for automatic Neomutt and OfflineIMAP configuration https://ift.tt/2OrEQfu

#IFTTT #Blogger

[our-umair-mehry-stuff]

Luke's mutt wizard for automatic Neomutt and OfflineIMAP configuration 39 by lwhsiao | 4 comments

#Blogger

[askanything-online-blog]

change laravel 5.4 text mail content-type to text/plain

change laravel 5.4 text mail content-type to text/plain

I am sending a small text mail with laravel:

public function build() { return $this->text('emails.empty')->subject($this->msg) ->with('msg',$this->msg); }

The view empty.blade.php should only print the message:

{{ $msg }}

But neomutt receives text/html content:

[-- text/html wird nicht unterstützt ('v' benutzen, um diesen Teil anzuzeigen) --]

and thunderbird also shows…

View On WordPress