On Mon, Aug 07, 2023, Jan Eden via Mutt-users wrote:
> I recently upgraded to macOS 13.5, and for the first time, there are
> redraw issues in the Terminal with mutt (2.2.10, installed via
"Terminal" broke screen handling for me in MacOS 13.5 with various
programs - even vi. Maybe file a bug
Just some idea (untested):
Use a script as "sendmail" program for mutt which
- submits the mail but tells the MTA to only queue it,
- gets the info about the queued msg from the MTA when
it accepts the mail,
- schedules a queue run for that item at the desired time.
and make sure the MTA does
On Wed, Mar 29, 2023, Mark E. Mallett wrote:
> to add and implement a couple of muttrc variables to set a top and
> bottom margin, since I like to break up any wall of solid text. As I
"Back then" I had my own patches to do that.
> This actually used to be a fairly non-trivial patch, having to
Maybe a basic check first:
mutt -v | fgrep '+USE_SSL_GNUTLS'
Does it show what you configured?
On Fri, Mar 11, 2022, Stefan Hagen wrote:
> > > 550-5.7.26 This message does not have authentication information or
> > > fails to
> Authenticated in this context means, you don't have SPF / DKIM / DMARC set up.
[more off-topic/rant]
Isn't it nice how Google et.al. enforce things which are
I recently wrote something like that but for mailboxes. It uses
formail etc and requires that each mail has a Message-Id (which
some didn't have...).
Look into the -D and -s options of formail, maybe it works for
maildirs too?
As I wrote before: check some online articles (this is not a problem
with mutt). In this case it seems the problem might be on the
server side. You can probably disable the use of DH ciphers (in
sendmail) in general or at least with those servers (that might
require a newer sendmail version).
On Wed, Nov 17, 2021, Andrew D. Arenson wrote:
> Oct 21 19:52:35 redsolar sm-mta[1465905]: STARTTLS=client, error:
> connect failed=-1, reason=dh key too small, SSL_error=1, errno=0,
It seems your sendmail version is a bit old? Check your favorite
search engine... you need to generate a larger
On Tue, Nov 16, 2021, Andrew D. Arenson wrote:
> I don't see any obvious configurations that set how email is
> sent, so my guess is that it is being send via sendmail on my
> Ubuntu workstation.
Then you should be able to check the maillog(?) for those
TLS problems and also
On Tue, Nov 16, 2021, Andrew D. Arenson wrote:
> Deferred: 403 4.7.0 TLS handshake failed.
This has nothing to do with the content of the mail, it's a problem
between the program you use to send (submit?) the mail at the SMTP
level and the MTA at uw.edu.
Do you use mutt directly for this
On Wed, Feb 03, 2021, Will Yardley wrote:
> Even if Mutt doesn't set one, the first MTA it hits will add one. Not
Not really - a MTA should not make such changes.
A MSA should do it, but Message-Id: is a SHOULD not a MUST.
> What exactly is your goal here?
That's the important question, aka
On Sun, Jan 31, 2021, Chinmaya Nagpal wrote:
> I have a similar setup as yours, except I use the built-in SMTP. What
> advantages are there to using an external sendmail program?
Queueing.
On Sun, Oct 11, 2020, Remco Rnders wrote:
> > save-hook "~C ietf-\\([a-z0-9]+\\)@ietf.org" =%1
> I know it is not a direct answer to your question, but it might perhaps get
> the
> end result you want; Have you considered using procmail or a sieve filter to
> automatically save mail matching
I'm trying to use a more generic approach for some patterns
to handle mailing list, e.g., something like:
save-hook "~C ietf-\\([a-z0-9]+\\)@ietf.org" =%1
instead of having one entry for each mailing list.
Is that possible with the current mutt features?
It seems that back-references in regular
On Fri, Jun 05, 2020, Will Yardley wrote:
> Anyone have any tricks / tips for accessing Office365 via Mutt? I know
Someone at $WORK got frustrated enough that he used Davmail to
access his mail. However, it seems it is specific to the fubared
$WORK setup? Here's a part of what he wrote about
On Fri, Dec 27, 2019, Kevin J. McCarthy wrote:
> Try refreshing your pgp_* commands against the version in contrib/gpg.rc in
Thanks, that solved the problem. Seems I didn't look far enough back
in the ChangeLog, sorry.
Now I need to find some time to resolve the merge conflicts so that
my
So I'm a "bit behind" and recently updated to 1.12.1 (from 1.9.x)
Based on ChangeLog I added
unset pgp_use_gpg_agent
to my muttrc which at least gives me a prompt asking for the pass
phrase (I'm not sure why that is set by default if there is no gpgv2
on the system?). However, I can no longer
On Mon, Sep 23, 2019, rand pie wrote:
> How to set the sendmail binary sender address
> base on different email addresses with mutt?
*-hook might work, e.g., something like:
folder-hook . "set sendmail=\"/usr/sbin/sendmail -i -oem -fUSER@B.C\""
send-hook ietf-smtp "set
On Wed, Dec 12, 2018, Victor Sudakov wrote:
> Is there a way to hide a message (e.g. with a certain subject) from view in
> a mailbox, without actually deleting it?
Maybe this works:
show only messages matching a pattern
Details can be found in the documentation.
On Sat, Oct 27, 2018, Ian Zimmerman wrote:
> On 2018-10-27 18:23, Claus Assmann wrote:
> > Just FYI: both test mails passed verification for me.
> RGH!! I am losing my mind!!
Hopefully it's backed up somewhere...
> Here are the intermediate Received headers of th
On Sun, Oct 28, 2018, Ken Moffat wrote:
> 3. Neither the post you were asking about, nor either of your tests,
> passed verification here.
Just FYI: both test mails passed verification for me.
On Thu, Sep 06, 2018, Kai Weber wrote:
> How can I have the same muttrc on both machines without running into
> errors during mutt start?
I split the rc file into
1) a common part
2) parts specific to the mutt version
and
- source the common part (1) in the specific version (2)
- use a wrapper
Is there some fast way to save the attachments from multiple messages?
That is, without going to every individual message, viewing and
then saving the attachments? I can tag the attachments in a single
message and save them easily, but seemingly not for multiple messages
(AFAICT). Something like a
On Wed, Jan 17, 2018, steve wrote:
> I tried to tag some messages
> with T then type ;m but this create an empty new message.
Did you try "reply"? ;r
Thanks for the patch, your approach is so much simpler than what I
tried so far.
In some basic testing it does what I want -- I also added a blank
line near the bottom (and now I have to figure out that hg stuff to
maintain a branch(?)/clone(?) of the original code plus some local
changes).
I hacked an old mutt version to have a blank line between
the status (on top) and the list of mails, e.g., it looks
like this:
Mbox: =admin (-) [[rest of status line]]
214 2016 Mar 01 Charlie Root( 33) esmtp.org daily insecurity output
215 2016 Mar 01 Cron Daemon ( 21) Cron
Sorry about that, it's actually something at the mailing list server
that does this : it not only adds X-FidoGuard-... headers, but
also munges the Subject with some utf-8 token (which seems like a
useless "encoding"). That software obviously has too many false-positives
:-(
IMNSHO it's rather annoying when people send mail to the list and
add a [SPAM] tag to the Subject: header.
If it were spam, why would you send it to the list?
[maybe the mailing list SW could filter/reject such mails :-) ...]
--
Reply-To: is set, please do not Cc' me.
On Thu, Sep 22, 2016, Ian Zimmerman wrote:
> muttgpg
> http://marc.info/?l=mutt-users=147417425713497=rawBAD GOOD
Verifies fine for me (in mutt).
Now the question is: is it "just" your setup, or does it fail for
others too?
On Tue, Aug 30, 2016, Derek Martin wrote:
> Why, then, do you feel the need to distinguish between a deletion
> caused by a copy, and a deletion caused by you explicitly deleting the
> message? In both cases, it is legitimately a deletion.
In the former case the user still has a copy of the
On Mon, Jun 27, 2016, Will Yardley wrote:
> On Mon, Jun 27, 2016 at 10:48:54AM -0700, Claus Assmann wrote:
> > mutt/gpg gives me a "BAD signature" for some recent mails on the
> > openssl users list, one example message is attached. Can someone
> > else reprodu
mutt/gpg gives me a "BAD signature" for some recent mails on the
openssl users list, one example message is attached. Can someone
else reproduce the problem (the author says it verifies for him)?
If the signature verifies for you, which mutt / gpg version do you
use? (and any hints what might be
On Thu, Apr 14, 2016, Xu Wang wrote:
> I use mutt's built-in SMTP client. I would like to press 'y' and
> immediately be able to move on to my next email without waiting. I
Did you check the fine manual?
3.234. sendmail_wait
Type: number
Default: 0
Specifies the number of seconds to wait for
On Tue, Jan 26, 2016, Xu Wang wrote:
> that in order to decrypt a message I need to put my passphrase in. But
> for signing, I do not need to. Is this normal? It is the same
Are you replying to an encrypted mail? Then the pass phrase is
most likely still cached. See the fine manual, look for
I asked about this when 1.3.25 came out and got the answer that
this should be fixed / will be looking into it. However, 1.3.28
still can't be configured without iconv. Any chance for a change?
I've attached a patch that seems to work. It's a bit of hack, a
clean solution would be to have an
On Sun, Mar 17, 2002, David Champion wrote:
* On 2002.03.17, in [EMAIL PROTECTED],
* Claus Assmann wrote:
I asked about this when 1.3.25 came out and got the answer that
this should be fixed / will be looking into it. However, 1.3.28
still can't be configured without iconv. Any
System: OpenBSD 2.8
./configure --without-iconv
doesn't work:
checking for catalogs to be installed... de ru it es uk fr pl nl cs id sk ko el zh_TW
zh_CN pt_BR eo gl sv da lt tr ja hu et ca
configure: error: Unable to find an iconv function. See INSTALL for help
I read the INSTALL file, that's
On Wed, Jan 02, 2002, Daniel Eisenbud wrote:
This is annoying. I've successfully compiled mutt without iconv by
commenting out lines in config.h, so I think that this is just a
braindead policy decision. Try commenting out the iconv test you quoted
below in configure, and see what happens
This behaviour is a bit strange on my OpenBSD 2.8 system:
$ ./mutt -f =mutt
123 kept, 3 deleted.
Between those two lines I read some mail and deleted 3.
At the end mutt asked me whether to (really) delete them.
I typed 'y' and then I had to hit return, which is different
from the old behaviour
On Wed, May 16, 2001, Louis-David Mitterrand wrote:
You're going to add an MTA first (reimplement sendmail). Then
Huh? Adding a few dozen lines of code to deliver via SMTP is
reimplementing sendmail? You need a serious reality check.
a few dozen lines of code... Did you ever write a SMTP
On Wed, May 16, 2001, Louis-David Mitterrand wrote:
Yes, telling the user try later or postpone your message and fix your
config is better than injecting the message into a poorly configured
/usr/sbin/sendail that will drop it on the floor without reporting it.
What a great alternative...
On Thu, Nov 30, 2000, Kelly Scroggins wrote:
The error produced by Mutt is :
/etc/sendmail.cf: line 90: fileclass: cannot open /etc/sendmail.cw:
Group writable directory
It's not mutt, it's sendmail.
-rw-r--r-- 1 root root 59 Sep 1 1999 /etc/sendmail.cw
It's complaining about the
On Wed, Oct 04, 2000, Peter Jaques wrote:
it does; i used to get all the "x-authentication-warning"s, till i changed
my sendmail.cf. sendmail IS honoring the -f; it correctly sets the
"From " header. it just doesn't set "Return-path" right.
This is somewhat off-topic for mutt...
The
On Wed, Sep 27, 2000, Mikko Hänninen wrote:
Suresh Ramasubramanian [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000:
Well... Thanks for this quick answer, but what choice do I have ?
Making my machine to resolve in the outside world, or have mails
bounce, or having this authentication
On Thu, Sep 21, 2000, Charles Cazabon wrote:
I seem to have found a bug in mutt, when using 'mutt recipient_address' from
the commandline. Minimal test case follows:
[charon]$ mutt foo@[EMAIL PROTECTED]
That's not a valid address.
It works fine with zero or one '@' signs in an address;
On Mon, Apr 17, 2000, Ralf Hildebrandt wrote:
Does mutt support TLS as described in
http://www.aet.tu-cottbus.de/personen/jaenicke/pfixtls/
?
Why should it? mutt doesn't use SMTP...
On Thu, Feb 10, 2000, Thomas Roessler wrote:
On 2000-02-09 18:15:03 -0500, Adam Sherman wrote:
Would it be possible to use Mutt with S/MIME cryptography?
It wouldn't be difficult to add support for this to mutt, once you
have a command-line based tool with the cryptographic
On Wed, Feb 09, 2000, Lars Hecking wrote:
The Sender: header is written by the MTA (eg. sendmail).
sendmail does not generate a "Sender:" header.
Which MTA does it?
On Wed, Nov 10, 1999, Shane Castle wrote:
It serves absolutely no useful purpose and causes
more problems that anything it was intended to solve. PLEASE don't use
it! Don't even try to fix it; it's too broken!
Which version are you talking about?
IMHO it is a very useful program, there
Hi!
I've received an e-mail where the From: header line contains a
quoted-printable encoded name:
From: =?iso-8859-1?Q?=22F=FCr=2C_Per=22?=
[name changed, address omitted...]
As you can see, this translates to:
"Für, Per"
However, the quotes have been encoded too.
Replying to this causes
On Sat, Jul 10, 1999, Aris Mulyono wrote:
I tried to set dsn_notify and dsn_return variable in mutt
but when I sent the email the sendmail complained about the option
-N not being recognized.
What FEATURE should I enable specifically in sendmail to do this?
None. It is enabled by default.
Is there a chance to modify the prompt:
Enter PGP passphrase:
to include an identification of the key that is required?
Background: I have multiple PGP keys protected with different
passphrases. Sometimes it is not clear which PGP key has been used
for encryption and then I have to look at the
On Fri, Apr 23, 1999, Hal Burgiss wrote:
Maybe this discussion should be done in a sendmail related list/group?
Well I am starting sendmail as : sendmail -bd -f [EMAIL PROTECTED] I
thought this might help, but doesn't seem to.
The daemon ignores the -f option for obvious reasons: you
On Tue, Feb 16, 1999, Randall Hopper wrote:
Claus Assmann:
|Question: how can I disable the X-Mailer: header?
I wonder if this would work:
unmy_hdr X-Mailer
Haven't tried it, but it seems like it should.
Unless I did something wrong, it doesn't work.
I use the suggestion
CFLAGS
On Fri, Feb 12, 1999, Thomas Roessler wrote:
Mutt 0.95.3 is out. This version should be considered BETA.
Question: how can I disable the X-Mailer: header? Before this
version I used to patch config.h, but now the definition is in
acconfig.h, which seems to be nowhere included...
Is there some
55 matches
Mail list logo
