Paul J Stevens wrote:
Bert Slagter wrote:
My conclusion is that we'll have to switch to IMAP APPEND as soon as
possible. One big issue for us now is that we don't know a user's
password to login to imap, only the user_idnr from dbmail_users and the
md5 password hash. Do you have any ideas on that, or do we have to store
the plain text passwords ourself? User authentication to webmail is now
handled separately by our own system.
If you want to use IMAP APPEND without knowing the user's password you'll have
to use the acl tables to grant access to those mailboxes to a special user.
Major maintenance hassle. It would be nicer if dbmail supported a special admin
account with full access to all users and all mailboxes via the #Users
namespace. Patches are most welcome :-)
Sounds like a good idea. I'm sorry we don't have the expertise to
contribute with code. But I'd love to be guinea pig :).
In your case: Why not use dbmail-smtp? Perhaps through a 'super' wrapper, or
something similar.
As far as I understand from the man pages dbmail-smtp allows me to let
dbmail deliver a message to a user. So I'm afraid this doesn't really
solve my problem. For example, I need to save a message in a specific
folder (like Sent or Drafts) and need to set specific flags (like seen).
And, I don't want sieve scripts to execute when I save this message. As
I can see this is not possible with dbmail-smtp. Or am I missing something?
So unless I don't understand dbmail-smtp yet, an xml/json-interface or
IMAP APPEND with a super user would be good solutions for me.
Actually dbmail really needs a xmlrpc interface for stuff like this ... Perhaps
that would be a nice project after I stabilize 2.4. It would make life a *lot*
easier for webapps.
[snip]
That would be great. JSON-RPC would be even better for PHP apps :).
Kind regards,
Bert
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
