Re: Multiple servers and NFS
Am 25.07.2014 um 16:12 schrieb Eduardo Ramos: > I did not understand what the advantage of use dovecot LMTP with > director too. in "very short" words... with nfs ,the director should avoid concurrent events which may happen with lmtp too, depending to multiple server setup Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: Multiple servers and NFS
Hi Richard, I think its better balance with a router too. Is there any problem with use postfix+amavis in the front-end? I did not understand what the advantage of use dovecot LMTP with director too. On 07/25/2014 01:58 AM, Richard Hector wrote: On 25/07/14 15:30, Eduardo Ramos wrote: Hi Richard, In fact I thought it a little confusing. I had some bad experience with DNS RR when one of my IMAP server got down. Clients continued trying connect to broken server and it caused some problems. But when everything is ok, it works well. I drew a diagram with my idea. What do you think? https://dl.dropboxusercontent.com/u/41373531/mail.png Interesting, thanks. I'd forgotten to draw in the director ring. As I said, if we need load balancing we can do that on the router, which as I understand it will do more or less the same thing as LVS. It might be Cisco SLB, but I'm not sure; I'm not the router guy :-) But what interests me most is that your diagram shows the mx servers connecting directly to the backend servers, rather than going through the proxy director - I thought that was a no-no. Oh, and I don't think we want to load down our front-end MX servers with amavis, either. Thanks for your input :-) Richard
Re: Pigeonhole Sieve LDAP support
Hi Nathan, Nathan Schultheiss schreef op 25-7-2014 12:08: Hi Stephan, Yesterday I've make a update with your repo and now I've the 2.2.13 (e07f504f1040) And today I've error on my LDA: 2014-07-25 11:29:43 LDA(nat...@schultheiss.fr): Panic: file sieve-storage.c: line 471 (sieve_storage_unref): assertion failed: (storage->refcount > 0) 2014-07-25 11:29:43 LDA(nat...@schultheiss.fr): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x710bf) [0x7f0a74a3f0bf] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f0a74a3f19a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0a749f47fe] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x2c9e9) [0x7f0a720bb9e9] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x2c80) [0x7f0a7232ec80] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x44) [0x7f0a74fd3464] -> /usr/lib/dovecot/dovecot-lda(main+0x3b2) [0x402a92] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f0a7462f76d] -> /usr/lib/dovecot/dovecot-lda() [0x40333d] This should fix the assert: http://hg.rename-it.nl/dovecot-2.2-pigeonhole/rev/e3d3d7a5f642 Regards, Stephan.
dovecot-2.2.13 and CentOS 7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 HI, if someone need/want dovecot-2.2.13 rpms for CentOS 7 here're some one: http://wiki.mailserver.guru/doku.php/centos:mailserver.guru ttyl Django - -- "Bonnie & Clyde der Postmaster-Szene!" approved by Postfix-God http://wetterstation-pliening.info http://dokuwiki.nausch.org http://wiki.piratenpartei.de/Benutzer:Django -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJT0lR2AAoJEAdOz2FQpr/tNmQP/3Mrd+cQs6S/UDfUpTYIqRIY dcZrxUvwoktz1JN/kkmZOVOpCw6hnz0HHIb3Dq/ncKCYnSa2qlJRpLaswQPjWERJ KFNuHeRqqpQPe49PwBVZjkAn4JJv5DhF/+ggM1ATSfWp7JFt82+9r+ozrWeIjNXH QiaLSahyxo6/sjqOhZftRsRcZQkxulb1Opc8vC1nCBDlJ/8z9ZDyhxFNmyCCfLtD FDyDzzruqKv9ozQMFz/+kw0eQS7Q7LHM3ZeCd6y495u/6xR/sIiCUDVlUplsaEFi hVQdZFXtH58io94ILHhTHjf9qfczlLWMNI/cZsbChg5XEnk3SmWxTYW6zbXC5L2t Ry0OpZwL6iQ9erA1av2y4ez+Y+sSYdgHpXX/BhyD6qN3hSTbqJPL5jgEHeFDEYS7 j0j3AYRjYzRHpfW1LyFNFtrFWqJMRqyPjVisJfztcSV3rO4tEybZjYdxL86ngB8x kZByvHBbyqG44Wj+6kqBtsBCPOkfrwBOmjU+zMlJAfd2/F30M2vQ8rSJql1NUqA3 FKqjuyxV22NL3NR53AKakMR2aX/eRgZTX9DYod+iIhVELcAQmmE3OLeRwfRfIGNx lVlfOWkMbOQ85Jzg7pUAxLvmjyktIiHHLxlCryV/SZ3di3vp/eYPvVbP7v+OPHhH 1W0gbYk6YXxQt0+Xr4sq =TgrN -END PGP SIGNATURE-
2.2.13 + hg: Panic: file ioloop.c: line 39 (io_add_file): assertion failed: (fd >= 0)
Hi, Found this in logfiles: Jul 25 14:12:38 dovecot: pop3(c...@so.red): Error: UIDL: File name lookup failed: Message was expunged Jul 25 14:12:38 dovecot: pop3(c...@so.red): Disconnected: POP3 UIDLs couldn't be listed top=187/356348, retr=0/0, del=0/1207, size=789346199 Jul 25 14:12:38 dovecot: pop3(c...@so.red): Panic: file ioloop.c: line 39 (io_add_file): assertion failed: (fd >= 0) Jul 25 14:12:38 dovecot: pop3(c...@so.red): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xbdfc1f] -> /usr/lib/dovecot/libdovecot.so.0 [0xbdfc9d] -> /usr/lib/dovecot/libdovecot.so.0 [0xbdf514] -> /usr/lib/dovecot/libdovecot.so.0 [0xbf162d] -> /usr/lib/dovecot/libdovecot.so.0(io_add_istream+0x3f) [0xbf272f] -> dovecot/pop3 [0x804d149] -> /usr/lib/dovecot/libdovecot.so.0 [0xbff17a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x48) [0xbf1d88] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xff) [0xbf375f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x1e) [0xbf1e2e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x48) [0xbf1eb8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2d) [0xb9842d] -> dovecot/pop3(main+0x2a9) [0x804b3b9] -> /lib/i686/nosegneg/libc.so.6(__libc_start_main+0xdc) [0x6f7dec] -> dovecot/pop3 [0x804aeb1] Jul 25 14:12:38 dovecot: pop3(c...@so.red): Fatal: master: service(pop3): child 27510 killed with signal 6 (core dumped) (gdb) bt #0 0x00b1a402 in __kernel_vsyscall () #1 0x0070af30 in raise () from /lib/i686/nosegneg/libc.so.6 #2 0x0070c911 in abort () from /lib/i686/nosegneg/libc.so.6 #3 0x00bdfc14 in default_fatal_finish (type=, status=0) at failures.c:193 #4 0x00bdfc9d in i_internal_fatal_handler (ctx=0xbf82cd34, format=0xc0c784 "file %s: line %d (%s): assertion failed: (%s)", args=0xbf82cd54 "\202\232�") at failures.c:657 #5 0x00bdf514 in i_panic (format=0xc0c784 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:267 #6 0x00bf162d in io_add_file (fd=-1, condition=IO_READ, source_linenum=816, callback=0x804d150 , context=0x83ba628) at ioloop.c:40 #7 0x00bf272f in io_add_istream (input=0x83ba960, source_linenum=816, callback=0x804d150 , context=0x83ba628) at ioloop.c:86 #8 0x0804d149 in client_output (client=0x83ba628) at pop3-client.c:815 #9 0x00bff17a in stream_send_io (fstream=0x83baa48) at ostream-file.c:468 #10 0x00bf1d88 in io_loop_call_io (io=0x83baaf8) at ioloop.c:441 #11 0x00bf375f in io_loop_handler_run_internal (ioloop=0x83a5498) at ioloop-epoll.c:220 #12 0x00bf1e2e in io_loop_handler_run (ioloop=0x83a5498) at ioloop.c:488 #13 0x00bf1eb8 in io_loop_run (ioloop=0x83a5498) at ioloop.c:465 #14 0x00b9842d in master_service_run (service=0x83a53c0, callback=0x804b4e0 ) at master-service.c:566 #15 0x0804b3b9 in main (argc=Cannot access memory at address 0x0 ) at main.c:277 (gdb) Thanks, Toni
Re: Error after Upgrade
am 25.07.14 12:14 schrieb Reindl Harald : Am 25.07.2014 11:49, schrieb Jim Knuth: am 25.07.14 11:38 schrieb Reindl Harald : Am 25.07.2014 11:23, schrieb Jim Knuth: after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mails stuck in the Queue. I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine What’s wrong? the Debian package thanks, but that is from deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main how does it matter from where it is? so what - you updated, the new version leads in SEGFAULTS so that binary is at least on your machine broken and unstable the answer to "what's wrong" remains: that package yes, I know. ;) But my question goes also to the Maintainer. Any ideas or solution greatly appreciated. Thanks. downgrade Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core dumps disabled) Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core dumps disabled) http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 SIGSEGV11 CoreInvalid memory reference -- Mit freundlichen Grüßen, with kind regards, Jim Knuth - “Jesus wurde gekreuzigt, weil er bemerkt wurde. Deswegen verschwinde ich häufig von der Bildfläche.” Bob Dylan
Re: Error after Upgrade
Am 25.07.2014 11:49, schrieb Jim Knuth: > am 25.07.14 11:38 schrieb Reindl Harald : > >> Am 25.07.2014 11:23, schrieb Jim Knuth: >>> after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => >>> 2:2.2.13-1~auto+113 >>> I discovered that in my log and all mails stuck in the Queue. >>> I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine >>> What’s wrong? >> >> the Debian package > > thanks, but that is from > deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main how does it matter from where it is? so what - you updated, the new version leads in SEGFAULTS so that binary is at least on your machine broken and unstable the answer to "what's wrong" remains: that package >>> Any ideas or solution greatly appreciated. Thanks. >> >> downgrade >> >>> Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): >>> child 25638 killed with signal 11 (core >>> dumps disabled) >>> Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local >>> Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): >>> child 25639 killed with signal 11 (core >>> dumps disabled) >> >> http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 >> SIGSEGV11 CoreInvalid memory reference signature.asc Description: OpenPGP digital signature
Re: Pigeonhole Sieve LDAP support
Hi Stephan,
Yesterday I've make a update with your repo and now I've the 2.2.13
(e07f504f1040)
And today I've error on my LDA:
2014-07-25 11:29:43 LDA(nat...@schultheiss.fr): Panic: file sieve-storage.c:
line 471 (sieve_storage_unref): assertion failed: (storage->refcount > 0)
2014-07-25 11:29:43 LDA(nat...@schultheiss.fr): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x710bf) [0x7f0a74a3f0bf] ->
/usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f0a74a3f19a]
-> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0a749f47fe] ->
/usr/lib/dovecot/libdovecot-sieve.so.0(+0x2c9e9) [0x7f0a720bb9e9] ->
/usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x2c80) [0x7f0a7232ec80] ->
/usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x44) [0x7f0a74fd3464] ->
/usr/lib/dovecot/dovecot-lda(main+0x3b2) [0x402a92] ->
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f0a7462f76d] ->
/usr/lib/dovecot/dovecot-lda() [0x40333d]
I use:
deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main
deb-src http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main
On my dovecot I've for sieve:
plugin {
sieve = file:~/sieve;active=~/.dovecot.sieve
sieve_before = /home/vmail/.sieve/virus.sieve
}
That working without problem since the update.
After the update, account with sieve rule work with the LDA and without does
not work with the error listed.
I've found, if I add on the plugin section:
sieve_default = /home/vmail/.sieve/default.sieve
That work again without errors :)
Evtl. this fix can help people who they have the same error :)
I've no entry on my default.sieve it's just here for "fix" the "Panic" error.
Bests Regards,
Nathan
- Mail original -
De: "Stephan Bosch"
À: "Dovecot Mailing List"
Envoyé: Jeudi 24 Juillet 2014 14:44:27
Objet: Pigeonhole Sieve LDAP support
Hi,
Yesterday, I committed two important and rather big changes to the
Pigeonhole repository.
The first creates a generic interface for implementing Sieve script
storages. It was already possible to some extent to read Sieve scripts
from other sources than the local filesystem, such as Dovecot dict, but
that was still pretty limited, as it was not possible to do this with
sieve_before/sieve_after. This is now supported. But, more importantly,
ManageSieve did not support storing Sieve scripts on locations other
than the local filesystem. Now, alternatives can be implemented. Still,
I haven't actually implemented write access to a storage other than the
local filesystem yet, but now this would be much easier to achieve.
The second creates an LDAP script storage implementation. Much like the
dict storage, it is still read-only. It can be compiled directly into
the Sieve interpreter, and, alternatively, it can also be compiled as a
plugin called sieve_storage_ldap.
I've updated the documentation in the sources. For all Xi repository
users: I added compilation of LDAP storage as a plugin. Read the INSTALL
files and other files referenced therein for more information about how
to use the plugin. The plugin is installed as part of the dovecot-ldap
package.
This is a rather big change, but it should all be backwards compatible
in terms of configuration.
If you have problems (I heard about one so far), please don't hesitate
to notify me.
Regards,
Stephan.
Re: Error after Upgrade
am 25.07.14 11:38 schrieb Reindl Harald : Am 25.07.2014 11:23, schrieb Jim Knuth: after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => 2:2.2.13-1~auto+113 I discovered that in my log and all mails stuck in the Queue. I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine What’s wrong? the Debian package thanks, but that is from deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main Any ideas or solution greatly appreciated. Thanks. downgrade Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): child 25638 killed with signal 11 (core dumps disabled) Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): child 25639 killed with signal 11 (core dumps disabled) http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 SIGSEGV 11 CoreInvalid memory reference -- Mit freundlichen Grüßen, with kind regards, Jim Knuth - Better to reign in hell, than to serve in heaven! (John Milton)
Re: Error after Upgrade
Am 25.07.2014 11:23, schrieb Jim Knuth: > after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 => > 2:2.2.13-1~auto+113 > I discovered that in my log and all mails stuck in the Queue. > I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine > What’s wrong? the Debian package > Any ideas or solution greatly appreciated. Thanks. downgrade > Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master: service(lmtp): > child 25638 killed with signal 11 (core > dumps disabled) > Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local > Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master: service(lmtp): > child 25639 killed with signal 11 (core > dumps disabled) http://unixhelp.ed.ac.uk/CGI/man-cgi?signal+7 SIGSEGV 11 CoreInvalid memory reference signature.asc Description: OpenPGP digital signature
Error after Upgrade
Hello,
after upgrade (Debian wheezy) from dovecot 2:2.2.13-1~auto+103 =>
2:2.2.13-1~auto+113
I discovered that in my log and all mails stuck in the Queue.
I’ve had downgrade v 2:2.2.13-1~auto+103 an everything is fine.
What’s wrong?
Any ideas or solution greatly appreciated. Thanks.
Jul 25 11:03:01 server2 dovecot: lmtp(25638): Fatal: master:
service(lmtp): child 25638 killed with signal 11 (core dumps disabled)
Jul 25 11:03:01 server2 dovecot: lmtp(25639): Connect from local
Jul 25 11:03:01 server2 dovecot: lmtp(25639): Fatal: master:
service(lmtp): child 25639 killed with signal 11 (core dumps disabled)
Jul 25 11:03:01 server2 postfix/lmtp[25617]: 20773D10003:
to=, orig_to=,
relay=server1.art-domains.de[private/dovecot-lmtp], delay=0.05,
delays=0.03/
0/0.01/0.02, dsn=4.4.2, status=deferred (lost connection with
server1.art-domains.de[private/dovecot-lmtp] while sending end of data
-- message may be sent more than once)
Jul 25 11:03:01 server2 amavis[25541]: (25541-01) Passed CLEAN
{RelayedInbound}, [213.203.238.6]:53401 [193.175.143.182]
-> , Queue-I
D: 62B8BD10001, Message-ID: <53d21b91.2070...@fh-landshut.de>,
mail_id: AE71HPGl9ZR5, Hits: -5, size: 13518, queued_as: 20773D10003,
2771 ms
Jul 25 11:03:01 server2 amavis[25541]: (25541-01) Passed CLEAN,
-> , Hits:
-5, tag=-.9, tag2=2.5, kill=3, queued_as: 20773D10003,
L/Y/0/0
Jul 25 11:03:01 server2 postfix/lmtp[25607]: 62B8BD10001:
to=, relay=127.0.0.1[127.0.0.1]:10024, delay=3.9,
delays=1.2/0/0.01/2.8, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[
127.0.0.1]:10025): 250 2.0.0 Ok: queued as 20773D10003)
Jul 25 11:03:01 server2 postfix/qmgr[25508]: 62B8BD10001: removed
Jul 25 11:03:02 server2 postfix/lmtp[25615]: 20773D10003:
to=, orig_to=,
relay=server1.art-domains.de[private/dovecot-lmtp], delay=0.06, del
ays=0.03/0/0.03/0.01, dsn=4.4.2, status=deferred (lost connection with
server1.art-domains.de[private/dovecot-lmtp] while sending end of data
-- message may be sent more than once)
Jul 25 11:03:02 server2 dovecot: lmtp(25653): Connect from local
Jul 25 11:03:02 server2 dovecot: lmtp(25653): Fatal: master:
service(lmtp): child 25653 killed with signal 11 (core dumps disabled)
--
Mit freundlichen Grüßen,
with kind regards,
Jim Knuth
-
Die Freiheit der Rede hat den Nachteil, daß immer wieder Dummes,
Häßliches und Bösartiges gesagt wird. Wenn wir aber alles in allem
nehmen, sind wir doch eher bereit, uns damit abzufinden, als
sie abzuschaffen. [Churchill]
