Closed
Bug 146041
Opened 23 years ago
Closed 21 years ago
broken signed message after moving from imap folder to another
Categories
(MailNews Core :: Security: S/MIME, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: pm, Unassigned)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/20020510
BuildID:
(S/MIME, signed Email, Exchange as IMAP Server)
I receive a signed email (with attachement), the mail arrives with correct
signatures, now I move the message from one Imap folder to another, now it's broken.
To reproduce this it's important to receive the email on the Exchange, and then
move arround. If I receive it eg. on a cyrus I can't move it around and on to
the exchange server as I like, but not on exchange.
It works moving from a exchange folder to a non exchange folder. Just within
Exchange, this doesn't work.
Reproducible: Always
Steps to Reproduce:
1.send email with attachment to exchange account and sign it.
2.move it from INBOX to another IMAP box on the exchange
3.now the signature is broken.
Actual Results: broken s/mime signature
Expected Results: as in the inbox, signed
Comment 1•23 years ago
|
||
-> PSM, S/MIME
Assignee: mstoltz → ssaux
Component: Security: General → S/MIME
Product: MailNews → PSM
QA Contact: junruh → carosendahl
Version: other → 2.3
Comment 2•23 years ago
|
||
Reporter,
Please take a look at the message headers and see if there are any "x-pkcs7"
references or just "pkcs7" references in the content type fields.
Esther, do we have an exchange server that I can use for testing purposes?
Thanks
Comment 3•22 years ago
|
||
can anybody reproduce this with a recent build like 1.1beta?
Comment 4•22 years ago
|
||
I have used an exchange 2000 server and have not encountered this bug. Which
exchange server are you using?
Comment 6•21 years ago
|
||
I'm closing this bug because the reporter has not responded. If this bug still
exist please reopen
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•