> 1) How do we know they are compatible? Thats the nightmare for you! not only do you have to conform to the java mail spec but also to the miriad RFC's for mail.
We have a lot of knowedge about how the stds should be implemented, but not a test kit of any kind. It is certainly reasonable to use James as a testbed, James' architecture provides several points at which test cases could be inserted. Its probably worth restating the enormity of the task, for the spec and an impl you'd have to test conformance with RFC's for: domain names email addresses POP SMTP & ESMTP (for both send and receive) NNTP IMAP Message format MIME - including providing handlers for at least a few common content types, especially the gruesome multipart/* ones. James relies on JavaMail to provide a lot of this, simply because the effort of producing reliable conformant implementations far outweighs the benefit of "ownership". Why re-invent the wheel when there weren't a great many of the JavaMail classes we'd like to change? Though I think that if it made proper use of interfaces as types we'd be more inclined to replace some of the key ones. > 2) Transport providers, especially SMTP James uses the sun RI ones, but we have some issues with them and would like to have the resources to write our one ones. Sadly we haven't done so yet. I can understand that the licence is an issue, we had an issue with it which we resolved by only distributing them with binaries. I also think we'd be happy to collaborate, I'm much less sure how much we can realistically offer beyond our knowedge. d. *************************************************************************** The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Limited. This footnote also confirms that this email message has been swept for the presence of computer viruses. ************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
