|
25-Jan-2003:
|
|
The following items are changed/fixed during the beta's 1 - 5:
- This version contains a complete working version of the Mercury/32 content control code. This is a major spam catcher... Content control is applied before filtering; if a content control action results in a message being moved or deleted, then filtering is not applied to it.
- Status storage has been overhauled for new mail. The biggest change in many ways is the least visible: Pegasus Mail is now much smarter in the way it writes X-PMFLAGS headers into new mail
- If there is an existing header in the message and the replacement header is shorter, then a blank-padded version of the string is written straight into the message without rewriting the whole thing.
- If there is no X-PMFLAGS header or the existing one is too short, Pegasus Mail now creates one with quite a few trailing blanks so it has space to expand the header without rewriting the message again; as a result, complete message rewrites will only ever happen once from this point.
- The POP3 engine adds a new header to the message to reserve space for X-PMFLAGS headers. This header, X-PM-Placeholder, has enough trailing spaces to handle an X-PMFLAGS header of any size and is replaced when Pegasus Mail needs to create the X-PMFLAGS header.
The overall result of this should be that flag storage should now be more or less instantaneous in the majority of cases, which should have a big impact on the performance of things like content control and filtering.
This version has a totally reworked POP3/SMTP interface, allowing the following new features:
- multiple definitions per identity
- definitions can be disabled and enabled on a per-identity basis
- full support for SSL/TLS in POP3, SMTP and IMAP
- POP3 allows downloading only "x" messages per connection
- POP3 has full server-side filtering support
- POP3 definitions can be told to poll at a less frequent period than the default poll setting for the identities that use them.
There are also some basic behavioural changes:
- Every identity has an internet e-mail address associated with it: this address is usable even if you do not have any active POP or SMTP definitions for the identity (this is to allow you to specify an explicit e-mail address for UDGs instead of having to use a default reply-to address;
- Each SMTP definition also allows you to specify an address that it should use in the SMTP envelope if your SMTP server is fussy about that kind of thing. Pegasus Mail will no longer ever try to form your address from your POP3 credentials.
- Every identity also has a default timeout value associated with it: any POP/SMTP definition that has its internal timeout set to 0 will use the default timeout for the identity.
- The program will automatically convert your existing old-style POP and SMTP data to new-style definitions when it detects an upgrade.
- There is an excellent chance that extensions using POP3 services, such as MultiPOP, will now be broken. There should no longer be any need to use MultiPOP. Multipop is really dead now!!
SSL: POP, SMTP and IMAP definitions now have a "Security" page where you can enable SSL support. There are three options for SSL - "never", "if the server advertises it" and "always". In essence, "if the server advertises it" means that Pegasus Mail will look for and use STARTTLS or STLS commands to initiate SSL connections prior to authenticating. This is the IETF's preferred way of doing things. "Always" tells Pegasus Mail that it should simply try opening the connection as a secure connection: you will typically use this if you have an SSL-tunnelled server listening on a non-standard port. The IETF deprecates this approach at present, but it's fairly commonly-used.
POP server-side filtering: you can now create filtering rule sets that Pegasus Mail will apply to mail *before it downloads it*. It does this by getting the headers and a certain number (user-specified) of lines from the body of each message then passing them through the filtering engine.
POP3 server-side filter rulesets are distinct from other types and must be created using the option in Tools|Mail Filtering Rules *before* you attempt to attach them to a POP3 definition. SSF rulesets have some actions removed (basically any action that is meaningless in the absence of the whole message, such as "forward" or "move") and have three new actions - "Download", "Leave on server" and "Delete on server". What's more, a POP3 definition that uses a rule set can have its own "default action" from these three actions for messages that pass through a rule set without triggering anything.
There is now a Tools|Options|Reader settings option to turn attachment preview off by default.
The "To disk" button on the main toolbar (if you're using a custom toolbar or the v2.x toolbar format) now saves the message in the body reader, and the selected attachment in the attachment view.
Copy-CC-field in replies should now work with CC fields of any length.
Pressing CTRL+V to paste addresses in a (saved) message's To: field will no longer paste this address into the main text area
Resending a message now correctly decodes RFC1522-encoded subject lines when they contain high-bit characters.
In preview mode, you can now view a message's attachments directly by pressing <F7>, or by clicking on the new "view" selector radio button. Pressing <F8> switches back to body view.
Group views. A "group view" is a hierarchical arrangement of the messages in a folder: depending on the sort mode in operation, there may be up to three different group views available - so, for example, if you sort by date, then the following group views are available:
Group messages by day
Group messages by week
Group messages by month
Groups can also have "captions", or special eye-leader entries in the list that identify each group. To control group views, use the "Group view" submenu on the "Message" menu in preview mode; the "Folders and previews" preference page also has some options for controlling their general behaviour.
|