Bolla Péter wrote:
Why to bother writing mail storage system, while it has been already
done by others, and maintained well in several real good IMAP servers,
and IMAP client libraries (libs both for perl and php)? I think
many-many hours of development AND maintenance time could be spared if
dspam would just connect to an IMAP server with it's own user, and
store quarantained mails for separate users in separate IMAP folders.
I think you're right on that one. For the time being I'll push ahead
with the mbox variety as it's there and I need a better way to work with
it than the existing web UI, but building it around IMAP would be better
in the long run.
Of-course mbox -> IMAP scripts probably exist, so I could still look at
this option now. (Instead of building mbox index, move content of mbox
into IMAP and continue from there.) I've not done much with IMAP, but if
people think this is the right route for now (with dspam changing in the
medium term to drop straight into IMAP) I'll look into it further.
Further advantage is that with an advanced imap server, which handles
ACLs, you could add the proper access rights to the qurantain folder
for its respective user, so you could manage your quarantain right
from your mail reader. How's that?
What IMAP server would you recommend?
One thing I'd note is that an existing dspam installation has pretty low
system requirements, I wouldn't want to see that jump significantly. The
existing web UI suffers from trying to do too much in RAM now (my PHP
version does much less that way), so the overhead of dropping spam into
an IMAP server would be a consideration.
My own dspam server is using Courier, btw.
--
Mark Rogers // More Solutions Ltd (Peterborough Office) // 0845 45 89 555
Registered in England (0456 0902) at 13 Clarke Rd, Milton Keynes, MK1 1LG
