phlyMail Support Board

We are pleased to announce the release of PHlyMail 3.3 Beta1!

The full and core applications of MessageCenter and Personal Edition are available in the customer service area, PHlyMail Lite can be downloaded from the usual place, now in various compression formats and as core application for updating a running installation of PHlyMail Lite.

Internal tests did not show any serious problems, but we cannot guarantee, that there's not still some
bad issues. In case maximum stability is your top priority, you should consider waiting for the final release.

This build is available in the customer service.

New features

• IMAP: PHlyMail now supports IMAP via the PHP extension. Users can add as many IMAP accounts as they wish. All the basic operations
  are already implemented like creating, renaming, deleting folders and manage mails. Mails in an IMAP folder are indexed at first
  sight, so subsequent access to those mails should be dimensions faster than downloading, parsing and displaying the mail directly
  from the server.
  Mails can be copied and moved freely across different IMAP servers and the local file system.
  When fetching mails via the frontend fetcher, the INBOX folders of IMAP profiles are checked for mails. Doing so via the backend
  fetcher will be possible as of the final release. The same applies to caching mails fully (not just indexing them) and the filtering
  rules, which are currently not applied to IMAP accounts.
  
• Much more comfortable mail list: Selecting mails can now be done like in usual desktop applications by modifying the selection through
  the Shift or Ctrl keys.
  
• Folder context menu: Folder operations (Rename, Move, Delete, ...) can now be accessed via a right click menu, which completely replaces
  the separate Folder Mangaement window. Additionally users can access a properties dialog there, which among other things allows to
  enable or disable the mail preview window on a per folder basis. The optionally definable list of mail header fields to show in the
  maillist gets saved already, but does not show up in the maillist itself yet. This will be available in the final release.
  Additionally the folder menus do not work for the contacts icon and calendar icon yet.
  
• Empty Trash / Junk on Logout: These two options can be selected in the user setup and do what their names imply. This works for the
  local junk / trash folder only at the moment.
  
• New Mail Notification via Email / SMS: This option is available in the filtering rules and allows users to get notified about new mails
  matching the respective rule. Notification via SMS needs a sufficient SMS deposit for that user.
  
• Autcomplete: In the new mail / new SMS window users can now just enter something in the recipient fields and their input is matched against the address
  book. Matching entries are shown in a dropdown menu beneath the field for easy selection. This saves the time to open the address book and manually
  select recipients.
  
• Return Receipts: PHlyMail now fully supports return receipts. This includes sending ones on its own. Users can define, wether return receipts are
  sent always, never or on request only.
  
• Lost Password: Forgetfull users now find a link in the login screen, where they can have a new password sent to their registered email address.
  
• Additional Theme: Now theres another theme (ClassicPlus) available, which is quite similar to the original Classic theme, but looks a bit more fresh
  and nice.
  
• Attachments upload now can be removed in case users do not actually want to send them with the mail.
  

Besides these new functions improving PHlyMail massively, we used the time to fix some bugs and oddities:

• Corrections and improvements in the mailparser and the SMTP and sendmail layers, which both now interact much better with buggy mailservers and
  mails sent from buggy mail clients.
  
• Various security fixes, closing potential weaknesses, which could allow attackers to inject bad Javascript into PHlyMail. The threat scenarios connected to
  the mentioned weaknesses all were quite esoteric and hard to exploit. Besides we had a close look on the database layer, inspecting it for potential
  SQL injection attacks. Places found, where this potentially could have been possible were fixed.
  
• The problem, that the frontend fetcher only jumped in every about 20 minutes has been fixed.
  
• The context and top drop down menu have been made a bit more nice and clean.
  

Happy testing!