On Tue, 20 Apr 2010 18:49:10 +0300
Timo Sirainen wrote:
>
> The above syntax would probably have to use IMAP parser.
>
> > doveadm fetch subject "(foo)"
>
> This works nowadays though. It's possible to use:
>
> doveadm fetch INBOX \( subject "(foo)" seen \) or unseen
>
> This works because th
Here is a patch to fix the problem where an imap process runs away when
imap-zlib is in use. The backtrace showed:
io_loop_handler_run ->
stream_send_io ->
client_output ->
o_stream_flush ->
o_stream_zlib_flush ->
o_stream_zlib_send_flush
When o_stream_zlib_flush returns 0, stream_send_io reins
If I had the file descriptor, I will reuse my functions to do this, made in
a separate library, that i use in the MTA.
So no need to rewrite again the part of split the message.
2010/4/20 Timo Sirainen
> You should write the message header to the ostream that you get, and
> message body to so
On Wed, 2010-04-14 at 12:04 +0300, Timo Sirainen wrote:
> I don't think the process creation is much of an issue. But something like
> this could work:
>
> doveadm expunge -A < Trash savedbefore 1w
> Trash/* savedbefore 1w
> Spam savedbefore 2mon
> EOT
The above syntax would probably have to use
You should write the message header to the ostream that you get, and
message body to some other file that you create. Use the o_stream_send()
function to write the message header to the ostream (which does
basically the same as write(fd)). I don't see how getting the stream's
fd would help with any
Because my plugin will separate the body of the message header.
With the FD I have control over the message to separate it.
Do you have any suggestions for this separation?
I do not quite understand how the struct ostream works.
Tks Timo.
2010/4/20 Timo Sirainen
> On Tue, 2010-04-20 at 11:
On Tue, 2010-04-20 at 15:18 +0200, Andre Hübner wrote:
> ../../src/login-common/.libs/libdovecot-login.so: undefined reference to
> `ERR_peek_last_error'
Your OpenSSL library is too old.
signature.asc
Description: This is a digitally signed message part
On Tue, 2010-04-20 at 11:40 -0300, Alex Baule wrote:
> There is a way to get the file descriptor from output used in ostream zlib
> plugin ?
No. Why do you need it? You should be writing to ostream, not to its fd.
signature.asc
Description: This is a digitally signed message part
Hello Everyone...
In zlib save mail have it:
struct ostream *output;
There is a way to get the file descriptor from output used in ostream zlib
plugin ?
to get in istream is i_stream_get_fd, but don't have o_stream_get_fd..
Hello,
try to compile current dovecot2 beta on older machine with gcc 3.3
Compiling results in error:
libtool: link:
gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith
-Wchar-subscripts -Wformat=2 -Wbad-function-cast -o .libs/imap-login
client.o client
Nobody ?
This can be a dovecot bug ?
--
Emerson Pinter
Picture Internet
55 11 5089-8130
http://www.picture.com.br/
On Mon, 19 Apr 2010 14:27:22 -0300, Emerson Pinter
wrote:
> Hi.
>
> I'm trying to use checkpassword for simple auth and masteruser auth.
> I have two programs, one called checkpa
in master.cf you said postfix to run deliver as user dovecot.
deliver then ask sql and get the info to stote the mail as uid 12345
deliver has to run setuid root to do that.
see http://wiki.dovecot.org/LDA#Multiple_UIDs
or you can change master.cf to
dovecot unix - n n - - pipe flags=DRhu user
Changed home dir of users, in my configuration they are
/var/postfix/spool and /var/postfix/dovecot/run, but with no effect.
I still got the "fatal setgid failed: Not owner" ( Fatal:
setgid(12345(postfix)) failed with euid=12346(dovecot),
gid=54322(dovecot), egid=54322(dovecot): Not owner )
2010
On Tue, 2010-04-20 at 10:39 +0200, Rodolphe Buret wrote:
> Example of 2 probably related messages in the cur folder:
> 1785 Apr 20 09:18 msg.zMeU:2,d
This is an MH file.
http://wiki.dovecot.org/MailboxFormat/Maildir#Procmail_Problems
> 0 Apr 20 09:18 _J9C%jVVzLB.{myhostname}:2,
I don't know wha
Hi,
I'm starting to see more and more duplicates in my cur directory. they
seem to be a copy of an incoming mail (messages share the same date) but
they appears in the client as a message without subject and without
sender or body. Their filename starts with an underscore and the 4th
letter i
Steffen Kaiser wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 19 Apr 2010, Stephan Bosch wrote:
Now I'm wondering.. should this be configurable/optional?
Ideally I would suggest a vendor feature, which one has to require
before use.
But this would make problems using the featu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 19 Apr 2010, Stephan Bosch wrote:
Now I'm wondering.. should this be configurable/optional?
Ideally I would suggest a vendor feature, which one has to require
before use.
But this would make problems using the feature from Webmail
fronte
17 matches
Mail list logo
