Re: [Dovecot] Create New Plugin
Hi Timo Tks, very much for the help... finally i finish my plugin and Its Work now. Now i will start the second phase about this modifications. I Need 3 more modifications one is encrypt my splited body (the header will still open)... but i have some doubt. The body email is splited in "boundarys", and i think that is better to encrypt only the content of each boundary, because is more easy to deal with seek, stat and anothers funcions, i can use the default seek, because its used to this, find every part of email...right ?.. Well if its right, there is some hook to deal only with the body response ? Or its better encrypt the entire body, and rewrite all functions ? The Second is more simple, i need to create some defaults folders, like "WHITE-LIST / BLACK-LIST" and "QUARENTINE / SPAM" and the user will move messages from the INBOX to this folders, but when the user move some message from "QUARENTINE" to WHITE-LIST, the message will moved to INBOX and the email address from the message will be put into white-list in postgres. There is some hook to do this ?! And the last one is more aasy lol. How i can put into conf.d or dovecot.conf, a configuration and read from my plugin to use with the plugin. Exemple: the folder that have my bodys, write this in configuration and get from configuration in dovecot.conf. Tks Again !! 2010/2/3 Timo Sirainen > On 4.2.2010, at 2.23, Alex Baule wrote: > > There is a date to the Dovecot 2.0 out as a official release ? > > > "When it's stable." > > I use the 2.0 version to make a my plugin. > > > That actually makes it easier then if you use configure > --enable-header-install. Then you'll get dovecot-config file that you can > use to find out what compiler flags you need. > > Actually that reminds me dovecot-config should probably be converted to > become a pkg-config file to make it even easier.. > >
Re: [Dovecot] Create New Plugin
On 4.2.2010, at 2.23, Alex Baule wrote: > There is a date to the Dovecot 2.0 out as a official release ? "When it's stable." > I use the 2.0 version to make a my plugin. That actually makes it easier then if you use configure --enable-header-install. Then you'll get dovecot-config file that you can use to find out what compiler flags you need. Actually that reminds me dovecot-config should probably be converted to become a pkg-config file to make it even easier..
Re: [Dovecot] Create New Plugin
Ok...There is a good example to do explicit, it's better because can be compiled separately from dovecot. Tks !! There is a date to the Dovecot 2.0 out as a official release ? I use the 2.0 version to make a my plugin. 2010/2/3 Timo Sirainen > On 3.2.2010, at 14.41, Alex Baule wrote: > > > i have a Little question > > > > I dont know to much the autoconf/automake...there is a command or > something > > to do, to include my plugin in the Makefile for dovecot compile them when > i > > compile the hole package ?? > > > > or i shoud go to the configure and makefile.am and put by hand ? > > > > I put my plugin in the plugins directory source tree. > > Well .. You could put them by hand and run autogen.sh and configure again. > Or you could do the same as how other external plugins do it, with an > explicit gcc line just giving all the necessary include paths etc. For > example see: http://dovecot.org/patches/1.2/penalty.c > >
Re: [Dovecot] Create New Plugin
On 3.2.2010, at 14.41, Alex Baule wrote: > i have a Little question > > I dont know to much the autoconf/automake...there is a command or something > to do, to include my plugin in the Makefile for dovecot compile them when i > compile the hole package ?? > > or i shoud go to the configure and makefile.am and put by hand ? > > I put my plugin in the plugins directory source tree. Well .. You could put them by hand and run autogen.sh and configure again. Or you could do the same as how other external plugins do it, with an explicit gcc line just giving all the necessary include paths etc. For example see: http://dovecot.org/patches/1.2/penalty.c
