Hello mse!
It's just a guess, but your S/MIME certificate says that it's 2048 bits.
I've had some bad experiences when I got my first 2048 bits certificate
and quickly stepped back to 1024 because too many clients can't handle
them and Outlook Express users even reported not being able to
Hello Martin,
when sending a mail to a friend who is using TheBat, too - he sees the
attached error message.
The friend I was talking about upgraded from 4.1.11 to 4.2.16 Final right
now. Before, signed mails from him were fine in Squirrelmail and everywhere
else, now signed mails from him
Hello mse!
when sending a mail to a friend who is using TheBat, too - he sees the
attached error message.
The friend I was talking about upgraded from 4.1.11 to 4.2.16 Final
right now. Before, signed mails from him were fine in Squirrelmail and
everywhere else, now signed mails from him are
On Thursday, January 7, 2010 at 16:20 Martin Sebald [MS] wrote:
MS The fun starts when you try to verify the signatures with another mailer
MS than TheBat, e.g. Squirrelmail, Thunderbird or something else.
It's just a guess, but your S/MIME certificate says that it's 2048 bits.
I've had some bad
Hi Maurice!
The fun starts when you try to verify the signatures with another mailer
than TheBat, e.g. Squirrelmail, Thunderbird or something else.
It's just a guess, but your S/MIME certificate says that it's 2048 bits.
I've had some bad experiences when I got my first 2048 bits certificate
Hello Maurice,
It's just a guess, but your S/MIME certificate says that it's 2048 bits.
I've had some bad experiences when I got my first 2048 bits certificate
and quickly stepped back to 1024 because too many clients can't handle
them and Outlook Express users even reported not being able to
Hello all,
problem still exists in 4.2.18...
...and obviously nobody cares...
...as always, adding new fancy features is more important than fixing stuff
which already worked before...
--
Regards,
Martin
The Bat! v4.2.18 Christmas Edition powered by Windows Server 2008 6.0 Build
6001
Hello all,
Wednesday, January 6, 2010, Martin Sebald wrote:
Hello all,
problem still exists in 4.2.18...
...and obviously nobody cares...
...as always, adding new fancy features is more important than fixing stuff
which already worked before...
christmas editions have more than 80
Hello Marek!
problem still exists in 4.2.18...
...and obviously nobody cares...
...as always, adding new fancy features is more important than fixing
stuff which already worked before...
christmas editions have more than 80 bugfixes, what new fancy features
are You talking about?
I'm
On Wednesday, December 30, 2009 at 03:45 Martin Sebald wrote:
This message should be signed, too.
Does someone else has the same problem or can say more about this?
It is signed, but my TB! as well as all those other clients don't have
the root and intermediate certificates that were used to
Hello Maurice,
I know that the certificate only appears valid when the root and
intermediate certificates are there.
The problem here is that it seems that there is some kind of message format
error. If the message format was ok, the signature would show as not valid.
But the mail client would
Hello all,
when sending a mail to a friend who is using TheBat, too - he sees the
attached error message.
Has anybody an idea what is going on?
--
Regards,
Martin
The Bat! v4.2.16.2 Christmas Edition powered by Windows Server 2008 6.0 Build
6001 Service Pack 1
ConCarne cooks best since
Hello again,
ok, it's a issue with the current TheBat! version.
when sending a mail to a friend who is using TheBat, too - he sees the
attached error message.
The friend I was talking about upgraded from 4.1.11 to 4.2.16 Final right
now. Before, signed mails from him were fine in Squirrelmail
13 matches
Mail list logo
