[Dovecot] sieve vacation
Hello, scenario: OK 1. created vacation script (see below) OK 2. send message from u...@anotherdomain.tld to u...@domain.tld = got auto vacation response (2010-02-11T19:42:13) OK 3. send message from u...@anotherdomain.tld to u...@domain.tld = no response (is ok because :days 1 settings) (2010-02-11T19:47:46) BAD 4. send message from anotheru...@anotherdomain.tld to u...@domain.tld = no response (2010-02-11T19:48:04) Why is discarding vacation response for message implicitly delivered to u...@domain.tld ? log: 2010-02-11T19:42:13.669321+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=052a01caab49$ec4752e0$c4d5f8...@tld: sent vacation response to u...@anotherdomain.tld 2010-02-11T19:42:13.732541+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=052a01caab49$ec4752e0$c4d5f8...@tld: stored mail into mailbox 'INBOX' 2010-02-11T19:47:46.271534+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=053201caab4a$b295ece0$17c1c6...@tld: discarded duplicate vacation response to u...@anotherdomain.tld 2010-02-11T19:47:46.275891+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=053201caab4a$b295ece0$17c1c6...@tld: stored mail into mailbox 'INBOX' 2010-02-11T19:48:04.958622+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=053701caab4a$bda90220$38fb06...@tld: discarding vacation response for message implicitly delivered to u...@domain.tld 2010-02-11T19:48:04.965875+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=053701caab4a$bda90220$38fb06...@tld: stored mail into mailbox 'INBOX' vacation script: --- require vacation; vacation :days 1 :subject Auto reply auto reply message; -- Thank you -- Lampa
Re: [Dovecot] sieve vacation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 12 Feb 2010, Lampa wrote: BAD 4. send message from anotheru...@anotherdomain.tld to u...@domain.tld = no response (2010-02-11T19:48:04) Why is discarding vacation response for message implicitly delivered to u...@domain.tld ? See: http://tools.ietf.org/html/rfc5230 Sec 4.5 list all and any address via :addresses. Or, alternatively, hack the Sieve plugin to ignore the address check. Regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBS3Uug7+Vh58GPL/cAQKmrQf/R53EFVyPo2D3NUpFEQn2gQszIsIiu8wa NoM26lWp596h/EAQC0gtqfWPa89ojuwwH8aM1uzwgnd/kA1zaQq+l5wCQoXo9Xtj BztKZCMQb0ZvZHEipRnuWo/Cno6DjsY9+xix+ZwPKjsnsPeQYXC1QEgoifLBPjmY 93n3WluMdGi2GIA4+mxpyIZpEGFc/Hpo7xvrrcBVSUevBhy78CmaB95+7kb/tmgj YTe5hzctFJhcEFwomXyqd55sUxqAncFPjDZwl+8W+vtoLs1Ki40UqMtX5K8ZkDVo BIaIwjDJ5bmHdsZbmRHecRsnD/WosSViKgazplh03rDeQeq+xH6dng== =G2M4 -END PGP SIGNATURE-
Re: [Dovecot] Problem in sharing mailboxes across users
Timo Sirainen ha scritto:
On Wed, 2010-02-10 at 20:47 +0100, Rampage wrote:
as you can see the shared folder is listed but something seems to be
wrong in the path.
I don't see anything wrong.
mhhh maybe it's an issue in thunderbird 2 that can't manage this?
couse actually in TB i cant see the shared folder.. or well, i can see
it in the subscription management, but i can't subscribe to it and i
cant access the content.
everything works fine when talking with the imap server directly.
Well, subscriptions aren't necessary in any way. You could just disable
subscriptions from TB completely and you should be able to access the
mailbox.
But, anyway, if you can't subscribe to it, that's the problem. And
looking at your dovecot -n output again, I do see a problem:
namespace:
type: private
separator: /
prefix: INBOX/
inbox: yes
list: yes
subscriptions: yes
Your primary namespace has INBOX/ prefix..
namespace:
type: shared
separator: /
prefix: shared/%%u/
location:
maildir:/var/utenti/%d/%%n/Maildir:INDEX=/var/utenti/%d/%
n/Maildir/shared/%%u
list: children
And here you don't have subscriptions=no, so it tries to create the
subscriptions to the remote user's Maildir. Either it fails, or it
modifies the other user's subscriptions. Neither is very good..
So you really should have subscriptions=no for the shared namespace. But
then you'll also need to create a namespace with empty prefix where the
subscriptions actually are saved to. I don't much like the INBOX/ prefix
in any case, so I'd just use:
namespace private {
prefix =
separator = /
subscriptions = yes
}
namespace private {
prefix = INBOX/
separator = /
subscriptions = yes
hidden = yes
list = no
}
So that the INBOX/ prefix still works for those people who already have
configured it to their clients, but others would be using the empty
prefix. That'll also fix the shared subscriptions.
Hi again :)
Definitely the problem seems to be namespace related.
i applied the modifications to the dovecot.conf file as you suggested
but now i'm experiencing duplicated folders.
-
b list *
* LIST (\HasNoChildren) / Trash
* LIST (\HasChildren) / INBOX
* LIST (\HasNoChildren) / INBOX/Trash
* LIST (\Noselect \HasChildren) / shared/catt...@ciccio.it
* LIST (\HasNoChildren) / shared/catt...@ciccio.it/bumbum
-
the dovecot.conf namespace section is as follow:
-
namespace private {
separator = /
prefix =
subscriptions = yes
}
namespace private {
separator = /
prefix = INBOX/
inbox = yes
hidden = yes
}
namespace shared {
separator = /
prefix = shared/%%u/
location =
maildir:/var/utenti/%d/%%n/Maildir:INDEX=/var/utenti/%d/%n/Maildir/shared/%%u
subscriptions = no
list = children
}
-
again... thank you very much for the help :)
Best regards
Francesco
Re: [Dovecot] sieve vacation
Following from Steffen Kaiser's response, RFC5230 explains the conditions necessary for the Sieve Vacation extension to trigger a response. This says: Vacation MUST NOT respond to a message unless the recipient user's email address is in a To, Cc, Bcc, Resent-To, Resent-Cc, or Resent-Bcc line of the original message. So your scenario 4 happens when the sender is only in the envelope, and not in the headers. For example: this transaction will get a response because the mailbox address is in the To: header ehlo there.com mail from: d...@there.com rcpt to: u...@domain.tld envelope recipient, mailsystem routes with this information data To: Some User u...@domain.tld header recipient must be correlated for Sieve Vacation to send a response From: Dude d...@there.com Subject: message Hi there . This transaction will not get a response, and will trigger the discarding vacation response for message implicitly delivered to u...@domain.tld log: ehlo there.com mail from: d...@there.com rcpt to: u...@domain.tld data Subject: message Hi there . Cheers, -Martin Foster Le 12-Feb-10 21:00, dovecot-requ...@dovecot.org a écrit : Message: 9 Date: Fri, 12 Feb 2010 09:18:23 +0100 From: Lampalamp...@gmail.com Subject: [Dovecot] sieve vacation To: Dovecot Mailing Listdovecot@dovecot.org Message-ID: 9aef75b11002120018v69f185b5hb0a9e0f7dad1e...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hello, scenario: OK 1. created vacation script (see below) OK 2. send message fromu...@anotherdomain.tld tou...@domain.tld = got auto vacation response (2010-02-11T19:42:13) OK 3. send message fromu...@anotherdomain.tld tou...@domain.tld = no response (is ok because :days 1 settings) (2010-02-11T19:47:46) BAD 4. send message fromanotheru...@anotherdomain.tld to u...@domain.tld = no response (2010-02-11T19:48:04) Why is discarding vacation response for message implicitly delivered tou...@domain.tld ? log: 2010-02-11T19:42:13.669321+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=052a01caab49$ec4752e0$c4d5f8...@tld: sent vacation response to u...@anotherdomain.tld 2010-02-11T19:42:13.732541+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=052a01caab49$ec4752e0$c4d5f8...@tld: stored mail into mailbox 'INBOX' 2010-02-11T19:47:46.271534+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=053201caab4a$b295ece0$17c1c6...@tld: discarded duplicate vacation response tou...@anotherdomain.tld 2010-02-11T19:47:46.275891+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=053201caab4a$b295ece0$17c1c6...@tld: stored mail into mailbox 'INBOX' 2010-02-11T19:48:04.958622+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=053701caab4a$bda90220$38fb06...@tld: discarding vacation response for message implicitly delivered tou...@domain.tld 2010-02-11T19:48:04.965875+01:00 hermes dovecot: deliver(u...@domain.tld): sieve: msgid=053701caab4a$bda90220$38fb06...@tld: stored mail into mailbox 'INBOX' vacation script: --- require vacation; vacation :days 1 :subject Auto reply auto reply message; -- Thank you -- Lampa --
Re: [Dovecot] POP3 with dovecot LDA and sieve
Does that really work? http://old.nabble.com/Virtual-POP3-Inbox-question-td27488956.html POP3 uses only the INBOX - by default. But you could add some 'magic' with the virtual plugin: http://wiki.dovecot.org/Plugins/Virtual Regards, Pascal
[Dovecot] passing parameters to deliver
Is any posibility to pass parameters/environment variables to deliver with sieve plugin? I have some procmail rules to decide where mail should go, which can't be migrated to sieve (uses external programs). So far I write it to maildirs, but I wonder to migrate to mdbox, and procmail can't handle it. Any ideas? KJ -- http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewskiej-wprowadzenie/ można nie mieć nawet żadnego sensownego argumentu, a dzięki odpowiedniej gestykulacji stworzyć poczucie wiarygodności. Puls Biznesu
[Dovecot] dovecot v1.2.10 + unknown mail_uid parameter
hi... i upgrading dovecot from v1.0.7 to v1.2.10, so i perform some modifications (http://wiki.dovecot.org/Upgrading/1.1 and http://wiki.dovecot.org/Upgrading/1.2), but i have the following problem when i want to test installation: in dovecot.conf, i set the user mail: mail_uid= 72940 mail_gid= 72941 but when i try to start dovecot i have the following error: # sbin/dovecot Error: Error in configuration file /etc/dovecot/etc/dovecot.conf line 962: Unknown setting: mail_uid Fatal: Invalid configuration in /etc/dovecot/etc/dovecot.conf # sbin/dovecot --version 1.2.10 i try, but i dont know how to fix them :( thanks in advance! :) -- Salu2 ;)
[Dovecot] dovecot v1.2.10 + unknown mail_uid parameter [RESOLVED]
hi.. i can resolve them setting de following parameters: in dovecot.conf: - coment mail_uid and mail_gid parameters: #mail_uid= 72940 #mail_gid= 72941 in dovecot-ldap.conf: - add the foollowing parameters in user_attrs: user_attrs= .,=uid=72940,gid=72941 thanks! -- Salu2 ;)
[Dovecot] deliver problem ( Error: file_dotlock_create )
Hello all ( Postfix and Dovecot ) Trying to use deliver as mailbox_command with Postfix I get this error each time an email is arriving deliver(): Error: file_dotlock_create(/var/mail/) failed: Permission denied (euid=3003() egid=3010(smig) missing +w perm: /var/mail) (set mail_privileged_group=mail) Doea this means I have to chmod 777 the /var/mail directory ? Thanks a lot
Re: [Dovecot] quick question
I think mail is the wrong application for nfs, because nfs is slow for metadata operations. Would rather use it for vm hosting than mail. We used to have a small clustered netapp with 10k hdds and three frontend servers with postfix and courier imap/pop3. the setup was stable however the performance was not good. So we build a imap cluster out of a pair of dell r710 (6 x 15K hdds) with centos 5 drbd and heartbeat. I will scale this setup by adding another pair of r710 servers and randomizing the mailboxes between the imap/pop3 cluster pairs. An imap proxy will direct the users to the right server and the frontend mx servers will also send the mail to the right server by using smtp as tranport and postfix transport maps for routing. In the future i would like to switch from courier to dovecot and using lmtp as transport to our mailstore. We currently have 1 mailboxes only 300 - 400 imap connections but a lot pop access the load an the active r710 is only 0.10 :) I think mail is a problem which you can easily partition so why have all eggs in one basket :) alex
Re: [Dovecot] Anyone successfully setup Continous Backup of mailboxes using rsync ?
i use drbd to keep the mailstore redundant and rsnapshot for backup.
[Dovecot] REPOST: mbox vs maildir
Ignoring my previous message just for a second, I realized that my
config wasn't correct. First the layout:
~mail/
~mail/Drafts
~mail/Ashley-Feb09
~mail/Others-Feb09
~mail-Archives/
~mail-Archives/2009/
~mail-Archives/2009/Ashley/
~mail-Archives/2009/Ashley/Ashley-Dec09
~mail-Archives/2009/Ashley/Ashley-Nov09
~mail-Archives/2009/Ashley/Ashley-Oct09
So I (now) have this for namespaces:
namespace private {
separator = /
prefix = mail/
location = mbox:~/mail:INBOX=/var/mail/%u
inbox = yes
hidden = no
list = yes # for v1.1+
}
namespace private {
separator = /
prefix = mail-Archives/
location = maildir:~/mail-Archives:LAYOUT=fs
inbox = no
hidden = no
list = yes
subscriptions = yes
}
But when I'm in Thunderbird and I try to subscribe to anything that
falls inside of ~/mail-Archives/ it won't work. I can browser all the
way down to the folder, but I can't see anything within that folder.
For example, consider the full path to the following 'Ashley-Dec09'
mailbox:
~mail-Archives/2009/Ashley/Ashley-Dec09
In Thunderbird, when I hit 'Subscribe' I can browse down to '2009'
and I can see 'Ashley', but I can't drill down into it and subscribe to
'Ashley-Jan09'.
What am I missing here?
Re: [Dovecot] Capability COMPRESS implemented?
On Tue, 2009-09-29 at 16:40 +0100, Ed W wrote: Yeah, not for next half a year at least. Anyway, it would basically need istream and ostream implementations for zlib. istream implementation kind of already exists in zlib plugin, except it's using gz*() functions instead of doing everything in memory. So: - create zlib istream using zlib's deflate*() functions (I think?) and which takes another istream as input - convert zlib plugin to use that stream instead The above is now done. Mainly because seeking backwards in bzip2 compressed mails was broken. - implement zlib ostream Done also. - create yet another proxy to login processes. Probably some day I should combine all of them to one that only proxies i/ostreams. Although implementing SSL i/ostreams could be a bit difficult. This isn't done.. I've a separate http://hg.dovecot.org/dovecot-2.0-sslstream/ that does ssl proxying with ssl iostreams. It's probably easier to change to support compression proxying as well. Lets see if I can manage to do that now.. Anyway that code would be merged only for v2.1, since it changes things so much. signature.asc Description: This is a digitally signed message part
[Dovecot] scalability
Hi Folks, How scalable is dovecot. Do you think a machine with a dual core 2.8Ghz processor and 2GB of RAM would do a business with 600 users? This server will have a 100Mbps link to the net, however it will be access by the business using a couple of ADSL lines (Roughly 7Mbps each). This machine will also be running Postfix Your help is appreciated Cheers Jonny
Re: [Dovecot] scalability
On Feb 12, 2010, at 4:57 PM, Jonathan Tripathy wrote: How scalable is dovecot. Do you think a machine with a dual core 2.8Ghz processor and 2GB of RAM would do a business with 600 users? This server will have a 100Mbps link to the net, however it will be access by the business using a couple of ADSL lines (Roughly 7Mbps each). I'm running about twice that (though mostly low-traffic users) on about 2/3 of a machine at one site. Dovecot is VERY fast. -Dave -- Dave McGuire Port Charlotte, FL
[Dovecot] problem with deliver segfaulting
i'm facing a pretty hard to debug problem when trying to use dovecot LDA (deliver) from postfix. After having all configured, mail deliver fails. This is from my maillog: Feb 12 21:27:54 correio postfix/pipe[12484]: 930F9F6105: to=solu...@domain.com.br, relay=dovecot, delay=0.21, delays=0.03/0.01/0/0.18, dsn=4.3.0, status=SOFTBOUNCE (Command died with signal 11: /usr/libexec/dovecot/deliver) at the same time, i have from my /var/log/messages: Feb 12 21:27:54 correio kernel: deliver[12485]: segfault at 0 ip 4c1be763 sp bff64c28 error 4 in libc-2.5.so[4c193000+13f000] so, seems deliver segfaults. so i tried enabling mail_debug=yes on dovecot.conf for getting some debug . and, with mail_debug enabled, deliver WORKS Feb 12 21:28:41 correio postfix/pipe[12748]: 1A969F6105: to=solu...@domain.com.br, relay=dovecot, delay=0.28, delays=0.03/0.01/0/0.24, dsn=2.0.0, status=sent (delivered via dovecot service) disabling mail_debug makes the segfault happens again and reenabling mail_debug make it works again ! how can i debug this !?!?!? -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email gertru...@solutti.com.br My SPAMTRAP, do not email it
Re: [Dovecot] problem with deliver segfaulting
Em 12/02/2010 22:35, Leonardo Rodrigues escreveu: Feb 12 21:28:41 correio postfix/pipe[12748]: 1A969F6105: to=solu...@domain.com.br, relay=dovecot, delay=0.28, delays=0.03/0.01/0/0.24, dsn=2.0.0, status=sent (delivered via dovecot service) disabling mail_debug makes the segfault happens again and reenabling mail_debug make it works again ! how can i debug this !?!?!? and now the most weird thing i found ... COMMENTING out the mail_debug line on dovecot.conf make it works Having 'mail_debug=no' makes it segfaults, having it mail_debug=yes make it works and commenting out the mail_debug line makes it works too !!! i have found something mentioning postfix and mail_debug on http://wiki.dovecot.org/LDA/Postfix but that says about dovecot older than 1.0.1, which is not my case, i'm running 1.2.10. that was weird . -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email gertru...@solutti.com.br My SPAMTRAP, do not email it
Re: [Dovecot] problem with deliver segfaulting
On Fri, 2010-02-12 at 22:35 -0200, Leonardo Rodrigues wrote: Feb 12 21:27:54 correio postfix/pipe[12484]: 930F9F6105: to=solu...@domain.com.br, relay=dovecot, delay=0.21, delays=0.03/0.01/0/0.18, dsn=4.3.0, status=SOFTBOUNCE (Command died with signal 11: /usr/libexec/dovecot/deliver) Can you cause it to crash by running deliver directly from command line? If so, gdb backtrace would be nice: gdb /usr/libexec/dovecot/deliver run it probably crashes here bt full signature.asc Description: This is a digitally signed message part
Re: [Dovecot] problem with deliver segfaulting
Em 12/02/2010 22:57, Timo Sirainen escreveu:
Can you cause it to crash by running deliver directly from command line?
If so, gdb backtrace would be nice:
gdb /usr/libexec/dovecot/deliver
run
it probably crashes here
bt full
yes i can make it crash from command line. Hope the informations help
you
i'm running a CentOS 5.4 i686 box, dovecot 1.2.10. i've just recompiled
1.2.10 to install it without stripping. i've always heard that
(stripping) makes debug with gdb too weak ... i dont know about that,
dont have sure. Anyway, i just recompiled and installed with 'make
install' instead of my usual 'make install-strip'
dovecot -n is at the end of the email
as i've already found this seems to be mail_debug dovecot.conf variable
related i'll try some variations here.
1) running with 'mail_debug=no' on dovecot.conf, deliver segfaults
[r...@correio dovecot]# gdb /usr/libexec/dovecot/deliver
GNU gdb Fedora (6.8-37.el5)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as i386-redhat-linux-gnu...
(gdb) run -c /etc/dovecot/dovecot.conf -p mensagem.eml -f
solu...@domain.com.br -d solu...@domain.com.br
Starting program: /usr/libexec/dovecot/deliver -c
/etc/dovecot/dovecot.conf -p mensagem.eml -f solu...@domain.com.br -d
solu...@domain.com.br
[Thread debugging using libthread_db enabled]
[New Thread 0xb8060a40 (LWP 20455)]
Program received signal SIGSEGV, Segmentation fault.
0x4c1be763 in unsetenv () from /lib/libc.so.6
(gdb) bt full
#0 0x4c1be763 in unsetenv () from /lib/libc.so.6
No symbol table info available.
#1 0x0805cc44 in main (argc=9, argv=0xbfe6da54) at deliver.c:497
_data_stack_cur_id = 2
config_path = 0xbfe6dbc0 /etc/dovecot/dovecot.conf
mailbox = 0x80f167d INBOX
auth_socket = value optimized out
home = value optimized out
destaddr = 0x0
user = 0xbfe6dc03 solu...@domain.com.br
errstr = value optimized out
path = 0x8107f70 /etc/dovecot/mensagem.eml
orig_user = value optimized out
extra_fields = {arr = {buffer = 0x0, element_size = 0}, v = 0x0,
v_modifiable = 0x0}
mail_user = value optimized out
raw_mail_user = value optimized out
raw_ns = value optimized out
storage = value optimized out
box = value optimized out
raw_box = value optimized out
input = value optimized out
t = value optimized out
headers_ctx = value optimized out
mail = value optimized out
cwd = /etc/dovecot, '\0' repeats 1232 times,
ä\021\000\000(Îæ¿Àÿ\030LìÏæ¿`µ\027L\000\0002Lä\021\000\000\003\000\000\0002\000\000\000,
'\0' repeats 45 times,
0L\000à1L\\Ñ1L\\Ñ1L\000\000\000\000\005\000\000\000\000à1L\000\0002L0ñ1Lä\0212L\\001\000\003\000\000\000\005\227\030L\b\000\000\000Àÿ\030L/\000\000\000X\006\031LhÎæ¿\005\227\030L\b\000\000\000\025\000\000\000Àÿ\030L°Îæ¿tù\027LP\032\006¸À\027\006¸\025\000\000\000\001\000\000\000O2LÀ\027\006¸Ø\027\006¸\020\000\000\000Ø...
process_euid = 0
stderr_rejection = false
keep_environment = false
user_auth = true
mtime = value optimized out
i = value optimized out
ret = value optimized out
userdb_pool = (pool_t) 0x0
str = value optimized out
error = MAIL_ERROR_NONE
(gdb) c
Continuing.
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) quit
[r...@correio dovecot]#
2) running with mail_debug line COMMENTED OUT or with mail_debug=yes on
dovecot.conf, deliver works just fine as its supposed to work :)
[r...@correio dovecot]# gdb /usr/libexec/dovecot/deliver
GNU gdb Fedora (6.8-37.el5)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as i386-redhat-linux-gnu...
(gdb) run -c /etc/dovecot/dovecot.conf -p mensagem.eml -f
solu...@domain.com.br -d solu...@domain.com.br
Starting program: /usr/libexec/dovecot/deliver -c
/etc/dovecot/dovecot.conf -p mensagem.eml -f solu...@domain.com.br -d
solu...@domain.com.br
[Thread debugging using libthread_db enabled]
[New Thread 0xb8004a40 (LWP 20698)]
Program exited normally.
(gdb)
dovecot -n output:
[r...@correio dovecot]# dovecot -c /etc/dovecot/dovecot.conf -n
# 1.2.10: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.29.1-grsec-Solutti i686 CentOS release 5.4 (Final) ext3
base_dir: /var/run/dovecot/
protocols: imap imaps pop3 pop3s
listen(default): *:143
listen(imap): *:143
listen(pop3): *:110
ssl_listen(default): *:993
ssl_listen(imap): *:993
ssl_listen(pop3): *:995
ssl_cert_file: /etc/dovecot/ssl/certs/dovecot.pem
ssl_key_file: /etc/dovecot/ssl/private/dovecot.pem
ssl_cipher_list: ALL:!LOW:!SSLv2
disable_plaintext_auth: no
login_dir:
Re: [Dovecot] problem with deliver segfaulting
On Fri, 2010-02-12 at 23:28 -0200, Leonardo Rodrigues wrote:
Program received signal SIGSEGV, Segmentation fault.
0x4c1be763 in unsetenv () from /lib/libc.so.6
(gdb) bt full
#0 0x4c1be763 in unsetenv () from /lib/libc.so.6
No symbol table info available.
#1 0x0805cc44 in main (argc=9, argv=0xbfe6da54) at deliver.c:497
Oh, this one. It's a libc bug.. I reported it to Ubuntu people already:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/380487
Wouldn't hurt to report it elsewhere too :)
Anyway, it crashes only if the problematic setting is first in the
config file. Also the attached patch probably helps?
diff -r 1ff706e7d95f src/deliver/deliver.c
--- a/src/deliver/deliver.c Sun Feb 07 01:55:06 2010 +0200
+++ b/src/deliver/deliver.c Sat Feb 13 03:43:45 2010 +0200
@@ -355,6 +355,7 @@
if (fd 0)
i_fatal_status(EX_TEMPFAIL, open(%s) failed: %m, path);
+ env_put(_glibc_bug_workaround=1);
input = i_stream_create_fd(fd, (size_t)-1, TRUE);
i_stream_set_return_partial_line(input, TRUE);
while ((line = i_stream_read_next_line(input)) != NULL) {
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] problem with deliver segfaulting
Em 12/02/2010 23:43, Timo Sirainen escreveu: Oh, this one. It's a libc bug.. I reported it to Ubuntu people already: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/380487 Wouldn't hurt to report it elsewhere too :) Anyway, it crashes only if the problematic setting is first in the config file. Also the attached patch probably helps? why i'm always that lucky to hit this weird bugs :) mail_debug was really the first option on dovecot.conf. i've moved base_dir to the first option and deliver works just fine, even having mail_debug = no .. well ... dovecot LDA is running and will be, from now on, my official delivery agent !!! I'm ready to try out that patch you commited to enable lda zlib compression but after patching and compiling, i cannot start dovecot anymore. I've just sent you an email some hours ago with that i dont know what to do by now, i'm stuck on that. -- Atenciosamente / Sincerily, Leonardo Rodrigues Solutti Tecnologia http://www.solutti.com.br Minha armadilha de SPAM, NÃO mandem email gertru...@solutti.com.br My SPAMTRAP, do not email it
Re: [Dovecot] Capability COMPRESS implemented?
On Sat, 2010-02-13 at 01:19 +0200, Timo Sirainen wrote:
- create yet another proxy to login processes. Probably some day I
should combine all of them to one that only proxies i/ostreams. Although
implementing SSL i/ostreams could be a bit difficult.
Looks like COMPRESS=DEFLATE is valid only after login, which made it
much easier to implement. It's now in v2.0 hg. Tested that it seems to
work with Thunderbird 3.0.1.
http://hg.dovecot.org/dovecot-2.0/rev/29f5567e0a9a
protocol imap {
mail_plugins = zlib imap_zlib
}
plugin {
imap_zlib_compress_level = 6 #default
}
Only COMPRESS=DEFLATE is advertised, but it actually supports all
compression methods supported by zlib plugin. So basically deflate and
bz2 (and gz, but it's basically same as deflate).
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] scalability
Quoting Jonathan Tripathy jon...@abpni.co.uk: How scalable is dovecot. Very, but also it will vary by how you implement it (mbox or maildir, local or remote disk, etc). Do you think a machine with a dual core 2.8Ghz processor and 2GB of RAM would do a business with 600 users? Yes, unless something else is slowing it down. This machine will also be running Postfix If it is only running Postfix, it will probably be okay most of the time, but if Postfix gets slammed it may slow down dovecot (actually the machine) for a bit... But if in addition to postfix it is doing (local) anti-virus and anti-spam and such, it may not be sufficient, depending on setup. In my experience, dovecot takes almost no resources, Postfix/sendmail on take excessive resources occasionally when a spammer/hacker is hitting the machine hard, and anti-spam/anti-virus programs can bring any system to its knees... Your help is appreciated To few details to give any definitive answers... Cheers Jonny -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns!
