[
http://issues.apache.org/jira/browse/JAMES-398?page=comments#action_12318539 ]
Stefano Bagnara commented on JAMES-398:
---
thanx to Markus Kühn for pointing to the typo. PKCS12 and not PKS12.
> Add SMIME mailets for signature verification and message d
- Original Message -
From: "Stefano Bagnara (JIRA)"
To:
Sent: Thursday, August 11, 2005 8:31 PM
Subject: [jira] Resolved: (JAMES-398) Add SMIME mailets for signature
verification and message decrypt
[ http://issues.apache.org/jira/browse/JAMES-398?page=all ]
Stefano Bagnara
[ http://issues.apache.org/jira/browse/JAMES-392?page=all ]
Stefano Bagnara updated JAMES-392:
--
Fix Version: 2.3.0
(was: 3.0)
> Resolve deprecation use from MailetAPI for the next release
> --
[ http://issues.apache.org/jira/browse/JAMES-400?page=all ]
Stefano Bagnara updated JAMES-400:
--
type: Task (was: Improvement)
> Move previous SMIME matcher/mailets to the new "smime" subpackages
> ---
[ http://issues.apache.org/jira/browse/JAMES-360?page=all ]
Stefano Bagnara resolved JAMES-360:
---
Fix Version: 2.3.0
Resolution: Fixed
> Support for Additional "received for" headers: e.g. X-Envelope-To
> --
Author: bago
Date: Thu Aug 11 12:16:41 2005
New Revision: 231503
URL: http://svn.apache.org/viewcvs?rev=231503&view=rev
Log:
Sample configuration for Additional "received for" headers to Fetchmail
(JAMES-360)
Modified:
james/server/trunk/src/conf/james-fetchmail.xml
Modified: james/server/t
[ http://issues.apache.org/jira/browse/JAMES-360?page=all ]
Stefano Bagnara reassigned JAMES-360:
-
Assign To: Stefano Bagnara
> Support for Additional "received for" headers: e.g. X-Envelope-To
> --
Author: bago
Date: Thu Aug 11 12:12:46 2005
New Revision: 231502
URL: http://svn.apache.org/viewcvs?rev=231502&view=rev
Log:
Added support for Additional "received for" headers to Fetchmail (JAMES-360)
Modified:
james/server/trunk/src/java/org/apache/james/fetchmail/Account.java
james/ser
> The next release of JAMES is being held up because we have
> new S/MIME support in the code, and as we understand it, that
> means we need to do something with BXA.
I think this is solved as long as we accept to bind to jdk1.4+ and to ask
the users download bcprov in order to use the SMIME mai
> > About S/MIME:
> > We developed a few S/MIME mailet/matchers.
> > [..]
> > If you agree I will commit them later in august.
>
> Cool! It would be great if you could also commit some
> accompanying xdocs to explain their usage too.
Committed. No Xdocs by now, just a simple configuration in con
I've done the patch. (hope other committers will like the move, or I'll
revert)
I've removed crypto libs.
We now compile against bcmail that should not contain crypto code: I had to
add a single class from bcprov to be able to build without bcprov and I
added it as a new jar named bcmail-jdk14-129
[ http://issues.apache.org/jira/browse/JAMES-399?page=all ]
Stefano Bagnara resolved JAMES-399:
---
Resolution: Fixed
> Update bouncycastle to 129 and remove jdk13 compatibility
> -
>
>
[ http://issues.apache.org/jira/browse/JAMES-398?page=all ]
Stefano Bagnara resolved JAMES-398:
---
Resolution: Fixed
Should works now with PKS12 and JKS keystores
> Add SMIME mailets for signature verification and message decrypt
>
Move previous SMIME matcher/mailets to the new "smime" subpackages
--
Key: JAMES-400
URL: http://issues.apache.org/jira/browse/JAMES-400
Project: James
Type: Improvement
Components: Matchers/Mailets (b
Update bouncycastle to 129 and remove jdk13 compatibility
-
Key: JAMES-399
URL: http://issues.apache.org/jira/browse/JAMES-399
Project: James
Type: Improvement
Components: James Core
Versions: 2.3.0
[
http://issues.apache.org/jira/browse/JAMES-399?page=comments#action_12318516 ]
Stefano Bagnara commented on JAMES-399:
---
Forgot to mention that this change should save us from the BXA as we don't ship
crypto code anymore! :-)
> Update bouncycastle t
[
http://issues.apache.org/jira/browse/JAMES-399?page=comments#action_12318515 ]
Stefano Bagnara commented on JAMES-399:
---
Removed bcprov from the repository.
In order to be able to compile I had to add the
"bcmail-jdk14-129-workaround.jar"
It simply
Author: bago
Date: Thu Aug 11 11:19:52 2005
New Revision: 231497
URL: http://svn.apache.org/viewcvs?rev=231497&view=rev
Log:
Upgraded Bouncycastle to 129 and java 1.4+ only (no more java 1.3 compatible)
(JAMES-399)
Added SMIME mailets for signature verification and message decrypt (JAMES-398 /
J
Author: bago
Date: Thu Aug 11 11:19:45 2005
New Revision: 231496
URL: http://svn.apache.org/viewcvs?rev=231496&view=rev
Log:
Upgraded Bouncycastle to 129 and java 1.4+ only (no more java 1.3 compatible)
(JAMES-399)
Added SMIME mailets for signature verification and message decrypt (JAMES-398 /
J
Add SMIME mailets for signature verification and message decrypt
Key: JAMES-398
URL: http://issues.apache.org/jira/browse/JAMES-398
Project: James
Type: Improvement
Components: Mailet API
Versio
> There are issues with this as well, since someip.dom/64 could
> be a valid IPv6 network but when it resolves to both IPv4 and
> IPv6 it's not alway simple to guess what was intended. And
> /64 on an IPv4 address will create an open relay, so perhaps
> it's a good idea to add a separete Author
And here is my preferences:
> I searched the james site/docs and i found no "versioning
> rules" so we can simply vote it, or better the PMC can choose.
> We probably need a single vote to:
> - choose to drop java 1.3
YES as it solve problems with SMIME and we probably already done this with
th
> With all of the changes we are apparently planning to put in
> this release, and particularly we are now talking about
> dropping support for JDK 1.3, perhaps we should call this version 3?
The next release incompatibilities:
- minor configuration changes (datasources=>datasource, and few othe
> Before I pose this question to our lawyers, can someone
> clarify that if we are dependent on JDK 1.4+, we are still
> shipping crypto code? And do we ship any code that
> IMPLEMENTS cryptography, or only code that USES it?
> Bouncy Castle implements, whereas our S/MIME mailets USE.
>
> I th
24 matches
Mail list logo
