<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Not using IMAP storage here, although that was one of the primary
drivers for upgrading to Asterisk 1.4. Why?<br>
<br>
The short answer is that it's too confining. There are too many
caveats that don't fit into our existing IMAP structure and make the
entire project rather iffy. Security is a concern too - we don't want
to have one set of credentials that have absolute access to everyone's
email from the CEO down. I suspect we <i>could</i> make it work, but
the thought of experimenting on our live IMAP server sends chills down
my spine. (we don't have the budget or time to duplicate our mail
server to allow fiddling on a non-production system)<br>
<br>
The idea is brilliant. The weird dependency on having a
compiled-but-not-installed UW-IMAP isn't - I would have thought that
using a library such as libvmime would have made more sense.<br>
<br>
Olivier wrote:
<blockquote
cite="mid:442fbb120710180238u7b9df4ebhf71e0af7b8640221@mail.gmail.com"
type="cite">Hi,<br>
<br>
>From personal experience, Asterisk 1.4 IMAP storage seems broken and
unusable.<br>
Is anyone using it successfully ?<br>
<br>
This kind of poll would be very useful to estimate is a code rewrite
has a chance to disturb a running system.
<br>
I we get no "successful report", it would help developers to consider a
code rewrite as patch instead of a new feature.<br>
<br>
So please, do not hesitate to report successful or unsuccessful or
never tried use of IMAP storage, it will increase our chances to get
this feature in 1.4 branch and not wait for 1.6.</blockquote>
</body>
</html>