Re: definition of signature separator

2009-01-21 Thread Chris G
On Tue, Jan 20, 2009 at 03:51:31PM -0600, Kyle Wheeler wrote:
 For one thing, the fact that it's never become a standardized format, 
 and is instead a mix-and-match set of conventions that every mail 
 program has their own ideas about (often with disastrous results). I 
 find that hilarious. And the fact that people continue to refer to 
 mbox as a mailbox format, and continue to use it as if it were a 
 portable useful format... As far as I can tell, it's good for one 
 thing: mail that will only ever be accessed by a single piece of 
 software.
 
No different from other formats such as maildir then!  :-)

-- 
Chris Green


Re: Certificate

2009-01-21 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, January 21 at 09:20 AM, quoth Tolga:
 When I connect to one remote server, I am told that my certificate 
 expired and get (r)eject, accept (o)nce. When I connect to another 
 one, I don't get it. What is this and what to do about it?

It's not *your* certificate that's expired, it's *their* certificate.

Whenever you connect to a server and encrypt that connection (i.e. 
with SSL), the server must have an encryption certificate to use for 
encrypting the connection (I'm being very broad here, but for the 
purposes of this discussion, this is relatively accurate). These 
certificates are generally only good for a certain amount of time (for  
several very good reasons), and so have an expiration date embedded in 
them. When you connect to a server, the server sends you information 
about its certificate that includes the expiration date. So what's 
happening is that one of the servers you connect to is using an 
expired certificate. Now, generally, that's bad: expired certificates 
*can* be a sign that someone has brute-forced the certificate and is 
performing a man-in-the-middle attack against you. Or it can also be a 
sign of a system administrator that's asleep at the wheel. Either way, 
it's something that needs to be fixed.

Unfortunately, there's very little YOU can do to fix it, other than 
complain loudly to the people in charge of that particular server.

~Kyle
- -- 
If I had been married earlier in life, I wouldn't have seen the double 
helix. I would have been taking care of the kids on Saturday. On the 
other hand, I was lonely a lot of the time.
-- James Watson
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkl3NyQACgkQBkIOoMqOI16nTgCgs4ZZAcbJ1zPQbqSL1SNoBM38
j44AoMuMAfBqcKg6Yn5zLLa9oa0sq7yT
=UHYW
-END PGP SIGNATURE-


Re: definition of signature separator

2009-01-21 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, January 21 at 09:09 AM, quoth Chris G:
On Tue, Jan 20, 2009 at 03:51:31PM -0600, Kyle Wheeler wrote:
 For one thing, the fact that it's never become a standardized format, 
 and is instead a mix-and-match set of conventions that every mail 
 program has their own ideas about (often with disastrous results). I 
 find that hilarious. And the fact that people continue to refer to 
 mbox as a mailbox format, and continue to use it as if it were a 
 portable useful format... As far as I can tell, it's good for one 
 thing: mail that will only ever be accessed by a single piece of 
 software.
 
No different from other formats such as maildir then!  :-)

How so? Maildir has a definitive definition written and published by 
the guy who designed it in the first place. 
http://cr.yp.to/proto/maildir.html (or, more formally, 
http://www.qmail.org/man/man5/maildir.html)

There's a slight modification, called Maildir++, that is also 
well-defined 
(http://www.courier-mta.org/imap/README.maildirquota.html).

What makes you say that Maildir is, like mbox, a poorly-defined 
non-standardized format that exists solely as an 
implementation-dependent manifestation that has disastrous 
inter-application results?

~Kyle
- -- 
I love America more than any other country in this world, and, exactly 
for this reason, I insist on the right to criticize her perpetually.
-- James Baldwin, Notes of a Native Son
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkl3Oj8ACgkQBkIOoMqOI15cvgCg5OCaEaQi98VrwyuUEQ1PbbFZ
DWIAnRAaPLZVOlkGP6NusK8CCkAmR3Rk
=MlsU
-END PGP SIGNATURE-


imap shuts down

2009-01-21 Thread Michael M. Tung

Hi all,

I have a problem with the local imap server which only maintains the
connection open for 15 seconds. Unfortunately there is no way to
convince the administrator to increase this timeout. Thunderbird
somehow keeps the connection open by pinging permanently. However,
Thunderbird is not my favorite email client. ;-)

I have tried to tweak the parameters

imap-keepalive
timeout
mail-check

but couldn't make it work (using perhaps the wrong combination).

Are there any other tricks you know of, maybe using tunneling
or an external Perl script pinging (or a workable combination
of mutt parameters)?

Many thanx. Best, Mike


-- 


pgpjp2lAmiEaq.pgp
Description: PGP signature


Re: Certificate

2009-01-21 Thread Tolga

Kyle Wheeler yazmış:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, January 21 at 09:20 AM, quoth Tolga:
  
When I connect to one remote server, I am told that my certificate 
expired and get (r)eject, accept (o)nce. When I connect to another 
one, I don't get it. What is this and what to do about it?



It's not *your* certificate that's expired, it's *their* certificate.

Whenever you connect to a server and encrypt that connection (i.e. 
with SSL), the server must have an encryption certificate to use for 
encrypting the connection (I'm being very broad here, but for the 
purposes of this discussion, this is relatively accurate). These 
certificates are generally only good for a certain amount of time (for  
several very good reasons), and so have an expiration date embedded in 
them. When you connect to a server, the server sends you information 
about its certificate that includes the expiration date. So what's 
happening is that one of the servers you connect to is using an 
expired certificate. Now, generally, that's bad: expired certificates 
*can* be a sign that someone has brute-forced the certificate and is 
performing a man-in-the-middle attack against you. Or it can also be a 
sign of a system administrator that's asleep at the wheel. Either way, 
it's something that needs to be fixed.


Unfortunately, there's very little YOU can do to fix it, other than 
complain loudly to the people in charge of that particular server.
  
The one I get the (r)eject, accept (o) message with is one I own. So, 
how can I generate such a certificate?


Regards,
~mto

~Kyle
- -- 
If I had been married earlier in life, I wouldn't have seen the double 
helix. I would have been taking care of the kids on Saturday. On the 
other hand, I was lonely a lot of the time.

-- James Watson
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkl3NyQACgkQBkIOoMqOI16nTgCgs4ZZAcbJ1zPQbqSL1SNoBM38
j44AoMuMAfBqcKg6Yn5zLLa9oa0sq7yT
=UHYW
-END PGP SIGNATURE-
  




html mails and umlaute

2009-01-21 Thread Nathan Huesken
Hi,

To view html mails, I have this line in my .mailcap:

text/html; elinks -dump -dump-charset ISO-8859-15 -default-mime-type text/html 
%s; needsterminal; copiousoutput;

But it does not display Umlaute properly. Since I am german speeking, this is 
kind of anoying. I tried using UTF-8 for encoding, but it did not help.
What should I do?

Thanks!
Nathan


Re: html mails and umlaute

2009-01-21 Thread Michael Wagner
* Nathan Huesken m...@lonely-star.org 22.01.2009
 
 To view html mails, I have this line in my .mailcap:
 
 text/html; elinks -dump -dump-charset ISO-8859-15 -default-mime-type 
 text/html %s; needsterminal; copiousoutput;
 
 But it does not display Umlaute properly. Since I am german speeking,
 this is kind of anoying. I tried using UTF-8 for encoding, but it did
 not help.  What should I do?

Hello Nathan,

I have this in my mailcap and mutt show me the umlauts.

text/html; elinks -dump -force-html %s; needsterminal; copiousoutput

Mutt 1.5.18 (2008-05-17)

Hth Michael

PS: Please keep your mails at 72 chars, because it's better to read.

-- 
Mary had a little lamb. The doctor was surprised.


signature.asc
Description: Digital signature


Re: html mails and umlaute

2009-01-21 Thread Joost Kremers
On Wed, Jan 21, 2009 at 06:41:25PM +0100, Nathan Huesken wrote:
 To view html mails, I have this line in my .mailcap:
 
 text/html; elinks -dump -dump-charset ISO-8859-15 -default-mime-type 
 text/html %s; needsterminal; copiousoutput;

i use:

text/html; elinks -dump -eval set document.codepage.assume = %{charset} %s; 
copiousoutput

if your system is set up properly, there should be no need to specify
-dump-charset, elinks should use the proper charset for your terminal. it
is IME necessary to tell elinks about the encoding of the mail it has to
process, which mutt stores in the variable charset. elinks doesn't have a
proper command line switch to specify the document codepage, but the above
trick works.

HTH


-- 
Joost Kremers, PhD
University of Frankfurt
Institute for Cognitive Linguistics
Grüneburgplatz 1
60629 Frankfurt am Main, Germany


Re: html mails and umlaute

2009-01-21 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, January 21 at 06:41 PM, quoth Nathan Huesken:
 To view html mails, I have this line in my .mailcap:

 text/html; elinks -dump -dump-charset ISO-8859-15 -default-mime-type 
 text/html %s; needsterminal; copiousoutput;

 But it does not display Umlaute properly. Since I am german speeking, this is 
 kind of anoying. I tried using UTF-8 for encoding, but it did not help. 
 What should I do?

One of the basic problems with that is that it's rather difficult to 
inform elinks about what the character set of the INPUT is. And since 
it doesn't know about the INPUT character set, it cannot correctly 
ensure that the OUTPUT is correct (the -dump-charset is telling it 
what character set you want the OUTPUT to be in).

I would suggest using w3m instead of elinks because it has much better 
character set handling. If you install w3m, here's the mailcap line 
you want:

text/html; w3m -I %{charset} -dump -T text/html %s; copiousoutput

On the other hand, w3m sometimes has trouble forcing bad HTML to 
render in 80 columns when in dump-mode. Personally, this isn't a big 
enough problem to make me stop using it, but your experience may be 
different.

~Kyle
- -- 
The liberty of a democracy is not safe if the people tolerate the 
growth of a private power to a point where it becomes stronger than 
the democratic state itself.
   -- Franklin D. Roosevelt
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkl3Yu4ACgkQBkIOoMqOI17wGACfVryPp5gxnyh1kwfol28lzjTD
vwsAoNiGOjek2+SB37QmKgChp6ZXs5K4
=Yn6+
-END PGP SIGNATURE-


Re: imap shuts down

2009-01-21 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, January 21 at 05:37 PM, quoth Michael M. Tung:
 I have a problem with the local imap server which only maintains the 
 connection open for 15 seconds. Unfortunately there is no way to 
 convince the administrator to increase this timeout.

Yike, that's a shockingly low timeout. He's aware that that timeout 
violates the IMAP protocol (which FORBIDS timeouts less than 30 
minutes), and wastes a lot of bandwidth in pointless pinging, right? 
:P

 Thunderbird somehow keeps the connection open by pinging 
 permanently. However, Thunderbird is not my favorite email client. 
 ;-)

Did you have to configure Thunderbird in a particular way? I ask 
because normally, Thunderbird is *incapable* of handling keepalive 
times of less than 1 minute.

My guess is that Thunderbird is NOT actually keeping the connection 
open, but is instead merely opening new connections as necessary.

 I have tried to tweak the parameters

   imap-keepalive 
   timeout 
   mail-check

 but couldn't make it work (using perhaps the wrong combination).

You may want to try updating your version of mutt. It had some 
problems with low values of imap_keepalive that got fixed recently (I 
*think* 1.5.19 has the necessary changes).

~Kyle
- -- 
It is precisely because it is fashionable for Americans to know no 
science, even though they may be well educated otherwise, that they so 
easily fall prey to nonsense.
-- Isaac Asimov
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkl3YB8ACgkQBkIOoMqOI17TfACfdWQehH0U9nqAIYAtr2wbc1Lo
Q3YAoMTcuIgU3lWGZJTa2dluTf9D50ad
=jlKo
-END PGP SIGNATURE-


Re: Certificate

2009-01-21 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, January 21 at 06:49 PM, quoth Tolga:
 Unfortunately, there's very little YOU can do to fix it, other than 
 complain loudly to the people in charge of that particular server.
 
 The one I get the (r)eject, accept (o) message with is one I own. So, how 
 can I generate such a certificate?

How did you generate it in the first place? And what server software 
are you using? (Really, this is a question better suited for the 
support forums of your email *server* software, rather than your 
*client* software.)

~Kyle
- -- 
And thou shalt smite the house of Ahab thy master, that I may avenge 
the blood of my servants the prophets, and the blood of all the 
servants of the LORD, at the hand of Jezebel. For the whole house of 
Ahab shall perish.
 -- Bible, II Kings (9:7-8)
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkl3YJIACgkQBkIOoMqOI15UYQCg5OF5Ro3c88MzLzp7ReRAvRcV
NYoAoKFU/tZC6Hm6rKQJ1Bcasaj4eq6y
=tSbQ
-END PGP SIGNATURE-


Re: Certificate

2009-01-21 Thread Tolga



Steve Searle yazmış:

Around 04:49pm on Wednesday, January 21, 2009 (UK time), Tolga scrawled:

  
The one I get the (r)eject, accept (o) message with is one I own. So, 
how can I generate such a certificate?



Just guessing - but did you install the server a year ago?  If so it
propbably created a one year certificate when you installed it.
  

Ubuntu Linux

~mto

What server is it (OS/distro?)

Steve

  


--
You'd like to do it instantaneously, but that's too slow.



Re: Certificate

2009-01-21 Thread Tolga



Kyle Wheeler yazmış:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, January 21 at 06:49 PM, quoth Tolga:
  
Unfortunately, there's very little YOU can do to fix it, other than 
complain loudly to the people in charge of that particular server.


  
The one I get the (r)eject, accept (o) message with is one I own. So, how 
can I generate such a certificate?



How did you generate it in the first place? And what server software 
are you using? (Really, this is a question better suited for the 
support forums of your email *server* software, rather than your 
*client* software.)
  

I had no idea I generated it, and I am using Postfix.

~mto

~Kyle
- -- 
And thou shalt smite the house of Ahab thy master, that I may avenge 
the blood of my servants the prophets, and the blood of all the 
servants of the LORD, at the hand of Jezebel. For the whole house of 
Ahab shall perish.

 -- Bible, II Kings (9:7-8)
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkl3YJIACgkQBkIOoMqOI15UYQCg5OF5Ro3c88MzLzp7ReRAvRcV
NYoAoKFU/tZC6Hm6rKQJ1Bcasaj4eq6y
=tSbQ
-END PGP SIGNATURE-
  


--
Q:  What's the difference betweeen USL and the Graf Zeppelin?
A:  The Graf Zeppelin represented cutting edge technology for its time.



Re: Certificate

2009-01-21 Thread David Maus
Hi,

On 22. Jan 2009 08:59, Tolga wrote:

 How did you generate it in the first place? And what server software  
 are you using? (Really, this is a question better suited for the  
 support forums of your email *server* software, rather than your  
 *client* software.)
   
 I had no idea I generated it, and I am using Postfix.

If mutt is complaining about the expired certificate when you are
_sending_ Mail, it's up to Postfix:

https://help.ubuntu.com/8.10/serverguide/C/postfix.html, Section SMTP
Authentication explains how to create a self-signed digital
certificate for postfix.

If mutt complains about the certificate when logging into a mailbox,
it's up to your IMAP/POP3 server software. Check the Ubuntu
serverguide for the help on creating a certificate for your IMAP/POP3
server software.

Regards,
David

-- 
Email. maus.da...@gmail.com
Jabber dmj...@jabber.org
ICQ... 241051416
OpenPGP... 0x316F4BE4670716FD


signature.asc
Description: Digital signature