On Tue, Mar 16, 2010 at 9:14 PM, Timo Sirainen wrote:
> I haven't tried to really understand what your plugin does, but looks
> like it does most of its work in mail_alloc(). deliver does the mail
> delivery via:
>
> typedef int deliver_mail_func_t(struct mail_namespace *namespaces,
>
On Tue, Mar 16, 2010 at 5:50 PM, Timo Sirainen wrote:
> That seems like a feature that's unlikely to be used by many people,
> even more so because it requires LDAP. It's fine if it's listed in
> http://wiki.dovecot.org/Plugins, but I don't think I'll add it to
> Dovecot distribution itself.
That
roper"/"better" way to save a
file in mail box with a particular file name. (the file name is
important for retrieving the corresponding mail when a confirmation
arrives) The file also needs to be removed later if a confirmation
does not arrive in a specified time.
with regards,
ra
On Fri, Feb 26, 2010 at 1:40 PM, Steffen Kaiser
wrote:
> Er, "qmail-secretary" looks like a part of "qmail", hence, the analogy would
> be postfix in your new setup, or am I mistaken?
it's a part of qmail-local which is responsible for delivering mails
to local users, analogous to dovecot deliver
On Thu, Feb 25, 2010 at 9:37 PM, Marcus Rueckert wrote:
> hi,
>
> maybe look into mlmmj. (http://mlmmj.org/)
qmail-secretary just works, no configuration is needed, all you have
to do is add appropriate entry in ldap. No mess with MTA configs and
fully controllable via web interface (via ldap)
T
Hi,
I have been using qmail-ldap for quite some time and now moved to
postfix/dovecot. One feature that I miss is that provided by
qmail-secretary. qmail-secretary basically is a mail list manager with
following features:
1 no limit, just explode to all members
2 members only, as the name say
On 6/16/07, Łukasz Mierzwa <[EMAIL PROTECTED]> wrote:
Speed is good, but what about security? You would need to create new db when
creating new user, if userdb is not in mysql than You would need to connect
to it with priviliges to create new db (quite high priviliges I think).
Also I have no ide
On 6/16/07, Timo Sirainen <[EMAIL PROTECTED]> wrote:
http://www.archiveopteryx.org/schema.html
http://www.archiveopteryx.org/sql-schema.html might be useful reading
too.
Thanks!
raj
On 6/16/07, Łukasz Mierzwa <[EMAIL PROTECTED]> wrote:
To spam this ml more I must say that per user db is not that good idea
I must confess that I got this idea from Zimbra. I was just curious as
to why they went for this instead of the obvious one table for all
users. I will of course run som
On 6/16/07, Łukasz Mierzwa <[EMAIL PROTECTED]> wrote:
Maybe You could make a checksum of an attachment and use it as a ID, this way
You could have each unique attachment stored only once in db. What do You
think?
Wonderful idea. I was thinking about the attachment id and identifying
unique att
On 6/16/07, Łukasz Mierzwa <[EMAIL PROTECTED]> wrote:
Wouldn't it be better to put here id of attachments?
I agree, these are just some idea that came to the top of my mind.
raj
On 6/16/07, Timo Sirainen <[EMAIL PROTECTED]> wrote:
I guess you mean http://dovecot.org/patches/mail-sql.tar.gz?
Yes.
If you're thinking about making it actually usable, it would be nice to
store the message body instead as MIME parts (with separated
header/body). That would allow identical
On 6/16/07, Timo Sirainen <[EMAIL PROTECTED]> wrote:
Unfortunately there isn't any plugin documentation currently. What kind
of a plugin do you want to write? Looking at the existing plugins is
probably the easiest way to get started. Also
src/lib-storage/mail-storage.h is the most important API
Hello all,
I had gone through the wiki, but could not find any page about writing
new plugins. Any pointers towards plugin api/docs will be very
helpful.
with warm regards,
raj
14 matches
Mail list logo
