Instead of spamassassin, I've made do with a bunch of procmail recipes,
which only let about one spam per week through. Another recipe weeds a
high traffic list, dumping stuff that won't interest me.
Erik
y them. mutt is conservative and
> uses multiple methods since there is no standard.
>
> me
So, looking from the other side also, it appears that both are respected.
Erik
s is
configurable. It also uses an "Attach:" header.
You'd think that someone who rereads before sending wouldn't forget that
an attachment was intended, but I have found its memory useful on more
than one occasion, especially on longish emails.
Erik
to other users for the
replacement behaviour to be optional only. Making the new behaviour the
default is in fact an (entirely acceptable) indulgence, I submit.
Erik
those opposed to the new
> Fcc behavior think this is an acceptable alternative, I'll be glad to
> include it in that release.
That would be brilliant, Kevin. I'll look for it next week, then.
Many thanks, again, for the effort you're putting in to make mutt the
ideal MUA - despite a variety of use cases in the wild.
Erik
e
without them. To deliberately create a potentially irrecoverable
situation in mutt is incomprehensible. If developers insist on the
backwards method for themselves, then is an fcc_order config option
possible for the benefit of users seeking the old reliability?
Mind you, I can avoid the problem by remaining on my old mutt, and never
updating.
Erik
7;s only one config command for postfix:
# postconf -ev relayhost=[yourmailhost.your.isp.domain]
The [] are needed.
Update running instance:
# postfix reload
Erik
--
Habit is habit, and not to be flung out of the window by any man, but
coaxed down-stairs a step at a time.
l -> postfix/sendmail -> procmail -> mailbox
later: mutt <- mailbox
For a single user, that is perhaps overweight, but if that's what one is
used to setting up, then it's no bother.
Erik
t
was pretty easy to get going. OK, like a number of others on the list, I
find fetchmail fine for pulling mail in from the ISP, and procmail for
collating it in a number of delivery mailboxes.
Can't advise on the other stuff, though.
Erik
(Who is also too content with an old mutt version to stop and update.)
'c' Change-Folder invocation in mutt takes me to that, for
immediate attention. It works like a bought one. :-)
Erik
c in one increasingly entropic morass?
(Apologies for the rhetorical query. It is intended to evoke
deliberation.)
Erik
r had never occurred to me as a
viable option. There are various incoming mail filtering tools in any
linux distro repository - the one I've used for decades is procmail.
I've set it to stream incoming mail to a separate inbox for each mailing
list, one for family, and the rest remain in
ame completion works too. It's what I expect and use.
In comparison, bash takes two additional tabs and a 'y' to bring up a
long list after one tab has partially completed "mail/cnc":
$ ls mail/cnc_linux_
Display all 456 possibilities? (y or n)
Erik
On 15.12.18 19:35, Cameron Simpson wrote:
> On 15Dec2018 17:01, Erik Christiansen wrote:
> > Is it in reality even remotely "likely" that any LDA contains code to
> > search out those headers and delete them in transit? (Please feel free
> > to post any cod
val - is there?
As for "blorgh", if you refer to e.g. colour keywords, then mutt assigns
colours on regexes evaluated at the time of display. There is no
connection between that and any LDA run some time beforehand.
So, is there anything factual in the assertion?
Erik
days of SunOS4.1.3 or a bit before,
with a variety of MUAs - between three and four decades of trouble-free
use. Migrating my 1254 mboxes to mdir would not give me anything
other than an extra pile of directories and a horrifying number of
files. (What it might give the reader is his concern entirely.)
Erik
what matters most is what Kevin thinks, as
he's the one with his sleeves rolled up. Then the thoughts of the
majority of the community bear consideration, especially when based on
reason. Last and least come a sole opinion based on taking an RFC as
evidence, then rewriting it when it fails to support an entrenched
inflexible view.
But full points for doggedness. ;-)
Erik
On 10.12.18 17:29, Derek Martin wrote:
> On Wed, Dec 05, 2018 at 05:31:28PM +1100, Erik Christiansen wrote:
> > Thread comment: It's OK to be unaware of the usefulness of RFC features,
> > but it does seem odd to pretend that they're not useful just because
> >
ied a responsibility to read and consult - not reply
unilaterally.
Thread comment: It's OK to be unaware of the usefulness of RFC features,
but it does seem odd to pretend that they're not useful just because
it's only others who need them.
Erik
ifference here, but letting
the CC list know they can leave the message on the back burner is
fractionally as important as signalling the TO recipients that they
can't.
Erik
"alias -group fam_grp rita r...@example.com"
line. It's an fcc-save-hook rather than just a save-hook to put my
replies there as well. Now _that_ is smart, and seems far more useful
than spraying emails disc-wide based on nothing more than "From:".
Erik
One or more of the above might be
similar ... or better, e.g. xlbiff.
Erik
tation is a quick and simple way to achieve the desired
watchdog function.
> The trick is simple: substitute $sendmail with a custom one.
Sounds more complex than a simple plugin install plus a Vim variable
setting, especially given the X dependencies and consequential
workarounds for termin
the MUA.
> Or is this a limitation of the RFC that subject lines need to be
> under a certain length?
My simple experiments suggest that it's just mutt joining vim's multiple
lines into one, then wrapping that for useful display on receipt.
Erik
¹ edit_headers is set.
all headers, then add back those desired. It is enough to
give me both From headers.
Is it possible that your problem lies in that area?
Erik
y run when the editor is
invoked by mutt.
An alternative might be to invoke the auto-edit via command-line
arguments added to the "set editor=myeditor" line in .muttrc. (Not
tried)
Erik
# Default reply_regexp is simplistic, though.
Fix: Added in .muttrc:
# Note: Keep reply_regexp lower-case, to keep it case-insensitive.
#
set reply_regexp="^(((re(\\[[0-9]\\])?|aw|fw|fwd|\\?\\?|):)[ \t]*)+"
There are even fancier regexes in the list archive, back in 2009/2010,
but they have more ambitious agendas.
Erik
ideas what to try to solve this?
What happens to the headers when you use & to join a tagged mail to a
thread? Presumably the thread display is now OK, and the change in the
headers will show whether it's In-Reply-To or a Reference that was
missing. (Whenever I've done that, mutt has added an In-Reply-To, IIRC.)
Erik
On 13.05.18 15:31, Brian Salter-Duke wrote:
> On Sun, May 13, 2018 at 03:03:55PM +1000, Erik Christiansen wrote:
> > On 13.05.18 09:52, Brian Salter-Duke wrote:
> > > It is time we gave up bottom posting!
...
> Eric, I tried to email you direct, but you do not allow that,
e whole message with:
"For clarity I'm answering in context, see below:"
Your partner's ignorance and your failure to compensate do not compel an
entire community to pander to your slow learning. Please man up and adapt.
Erik
ch allow an Awk daemon to talk to other processes over pipes, but you
can just invoke Awk once per email.
Erik
pients, as described in the manual. That is
with no $followup_to setting, i.e. default, as Matthias has.
What other configuration is required in order to place the sender's
address in Mail-Followup-To, in contradiction to the manual entry is
then a curiosity.
Erik
will weed headers and will attempt to decode the messages
first." Whether an "ignore *" is also needed to make it weed out all
headers, I haven't tested.
Erik
On 14.03.18 10:48, Tim Chase wrote:
> On 2018-03-15 00:37, Erik Christiansen wrote:
> > Yup, forward:
> > View the email to attach.
> > Hit 'f', and mutt will prompt: Forward as attachment? ([yes]/no):
> > Hit Enter, compose the accompanying email, with forwar
his?
Yup, forward:
View the email to attach.
Hit 'f', and mutt will prompt: Forward as attachment? ([yes]/no):
Hit Enter, compose the accompanying email, with forward address, etc.
Erik
On 13.03.18 11:13, Marco Dickert wrote:
> On 2018-03-13 20:50:20, Erik Christiansen wrote:
> > On 13.03.18 10:09, andreas.muel...@biologie.uni-osnabrueck.de wrote:
> > > can I switch the editor key bindings to the vi style ?
> > There is better than that - you can us
unable to use your
favourite editor everywhere.
Erik
k, to prompt that.)
Many thanks Kevin, for keeping us afloat - and for building the ship.
Erik
er that the post
has been trivially munged.
The ^TO_ on line 2 accepts either "To:" or "Cc:", as adjunct to simple
duplicates management via formail. (Forces "courtesy copy" to the list
mailbox.)
Erik
ined in the environment,
mutt has always found the mail spool, as is the case for most mutt users,
I expect.
In the index view, press y for the mailboxes view, which in my case
presents:
1 -rw--- 1 erik erik 6.1M Feb 05 15:41 =avr_chat_u
2 -rw--- 1 erik erik
it ~C
In the index, "/ ~h elephant" will find any such hiding in headers.
Haven't you used ~b to search mail bodies? Admittedly the latter does
not work on collapsed threads, in version 1.8.0.
Erik
_view commands, without having to split the email and type those commands
> separately in command line?
If you wanted to select a specific multipart alternative in the
Attachment Menu, then there is only 's' or '|'. With a key mapping to
invoke a macro, you could pipe the alternative to qprint, outputting to
a file - with minimal keystrokes.
Erik
to substitute another address if you're not replying.
Erik
> achieve.
On the contrary, Ben's key bindings do keep you in the pager,
substituting line up/down for message up/down. (It's something which
I've also adopted long ago, as the default is alien.)
Erik
ere unclassified, and the
rest were sorted by procmail.
Placing +/family_u /var/spool/mail/erik first on the first "mailboxes"
line in .muttrc gives them priority when changing mailbox with the 'c'
command.
An fcc-save-hook defaults email saving to "family" from &qu
threads uncollapsed. It saves both time and
labour, since it's not necessary to manually uncollapse the thread to
see what is unread in there.
Erik
cumstances, I'd do a :set nopipe_decode,
for emphasis. If a coffee and a break doesn't help with the gremlins,
then a new mutt version?
Erik
ork as "mutt" would seem to
clearly contravene the asserted and enforcible licence.
We pay our FOSS benefactors only in respect and correct attribution. To
fail to do so is IP theft and or misrepresentation, I contend, and is
dishonest and intolerably reprehensible. It reflects appallingly on the
debian distribution. It needs to be rectified immediately.
Erik
loaded with my business address. How I change that
> behaviour?
To force the from address, you can, in .muttrc:
set from="marcelol...@gmail.com"
That relies on: set use_from=yes
but that is the default.
(I notice that I set "from", but don't recall why I needed to.)
Erik
re, you can not
> do anything at that time, let alone sending email.
That is then not a useful configuration. Taking a process half way can
end up like that.
Erik
owned by
"mail", with write permission denied, but you could own the directory,
so you can delete the files despite not owning them. There are such neat
ways to do things on *nix.
Erik
cum
of clumsiness protection.
The pager can be set in hooks, e.g. so the external pager is only used
for some folders or senders.
Erik
know what was written by Arthur, Martha, or Mo.
(Maybe the GUI world doesn't fuss much with attribution?)
Erik
On 28.04.17 10:44, Darac Marjal wrote:
> On Fri, Apr 28, 2017 at 07:16:19PM +1000, Erik Christiansen wrote:
> >On 27.04.17 09:21, Darac Marjal wrote: >> On Wed, Apr 26, 2017 at
> 08:54:45PM +, Grant Edwards wrote: >> > OK, so how does one do that
> within mu
viewed (as source) in the pager or rendered (as presentation
> form) by a mailcap entry.
Is it necessary to send the body as an attachment in order to awaken
that mime stuff?
When I had to pretty-font a report for management over a decade ago, I
composed it in vim, then performed a fontification i
spellchecking to flag bung aliases. Thus a quick hack is to hit zg on
any good alias which fails spellchecking, to add it to the private OK
spell-list.)
Anyway, +1 for accepting the need for aliases for local destinations, as
the price for fumble checking in mutt.
Erik
On 22.04.17 14:33, Charles E Campbell wrote:
> Hello, Erik:
>
> I tried both mail and mailx. Both fail silently when I attempt to send an
> email off my machine (didn't try mailx, but mail will send email to accounts
> on the same machine), although I suppose its possibl
ing an MTA here (postfix these days)
is what avoids your problems. That was easy to set up after the first
effort, given that I keep a few notes to avoid excessive brow furrowing
next time round.
¹ It was what we had on HP-UX and Solaris boxes back in the 1980s, and
it still works the same.
Erik
o From Date Subject
some just for information or deletion.
The closest received message editing usage I have is to send myself an
email as a reminder, then later edit it with updates, until it is
resolved and can be deleted/archived. There are worse places than the
primary inbox for reminders.
Erik
from the target sender), and it doesn't.
Checking multiple senders for a match is perhaps feature creep, I am
forced to admit. :-)
Erik
On 22.02.17 18:50, Erik Christiansen wrote:
> On 21.02.17 13:28, Kevin J. McCarthy wrote:
> >
> > You'll want to use the "push" command:
> > reply-hook '~f x...@yyy.asn.au' \
> > 'push z...@bigpond.com'
> >
&
On 27.02.17 16:49, Tim Ye wrote:
> Hi Erik,
>
> I just tried './configure' on my Debian, no error showed up.
>
> Have you tried:
>
> $ sudo apt-get build-dep mutt
Bullseye! That's easier than fiddling with install paths.
The "make Install" put
On 27.02.17 19:28, Erik Christiansen wrote:
> configure: error: no curses library found
> ###
All right, some or all of the libraries mentioned in the OP are dynamic
libraries, so definitley not enough caffeine. So I'd have to apt-get
source, or
ncursesw5 is already the newest version.
Now I am beginning to run out of ideas. There's something less than
blindingly obvious afoot here ... or I need a higher caffeine to
haemoglobin ratio.
Erik
older.)
> It would be very helpful to my workflow if I could mark important
> items in Mutt and then be able to act on them when I am back in the
> work environment.
That desirable configurability is where mutt really shines.
Erik
On 21.02.17 13:28, Kevin J. McCarthy wrote:
> On Tue, Feb 21, 2017 at 05:27:55PM +1100, Erik Christiansen wrote:
> > reply-hook '~f x...@yyy.asn.au' \
> >'z...@bigpond.com'
>
> You'll want to use the "push" command:
>
is just a copy of
Kyle's example, so I'm a little short on things to tweak to make it go.
When I substitute send2-hook or send-hook for reply-hook, there is no
error, but the To: address is unaltered, i.e. the hook does nothing at
all.
Has anyone made something like this work?
Erik
y, thus 72 characters rather than 80.
The topic was recently discussed at some length, as recorded in the
archive.
Erik
jam for some reason, and you want to get e.g. a
resume out fast.
Erik
use fetchmail to bring mail in
via POP3. It has served me well for several decades now.
Erik
unately obviates
the need to play with display_filter. ;-)
¹ I do have:
set smart_wrap # Wrap
set wrapmargin=10 # long lines.
unset markers # No '+' email line continuation crap.
# Busts URLs!
Erik
" for me, because I didn't notice
> that you answered my mail as well, as mutt didn't show this
> message as reply to my mail.
Ah, that's a disappointment. I had hoped for:
On 08.11.16 23:57, Erik Christiansen wrote:
> Here it was displayed as a reply to my post. If Camero
ere it was displayed as a reply to my post. If Cameron and Simon's
mutts display it under their post, then mutt is doing very well indeed.
(Convenience is maximised, and confusion is negligible - within a
thread.)
Erik
y replies, and to put all of the information
regarding several facets in one place, for the record. (I use it only
very occasionally.)
It can be advantageous to swap the order of the quoted messages for a
more logical flow in the reply, and trimming of the quoted text is even
more important in the case of several long messages.
Erik
On 13.09.16 12:08, mimosinnet wrote:
> When the members of the group CoordsM change, I have to change the
> alias.
>
> Is there a way I can use the definition of the "Address Groups"
> (http://www.mutt.org/doc/manual/#addrgroup) to be able to define an
> alias (http://www.mutt.org/doc/manual/#alia
is done with mutt.
No, that is not the reality. ;-)
The reality is that it's a simple thing because editing is in vim and
browsing is done with mutt. Try the described methods and you will learn
the truth of that.
If you can stop trying to eat soup with a fork, and use the offered
spoon, success will follow.
Erik
an characters will not render.
BUT if I open a new xterm _after_ gnome is all there, then an "xterm
-lc" does honour the UTF8 locale, and the characters display fine.
I don't know if that xterm-related datapoint muddies the waters in a
beneficial way.
Erik
On 19.08.16 07:39, Matthias Apitz wrote:
> If I unset it in ~/.muttrc and run
>
> $ LANG=es_ES.UTF-8 LC_ALL=es_ES.UTF-8 LC_TIME=es_ES.UTF-8 mutt
>
> it gives the month name as 'Aug', which is not correct.
Try:
$ export LANG=...
Erik
text encourages more assiduous
pruning in lieu of profligate over-quoting, then let's keep it manual, I
say.
Erik
(Where's my tin hat & flak jacket?)
Kevin,
Many thanks for your effort to keep us flea-free.
This time I do plan to upgrade.
Erik
abused by quoting an email of your own, then
deleting the "> " quotation marks, e.g. with !Gs/^> //
That presupposes that your source email is in the same mail folder,
which is a limitation - but the method is very quick.
That's probably enough options, without looking for obscure methods.
None of them require a new instance of mutt.
Erik
tes, and a bit of keyboard thumping.
Erik
On 04.08.16 09:27, Patrick Shanahan wrote:
> * Gabriel Philippe [08-04-16 09:25]:
> > On Tue, Aug 2, 2016 at 1:00 PM, Erik Christiansen
> > wrote:
> > > Subscribing to the procmail mailing list would help while learning.
> >
> > Does it still exist? pro
procmailex".
The manpages seem to be included in the procmail .deb package - at least
I don't see a procmail-doc package to bother with.
Erik
allows me to categorize my junk mail and then move them to
> my main mail box if I want to keep one.
There's no need for any script. Once procmail has sorted incoming mail
into a bunch of mailboxes, e.g. one per mailing list, etc., then in
.muttrc, something like:
mailboxes +/family_u
, and so may work well.
Heck, some respondents may even have time/experience to answer more than
one of them. ;-)
Erik
arly benefit from becoming
current.
Erik
m
hit 'e' on the email, and then use vim's syntax highlighting do go to
town. A google for "vim syntax diff" seems to throw up all sorts of
stuff, including mimicking the colours of a git diff.
Erik
together with mutt, if the MDA also uses MBOXCL.
(I will admit to not having found anything in man procmailrc to allow
one to make that tweak.)
Erik
--
The wonderful thing about standards is that there are so many of them.
- Andy Tanenbaum
n than that the format mboxcl2 is being used, which does
> not from munge and relies on Content-Length:. Can anyone confirm? I
> searched for mboxcl2 in man muttrc but no instance.
erik@ratatosk:~$ mail -s "From test" erik
>From today, it is all future.
>From Erik
Cc:
erik@rat
in remembering
replacement utilities with a greater future availability, I think.)
Erik
(who remembers when uuencode was the go-to decoding utility.)
On 03.06.16 10:52, Christian Brabandt wrote:
>
> An alternative might be qprint (package qprint)
Indeedy! :-)
Thank you Christian. I've made a note of that.
(Stuff from many years ago now sticks better than new stuff. :(
Regards,
Erik
, but I'm not able to find it on my
debian install, and apt-search doesn't do any good either. We used to
have mimencode, but that was obsoleted years ago. I tried munpack, but
that doesn't seem to make any attempt to handle mime fragments.
Any clue on where mmencode might be snaffled would be very handy.
Erik
d support vi as well
> as emacs key bindings.
The "map Escape in the terminal" work-around, described at the link,
would seem to be a non-starter, since it would completely muck up vim/vi
when used as editor in mutt.
Erik
to e.g. message 2144, type in 2144, and see what happens. ;-)
For going to the first/last message in a folder, the / keys
suffice.
Beyond that, for speedier moves than /, ^P/^N are good for
flitting by thread.
Erik
he
meeting date.
Another option is an autocommand which defines a key mapping which
inserts the Bcc:, but only when editing a mutt tmpfile. (Lets you use
the key in other ways outside mutt edits.)
Erik
On 12.04.16 13:05, Derek Martin wrote:
> On Tue, Apr 12, 2016 at 05:28:08PM +1000, Erik Christiansen wrote:
> > The really big benefit of the Unix approach is that the same utility
> > know-how can be applied to every problem, as it is only the mix of
> > utilities used,
On 11.04.16 11:11, Derek Martin wrote:
> On Mon, Apr 11, 2016 at 10:13:06PM +1000, Erik Christiansen wrote:
> > In the latter half of several decades of software development, I took to
> > heart "Unix _is_ the IDE". Similarly, there's no need for mutt to do
&
ited search, as above, to scan all files. I had archived
the post under a more relevant topic.
A simple but useful aid has been the shell function:
mls ()
{
ls -xF ~/mail/*$1*
}
Now any part of a subject name finds all related collections:
$ mls security
/home/erik/mail/cnc_lin
On 27.03.16 21:05, Erik Christiansen wrote:
> That's not what happens here, I hit 'c' and mutt immediately offers the
> mailbox with new mail which appears highest in the (one or more)
> "mailboxes" lines in my .muttrc.
Jon, if mutt isn't detecting new mail
1 - 100 of 354 matches
Mail list logo
