Re: Certificate

--On 2008-10-31 15.23 +0100 Steve Roylance <steve.roylance <at> globalsign.com> 
wrote:

> David,
>
> The GlobalSign Root Certificates are located here:-
>
> http://secure.globalsign.net/cacert/xxx from the choice below
>
> Root-R1.cacert
> Root-R1.crt
> Root-R1.der
> Root-R1.pem
> Root-R2.cacert
> Root-R2.crt
> Root-R2.der
> Root-R2.pem
> Root.cacert
> Root.crt
> Root.der
> Root.pem
>
> Root is our most ubiquitous root which expires in 2014 and seems to be
> inside Mulberry by default on Windows (I'm checking MAC OS later however
> we are in the base MAC OS so there should be no major issues)
> Root-R1 is the same key material extended until 2028 expiry
> Root-R2 is our new root created in 2006 which is being seeded.
>
> The cert that you point to is the GTE CyberTrust root and is located there
> due to the previous relationship between GlobalSign and CyberTrust.

Re: character encoding yet again

--On 2008-10-07 20.12 +0200 Joan Korenman <korenman <at> umbc.edu> wrote:

> Hi, Cyrus.  Thanks for your prompt response.  If it were just one or two
> people whose messages were causing this problem, I would at least try to
> get them to change, though since many email clients don't have a problem
> with their messages, I doubt that they'd be willing to do something like
> that simply to please me.  But in fact the problematic messages I receive
> come from many different sources, not just one or two.  I suppose that
> each time I get such a message, I could open Thunderbird and read the
> message there, but frankly that's far from an ideal solution.  Is there
> some way that you can make Mulberry better able to accommodate all these
> other email clients that apparently don't provide the information
> Mulberry currently needs?

I don't understand your problem. You must be receiving mail from a very 
specific group of users. Since I am Swedish most mails I receive contains 
accented characters (åäö) and I can't recall that it ever happened to me 
that these letters didn't display correctly.

--

-- 
Visit the Mulberry IRC-channel

irc://irc.freenode.net/mulberry

Re: sending smtp with gmail issues

--On 2008-10-09 21.31 +0200 1840trader <at> gmail.com wrote:

> Thaat's what I figured had happened, but when I pull up Thunderbird and
> other such apps, they have no problem sending at all.  Oh well.  At least
> I know it's not my end.  Thanks for the reply.  I appreciate knowing it's
> not just me.

I have two gmail accounts, setup differently with respect to their smtp 
settings, and haven't had this problem.

FWIW my settings are as follows:

smtp.gmail.com:465 - SSLv3
smtp.gmail.com:587 - STARTTLS - TLSv1

Both are set to plain text authentication.

--

-- 
Visit the Mulberry IRC-channel

irc://irc.freenode.net/mulberry

Re: character encoding yet again

--On Monday, November 03, 2008 12:09 AM +0100 david <davidbo <at> kth.se> wrote:

> I don't understand your problem. You must be receiving mail from a very
> specific group of users. Since I am Swedish most mails I receive contains
> accented characters (åäö) and I can't recall that it ever happened to me
> that these letters didn't display correctly.

Hi, David.  As I indicated in my message, the problem comes not just from one 
or two people nor a specific group but from LOTS of different sources.  I 
think that the problem may be that many of the problematic sources are in the 
United States, and they may not have their email clients set up to provide 
the correct information that Mulberry needs (though Thunderbird and some 
other email clients manage to function well even without the correct 
information).  My guess is that email clients in Sweden and other countries 
that use accented characters routinely are much more likely to be set up to 
provide the information Mulberry needs (the charset parameter on the 
Content-Type header).

Since Thunderbird and a number of other email clients can provide the proper 
characters even if there's no charset parameter, I'd love to see Mulberry do 
so as well.

	Joan

        Joan Korenman
        Professor Emerita of English
        Founder, Center for Women & Information Technology
        University of Maryland, Baltimore County
        Baltimore, MD 21250  USA
        korenman AT umbc.edu

Re: Certificate

-- david <davidbo <at> kth.se> is rumored to have mumbled on 3. November 2008 
00:00:15 +0100 regarding Re: [Mulberry-discuss] Certificate:

> I guess this means that the necessary certificate is in my keychain -
> doesn't Mulberry use the keychain?

No, it doesn't. As Cyrus wrote:

> Mulberry maintains its own root certificate store (though on Linux it
> also reads the default openssl root directory).
...
> The root certificates are stored in a CACerts directory inside the
> Plug-ins directory.
>
> Also, users can import their own roots via the Manage Certificates option
> in the Security preferences panel.
--
Sebastian Hagedorn - RZKR-R1 (Flachbau), Zi. 18, Robert-Koch-Str. 10
Zentrum für angewandte Informatik - Universitätsweiter Service RRZK
Universität zu Köln / Cologne University - Tel. +49-221-478-5587

User certificates

Since we have had a nice thread on root/CA certs, I'd like to
describe what I see when I try to handle user certs with
Mulberry 4.0.8 on Windows.  I'm wondering whether this is the
expected behavior and whether it is worth queuing a change
request:

Assume I have three user certificates stored in Mulberry, two
with the email address associated with one identity and one with
the other.  The two for the same identity differ by having been
certified by different CAs, so there are reasons why one might
want to select one and reasons why one might select the other.

What I see in the cert store is 
   identity1 <at> jck.com
   identity1 <at> jck.com
   identity2 <at> jck.com

Note that there is no way to tell the first one from the second
one without looking inside the cert -- no way to, e.g.,
associate some sort of mnemonic with each that would distinguish
them.

If I try to send signed S/MIME mail from identity1, I get a
pop-up that asks for the passphrase.   It apparently has a
pull-down for selection of the key to be used, but that
pull-down offers only a single address, identified as
"identity1 <at> jck.com" (i.e., it gives me no information).  The
other two keys are not available at all.  From experimenting,
the key it offers is the one most recently added, which would be
reasonable if both came from the same CA, but they don't.

Re: character encoding yet again

--On 2008-11-03 05.05 +0100 Joan Korenman <korenman <at> umbc.edu> wrote:

> Hi, David.  As I indicated in my message, the problem comes not just from
> one  or two people nor a specific group but from LOTS of different
> sources.  I  think that the problem may be that many of the problematic
> sources are in the  United States, and they may not have their email
> clients set up to provide  the correct information that Mulberry needs
> (though Thunderbird and some  other email clients manage to function well
> even without the correct  information).  My guess is that email clients
> in Sweden and other countries  that use accented characters routinely are
> much more likely to be set up to  provide the information Mulberry needs
> (the charset parameter on the  Content-Type header).

I certainly doubt that Gmail, Thunderbird, Mail.app, Hotmail, Outlook et al 
are setup differently depending on your location. By the method of 
elimination I say it is your mailserver that mangles these messages. I have 
seen that happen with old Exchange and FirstClass servers (although it is 
weird that it doesn't happen with Thunderbird).

--

-- 
Visit the Mulberry IRC-channel

irc://irc.freenode.net/mulberry

Re: character encoding yet again

--On Monday, November 03, 2008 9:28 PM +0100 david <davidbo <at> kth.se> wrote:

> I certainly doubt that Gmail, Thunderbird, Mail.app, Hotmail, Outlook et al
> are setup differently depending on your location. By the method of
> elimination I say it is your mailserver that mangles these messages. I have
> seen that happen with old Exchange and FirstClass servers (although it is
> weird that it doesn't happen with Thunderbird).

I'm not sure I see how it could be my mailserver, since my messages are NOT 
mangled when I read them in Thunderbird or Pegasus, just in Mulberry.  The 
problem, as Cyrus explained it earlier, is that Mulberry depends on the 
charset parameter on the Content-Type header; a number of other mail clients 
(Thunderbird and Pegasus among them) have apparently created workarounds when 
the charset parameter is missing.  My guess is that in countries whose 
languages use a more extended character set, it's more common for the charset 
parameter to be present.  That's just a guess, but it would explain why 
people can use Mulberry for such languages more easily in, say, Sweden than I 
can in the United States.

	Joan

        Joan Korenman
        Professor Emerita of English
        Founder, Center for Women & Information Technology
        University of Maryland, Baltimore County
        Baltimore, MD 21250  USA
        korenman AT umbc.edu

Re: character encoding yet again

--On November 3, 2008 5:49:59 PM -0500 Joan Korenman <korenman <at> umbc.edu> 
wrote:

>  The problem, as Cyrus explained it earlier, is that Mulberry depends on
> the charset parameter on the Content-Type header; a number of other mail
> clients (Thunderbird and Pegasus among them) have apparently created
> workarounds when the charset parameter is missing.

To which I reply:

My guess is that the workaround is "they guess".

Mulberry has long had a pretty strict policy of sticking to the standards, 
and not coddling badly-behaved MUAs or MTAs.  That can be seen as a vice or 
a virtue, depending on on your point of view .

--

-- 
Steve Burling                                    <mailto:srb <at> umich.edu>
University of Michigan, ICPSR                    Voice: +1 734 615.3779
330 Packard Street                               FAX:   +1 734 647.8700
Ann Arbor, MI 48104-2910

UI on Linux