Jar file and its portability between engines

[Comal Rajagopalaratnam Muthukumar]

Hi
Having created  a Jar file ,the forwardal of the same through Email becomes tantalizing .and not consistent enough
between one engine to other engine.One engine accepts it with provion to unblock the Bolcking while other engine refuses .How to remove this sort of  obstacle
and include the free=portablty durng the creation of Jar file iself. there by the jar can be successfully  sent authenticating the feature of jar for its portabilty.
Also i am surprised to find this removal of block by a dialog message for the same jar file in the properties whose exampels are shown as screnshots
AS
CRMK

[Norm Radder]

What is an "Engine" that you talk about?

[Comal Rajagopalaratnam Muthukumar]

Norm Radder wrote:What is an "Engine" that you talk about?

Hi
Please note that the usage of the word Engine is only a contextual one meaning the media through wich any one normally sends mails & not to be treated as a technical one of Java. Here Engine is secondary
while Jar is primary  whose method required.Just please indicate if a jar file can be created besides sealing and signing etc that can be used for mailing
irrespective of blockage or not blockage provison/feature(builtin) prevailng in the mailer.(for a JavaApplication)
Thanks
As
CRMK

[Jesper de Jong]

With the way you describe things, it is very hard to understand what you mean. Please use clear and simple language, instead of abstract and general terms such as an "engine".

What are you trying to do, and what problem are you experiencing exactly?

Are you trying to send a JAR file as an attachment via e-mail, and is your mail server blocking it? If yes, then that's most likely for security reasons. Some mail servers do not allow you to send any kind of file that might contain executable code, to protect the receiver of the e-mail from running arbitrary code received from an e-mail (which is one way that computer viruses are distributed).

If this is your problem, then it doesn't have anything to do with Java or JAR files, and is simply a security feature of the e-mail system. One simple way to fix it could be to change the extension of the JAR file to something else (".xyz" for example) and then asking the receiver to rename it back to ".jar" before running it.