Sending Lazarus applications via the Internet.

[oproescu]

Hi!
How can be sent a Lazarus application over internet networks such as gmail? Archived or with the extension changed is not possible for me.
Thanks!

[JuhaManninen]

How can be sent a Lazarus application over internet networks such as gmail? Archived or with the extension changed is not possible for me.

Why is archiving to a compressed package not possible?
I would suggest archiving all source code to a .zip or .tar.gz or similar file.
Then recipients can build from sources on their own platform.

[MarkMLl]

I presume that you're talking about built binaries rather than source.

How can be sent a Lazarus application over internet networks such as gmail? Archived or with the extension changed is not possible for me.

You need to give us far more information.

* What operating systems are you and your associates using?

* Why are archives (tarballs etc.) not possible?

MarkMLl

[trev]

If it's the usual mail system rejection of binaries whether zipped or not, then I only send a URL via email and let the enduser download the archive from one of my webservers (you could also use dropbox, iCloud, OneDrive, Google Drive or another third party storage provider).

[dbannon]

I routinely email zipped binaries to willing beta testers, have not had a problem yet.

With windows users, its best to tell them to unzip (happens automatically in the file manager) AND then drag the binary onto, eg, their desktop. That is, don't try to run it from within the zip file.

Some corporate email systems will scan attached zip files looking for (potentially nasty) binaries inside and block them just in case. And who can blame them ?

Davo

[avk]

It is possible, for example, to encode the binary as Base64 or Hex and then compress it.
It turns out pretty compact.

[dsiders]

I routinely email zipped binaries to willing beta testers, have not had a problem yet.

Then you have never sent them to a GMail email address . They won't transmit it. Perils of using free services.

[MarkMLl]

Then you have never sent them to a GMail email address . They won't transmit it. Perils of using free services.

I've never seen a problem, and I think we should be waiting for more info from RP rather than drowning his thread with comments that might be irrelevant.

MarkMLl

[oproescu]

Thanks MarkMLI, I'm using WINDOWS 10 on a Core'I5 computer. I can archive the application file (exe), but it is not supported by gmail or similar. I can still send with engines like WeTransfer, but not many recipients know how to download files from such an engine. I'm interested in a direct shipping method.

[oproescu]

Thank trev!
I used https://www.filehosting.org/ but not all my beneficiaries know how to work with such platforms and that's why I wanted to know if it is possible and directly on gmail.

[Handoko]

I am not sure but if I remember correctly. My email ever blocked by a mail server, the email had a zip file that contains an executable binary. I just recompressed the file and added a password, problem solved.

[MarkMLl]

Thanks MarkMLI, I'm using WINDOWS 10 on a Core'I5 computer. I can archive the application file (exe), but it is not supported by gmail or similar. I can still send with engines like WeTransfer, but not many recipients know how to download files from such an engine. I'm interested in a direct shipping method.

In that case I can't add a great deal to what other people have said: if you want a reliable email system don't rely on a freebie that can be discontinued or have its T&C changed with minimal warning.

MarkMLl

[dbannon]

Yep, thats right !   

I just tried to send a zipped windows exe and a password protected exe and both were blocked.  But a less worrying zipped file, a Spanish translation for my app, went through OK.

So, they can tell if its an executable even if password protected ? Wow.

So, I tried sending a linux executable and that went through OK too, so they don't seem to think Linux users need to be protected as much as windows users :-)

oproescu, I suggest you and your end users all switch to Linux as soon as possible.   

Davo

[korba812]

Yep, thats right !   

I just tried to send a zipped windows exe and a password protected exe and both were blocked.  But a less worrying zipped file, a Spanish translation for my app, went through OK.

So, they can tell if its an executable even if password protected ? Wow.

So, I tried sending a linux executable and that went through OK too, so they don't seem to think Linux users need to be protected as much as windows users :-)

oproescu, I suggest you and your end users all switch to Linux as soon as possible.   

Davo

Files are recognized and blocked by extension. ZIP format keeps original file names even with encryption. Try to compress exe file into 7zip with encrypted filenames.

edit

I just checked. Encrypted 7zip is also rejected by gmail. Probably because google can't look inside the archive.

[PascalDragon]

I usually use 7z to compress binaries and then change the second byte of the file from "z" to "y" so that Google's servers don't recognize it as a 7z anymore.