headers
Sascha Silbe | 1 Jun 01:57

SSL client cert support with GnuTLS?

Hi!

After switching from Gentoo to Ubuntu (which is based on Debian and thus 
links mutt against GnuTLS instead of OpenSSL), I noticed that there's no 
SSL client certificate support anymore, even the config variable 
ssl_client_cert is invalid. Since I'm using this (instead of passwords) 
for authentication on my IMAP server, mutt is currently useless for me 
on Ubuntu.
Is there a specific reason why there's no client cert support when 
linked against GnuTLS? How hard would it be to add it?

CU Sascha

--

-- 
http://sascha.silbe.org/
Permalink | Reply | 1 comment |
headers
markus reichelt | 4 Jun 02:22
Picon

Re: Bad IDN

* markus reichelt <ml <at> mareichelt.de> wrote:

> * Kyle Wheeler <kyle-mutt <at> memoryhole.net> wrote:
> 
> > On Saturday, May 26 at 01:35 AM, quoth markus reichelt:
> > >Error in ~/.mutt-aliases, line 1: Warning: Bad IDN 'cs.hmc.edu'
> > >in alias 'muttdude'.
> > 
> > I don't entirely understand the IDN business (it seems like black
> > voodoo to me), but it might go away if you compile mutt without
> > idn support (--without-idn).
> 
> Must be some kind of voodoo indeed. mutt 1.5.13 uses the same
> libidn and just works.

Ok, after some testing I'm back on 1.5.13 for good. Without the IDN
voodoo my charset setup (which works just fine in .13) is borked.
Messages with correct header info like

Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline

aren't displayed correctly (when it comes to umlauts, f.e.)

--

-- 
left blank, right bald
Permalink | Reply | 2 comments |
headers
Brendan Cully | 5 Jun 01:44
Gravatar

Re: Bad IDN

On Monday, 04 June 2007 at 02:22, markus reichelt wrote:
> * markus reichelt <ml <at> mareichelt.de> wrote:
> 
> > * Kyle Wheeler <kyle-mutt <at> memoryhole.net> wrote:
> > 
> > > On Saturday, May 26 at 01:35 AM, quoth markus reichelt:
> > > >Error in ~/.mutt-aliases, line 1: Warning: Bad IDN 'cs.hmc.edu'
> > > >in alias 'muttdude'.
> > > 
> > > I don't entirely understand the IDN business (it seems like black
> > > voodoo to me), but it might go away if you compile mutt without
> > > idn support (--without-idn).
> > 
> > Must be some kind of voodoo indeed. mutt 1.5.13 uses the same
> > libidn and just works.
> 
> Ok, after some testing I'm back on 1.5.13 for good. Without the IDN
> voodoo my charset setup (which works just fine in .13) is borked.
> Messages with correct header info like
> 
> Mime-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Disposition: inline
> 
> aren't displayed correctly (when it comes to umlauts, f.e.)

Your $charset is probably botched. It should set itself correctly
depending on your environment anyway, so if you have explicitly set
$charset, try commenting out that bit.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alain Bench | 5 Jun 00:34
Picon
Favicon

Re: Best way to handle DOS newlines

Hello Michelle,

 On Saturday, May 26, 2007 at 15:06:43 +0200, Michelle Konzack wrote:

> But it seems, your MTA/MUA has eaten the <backslash>r<backslash>n
> It should be [...] \r\n

    Alex has no problem. The thing eating certain characters is on your
incoming path, Michelle.

Bye!	Alain.
--

-- 
Mutt muttrc tip to send mails in best adapted first necessary and sufficient
charset (version for East Europe Latin-2/CP-852/CP-1250 terminal users):
set send_charset="us-ascii:iso-8859-1:iso-8859-15:windows-1252:iso-8859-2:windows-1250:utf-8"
Permalink | Reply | 1 comment |
headers
Alain Bench | 5 Jun 00:37
Picon
Favicon

Re: Bad IDN

Hello Markus,

 On Monday, June 4, 2007 at 2:22:27 +0200, Markus Reichelt wrote:

> my charset setup (which works just fine in .13) is borked.

    Sorry: Your charset setup is also borked on 1.5.13, you just didn't
notice it. Surely a bad $send_charset, probably bad iconv-hooks, and
perhaps yet another glitch or two. And this borkage may well be the
cause of the "Bad IDN" errors.

Bye!	Alain.
--

-- 
Give your computer's unused idle processor cycles to a scientific goal:
The Folding <at> home project at <URL:http://folding.stanford.edu/>.
Permalink | Reply | 0 comments |
headers
Wilkinson, Alex | 5 Jun 16:29
Picon

Re: Best way to handle DOS newlines

    0n Tue, Jun 05, 2007 at 12:34:52AM +0200, Alain Bench wrote: 

    >Hello Michelle,
    >
    > On Saturday, May 26, 2007 at 15:06:43 +0200, Michelle Konzack wrote:
    >
    >> But it seems, your MTA/MUA has eaten the <backslash>r<backslash>n
    >> It should be [...] \r\n
    >
    >Alex has no problem. The thing eating certain characters is on your
    >incoming path, Michelle.

True, true.

 -aW

IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the
jurisdiction of section 70 of the CRIMES ACT 1914.  If you have received this email in error, you are
requested to contact the sender and delete the email.
Permalink | Reply | 0 comments |
headers
meino.cramer | 6 Jun 03:57
Picon
Picon

No new email in certain folder?!

Hi,

 is it possible to inhibt the setting of the "N" flag (new email) 
 for a certain mailfolder?
 I am not interested in knowing of "new mail" in my spam folder...

 Thank you very much in advance for any help!

 Best regards,
  mcc
--

-- 
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.
Permalink | Reply | 8 comments |
headers
Nick Hastings | 6 Jun 04:47
Favicon

Re: No new email in certain folder?!

Hi,

* meino.cramer <at> gmx.de <meino.cramer <at> gmx.de> [070606 10:58]:
> 
>  is it possible to inhibt the setting of the "N" flag (new email) 
>  for a certain mailfolder?
>
>  I am not interested in knowing of "new mail" in my spam folder...

I don't know about removing that flag, but if you omit that mailfolder
from your "mailboxes" list in your muttrc then mutt won't prompt you when
new mail arrives there.

Cheers,

Nick.
Permalink | Reply | 7 comments |
headers
Joel Esler | 6 Jun 05:03

Re: No new email in certain folder?!

Or you can use a procmail recipe to mark the email as read upon  
insertion into the mailbox.

joel

On Jun 5, 2007, at 10:47 PM, Nick Hastings wrote:

> Hi,
>
> * meino.cramer <at> gmx.de <meino.cramer <at> gmx.de> [070606 10:58]:
>>
>>  is it possible to inhibt the setting of the "N" flag (new email)
>>  for a certain mailfolder?
>>
>>  I am not interested in knowing of "new mail" in my spam folder...
>
> I don't know about removing that flag, but if you omit that mailfolder
> from your "mailboxes" list in your muttrc then mutt won't prompt  
> you when
> new mail arrives there.
>
> Cheers,
>
> Nick.
>
Permalink | Reply | 6 comments |
headers
David Haguenauer | 6 Jun 05:14
X-Face
Favicon

Re: No new email in certain folder?!

Hi all,

* Joel Esler <joel.esler <at> sourcefire.com>, 2007-06-05 23:03:11 Tue:
> On Jun 5, 2007, at 10:47 PM, Nick Hastings wrote:
> >* meino.cramer <at> gmx.de <meino.cramer <at> gmx.de> [070606 10:58]:
> >> is it possible to inhibt the setting of the "N" flag (new email)
> >> for a certain mailfolder?
> >I don't know about removing that flag, but if you omit that mailfolder
> >from your "mailboxes" list in your muttrc then mutt won't prompt  
> >you
> Or you can use a procmail recipe to mark the email as read upon  
> insertion into the mailbox.

How? That would definitely be nice, but I did not notice that procmail
had the ability to deliver mail read (not to Maildir, at least).

--

-- 
David Haguenauer
Permalink | Reply | 5 comments |

Gmane