Ports Search

Balsa is a mail reader for the GNOME Desktop. It supports many features: * Support for local mailbox formats: mbox, maildir, mh * Allows nested mailboxes * Support for POP3 and IMAP mail access protocols * Printing * Spell Checking * Multi-threaded mail retrevial (optional) * MIME support (view images inline, save parts) * Supports SMTP and/or use of local MTA, ie. Sendmail * Address Book that integrates with GnomeCard * Highly configurable * Active, open development * Multiple character sets for composing and reading messages * Allows file attachments to outgoing messages * GPG/OpenPGP mail signing and encryption

Postfix attempts to be fast, easy to administer, and secure, while at the same time being sendmail compatible enough to not upset existing users. Thus, the outside has a sendmail-ish flavor, but the inside is completely different. Some feautures: Connection cache for SMTP, DSN status notifications, IP version 6, Plug-in support for multiple SASL implementations (Cyrus, Dovecot), TLS encryption and authentication, Configurable status notification message text, Access control per client/sender/recipient/etc, Content filter (built-in, external before queue, external after queue), Berkeley DB database, LDAP database, MySQL database, PostgreSQL database, Maildir and mailbox format, Virtual domains, VERP envelope return addresses and others.

The dovecot antispam plugin watches a defined spam folder (defaults to "SPAM"). Instead of moving mail into special folders or forwarding them to special mail addresses for retraining, the plugin offers two actions for the user: 1. moving mail out of the SPAM folder and 2. moving mail into the SPAM folder. The dovecot plugin watches these actions (and additionally prohibits APPENDs to the SPAM folder, more for technical reasons than others) and tells the spam classifier that it made an error and needs to re-clas- sify the message (as spam/not spam depending on which way it was moved.)

GMime is a set of utilities for parsing and creating messages using the Multipurpose Internet Mail Extension (MIME) as defined by the following RFCs: * 0822: Standard for the Format of Arpa Internet Text Messages * 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies * 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types * 2047: Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text * 2048: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures * 2049: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples * 2183: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field

GMime is a set of utilities for parsing and creating messages using the Multipurpose Internet Mail Extension (MIME) as defined by the following RFCs: * 0822: Standard for the Format of Arpa Internet Text Messages * 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies * 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types * 2047: Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text * 2048: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures * 2049: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples * 2183: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field

GMime is a set of utilities for parsing and creating messages using the Multipurpose Internet Mail Extension (MIME) as defined by the following RFCs: * 0822: Standard for the Format of Arpa Internet Text Messages * 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies * 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types * 2047: Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text * 2048: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures * 2049: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples * 2183: Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field

Object methods for ezmlm mailing lists. This software is beta release. As such, please treat it with the appropriate amount of caution. Let me know if you find any bugs, etc. The main reason for release is to sort of 'test the waters' ... Does anyone apart from me think this is a good idea?? Install by doing the following ... # perl Makefile.PL # make test # make install One thing. For some reason MakeMaker doesn't like symlinks. Please make sure you use the full cantonical path for the qmail and ezmlm binaries. Documentation is in pod format. Please run perldoc Mail::Ezmlm after you have installed it.

Postfix attempts to be fast, easy to administer, and secure, while at the same time being sendmail compatible enough to not upset existing users. Thus, the outside has a sendmail-ish flavor, but the inside is completely different. Some feautures: Connection cache for SMTP, DSN status notifications, IP version 6, Plug-in support for multiple SASL implementations (Cyrus, Dovecot), TLS encryption and authentication, Configurable status notification message text, Access control per client/sender/recipient/etc, Content filter (built-in, external before queue, external after queue), Berkeley DB database, LDAP database, MySQL database, PostgreSQL database, Maildir and mailbox format, Virtual domains, VERP envelope return addresses and others.

Postfix attempts to be fast, easy to administer, and secure, while at the same time being sendmail compatible enough to not upset existing users. Thus, the outside has a sendmail-ish flavor, but the inside is completely different. Some feautures: Connection cache for SMTP, DSN status notifications, IP version 6, Plug-in support for multiple SASL implementations (Cyrus, Dovecot), TLS encryption and authentication, Configurable status notification message text, Access control per client/sender/recipient/etc, Content filter (built-in, external before queue, external after queue), Berkeley DB database, LDAP database, MySQL database, PostgreSQL database, Maildir and mailbox format, Virtual domains, VERP envelope return addresses and others.

What is is: [excerpt from the patch homepage] A few people have done qmail - MySQL integration and this is my crack at it. My work is based on takeshi@softagency.co.jp's patches, which you can find at http://www.softagency.co.jp/mysql/qmail.en.html. However I wanted to tidy up some of the code to make it use strallocs and do more error checking. I also wanted to simplify the configuration, whilst at the same time allowing more flexibility. Plus there were some things I just didn't want: quotas and APOP support for example...