Bug#1024427: reproducible segfault in bullseye mutt

Note this was fixed in Mutt 2.2.8. See https://gitlab.com/muttmua/mutt/-/issues/428 for the Mutt bug report. This important fix is at: https://gitlab.com/muttmua/mutt/-/commit/48b6ea32e21db8b580cd3ca8c346c3e2c22756f6.patch There are two related commits, that may be of interest in

Bug#990828: mutt can not delete mails due to access rights

On Mon, Nov 21, 2022 at 02:53:14PM +0100, Juan Pedro Vallejo wrote: Yes, you were right. Architecture: i386 (i686) Thank you Juan. So you are running the i386 mutt package on an i386 architecture. I believe this means something is wrong the package building environment. I've just looked

Bug#990828: mutt can not delete mails due to access rights

On Sun, Nov 20, 2022 at 01:50:41PM +0100, Juan Pedro Vallejo wrote: "mutt_dotlock" is the one to blame: # ls -l /usr/bin/mutt_dotlock -rwxr-sr-x 1 root root 13804 Nov 13 18:01 /usr/bin/mutt_dotlock This works for me: # chown root:mail /usr/bin/mutt_dotlock #

Bug#1023599: mutt: FTBFS due to lack of gpgme-config since gpgme1.0 1.18.0-2

I've just released mutt 2.2.9, which I believe should fix this problem. -Kevin signature.asc Description: PGP signature

Bug#1023599: mutt: FTBFS due to lack of gpgme-config since gpgme1.0 1.18.0-2

On Mon, 7 Nov 2022 13:04:04 +0100 Vincent Lefevre wrote: The gpgme-config utility was removed in gpgme1.0 1.18.0-2 (because it needs gpg-error-config, which has been removed). As a consequence the use of --enable-gpgme to build Mutt yields an error: Just as a note, with Vincent's help, I've

Bug#1014524: mutt: Mutt depends on moreutils package, but, it is not listed on dependencies, nor suggestions

On Thu, 7 Jul 2022 08:17:26 -0300 Marcelo Laia wrote: Mutt depends on moreutils package, but, it is not listed on dependencies, nor suggestions. I see that pee is necessary to open html messages. With out moreutils package, when I try to open a html messages, it shows: sh: 1: pee not found

Bug#1009791: mutt: change-folder no longer selects next folder with new mail

On Sat, 30 Apr 2022 13:39:07 -0700 "Kevin J. McCarthy" wrote: On Thu, Apr 28, 2022 at 01:36:10PM -0700, Kevin J. McCarthy wrote: >I don't know if you've compiled Mutt from git before, but if you are >able and willing to try, I would appreciate hearing it that helped >with y

Bug#1010915: mutt: GSSAPI SMTP authentication no longer works

I've pushed the fix into the stable branch: , and will release 2.2.5 in the next few days. My apologies for the botched patch file included in my previous email. I realized I did this when backing out

Bug#1010915: mutt: GSSAPI SMTP authentication no longer works

On Fri, May 13, 2022 at 11:24:44PM +, brian m. carlson wrote: I built the Debian package with the patch applied below. It didn't quite apply cleanly with patch -p1, but I copied and pasted the change. It does appear to work, and I'm using the patched version to send this. Thanks so much

Bug#1010915: mutt: GSSAPI SMTP authentication no longer works

On Fri, 13 May 2022 15:02:38 -0700 "Kevin J. McCarthy" wrote: > Thanks for the bug report. Yes, it most definitely is. I'll take a > look to see what I can find. Perhaps I've missed setting up some > callback information that gsasl needs. > > Would you be able to test

Bug#1010915: mutt: GSSAPI SMTP authentication no longer works

On Fri, 13 May 2022 17:54:14 +0200 wrote: I've run into this issue too, and it is clearly gsasl which is broken: [2022-05-13 17:40:38] smtp_authenticate: Trying method GSSAPI LOGIN PLAIN [2022-05-13 17:40:38] mutt_gsasl_get_mech() returned no usable mech [2022-05-13 17:40:38] No authenticators

Bug#1010915: mutt: GSSAPI SMTP authentication no longer works

On Fri, 13 May 2022 01:58:53 + "brian m. carlson" wrote: I use Kerberos on my personal network at home, and therefore I use GSSAPI authentication for IMAP and SMTP. While GSSAPI with IMAP works fine, recently, GSSAPI with SMTP stopped working. I suspect this is related to the move to

Bug#1010658: set smtp_authenticators=login works!

On Thu, May 12, 2022 at 04:57:55PM +0200, Václav Ovsík wrote: I have added set smtp_authenticators=login and things works now! Great! Thank you for checking that LOGIN works properly. I wanted to make sure there weren't other problems I needed to address inside Mutt. So the problem is

Bug#1010658: mutt: SMTP SASL authentication broken (base64 encoding?)

On Fri, 6 May 2022 13:04:50 -0700 "Kevin J. McCarthy" wrote: However, in the mean time I've pushed a commit up to branch 'kevin/gsasl-smtp-plain-workarounds' on gitlab: I've merged this branch into stable, and it will be a part of 2.2.5 sometime in the next few weeks.

Bug#599309: mutt: Reply->Postpone->Recall loses message associations

On Thu, 30 Dec 2010 13:56:51 + Antonio Radici wrote: tag 599309 +confirmed upstream thanks Hi Toni, thanks for your report, I will forward this issue upstream. The threading issue was fixed upstream in commits 1) 3c44f482

Bug#1010658: mutt: SMTP SASL authentication broken (base64 encoding?)

On Fri, 6 May 2022 11:18:39 -0700 "Kevin J. McCarthy" wrote: According to my understanding of RFC4954, the "server challenge" 334 response must either be blank (i.e., "334 "), or if there is data it must be base64 encoded. I'm still interested to hear if 'set sm

Bug#1010658: mutt: SMTP SASL authentication broken (base64 encoding?)

On Fri, 06 May 2022 12:03:27 +0200 Vaclav Ovsik wrote: after Mutt upgrade from version 2.1.4-1 to version 2.2.3-2 SASL authentication stopped working. Debug from Mutt version 2.2.3: [...] [2022-05-06 10:33:39] smtp_auth_gsasl: using mech PLAIN [2022-05-06 10:33:39] Authenticating

Bug#1010500: mutt: Testing upgrade to 2.2.3-2 breaks sending mail

On Tue, May 03, 2022 at 12:00:44PM -0400, ant wrote: i don't explicitly set that variable anywhere in any of my mutt profiles that i know of. unsetting that does allow mutt to send mail again using the 2.2.3-2 version so that did take care of the problem. thank you! :) I'm glad that fixed

Bug#1010500: mutt: Testing upgrade to 2.2.3-2 breaks sending mail

On Mon, 2 May 2022 20:35:13 -0700 "Kevin J. McCarthy" wrote: I'll try to see if I can duplicate the problem, but I don't have access to a smtp server supporting cram-md5. Is the server you are using accessible for me to try (and of course fail) authenticating with? I've just n

Bug#1010500: mutt: Testing upgrade to 2.2.3-2 breaks sending mail

On Mon, 02 May 2022 19:20:29 -0400 ant wrote: Package: mutt Version: 2.2.3-1 Just checking this is for 2.2.3-2. That update switched to the gsasl library, which unfortunately needs some bugs worked out with its mutt implementation. :-( From the debug log, it looks like you have

Bug#1009791: mutt: change-folder no longer selects next folder with new mail

On Thu, Apr 28, 2022 at 01:36:10PM -0700, Kevin J. McCarthy wrote: I don't know if you've compiled Mutt from git before, but if you are able and willing to try, I would appreciate hearing it that helped with your problem. I've just released version 2.2.4 with a fix that I believe will also

Bug#1009791: mutt: change-folder no longer selects next folder with new mail

On Wed, 27 Apr 2022 15:10:09 -0700 "Kevin J. McCarthy" wrote: One change in 2.2.x was normalizing Maildir paths when opening them (as IMAP does) - removing a trailing delimiter. This might cause the behavior you are describing. Until I hear otherwise, I've been assuming t

Bug#632570: fails to join RFC 2231 continuations

On Mon, 13 Dec 2021 19:34:21 -0800 "Kevin J. McCarthy" wrote: I believe this was fixed in Mutt 1.6.0, and this ticket can be closed. Again, this bug should be close-able. Thank you! -Kevin signature.asc Description: PGP signature

Bug#1009791: mutt: change-folder no longer selects next folder with new mail

On Sun, 17 Apr 2022 14:20:54 -0600 Bob Proulx wrote: Starting with 2.2.3-1 the 'c' change-folder action now prompts with the *previous folder always* and never prompts with any other folders. It no longer selects a mailboxes folder with new mail. It prompts with the previous folder even if no

Bug#999672: mutt: license conflict with libsasl2

On Wed, Dec 15, 2021 at 01:30:29PM -0800, Kevin J. McCarthy wrote: I'm starting to look into adding libgsasl support. Since I haven't touched the SASL code in Mutt that much, I need to proceed with caution. It may not make it into the 2.2.0 release, but if not I will try to have

Bug#999672: mutt: license conflict with libsasl2

On Sun, 14 Nov 2021 18:51:51 +0100 Bastian Germann wrote: mutt depends on libsasl2-2, which is licensed under CMU's BSD-4-clause license and covered by the RSA-MD and OpenSSL licenses. All of them have an advertisement clause in place, which is known to be incompatible with GPL. There are

Bug#982555: mutt: Messages sent by Gmail SMTP are recorded in sent box with wrong charset/encoding

On Thu, 11 Feb 2021 16:40:53 -0300 Marcelo Luiz de Laia wrote: Package: mutt Version: 2.0.5-1 Severity: minor Dear Maintainer, After upgrade to mutt:amd64 2.0.5-1, messages sent by gmail was recorded in sent box with wrong charset, like this: Finalizei a inser��o das ATA no Processo.

Bug#965948: mutt: Incorrect handling of whitespace in aliases file

On Tue, 21 Jul 2020 11:38:18 +0100 Matthew Foulkes wrote: Package: mutt Version: 1.14.5-1 Severity: minor X-Debbugs-Cc: m.foul...@blueyonder.co.uk Dear Maintainer, Before version 1.14.15-1, mutt used to ignore extra whitespace between the end of the long name and the beginning of the email

Bug#990828: mutt can not delete mails due to access rights

On Thu, 08 Jul 2021 19:26:06 +0200 "Hans-J. Ullrich" wrote: Package: mutt Version: 2.0.5-4.1 Severity: important Dear Maintainer, it looks like, that mutt is not able to delete mails due to access rights. I checked the settings of the files and directories, but these seem to be ok for me.

Bug#969279: mutt - could not create tempory files

On Tue, 31 Aug 2021 11:09:30 +0200 "Hans-J. Ullrich" wrote: Package: mutt Version: 2.0.5-4.1 Followup-For: Bug #969279 Dear Maintainer, I can confirm this issue now for almost half a year, maybe longer. However, this issue appears only on amd64, on i386 it seems to work well. Sorry, I

Bug#671847: [Mutt] #3879: mutt: encoded-words are not decoded in mailto:

On Sat, 01 Oct 2016 21:01:11 - Mutt wrote: #3879: mutt: encoded-words are not decoded in mailto: +-- Reporter: antonio@… | Owner: mutt-dev Type: defect | Status: closed Priority: major | Milestone: Component:

Bug#986368: mutt: Add support for client certificate without AUTH in smtp

On Sun, 4 Apr 2021 15:32:59 +0200 Adam Majer wrote: Current implementation of mutt always seems to ask for SMTP username even if one is not set in the config (smtp_url) and AUTH is not an allowed option of submit server. This then results in an email send failure SMTP server does not support

Bug#838992: mutt: using mutt, will not default to home mail directory: "c", "?" with "set folder" remains in /var/mail

On Tue, 27 Sep 2016 09:56:38 -0400 jackson wrote: Package: mutt Version: 1.7.0-6 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrading from older version * What exactly did you do

Bug#995881: mutt: displays text/html raw instead of using mailcap

On Thu, 07 Oct 2021 18:04:53 +0200 Anton Ertl wrote: Package: mutt Version: 2.0.5-4.1 Severity: normal Dear Maintainer, I viewed a text/html email, shown as plain text. Selecting v to view attachments, and then selecting the text/html part and typing Enter also showed the plain text. I

Bug#961247: mutt -s'a b c' x < somefile sends post also to "b" and "c"

On Thu, 21 May 2020 23:08:03 + Bjarni Ingi Gislason wrote: Package: mutt Version: 1.14.0-1+b1 Severity: normal Dear Maintainer, * What led up to the situation? mutt -s'Test the mailer' bg < The '-s' argument requires a space between it and the subject to be used. Mutt uses the

Bug#958903: mutt: Broken file name in attachment if file name has cyrillic symbols (file name charset is UTF-8)

On Sun, 26 Apr 2020 16:34:57 +0300 Andrey Stankevich wrote: Package: mutt Version: 1.10.1-2.1 Severity: normal Dear Maintainer, I attached file to outgoing mail in mutt. File name has cyrillic symbols. Number of cyrillic symbols in file name is bigger than approximately forty symbols. In

Bug#899992: mutt: allow spaces in "Open mailbox" prompt

Would it be possible to support mailboxes with spaces (and/or some syntactic sugar to not have to type "notmuch://?query=" all the time)? There are a couple solutions within your control. You can rebind the editor menu function to another key (or to noop): it defaults to space.

Bug#632570: fails to join RFC 2231 continuations

On Mon, 04 Jul 2011 00:59:46 +0900 Akihiro Terasaki wrote: mutt fails to join continuations. Content-Disposition: attachment; filename*0=foo; filename*1=.; filename*2=txt mutt prints `footxt.', rather than the expected `foo.txt'. I believe this was fixed in Mutt

Bug#1001013: mutt: 2.1.x regression - SMTP AUTH mandated if available

On Mon, 13 Dec 2021 19:00:47 -0800 "Kevin J. McCarthy" wrote: 2.0.4 just came out, so I likely won't release 2.0.5 for at least a few weeks. However, Antonio if you get around to packaging 2.0.4 before the release, feel free to grab the patch file. Sigh... it's been

Bug#1001013: mutt: 2.1.x regression - SMTP AUTH mandated if available

On Mon, 13 Dec 2021 15:21:19 -0800 "Kevin J. McCarthy" wrote: I'll add a commit to the stable branch for 2.0.5, reverting the behavior to have either the smtp username or a client cert set before attempting authentication when AUTH is advertised. I've added <https://gitlab.com

Bug#1001013: mutt: 2.1.x regression - SMTP AUTH mandated if available

On Thu, 2 Dec 2021 18:51:39 +0100 Andreas Metzler wrote: After todays mutt upgrade (from 2.0) mutt suddenly *requires* successful SMTP AUTH when sending mail, at least when the SMTP server advertises AUTH support. (My server=localhost offers AUTH, but does not require it). There does not seem

Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug

On Tue, Nov 23, 2021 at 08:45:47PM +0100, Hannes von Haugwitz wrote: Is there any progress with this bug? Mutt 2.1.3 included the corrected sort commit referenced in my last email. So, for unstable/testing it would be nice to get 2.1.3 uploaded. For stable/oldstable I guess it rests in the

Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug

On Tue, Sep 07, 2021 at 08:20:49PM -0700, Kevin J. McCarthy wrote: I think the probability of users encountering that in practice is low. But if you're going through the effort of back-porting the fix, please wait and I'll commit a corrected fix tomorrow. This is still on a branch, waiting

Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug

Antonio, I was going through recent Mutt commits, and I realized my fix for this is not quite correct. The IMAP UID field is a 32-bit unsigned integer. I unfortunately modeled the new compare_uid() function after all the other ones use by Mutt for sorting, which just uses subtraction.

Bug#980326: mutt: diff for NMU version 2.0.2-1.1

On Wed, Jan 20, 2021 at 10:36:59PM +0100, Antonio Radici wrote: yes that will definitely help so we will get additional commits that are not yet in 2.0.4. If you can't make it by the weekend I should be able to find some time on Mon/Tue to do the upload! I've just released 2.0.5. For this

Bug#980326: mutt: diff for NMU version 2.0.2-1.1

On Tue, Jan 19, 2021 at 08:47:01PM +0100, Antonio Radici wrote: Thanks for the patch, I will upgrade to the latest upstream version by Sunday this week Antonio, if it helps, I can try to get a 2.0.5 release out before the weekend. -Kevin signature.asc Description: PGP signature

Bug#966100: notmuch-mutt: symlinking now fails for indexed mailboxes with a space in the name

On Tue, Aug 11, 2020 at 11:24:16AM -0300, David Bremner wrote: If you can, please test the upstream patch https://nmbug.notmuchmail.org/nmweb/show/20200727193833.4654-1-tomi.ollila%40iki.fi You'll need to build notmuch from source after applying the patch. "make debian-snapshot" will

Bug#870635: mutt package is not using the official mutt tarball

On Mon, Nov 20, 2017 at 06:59:16PM +, Jonathan Dowland wrote: > On Mon, Nov 20, 2017 at 10:35:52AM -0800, Kevin J. McCarthy wrote: > > Yes, I can understand the desire to sweep the whole mess under the rug. > > That's not what I am proposing at all. I'm suggesting we put ou

Bug#870635: mutt package is not using the official mutt tarball

On Fri, Nov 17, 2017 at 04:46:21PM +, Jonathan Dowland wrote: > I think there are a facts you should seriously consider before > continuing with this approach. > > Firstly, the existing package is neomutt, but called mutt. So the > existing package users are neomutt users, and the existing

Bug#840850: mutt: Mutt can't find S/MIME key to sign messages

Debian changed the default to use GPGME for GPG and S/MIME encryption. Please try putting "unset crypt_use_gpgme" in your .muttrc and restart mutt. (You must restart mutt for this option to have any effect). -Kevin

Bug#434235: mutt -H ignores Content-Type:

FYI. This is fixed upstream in https://dev.mutt.org/hg/mutt/rev/a4d885bb36ab

Bug#743744: mutt: S/MIME: mismatching documentation and supported algorithms for encryption (smime_encrypt_with)

FYI. This was fixed upstream in https://dev.mutt.org/hg/mutt/rev/1235dd48ef3f

Bug#800780: mutt: folder-hook: current mailbox shortcut '^' is unset

The warning for this is new in 1.5.24, but the behavior has been the same for 9 years. A leading '^' in a folder-hook or mbox-hook expands to "current mailbox", not "beginning of line". See https://dev.mutt.org/doc/manual.html#mailbox-hook and https://dev.mutt.org/trac/ticket/3788 If you need

Bug#741147: mutt: Mutt generated smime signatures fail verification in icedove/thunderbird

This was fixed upstream in https://dev.mutt.org/hg/mutt/rev/428a92464d5b Note that fix requires $smime_sign_digest_alg to have a "-md %d" added to it, so the header matches the actual digest used. The digest algorithm can be set with $smime_sign_digest_alg. See contrib/smime.rc.

Bug#677687: Mutt crashes while managing attachments

Just an FYI that this was fixed upstream in https://dev.mutt.org/hg/mutt/rev/f99561e22a99. -Kevin

Bug#814949: notification-daemon: /etc/xdg/autostart file only starts for "GNOME-Flashback"

On Thu, Feb 18, 2016 at 08:24:23PM +0200, Alberts Muktupāvels wrote: > If you want you can add autostart file for notification-daemon in your home > dir: > ~/.config/autostart > There is nothing specific to GNOME in notification-daemon so you can use it > generic solution if you want. Thank you,

Bug#814949: notification-daemon: /etc/xdg/autostart file only starts for "GNOME-Flashback"

On Thu, Feb 18, 2016 at 12:07:58PM +0200, Alberts Muktupāvels wrote: > Openbox is window manager, why should it start something? Openbox runs the XDG autostart programs because it is helpful. This way when I install, say, parcimonie or hplip-gui or notification-daemon, all those packages need to

Bug#658324: mutt: smime_keys.pl fails on filenames with spaces

Just a note that this is fixed upstream. There were a series of patches cleaning up up smime_keys. I think the relevant one for this bug was http://dev.mutt.org/hg/mutt/rev/577987ca2d02 but it probably won't apply outside of the series of commits. -Kevin

Bug#797923: mutt: Updated Danish translation

Morton, I've just added your translations upstream. Please feel free to join the Mutt Translators mailing list, mutt...@mutt.org, (see also http://www.mutt.org/mail-lists.html). You can post your updated translations to that list anytime and we will commit them directly upstream. I just

Bug#128945: Sending mail encrypted with additional keys

Just a note that the multiple crypt hook patch was slightly modified and committed upstream at http://dev.mutt.org/hg/mutt/rev/b4c57d3fd7e8 Also, a $crypt_confirmhook option was added to turn off the confirmation prompt at http://dev.mutt.org/hg/mutt/rev/067a3ac42c3b -Kevin

Bug#775199: smime_keys: insecure use of /tmp

Thank you for the suggestion to use File::Temp. This should be fixed upstream in http://dev.mutt.org/hg/mutt/rev/babc30377614 -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#763522: mutt: SEGV when choosing pgp keyID from list (mutt/mutt-patched)

I'm not a good judge of what is an RC bug, but this patch would be *really* nice to have in Jessie+1. It's a very low risk patch and stops an easy to hit segfault. -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#751476: mutt: 1.5.22 major performance regression with color regexp matching

This may be fixed by http://dev.mutt.org/hg/mutt/rev/755a18da99bc just committed upstream. ~b has a pretty big performance regression fixed by that changeset. -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#742627: mutt-patched: full text search (l + ~b text) is extremely slow

This may be fixed by http://dev.mutt.org/hg/mutt/rev/755a18da99bc just committed upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#780730: mutt: Does not work correctly with newer gpg-agent

Also note that http://dev.mutt.org/hg/mutt/rev/df55f14f4585 committed upstream removes the agent check. -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#439308: should be able to delete certain attachments in crypted mail

http://dev.mutt.org/hg/mutt/rev/bd21cff208c4 was just committed upstream, and allows attachments to be deleted from unencrypted emails. It displays a warning message if the email is signed or part-signed, but doesn't prevent the deletion anymore. -Kevin -- To UNSUBSCRIBE, email to

Bug#728377: Cannot supply additional addresses with -H

Note that http://dev.mutt.org/hg/mutt/rev/4909bd9c9149 committed upstream fixes this. -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#755538: mutt: Add gpgme support to vk.pgp_verbose_mime.patch

Also just a note that http://dev.mutt.org/hg/mutt/rev/789501922727 was committed upstream. It didn't include the options and the description, but does work for both classic and gpgme. -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe.

Bug#753437: FTBFS with clang instead of gcc

The log file is actually at http://clang.debian.net/logs/2014-06-16/mutt_1.5.23-1_unstable_clang.log It looks like this is caused by the compressed-folders.patch added by Debian, and can be fixed by simply adding declarations for restore_path() and remove_file() to the top of compress.c. (Or

Bug#774666: Mutt segfaults when no encryption key exists

This looks like a duplicate of #763522 and #772782, and like those two is probably fixed by http://dev.mutt.org/hg/mutt/rev/5a86319adad0 -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#763522: mutt segfault when selecting pgp key goes away with noopt

This was probably fixed by http://dev.mutt.org/hg/mutt/rev/5a86319adad0. -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#772782: mutt: segfault in pgp_getkeybystr at pgpkey.c:997

This looks like a duplicate of #763522, and is probably also fixed by http://dev.mutt.org/hg/mutt/rev/5a86319adad0 -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#759013: mutt: Incorrect fix in fix-configure-test-operator.patch

Just a note that this patch has been committed upstream at 80186ee6eb57. -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#757119: mutt: Documentation claims %a is possible in the pgp_encrypt_only_command but it's not

This is committed upstream at daf61444d454. -Kevin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#673924: [Pkg-openssl-devel] Bug#673924: openssl: 0.9.8o-4squeeze13 update broke exim4 TLS connection to FastMail

Kurt Roeckx wrote: Exim is using gnutls, not openssl ... Hmmm... I don't see any updates to gnutls for a couple months. That probably means FastMail did something then. Thank you for your help! Please close this bug out. -- To UNSUBSCRIBE, email to

Bug#673924: openssl: 0.9.8o-4squeeze13 update broke exim4 TLS connection to FastMail

Package: openssl Version: 0.9.8o-4squeeze13 Severity: normal My exim4 server is configured to relay messages to FastMail as a smarthost (using mail.messagingengine.com::587). The day the openssl security update 0.9.8o-4squeeze13 was installed, exim4 started failing to relay, logging: TLS