Free zip files email software for linux

Email Files Thunderbird is a very simple service menu script, to email one or more files with Thunderbird to any address or to a given address, which i assume is used as a "backup" space.

The subject is automatically updated according to the attached files and, in case you choose to send to your specific email address, details about sending date, user and host are automatically added in the body.

There are other similar service menus around, but i wanted a script that allows to attach more than one file at one time and that automatically updates the subject line.

USAGE: pretty straightforward.. Just make the two .sh files executable (if necessary) and place them in a directory of your path, for example /home/YOUR_USERNAME/bin. Place the service menu file EmailWithThunderbird.desktop in /home/YOUR_USERNAME/.kde/share/apps/konqueror/servicemenus

IMPORTANT: In file EmailWithThunderbirdToMyAddress.sh, you need to specify your email address in to=.... (that is, where i wrote: YOUR_EMAIL_ADDRESS@DOMAIN.NAME)

This project was tested on OpenSuSE 10.2, KDE 3.5.6

Enterprise File Exchange (EFX) slots in where email file attachment limits stop your users from sending those important files to a contact.

In the EFX world, the user visits the EFX site, uploads the file, enters the receivers email address and lets the system notify the receiver that theres a file waiting for them, via a simple email message.

Senders need to sign up, and the EFX system only allows transfers between internal users (those with addresses in an approved list) and external users, never external to external.

It is written in Python, using the Pylons framework.

This project is licensed under the GNU GPL version 3.

KSendfile is a native SAFT client. Compared to the Bitnet up to now there was no asynchronous file transfer service defined in the Internet. The existing standard file transfer, the ftp, is a synchronous service: an interactive login on both ends of the file transfer is mandatory for the user to set up a connection between both points.
If a user A wants to send a file to user B they have the following choices:
- ftp to a recipients account B
In this case one has to know the password of the recipients account. If A and B are not the identical person, severe questions of security arise and it is not the method of choice. Even if account A and B belong to the same person, the typed ASCII password characters for ftp access will travel open (readable) as ordinary TCP packets through the network.
- ftp using an anonymous ftp server
The file has to be uploaded by A onto the anonymous ftp server using an ftp session. After that A has to notify B about this using e-mail informing this user about the fact that the file is ready for download now. B can get the file now by doing another ftp transfer. This procedures requires a common reachable ftp server, with an upload (write access) facility. During the time the file resides on the anonymous ftp server it is open to anyone, it may be readable, writeable, changeable or erasable.
- sending a file via e-mail
A is sending a file to B enclosed into an e-mail. According to RFC 822 a mail must contain characters from the NVT-ASCII character set, which is a subset of the 7 bit ASCII character set. The file transfer via e-mail is limited to English text documents or the text to be sent must be encoded properly, of course using the NVT-ASCII character set. Encoding procedures like uuencode or MIME are available. It is not a pleasure to use either of them, they dont support all file ownership attributes and they will enlarge the amount of data to be transferred by encoding. In addition to this most of the existing MTAs are not designed to handle large amount of data transfers.
To avoid all the described disadvantages the SAFT-protocol (Simple Asynchronous File Transfer) has been developed and the sendfile software has been created as a reference implementation for UNIX platforms.
Enhancements:
- Fixed a bug in ksendfilenetclient::sendFile when getting status code 531
- Added Resend Function
- Fixed bug in ksendfilenetclient::sendfile in the date function
- Now sends the file date, not the actual system date.

httpFileManager is a file management script written in PHP allowing the remote administration of files over HTTP.
httpFileManager will turn your standard browser into a "Windows Explorer" and allow managing files on your web server on the fly. Its a complete replacement of traditional FTP, allowing you to manage files on your web server just with a web browser instead of a FTP client.
httpFileManager project also will provide extended features which are impossible with FTP such as creating and editing HTML files right on the server and zipping and unzipping files on the fly.
The purpose of httpFileManager is allowing file management and Web site maintenance right on the server. It may be used to manage a single site or multiple sites. The root of the files to be managed must of course be Web accessible.
httpFileManager is a simple, yet powerful tool allowing the administration of files through HTTP.
Enhancements:
- This release fixed a security issue.
- A number of smaller bugfixes and code improvements were also included.

PloneFilesZip allows your visitor download the files and images from folders in a single ZIP file.
loneFilesZip provides a new document action in all folderish contents (ATFolder, ...) that let the user download files (and images) contained in the fields of any AT based content (ATContentTypes and others) in that folder.
PloneFilesZip works - out of the box - with any content type which schema has a FileField, an ImageField or any field that acts like a FileField, as the AttachmentField.
Customizing (site manager)
.Choose the content types that can profide files to the user among compatible types.
.Add Dublin Core information (RDF formatted) about the contents in the ZIP archive.
.Tweak the condition/permission to let the user download.
.Customizing (content type developers)
Some content types have schemas that do not "show" the compatible fields through the standard AT API. In order to let these content types provides files in a ZIP archive, developers can add type adapter classes in the PloneFilesZip types registry. An adapter for PloneArticle is less than 20 Python lines.
Some custom field types may provide files. In order to let the content types built with such fields provide files to a ZIP archive, developers can add field adapter classes in the PloneFilesZip fields registry.
Enhancements:
- Fix a bug in file retrieving. Append arg (full=True) while creating BaseUnit to make sure we get the entire file and not a chunk file
- Fix a bug on DeepZipStructurePolicy:getZipFilePath (add **kwargs on method)

Zip is a compression and file packaging utility for Unix, VMS, DOS, OS/2, Windows 9x/NT, Amiga, Atari, Macintosh, BeOS, SMS/QDOS, MVS, VM/CMS, and others.
Zip is analogous to a combination of the Unix commands tar(1) and compress(1) and is compatible with PKWAREs PKZIP and Nico Maks WinZip. Its part of the Info-ZIP project.
Main features:
- creating zipfiles in a pipe or on a device
- VMS and OS/2 extended file attributes
- conversion between Unix, MS-DOS and Macintosh text file formats
- the ability to run on most of your favorite operating systems.
Enhancements:
- fixed -R operation to match the supplied file patterns in all recursed subdirectories, like PKZIP 2.04 "-p -r" (or PKZIPC 4+ "-recurse")
- handle cases where -x, -R, and -i patterns are mixed
- new example C-Sharp code for using DLLs
- added some directory-search speedups
- fixed bug when encrypting large uncompressible files
- fixed Windows NTFS time problem
- fixed VMS logical name parse problem
- added VMS DEBUG option
- updated VMS help
- fixed selection of files to delete by date
- added -MM option where each input file pattern must match at least one file and all input files must be readable
- added check for when Zip tries to exceed seek limit in output file
- minor changes to compile with Visual C++ 2005
- added support for Unix FIFOs (named pipes)
- other minor fixes

ZZIPlib library is intentionally lightweight, it offers the ability to easily extract data from files archived in a single zip file. Applications can bundle files into a single zip archive and access them. The implementation is based only on the (free) subset of compression with the zlib algorithm which is actually used by the zip/unzip tools.

The library allows reading zip archives in a number of ways,
archive mode:

reading the zip directory and extracting files from it. This is the traditional mode as seen with unzip-utilities. Some extra unzip-utiles for transparent/magic mode are shipped as well.

replacement mode:

Use ZZIP_FILE / ZZIP_DIR pointers provided by zziplib and put them to work with routines originally developped to work with real directories and file handles. The API calls do follow traditional synopsis from posix/stdio.

transparent mode:

Use replacement handles and allow the open()-calls to automatically detect when a file is contained in a zip archive or when it is a real file in the file system. A filepath can be partly in a real filesystem and partly within the zip archive when one is seen.

ext magic

Use the same filepath to access either a zipped or real file - it looks for a real file and there is none then every subdirectory of the path is checked, a ".zip" extension appended, and the zipped file transparently opened. This can speed up dat-file development dramatically.

io/xor magic

The access to the filesystem can be hooked up - examples are given for xor obfuscation which is great for game artwork and AI data. A small intro for SDLrwops usage is given as well.

Riley is a file integrity checker written in Perl,somewhat similar to Tripwire.
Running riley -initialize puts a file called .riley in each directory specified in the configuration file. Each .riley file contains N one-line descriptions, one description per file. Each description contains the name of the file, type, size, owner, group,
permissions, and number of links. If the file is a regular file, each description also contains an MD5 checksum of the contents of the file. Each .riley file also contains a MD5 checksum of the file itself to forestall tampering.
Running riley -examine compares the current state of every file against the description created earlier by running riley -initialize. If anything has changed, it notes the change both in the system log file and via email. It is noticing the existance of new files as well as the non-existance of deleted files.
If youre feeling paranoid, you can run riley -correct instead of riley -examine. Doing this changes the permissions/ownership of changed files back to what the description file says they should be. riley -correct treats new files suspiciously, changing their ownership/
group to nobody/nobody (99/99 on most RedHat systems), and their permissions to 0. If you dont want to use nobody/nobody, change the values of the global variables $unpriv_u and $unpriv_g to something else, perhaps an owner/group youve specifically created for the occasion.
Enhancements:
- added code to handle dangling symlinks (thanks to chad townsend)
- added code to print usage when option "-help" given
- minor cosmetic fixes (removed un-used variables, added comments)
- added code to install program to check for "chattr"