-
-
Notifications
You must be signed in to change notification settings - Fork 18
Documentation Features
Jens Maus edited this page Feb 13, 2017
·
3 revisions
The following list is a short summarise of the currently available features YAM provides in its latest version available:
General features:
- Straightforward installation and configuration, taking only a few minutes to set everything up.
- Runs "Out-of-the-Box" without any installation or Assign required for expert users.
- Easy operation using toolbar buttons, menus, keyboard and drag&drop functionality.
- Basic e-mail functions: Read, Write, Reply, Forward and Bounce mail
- Six standard folders: Incoming, Draft, Outgoing, Sent, Trash and Spam.
- Any number of user-definable folders, which can be compressed and/or encrypted via own passwords set.
- Hierarchical ordering of folders.
- Multiuser support. Optionally, address books and other configuration files can be shared.
- Searchable address book supporting groups and distribution lists.
- Full POP3 support allowing to check/download mails on startup, on demand or at regular time intervals.
- Configure an unlimited amount of POP3 accounts.
- Message download pre-selection: browse message headers and select only those mails you want to download.
- Write or Reply to your mails off-line and send them to the mail server using the built in SMTP support
- Extract sender information from message headers and create an address book entry with just a simple mouse click.
- Built-In support for MIME encoding/decoding for sending and receiving binary files.
- Interaction with web browsers: send mail from your browser, pass an URL to the browser.
- Handle message disposition notifications (MDN).
- Direct support for anonymous remailing (remailers) and mailing lists.
- PGP/MIME support: encrypt and/or sign outgoing messages, check signatures, decrypt messages. Direct support for PGP 2.6.x and PGP 5.
- Fast internal text editor with support for common mail styles (bold/italic/underline), glossary and with a spell checking interface.
- Comprehensive search capabilities. For example a full text search through all articles using a single query or a quick search to find/sort mails quickly in a folder.
- Automatic sorting of the post with an unlimited number of filters. Archiving or diversion of specified articles, automatic replies or the deletion of advertising are just a few of the possible applications of the filters.
- Event-sensitive starting of macros and comprehensive ARexx support.
- Freely customisable interface, thanks to MUI.
- Usable on either an own screen or on any public screen configured in MUI.
- Context-sensitive online help system, using help bubbles and online documentation.
- Context sensitive menus for direct operations on each mail.
- Localised to many languages.
- ... and much, much more
Technical highlights:
- Fully buffered TCP/IP interface with non-blocking I/O socket connections.
- POP3 compliant post office protocol implementation.
- TLSv1/SSLv3 secure layer connection support (requires AmiSSL v3) either by direct connection to port 993 or by using the STLS compliant SSL implementation through normal port 110 connections.
- APOP authentication support.
- SMTP compliant mail transfer protocol implementation.
- TLSv1/SSLv3 secure layer connection support (requires AmiSSL v3).
- SMTP-AUTH authentication support (DIGEST-MD5/CRAM-MD5/LOGIN/PLAIN).
- MIME compliant mail reading/writing.
- Base64 encoding/decoding.
- Quoted-Printable (QP) encoding/decoding
- UUcode encoding/decoding.
- Automatic selection of the "smartest" encoding algorithm.
- MBOX format compliant mail import/export routines.
- internal maildir format like mail management by storing each mail in a separate file.
Right from the beginning of the open source era of YAM, we tried to make YAM more compliant to well accepted standards like the RFC - Request for Comment papers available for defining internet relevant standards. The following list should give you a short overview of the RFC s YAM tries to be compliant to.
- RFC 976 - UUCP Mail Interchange Format Standard
- RFC 1652 - SMTP Service Extension for 8bit-MIME transport
- RFC 1847 - Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted
- RFC 1869 - SMTP Service Extensions
- RFC 1870 - SMTP Service Extension for Message Size Declaration
- RFC 1891 - SMTP Service Extension for Delivery Status Notifications
- RFC 1939 - Post Office Protocol - Version 3 (POP3)
- RFC 1985 - SMTP Service Extension for Remote Message Queue Starting
- RFC 2015 - MIME Security with Pretty Good Privacy (PGP)
- RFC 2034 - SMTP Service Extension for Returning Enhanced Error Codes
- RFC 2045 - Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
- RFC 2046 - Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
- RFC 2047 - Multipurpose Internet Mail Extensions (MIME) Part Three: Message Header Extensions for Non-ASCII Text
- RFC 2049 - Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
- RFC 2076 - Common Internet Message Headers
- RFC 2195 - IMAP/POP AUTHorize Extension for Simple Challenge/Response
- RFC 2231 - MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
- RFC 2246 - The TLS Protocol Version 1.0
- RFC 2387 - The MIME Multipart/Related Content-type
- RFC 2440 - OpenPGP Message Format
- RFC 2487 - SMTP Service Extension for Secure SMTP over TLS
- RFC 2554 - SMTP Service Extension for Authentication
- RFC 2595 - Using TLS with IMAP, POP3 and ACAP
- RFC 2616 - Hypertext Transfer Protocol -- HTTP/1.1
- RFC 2821 - Simple Mail Transfer Protocol
- RFC 2822 - Internet Message Format
- RFC 2831 - Using Digest Authentication as a SASL Mechanism
- RFC 2852 - Deliver By SMTP Service Extension
- RFC 2920 - SMTP Service Extension for Command Pipelining
- RFC 3462 - The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages
- RFC 3798 - Message Disposition Notification
- RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax