Link to home
Create AccountLog in
Avatar of jedistar
jedistarFlag for Singapore

asked on

JavaMail Vs Other mail compatibles

Why do people use JavaMail instead of other mail compatibles such
as .NET components (.NET mailing features)..

Or do people use .NET more?

What other easy to implement mail protocols are there?
Avatar of CEHJ
CEHJ
Flag of United Kingdom of Great Britain and Northern Ireland image

Well you'd have to be running Windows on your server for one thing - not a good idea ;-)
'have to be' is not strictly correct, but practicably so
Because Java is platform independent - you can use the same code and deploy it on any platform. The exchange-server can be a Microsoft exchange server or any other mail-server. The .NET code that you write will work with any mail-server but the code can be deployed on only Windows platform, unless you're using one of the 3rd party .NET implementations for Linux/ Mac like Mono (not recommended as they are not tried and tested).
ASKER CERTIFIED SOLUTION
Avatar of Mayank S
Mayank S
Flag of India image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
>> other than to say that the use of any *already written* clients other than Microsoft's is probably too insignificant to count

Don't forget Lotus and the others :) anyway that is because most of the users (not developers) in this world use Windows. However, let's not mislead by talking about only mail-clients. The mail API is used in applications too, and when it comes to applications, we know Java almost leads the way now :)
>>anyway that is because most of the users (not developers) in this world use Windows

Yes

Unfortunately. (So do I)
JavaMail is the standard *Java* api for handing mail
.NET components are primarily intended for use by .NET applications.
You could interchange if you wanted but its just making more work for yourself.
Using a different implementation of the protocols is also an option, but again for developing Java an impleemntation with a Java API would be far easier to use for Java development.
:-)