Re: Suppress error messages

On 2022-03-01 18:30 -0600, sunnycemet...@gmail.com wrote: > Consider appending the macro chain with . That works out pretty nicely indeed, thanks! -- Akshay.

Re: Suppress error messages

Consider appending the macro chain with .

Re: Unexplained mutt error

On Fri, Feb 25, 2022 at 06:25:01PM -0600, Ranjan Maitra wrote: On Fri Feb25'22 04:31:32PM, Jon LaBadie wrote: From: Jon LaBadie Date: Fri, 25 Feb 2022 16:31:32 -0500 To: mutt-users@mutt.org Subject: Re: Unexplained mutt error On Fri, Feb 25, 2022 at 01:33:52PM -0600, Ranjan Maitra

Re: Unexplained mutt error

On Fri Feb25'22 04:31:32PM, Jon LaBadie wrote: > From: Jon LaBadie > Date: Fri, 25 Feb 2022 16:31:32 -0500 > To: mutt-users@mutt.org > Subject: Re: Unexplained mutt error > > On Fri, Feb 25, 2022 at 01:33:52PM -0600, Ranjan Maitra wrote: > > > > My apologies, I

Re: Unexplained mutt error

On Fri, Feb 25, 2022 at 01:33:52PM -0600, Ranjan Maitra wrote: My apologies, I guess I was not at all clear in my question. I want a hook which if I press "r" would give me a query about if I want to answer to the list or reply to the sender. Doesn't the "reply_to" setting allow you to do tha

Re: Unexplained mutt error

On Fri Feb25'22 01:29:14PM, Kurt Hackenberg wrote: > From: Kurt Hackenberg > Date: Fri, 25 Feb 2022 13:29:14 -0500 > To: mutt-users@mutt.org > Subject: Re: Unexplained mutt error > > On 2022/02/25 10:53, Ranjan Maitra wrote: > > > Regardless, actually I think that

Re: Unexplained mutt error

On 2022/02/25 10:53, Ranjan Maitra wrote: Regardless, actually I think that all I would be happy with would be a query or something that alerts me to the fact that I am potentially writing to an individual address (or a list) (for when I am on a list, but not in general, because then I start

Re: Unexplained mutt error

* Ranjan Maitra [02-25-22 10:54]: > On Fri Feb25'22 07:00:05AM, Charles Cazabon wrote: > > From: Charles Cazabon > > Date: Fri, 25 Feb 2022 07:00:05 -0600 > > To: mutt-users@mutt.org > > Subject: Re: Unexplained mutt error > > > > Kurt Hackenberg wro

Re: Unexplained mutt error

Ranjan Maitra wrote: > On Fri Feb25'22 07:00:05AM, Charles Cazabon wrote: > > > > That's the right solution, but I've also seen people configure their MDA > > to add a Reply-To: header to incoming list messages that don't have them. > > I see: I use fetchmail and then procmail for fetching email.

Re: Unexplained mutt error

On Fri Feb25'22 07:00:05AM, Charles Cazabon wrote: > From: Charles Cazabon > Date: Fri, 25 Feb 2022 07:00:05 -0600 > To: mutt-users@mutt.org > Subject: Re: Unexplained mutt error > > Kurt Hackenberg wrote: > > On 2022/02/22 18:10, Ranjan Maitra wrote: > > >

Re: Unexplained mutt error

Kurt Hackenberg wrote: > On 2022/02/22 18:10, Ranjan Maitra wrote: > > > As an aside, for others: is there, in .muttrc a way to set things such > > that hitting "r" would automatically switch to reply list ("L") for > > specific folders? [...] > It's possible to change key bindings, so maybe you

Re: Unexplained mutt error

On 2022/02/22 18:10, Ranjan Maitra wrote: As an aside, for others: is there, in .muttrc a way to set things such that hitting "r" would automatically switch to reply list ("L") for specific folders? I have seen that for some list mail, "r" responds to list, and for others, to the sender. So

Re: Unexplained mutt error

I think the OPs problem is with sending, not accessing email. Ranjan On Wed Feb23'22 02:29:12AM, Sam Kuper wrote: > From: Sam Kuper > Date: Wed, 23 Feb 2022 02:29:12 + > To: mutt-users@mutt.org > Subject: Re: Unexplained mutt error > > On Tue, Feb 22, 2022 at 04:4

Re: Unexplained mutt error

On Tue, Feb 22, 2022 at 04:40:06PM -0600, Ion wrote: > Thanks to all of you for trying to solve my problem. But I have been > trying to setup mutt for nine days now. I have followed all your > advice and instructions to the best of my ability, to no avail. [...] > Much as I want to use a CLI clie

Re: Unexplained mutt error

Can't type, sorry. No apostrophe at the end. > This got mangled. set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465"; set ssl_force_tls = yes; set ssl_starttls = yes or set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465" set ssl_force_tls = yes set ssl_starttls = yes Ho

Re: Unexplained mutt error

or specific > folders? > > I have seen that for some list mail, "r" responds to list, and for others, to > the sender. > > Many thanks and best wishes, > Ranjan > > > > > On Tue Feb22'22 04:40:06PM, Ion wrote: > > From: Ion > > Date: T

Re: Unexplained mutt error

best wishes, Ranjan On Tue Feb22'22 04:40:06PM, Ion wrote: > From: Ion > Date: Tue, 22 Feb 2022 16:40:06 -0600 > To: mutt-users@mutt.org > Subject: Re: Unexplained mutt error > > Thanks to all of you for trying to solve my problem. But I have been > trying to setup mutt f

Re: Unexplained mutt error

onm...@eml.cc@smtp.fastmail.com:465" set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465" Thanks Ranjan - that's right.  Remember port 465 uses smtps:// both produced "Invalid SMTP URL: smtp.fastmail.com:465" Check your muttrc to make sure you don't h

Re: Unexplained mutt error

465" set smtp_url ="smtps://ionm...@eml.cc@smtp.fastmail.com:465" Thanks Ranjan - that's right. Remember port 465 uses smtps:// both produced "Invalid SMTP URL: smtp.fastmail.com:465" Check your muttrc to make sure you don't have the value specified twice or s

Re: Unexplained mutt error

On Tue Feb22'22 02:06:57PM, Ion wrote: > From: Ion > Date: Tue, 22 Feb 2022 14:06:57 -0600 > To: mutt-users@mutt.org > Subject: Re: Unexplained mutt error > > On 21/02/2022 21:53, Kevin J. McCarthy wrote: > > > On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote:

Re: Unexplained mutt error

On 21/02/2022 21:53, Kevin J. McCarthy wrote: On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote: I tried both set smtp_url ="smtp://smtp.fastmail.com:465" and set smtp_url ="smtp://smtp.fastmail.com:587" and got "SMTP session failed: 530 5.7.1 Authentication required". You'll need to add yo

Re: Unexplained mutt error

I have already done that. On 22/02/2022 08:42, José María Mateos wrote: On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote: I used the same password as IMAP as the Fastmail help page tells me "Your app-specific password. You cannot use your regular Fastmail password." So does the "set ssl_forc

Re: Unexplained mutt error

On Tue, Feb 22, 2022 at 09:42:46AM -0500, José María Mateos wrote: On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote: I used the same password as IMAP as the Fastmail help page tells me "Your app-specific password. You cannot use your regular Fastmail password." So does the "set ssl_force_tls

Re: Unexplained mutt error

On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote: I used the same password as IMAP as the Fastmail help page tells me "Your app-specific password. You cannot use your regular Fastmail password." So does the "set ssl_force_tls =yes" not cover authentication? You need to create a password to u

Re: Unexplained mutt error

On Mon, Feb 21, 2022 at 06:10:51PM -0600, Ion wrote: I tried both set smtp_url ="smtp://smtp.fastmail.com:465" and set smtp_url ="smtp://smtp.fastmail.com:587" and got "SMTP session failed: 530 5.7.1 Authentication required". You'll need to add your username to the $smtp_url, so something like

Re: Unexplained mutt error

cific password. You cannot use your regular Fastmail password." So does the "set ssl_force_tls =yes" not cover authentication? On 21/02/2022 16:40, Kevin J. McCarthy wrote: On Mon, Feb 21, 2022 at 02:46:11PM -0600, Ion wrote: set smtp_url ="smtp://smtp.fastmail.com:465" But

Re: Unexplained mutt error

On Mon, Feb 21, 2022 at 02:46:11PM -0600, Ion wrote: set smtp_url ="smtp://smtp.fastmail.com:465" But the response was... "SMTP session failed: read error" The prefix 'smtps://' should be used with port 465: set smtp_url ="smtps://smtp.fastmail.com:46

Re: Unexplained mutt error

" set record ="+Sent Items" set postponed="+Drafts" set trash = "+Trash" set editor ="nano" set timeout=15 set mail_check=1 set check_new=yes auto_view text/html But the response was... "SMTP session failed: read error"

Suppress error messages

Hello, I've been trying to find a way to suppress error messages in a macro or a key binding that I create. I couldn't find a builtin way to do so by reading through the docs and searching online. To provide a basic example, I have a macro to open the error history, scrolling to the

Re: Unexplained mutt error

On Sun, Feb 20, 2022 at 03:37:45PM -0500, Kurt Hackenberg wrote: > On Sun, Feb 20, 2022 at 01:10:11PM -0600, Hokan wrote: > > >Replying to the sender seems to be the default behavior for the list. > > Do y'all know about the command 'L' ? > > See the manual: >

Re: Unexplained mutt error

On Sun, Feb 20, 2022 at 01:10:11PM -0600, Hokan wrote: >Replying to the sender seems to be the default behavior for the list. Do y'all know about the command 'L' ? See the manual:

Re: Unexplained mutt error

On 20/02/2022 14:41, Kevin J. McCarthy wrote: On Sun, Feb 20, 2022 at 01:49:45PM -0600, Ion wrote: Here are my account settings from Thunderbird. They work. IMAP server mail.messagingengine.com ionm...@eml.cc 993 SSL/TLS SMTP server smtp.pobox.com i...@pobox.com 587 STARTTLS So doesn't that

Re: Unexplained mutt error

On Sun, Feb 20, 2022 at 01:49:45PM -0600, Ion wrote: Here are my account settings from Thunderbird. They work. IMAP server mail.messagingengine.com ionm...@eml.cc 993 SSL/TLS SMTP server smtp.pobox.com i...@pobox.com 587 STARTTLS So doesn't that indicate that I have an accessible "Sent" folder?

Re: Unexplained mutt error

ay also be useful to run mutt in debug mode, e.g. with '-d 2' as an argument.  If it's compiled with debug mode, that will generate a file, ~/.muttdebug0 with commands sent to the SMTP and IMAP servers.  Perhaps that will give a clue as to where the error is coming from. Unfortunately DEBUG was not defined during compilation, and I don't think I am sufficiently advance to compile it.

Re: Unexplained mutt error

* Hokan [02-20-22 14:11]: > Replying to the sender seems to be the default behavior for the list. > > Perhaps the list owner could set the "Reply-to" header to help with this. > > > On Sun, Feb 20, 2022 at 10:37:22AM -0800, Kevin J. McCarthy wrote: > > Please don't reply to me personally, it's

Re: Unexplained mutt error

ite to? Perhaps you could try another mailbox that you are sure exists and you can write to? It may also be useful to run mutt in debug mode, e.g. with '-d 2' as an argument. If it's compiled with debug mode, that will generate a file, ~/.muttdebug0 with commands sent to

Re: Unexplained mutt error

On 20/02/2022 12:37, Kevin J. McCarthy wrote: Please don't reply to me personally, it's poor etiquette.  Redirecting back to the mailing list. Understood. I apologize. On Sun, Feb 20, 2022 at 11:55:06AM -0600, Ion wrote: Thanks for the speedy reply. There was no prompt. So I added "set confi

Re: Unexplained mutt error

Replying to the sender seems to be the default behavior for the list. Perhaps the list owner could set the "Reply-to" header to help with this. On Sun, Feb 20, 2022 at 10:37:22AM -0800, Kevin J. McCarthy wrote: > Please don't reply to me personally, it's poor etiquette. -- Hokan Bicyclist Sysa

Re: Unexplained mutt error

Please don't reply to me personally, it's poor etiquette. Redirecting back to the mailing list. On Sun, Feb 20, 2022 at 11:55:06AM -0600, Ion wrote: Thanks for the speedy reply. There was no prompt. So I added "set confirmcreate = yes" to my .muttrc file and tried gain. No change. Another obse

Re: Unexplained mutt error

On Sun, Feb 20, 2022 at 10:56:05AM -0600, Ion wrote: ...while executing mutt and using the menus, with the same addresses leaves me with... Code: CREATE failed: Permission denied That's an IMAP permission error. It would usually be preceded by a prompt to create a mailbox that doesn&#x

Unexplained mutt error

New user. Gecko Linux O.S. My incoming mail goes to pobox.com and is redirected to ionm...@eml.cc. It shows up in mutt. My outgoing mail is sent to smtp.pobox.com. This method works... Code: :~> echo "" | mutt -s "subject" -i file.txt  ionm...@gmx.us ...while executing mutt and using the menus,

Re: Strange error with mairix and a maildir stored by mutt

On Thu, Mar 25, 2021 at 05:08:58PM -0400, Kurt Hackenberg wrote: > On 2021/03/25 16:37, Chris Green wrote: > > > Brilliant! :-) That was it. I've not seen an error like that before > > but I guess it must be because of when I did something to that message > > rela

Re: Strange error with mairix and a maildir stored by mutt

On 2021/03/25 16:37, Chris Green wrote: Brilliant! :-) That was it. I've not seen an error like that before but I guess it must be because of when I did something to that message relative to when the mairix index was built. You replied to that message. That's what the R in th

Re: Strange error with mairix and a maildir stored by mutt

On Thu, Mar 25, 2021 at 03:56:41PM -0400, Kurt Hackenberg wrote: > On 2021/03/25 14:19, Chris Green wrote: > > > However I'm now getting a rather odd error on one particular message > > when I search using mairix:- > > > > chris@esprimo$ mairix 183493 >

Re: Strange error with mairix and a maildir stored by mutt

On 2021/03/25 14:19, Chris Green wrote: However I'm now getting a rather odd error on one particular message when I search using mairix:- chris@esprimo$ mairix 183493 stat '/home/chris/mail/folder/shopping/food/wine/cur/1612869077.1202519_3.esprimo:2,S': No such fi

Strange error with mairix and a maildir stored by mutt

I use maildir with mutt and mairix, I changed from mbox several months ago. It has been working reliably for all these months. However I'm now getting a rather odd error on one particular message when I search using mairix:- chris@esprimo$ mairix 183493 stat '/home/chris/m

Re: Passphrase error

On 2021-02-07 09:27:03, Rob Pyott wrote: > Hello Mutt team! > > I installed Mutt on AntiX Linux and can read my Yahoo mail. When > sending though, I’m asked for a passphrase. I don’t have one, so then > I get “no key specified” and I can’t send. > > My muttrc is basic with nothing on passphrase o

Passphrase error

Hello Mutt team! I installed Mutt on AntiX Linux and can read my Yahoo mail. When sending though, I’m asked for a passphrase. I don’t have one, so then I get “no key specified” and I can’t send. My muttrc is basic with nothing on passphrase or SMIME. Any suggestions? Thanks!

Re: error in displaying pdf

Yes, this group is amazing! I should have asked earlier. On Thursday, December 3, 2020, 7:56:33 AM CST, José María Mateos wrote: On Thu, Dec 03, 2020 at 03:30:47AM +, Globe Trotter via Mutt-users wrote: >Thank you very much! This works. Thanks very much from me too. This has be

Re: error in displaying pdf

On Thu, Dec 03, 2020 at 03:30:47AM +, Globe Trotter via Mutt-users wrote: Thank you very much! This works. Thanks very much from me too. This has been bothering me for a while but never thought there could be a very simple solution :-) Cheers, -- José María (Chema) Mateos || https://rin

Re: error in displaying pdf

Thank you very much! This works. On Wednesday, December 2, 2020, 11:44:24 AM CST, Zenithal wrote: > '=?utf-8?Q?efficient=5Fkkmeans.pdf?=' This is RFC2047-encoded MIME parameters. You may add set rfc2047_parameters = yes in your muttrc. -- GPG Fingerprint: 1127F188280AE31236193329

Re: error in displaying pdf

> '=?utf-8?Q?efficient=5Fkkmeans.pdf?=' This is RFC2047-encoded MIME parameters. You may add set rfc2047_parameters = yes in your muttrc. -- GPG Fingerprint: 1127F188280AE3123619332987E17EEF9B18B6C9 signature.asc Description: PGP signature

error in displaying pdf

Hi, I have a strange issue in that my pdf attachments (or at least some of them) are getting their names converted to something like: '=?utf-8?Q?efficient=5Fkkmeans.pdf?=' in mutt. I don't think that this happened before. As a result, this is not being identified as a pdf and my mailcap file

Re: FCC error, may be caused by missing dir ~/Mail

rence would be removing an error message for you versus ignoring an error that another user ought to be notified of. I'm performing a release this weekend, so am a bit distracted now; but I invite you to start a discussion about this on mutt-dev. I'd like some of the other (i.e. wiser

Re: FCC error, may be caused by missing dir ~/Mail

El día viernes, noviembre 06, 2020 a las 10:02:46a. m. -0800, Ian Zimmerman escribió: > On 2020-11-06 08:25, Matthias Apitz wrote: > > > See also man page of wait(2): the errno=ECHILD: > > >ECHILD (for waitpid() or waitid()) The process specified by pid > >(waitpid()) or idtype

Re: FCC error, may be caused by missing dir ~/Mail

On 2020-11-06 08:25, Matthias Apitz wrote: > See also man page of wait(2): the errno=ECHILD: >ECHILD (for waitpid() or waitid()) The process specified by pid >(waitpid()) or idtype and id (waitid()) does not exist or is >not a child of the calling process. (This can happe

Re: FCC error, may be caused by missing dir ~/Mail

self isn't the culprit perhaps. > > Okay, it definitely sounds like something beyond my ability to assist > deeply. :-) > > From Mutt's point of view, it is looking for the exit code after > waitpid() finishes. If there is an error from waitpid() or the > WEXIT

Re: FCC error, may be caused by missing dir ~/Mail

prit perhaps. > > Okay, it definitely sounds like something beyond my ability to assist > deeply. :-) > > From Mutt's point of view, it is looking for the exit code after > waitpid() finishes. If there is an error from waitpid() or the > WEXITSTATUS is not 0,

Re: FCC error, may be caused by missing dir ~/Mail

iew, it is looking for the exit code after waitpid() finishes. If there is an error from waitpid() or the WEXITSTATUS is not 0, then Mutt will print that message out. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature

Re: FCC error, may be caused by missing dir ~/Mail

-d4 -e "set sendmail=\"cat --\"" ... | sendmail -t > > I see. But wouldn't the recipients be appended to $sendmail, and then > cat complain with an error message (and error code) that the "recipient" > filenames couldn't be found? The error

Re: FCC error, may be caused by missing dir ~/Mail

$sendmail, and then cat complain with an error message (and error code) that the "recipient" filenames couldn't be found? The error code would then cause Mutt to report an error invoking $sendmail... -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 80

Re: FCC error, may be caused by missing dir ~/Mail

El día jueves, noviembre 05, 2020 a las 10:17:25a. m. -0800, Kevin J. McCarthy escribió: > >Thanks for the reply. The used mutt is version 1.18.3 (see debug log > >below). I put a tee command between mut and sendmail to see what mutt > >is spilling out to sendmail: > > > > ... | mutt -d4 |

Re: FCC error, may be caused by missing dir ~/Mail

On Thu, Nov 05, 2020 at 09:41:55AM +0100, Matthias Apitz wrote: El día miércoles, noviembre 04, 2020 a las 09:33:34a. m. -0800, Kevin J. McCarthy escribió: On Wed, Nov 04, 2020 at 01:17:44PM +0100, Matthias Apitz wrote: >We use mutt in batch mode to assemble mails with all attachments etc. >an

Re: FCC error, may be caused by missing dir ~/Mail

ndmail -t which works also > >fine. But is complaining on STDERR that the mail could not be sent with > > > >Could not send the message. > > > >I looked into the source send.c and the error message is triggered by > >some internal FCC error, perhaps just due to the mi

Re: FCC error, may be caused by missing dir ~/Mail

message. I looked into the source send.c and the error message is triggered by some internal FCC error, perhaps just due to the missing ~/Mail dir or something the like. The mail is sent fine. You didn't mention what version of Mutt you are using on the server. There has been a fair amou

FCC error, may be caused by missing dir ~/Mail

mail to /usr/lib/sendmail -t which works also fine. But is complaining on STDERR that the mail could not be sent with Could not send the message. I looked into the source send.c and the error message is triggered by some internal FCC error, perhaps just due to the missing ~/Mail dir or something

FETCH Server error while fetching messages

Wasn't happening earlier today. No apparent error with MacOS Mail.app I deleted all recent messages and emptied Trash. Happens on both BunselLabs under VirtualBox and Raspberry Pi 506 $ uname -a Linux RaspbPi-3-2700 4.14.93-v7+ #1191 SMP Wed Jan 16 11:53:33 GMT 2019 armv7l GNU/Linux 507 $

Re: SMTP error from remote mail server after RCPT TO:

El día viernes, octubre 26, 2018 a las 03:47:03p. m. -0500, Hokan escribió: > This rejection is the result of the "percent hack" implimented on > sendmail, postfix and, perhaps, other mail servers. > > Nothing to do with Mutt. Yes, it's a bit off-topic. And, thanks for the pointer to that "perce

Re: SMTP error from remote mail server after RCPT TO:

very failed: returning message to sender > > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > jw%leserin

SMTP error from remote mail server after RCPT TO:

This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: jw%leserini-...@gmx.de host 172.16.28.206 [172.16.28.206] SMTP error from remote

Re: Re: Firefox throw can't find temp file error

On 08/13, David Woodfall wrote: On Monday 13 August 2018 10:55, dekkz...@gmail.com put forth the proposition: Hi I've noticed recently after i've finished in mutt Firefox has a tab open with an error saying it cant find a temp file that mutt sent it. Any ideas? What do you h

Re: Firefox throw can't find temp file error

On Wed, Aug 15, 2018 at 12:55:03PM +0200, Till Smejkal wrote: > On Mon, 13 Aug 2018, Francesco Ariis wrote: > You can change your mailcap maybe so that it creates a copy of the file > to show before calling firefox. Copying to /tmp and then open it worked like a charm, thanks again!

Re: Firefox throw can't find temp file error

Hello Till, On Wed, Aug 15, 2018 at 12:55:03PM +0200, Till Smejkal wrote: > I guess the difference and hence the problem is, that if firefox is already > running, > the firefox process started via mailcap will actually not do anything except > signaling the main process to open the file. However,

Re: Firefox throw can't find temp file error

On Mon, 13 Aug 2018, Francesco Ariis wrote: > On Mon, Aug 13, 2018 at 08:22:59PM +0200, Matthias Apitz wrote: > > Well, verifying the identity of an unknown person with some server over the > > Inrernet is not very reliable, isn't it? > > Interesting but I suppose we should keep this OT. > > OP,

Re: Firefox throw can't find temp file error

On Mon, Aug 13, 2018 at 08:22:59PM +0200, Matthias Apitz wrote: > Well, verifying the identity of an unknown person with some server over the > Inrernet is not very reliable, isn't it? Interesting but I suppose we should keep this OT. OP, I too have a similar problem: if I try to open a text/html

Re: Firefox throw can't find temp file error

On Monday, 13 August 2018 18:59:38 CEST, David Woodfall wrote: On Monday 13 August 2018 13:46, Matthias Apitz put forth the proposition: El día Monday, August 13, 2018 a las 12:34:08PM +0100, David Woodfall escribió: ... > PS: > > Do you have your key on a keyserver somewhere? I got a huge 3

Re: Firefox throw can't find temp file error

On Monday 13 August 2018 13:46, Matthias Apitz put forth the proposition: > El día Monday, August 13, 2018 a las 12:34:08PM +0100, David Woodfall > escribió: > > ... > > PS: > > > > Do you have your key on a keyserver somewhere? I got a huge 30 sec > > delay opening this because I only have keys.

Re: Firefox throw can't find temp file error

El día Monday, August 13, 2018 a las 12:34:08PM +0100, David Woodfall escribió: ... > PS: > > Do you have your key on a keyserver somewhere? I got a huge 30 sec > delay opening this because I only have keys.gnupg.net set as > keyserver. Not sure if there more popular ones these days? Dave, do yo

Re: Firefox throw can't find temp file error

On Monday 13 August 2018 10:55, dekkz...@gmail.com put forth the proposition: > Hi > > I've noticed recently after i've finished in mutt Firefox has a tab open with > an error saying it cant find a temp file that mutt sent it. > > Any ideas? What do you have in you

Firefox throw can't find temp file error

Hi I've noticed recently after i've finished in mutt Firefox has a tab open with an error saying it cant find a temp file that mutt sent it. Any ideas? -- regards. Dekks Herton Thinkpad T61 2.0Ghz 2GB WSXGA+ Jabber IM: dekkz...@jabber.hot-chilli.net signature.asc Descri

Re: GPGME error

On Thu, Mar 15, 2018 at 10:03:22AM +, Darac Marjal wrote: > I managed to see it read "[setting sender] mailbox ...". That was > enough for me to find the function "void mutt_gpgme_set_sender()". > > I can see that this function sets the sender for gpgme (presumably so it > knows who to sign as

GPGME error

Hello all, For a while now, when I sign messages with GPG, I see an error message flash up briefly before being replaced by the signing prompt. Up until now, I'd not been able to read the message before it disappeared, but today (perhaps my terminal was being a bit slow) I managed to s

Re: configure: error: could not find sasl lib

On Fri, Dec 29, 2017 at 04:04:43PM -0500, Todd Zullinger wrote: > Cameron Simpson wrote: > >> Another interesting thing is that although mutt doesn't finally send the > >> mail, msmtp reports it as sent. I mean that in the sent file of msmtp you > >> can > >> find: > > > > The tail of your messag

Re: configure: error: could not find sasl lib

On 31Dec2017 08:29, Cameron Simpson wrote: On 29Dec2017 16:04, todd zullinger wrote: Cameron Simpson wrote: The tail of your message from this point seems to be missing. Perhaps you're reading this from an mbox and the leading From_ line was not escaped Cameron? It's present in the origina

Re: configure: error: could not find sasl lib

On 29Dec2017 16:04, todd zullinger wrote: Cameron Simpson wrote: Another interesting thing is that although mutt doesn't finally send the mail, msmtp reports it as sent. I mean that in the sent file of msmtp you can find: The tail of your message from this point seems to be missing. Perhaps

Re: configure: error: could not find sasl lib

Cameron Simpson wrote: >> Another interesting thing is that although mutt doesn't finally send the >> mail, msmtp reports it as sent. I mean that in the sent file of msmtp you can >> find: > > The tail of your message from this point seems to be missing. Perhaps you're reading this from an mbox a

Re: configure: error: could not find sasl lib

ot; And this is the error: checking whether SSL_set_mode is declared... yes checking whether SSL_MODE_AUTO_RETRY is declared... yes checking whether X509_V_FLAG_PARTIAL_CHAIN is declared... yes checking for library containing sasl_encode64... no configure: error: could not find sasl lib but, I ha

configure: error: could not find sasl lib

Hello, I'm building mutt-1.9.2 from source, and I'm having a problem with sasl in the ./configure stage: ./configure --prefix=/usr --enable-imap --enable-smtp --enable-debug \ --with-ssl --with-gnutls --with-sasl SENDMAIL="/usr/local/bin/msmtp" And this is the err

Re: Inermittant error downloading gmail to mutt

On Tue, Dec 05, 2017 at 16:46:02 +1100, Brian Salter-Duke wrote: > sslcertpath '***' No, gmail has rotated their top-level certificates. You'll need a new certificate chain. Attached is the one I extracted yesterday. --Ben -BEGIN CERTIFICATE- MIIEgjCCA2qgAwIBAgIIXd5P76LAUKc

Re: Inermittant error downloading gmail to mutt

* Brian Salter-Duke [12-05-17 00:51]: > I am increasing getting an error when I try to download my gmail email into > mutt. Clearly it is not a mutt error, but maybe some mutters can help me. > > I use a script that includes:- > > fetchmail -f ~/.fetchmailrc-gmail --keep >

Re: New mutt GPGME error

On Fri, Jun 02, 2017 at 09:10:01AM -0400, Mark H. Wood wrote: > > I'm another Gentoo user. I unmasked Mutt 1.8.2-r2 to see if it > would help a problem I was having with some S/MIME signed messages, > and that pulled in gpgme 1.8.0-r3. I have fewer problems now with > S/MIME and no new issues. E

Re: New mutt GPGME error

I'm another Gentoo user. I unmasked Mutt 1.8.2-r2 to see if it would help a problem I was having with some S/MIME signed messages, and that pulled in gpgme 1.8.0-r3. I have fewer problems now with S/MIME and no new issues. -- Mark H. Wood Lead Technology Analyst University Library Indiana Univ

Re: New mutt GPGME error

On Thu, Jun 01, 2017 at 02:58:56PM -0700, Ian Zimmerman wrote: > On 2017-06-02 04:51, Ben McGinnes wrote: > >> There shouldn't be. While new functions are periodically added to >> GPGME as features are added to GPG and its related projects, >> efforts are made not to change existing functions. >

Re: New mutt GPGME error

On 2017-06-02 04:51, Ben McGinnes wrote: > There shouldn't be. While new functions are periodically added to > GPGME as features are added to GPG and its related projects, efforts > are made not to change existing functions. I think I found it: https://bugs.gentoo.org/show_bug.cgi?id=600600 Mo

Re: New mutt GPGME error

On Thu, Jun 01, 2017 at 12:28:07PM -0700, Kevin J. McCarthy wrote: > On Thu, Jun 01, 2017 at 11:09:40AM -0700, Ian Zimmerman wrote: >> Is there a good reason for this restriction, i.e. a known >> incompatibility with gpgme-1.8 and later? > > I'm compiling against gpgme 1.8.0, and am not aware of a

Re: New mutt GPGME error

On Thu, Jun 01, 2017 at 11:09:40AM -0700, Ian Zimmerman wrote: > Is there a good reason for this restriction, i.e. a known > incompatibility with gpgme-1.8 and later? I'm compiling against gpgme 1.8.0, and am not aware of any issues. I haven't tested against 1.9.0 yet, but haven't received any re

Re: New mutt GPGME error

urged, but that work hasn't been done yet and it's highly unlikely that any of it will affect Mutt, either adversely or otherwise. That's all the GTK2 stuff that's buried in there, some of which is used with GPA, but most of it isn't used by anything. This was an error in GPG&

Re: New mutt GPGME error

On 2017-05-30 10:00, Kevin J. McCarthy wrote: > > I just upgraded to Ubuntu 17.04 and got a new version of mutt: 1.7.2.1 > > > > I now frequently get the following error message for delivered mail: > > > > "GPGME: CMS protocol not available" &g

Re: New mutt GPGME error

On Tue, May 30, 2017 at 06:57:00AM -0700, Jeffery Small wrote: > > I just upgraded to Ubuntu 17.04 and got a new version of mutt: 1.7.2.1 > > I now frequently get the following error message for delivered mail: > > "GPGME: CMS protocol not available" > >

New mutt GPGME error

I just upgraded to Ubuntu 17.04 and got a new version of mutt: 1.7.2.1 I now frequently get the following error message for delivered mail: "GPGME: CMS protocol not available" I'm not using gpg and would like to stop the continual generation of these messages. I'm

  1   2   3   4   5   6   >