Re: [Dovecot] v1.2.2 released
I experienced a strange effect after updating from 1.2.1 to 1.2.2 with Horde. IMP 4.3.4 had problems with GnuPG handling while Dovecot 1.2.1 was installed, but IMP 4.3.3 had no problems. Now I updated to Dovecot 1.2.2 and IMP 4.3.4 is also running flawless :-) Is that an known issue ? Christian
Re: [Dovecot] High Availability strategies
Thanks a lot for all the answers. We already have high availability on the storage, so we'll go with Timo's proposal, mainly because it's the closer one to our current situation. Thanks! El Sábado 25 Julio 2009 a las 01:58, Timo Sirainen escribió: On Jul 24, 2009, at 5:00 AM, Joseba Torre wrote: we have a medium setup (8000 pop and imap users using almost every available client, 800GB of stored mails using maildir on a Celerra NFS server, with index files on local disks, and procmail for local delivery), being served by a Dell PowerEdge 2850 (2GB RAM and dual P4 Xeon 3,2GHz). Our current not-so-high availability setup is based on a similar server with the same setup and a easy but manual process to switch from one server to another. So you currenly have a single server serving all imap/pop3 users? - The recommended setup, with each user being sent always to the same server, is not possible because our load balancers (Cisco Catalyst 6000) can't do that. - We could put both servers behind the load balancer, and keep local index files on each server. Usually the same ip we'll be redirected to the same server, so few problems will arise. When a user is sent to a new server, index will be rebuilt so performance will be bad but we should not expect other problems, right? If a single server can handle all users fine, I wouldn't try anything special here. Just have them work as a master/slave and install some kind of a heartbeat to switch between them. - We could also put the index files on a nfs share. No problems, but pretty bad performance. If there's only a single server accessing the mails, you can use mail_nfs_*=no and the performance shouldn't be that bad. - We could also get more ram for the servers and keep indices in memory. I'd say local disk is much better. Using deliver instead of procmail could improve performance? http://wiki.dovecot.org/LDA/Indexing - We've also thought about some more or less weird setups, like setting up a GFS filesystem for the index files, or setting up a proxy on every server which redirect users to their fixed server, but they seem too complex for few advantages. Assuming still a master/slave setup, you could use DRBD to replicate indexes between local disks. -- Joseba Torre. Vicegerencia de TICs, área de Explotación
Re: [Dovecot] Unable to (un)subscribe mbox with AIX, NFS and netapp filer
Hi Timo,
today I found this in the logs again:
Jul 29 10:38:27 trevi mail:err|error dovecot: IMAP(beckerr):
fchown(/u/f0/rzuser/beckerr/Mail/.subscriptions.lock, -1, -1)
failed: Invalid argument
Jul 29 10:38:27 trevi mail:err|error dovecot: IMAP(beckerr):
file_dotlock_open() failed with subscription file
/u/f0/rzuser/beckerr/Mail/.subscriptions: Invalid argument
I located the bug in src/lib/file-dotlock.c ... a patch is attached.
Ralf
Timo Sirainen schrieb am 07.07.2009 18:40:
On Tue, 2009-07-07 at 17:58 +0200, Axel Luttgens wrote:
Is my understanding of these sentences correct?
If owner and group are -1, nothing is done?
In this case it should be save to skip the call, shouldn't it?
Yes, I guess so.
Yes. Committed: http://hg.dovecot.org/dovecot-1.2/rev/d6337be8ae30
Unless the rationale for that call is to ensure a correct cache
flushing for NFS clients, while being some kind of (costly) no-op
otherwise?
In that case I would have used those nfs_flush_*() functions.
--
__
Dipl.-Inform. (FH) Ralf Becker Rechenzentrum (r/ft) der FH Trier
(Network|Mail|Web|Firewall) University of applied sciences
Administrator Schneidershof, D-54293 Trier
Mail: beck...@fh-trier.deFon: +49 651 8103 499
Web: http://www.fh-trier.de/~beckerrFax: +49 651 8103 214
PubKey: http://www.fh-trier.de/~beckerr Crypto: GnuPG, S/MIME
__
Wenn Gott gewollt haette, dass E-Mail in HTML geschrieben wuerden,
endeten Gebete traditionell mit /amen. (Tom Listen)
--- dovecot-1.2.2/src/lib/file-dotlock.c.org2009-07-29 10:44:21.0
+0200
+++ dovecot-1.2.2/src/lib/file-dotlock.c2009-07-29 10:44:42.0
+0200
@@ -780,7 +780,7 @@
fd = file_dotlock_open(set, path, flags, dotlock);
umask(old_mask);
- if (fd != -1 (uid != (uid)-1 || gid != (gid_t)-1)) {
+ if (fd != -1 (uid != (uid_t)-1 || gid != (gid_t)-1)) {
if (fchown(fd, uid, gid) 0) {
if (errno == EPERM uid == (uid_t)-1) {
i_error(%s, eperm_error_get_chgrp(fchown,
smime.p7s
Description: S/MIME Cryptographic Signature
Re: [Dovecot] v1.2.2 released / horde
Christian Felsing schrieb: I experienced a strange effect after updating from 1.2.1 to 1.2.2 with Horde. IMP 4.3.4 had problems with GnuPG handling while Dovecot 1.2.1 was installed, but IMP 4.3.3 had no problems. Now I updated to Dovecot 1.2.2 and IMP 4.3.4 is also running flawless :-) Is that an known issue ? Christian Hi , what means strange ? where is the relation from dovecot and imp handling gpg i speculate gpg problems are pure to imp and do not relate do dovecot in anyway -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
Re: [Dovecot] High Availability strategies
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 27 Jul 2009, Timo Sirainen wrote: BTW. http://dovecot.org/talks/berlin-2009-07-02.pdf has a list of some possible ways to cluster Dovecot. IMO You should place all slides and conference papers online - at least I did not found them on dovecot.org ... . Some people asked me lately about how professional Dovecot is. Regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSnAY8HWSIuGy1ktrAQJJNgf/bNkRmQPSzN+scVAaHmnRVp4Q+BZaCETF ybDsZo6THC6xAG73ZDcGHJQpIt5F9WFo4Gvft4JK/m3cL86LQ2fa2qlZgOo6vPgJ FsXhtUHRPd5AyC6UgbRMgjNj5u1H9L86dz+XM1DSDKYUCMZuwD+jBahCXhMMzBNC FoeENhx+XgU2T8JsaPTXMS2Z0qpjTblyT7WwarKk69F9q1BsCT1IdDgvLwOkIq+G 4WghwWNM5MW6NjLLmGjGP/jfdSa5LB1gs6DFBqmTuK7FHB9nR6OqCWagUninBPlS T2ILMVtNhsTx3/D/q97QDBQN7TMKSOk5Okmn6rpUlRn2uvwU3YhCvw== =4C0o -END PGP SIGNATURE-
Re: [Dovecot] dovecot-1.2.2+sieve 0.1.9: sieve issues with (global?) includes
Stephan Bosch schreef:
Tom Hendrikx schreef:
Hi,
After upgrading from dovecot 1.1 to dovecot 1.2.2 and the new sieve
implementation (0.1.9), I'm having some strange problems. I'm including
some general purpose scripts into my user script from sieve_global_dir.
After some tests it seems that ths scripts get executed at random:
sometimes the mail gets stored in the correct dir, and sometimes it goes
to inbox. This also happens while using the same compiled .svbin file.
Another indication that something is wrong with the compiled .svbin is
output of sieved (see below). Running sieved on the compiled
test{1,2,3}.svbin files gives regular output.
Output of 'sieved /home/tomhendr/.default.svbin
===
* Required extensions:
0: include (16)
1: fileinto (5)
Panic: file ext-include-variables.c: line 133
(ext_include_variables_dump): assertion failed: (global_vars != NULL)
Error: Raw backtrace: sieved [0xa7fbfe10] -
sieved(default_fatal_handler+0x57) [0xa7fbfe97] - sieved [0xa7fc006e]
- sieved [0xa7f7384c] - sieved(ext_include_binary_dump+0x48)
[0xa7f531c8] - sieved(sieve_binary_dumper_run+0x119) [0xa7f671a9] -
sieved(sieve_dump+0x42) [0xa7f4bf82] -
sieved(sieve_tool_dump_binary_to+0x6f) [0xa7f7b77f] -
sieved(main+0x174) [0xa7f42564] -
/lib/libc.so.6(__libc_start_main+0xe2) [0xa7dce712] - sieved
[0xa7f422b1]
Aborted
===
Thanks for the thorough bug report. I could reproduce this instantly. I
forgot to initialize the binary for use with the include extension in
one particular situation: when the binary is loaded from disk. Directly
after compilation, all works well. Fixed:
http://hg.rename-it.nl/dovecot-1.2-sieve/rev/d989537882d0
Applied and tested. sieved and sieve-test now complain with an error
message, but everything seems to function when run from within dovecot.
Error: sieve: include: sieve_dir and home not set (wanted script spam.sieve)
Error: failed to load binary: .default.svbin
I'll wait for your new release, but of course I'm willing to test
another patch beforehand :)
--
regards,
Tom
signature.asc
Description: OpenPGP digital signature
Re: [Dovecot] dovecot-1.2.2+sieve 0.1.9: sieve issues with (global?) includes
Tom Hendrikx schreef: Applied and tested. sieved and sieve-test now complain with an error message, but everything seems to function when run from within dovecot. Error: sieve: include: sieve_dir and home not set (wanted script spam.sieve) Error: failed to load binary: .default.svbin I'll wait for your new release, but of course I'm willing to test another patch beforehand :) Oh yes, I should have mentioned that. The sieve tools don't retrieve settings from the dovecot config file, nor are they (yet) aware of the config settings extensions may rely on. So, the SIEVE_DIR and SIEVE_GLOBAL_DIR environments are not set. Setting these beforehand will fix the problem. BTW, before I fixed your bug I had the same error for the above reason. But, as you may have noticed, that error is wrong, since you are using :global. I've committed a fix for that already: http://hg.rename-it.nl/dovecot-1.2-sieve/rev/449d8ecb0f34 Executing something like this should work: export SIEVE_GLOBAL_DIR=/var/lib/dovecot/sieve sieved ~/.dovecot.svbin I will add the means to specify configuration items at the command line in the near future. Regards, -- Stephan Bosch step...@rename-it.nl
Re: [Dovecot] Public folders, individual SEEN flags
This file probably isn't in the right place. It needs to be in each maildir under the publicfolders/ directory (i.e. where the dovecot-uidlist files are also). Thanks Timo. That seems to work, which in turn suggests that the directory listing in the second code example at http://wiki.dovecot.org/SharedMailboxes/Public is incorrect. I'm happy to change it, but could you confirm that it is, indeed, wrong? Thanks, Keith
[Dovecot] STARTTLS problem
Hi I have a problem with STARTTLS, with imaps all ok. I have tried to connect to server with different clients (thunderbird, the bat, mulberry) and had same result. Thunderbird log for example: 0[284708]: 25c0e08:192.168.4.200:NA:SetupWithUrl: clearing IMAP_CONNECTION_IS_OPEN 1920[25c77c8]: ImapThreadMainLoop entering [this=25c0e08] 1920[25c77c8]: 25c0e08:192.168.4.200:NA:ProcessCurrentURL: entering 1920[25c77c8]: 25c0e08:192.168.4.200:NA:ProcessCurrentURL:imap://test%40my%2elo...@192.168.4.200:143/select%3E/INBOX: = currentUrl 1920[25c77c8]: ReadNextLine [stream=25c8020 nb=210 needmore=0] 1920[25c77c8]: 25c0e08:192.168.4.200:NA:CreateNewLineFromSocket: * OK [CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. 1920[25c77c8]: 25c0e08:192.168.4.200:NA:SendData: 1 capability 1920[25c77c8]: ReadNextLine [stream=25c8020 nb=190 needmore=0] 1920[25c77c8]: 25c0e08:192.168.4.200:NA:CreateNewLineFromSocket: * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 STARTTLS AUTH=PLAIN AUTH=LOGIN 1920[25c77c8]: ReadNextLine [stream=25c8020 nb=28 needmore=0] 1920[25c77c8]: 25c0e08:192.168.4.200:NA:CreateNewLineFromSocket: 1 OK Capability completed. 1920[25c77c8]: 25c0e08:192.168.4.200:NA:SendData: 2 STARTTLS 1920[25c77c8]: ReadNextLine [stream=25c8020 nb=33 needmore=0] 1920[25c77c8]: 25c0e08:192.168.4.200:NA:CreateNewLineFromSocket: 2 OK Begin TLS negotiation now. 1920[25c77c8]: 25c0e08:192.168.4.200:NA:SendData: 3 capability my comment - at this place the process is waiting 1920[25c77c8]: ReadNextLine [stream=25c8020 nb=0 needmore=1] 1920[25c77c8]: 25c0e08:192.168.4.200:NA:CreateNewLineFromSocket: clearing IMAP_CONNECTION_IS_OPEN - rv = 804b0014 1920[25c77c8]: 25c0e08:192.168.4.200:NA:TellThreadToDie: close socket connection 1920[25c77c8]: 25c0e08:192.168.4.200:NA:CreateNewLineFromSocket: (null) 1920[25c77c8]: 25c0e08:192.168.4.200:NA:ProcessCurrentURL: aborting queued urls 1920[25c77c8]: ImapThreadMainLoop leaving [this=25c0e08] At same time dovecot log: Jul 29 18:33:08 freebsd dovecot: auth(default): new auth connection: pid=3339 Jul 29 18:33:34 freebsd dovecot: imap-login: Disconnected (no auth attempts): rip=192.168.4.100, lip=192.168.4.200, TLS handshaking: Disconnected What does it mean, i don't know, because if I try to connect with gnutls-cli it works perfectly. freebsd# dovecot -n # 1.1.16: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-RELEASE i386 ufs syslog_facility: local0 protocols: imap imaps pop3 pop3s ssl_key_file: /etc/ssl/keys/dovecot.pem disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_uid: 4738 mail_gid: 4738 mail_location: maildir:/var/mail/vmail/%d/%n mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): acl mail_plugins(imap): acl mail_plugins(pop3): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: public/ location: maildir:/var/mail/vmail/%d/public:INDEX=/var/mail/vmail/%d/%n/public/index:CONTROL=/var/mail/vmail/%d/%n/public/control list: yes subscriptions: yes auth default: mechanisms: plain login username_format: %Lu verbose: yes debug: yes passdb: driver: passwd-file args: /usr/local/etc/passwd.dovecot userdb: driver: passwd-file args: /usr/local/etc/passwd.dovecot socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 plugin: acl: vfile any ideas ? Regards, Sergey
Re: [Dovecot] Stuck with dovecot-sieve and horde-ingo ...
Robert Schetterer schrieb: if you get problems with sieve dovecot try http://www.woozle.org/~neale/src/pysieved/ exactly the same behavior: ingo complains driver not in transaction state ... Seems as if ingo fails to even contact port 2000 ... any idea on how to debug ingo itself? Stefan
Re: [Dovecot] Stuck with dovecot-sieve and horde-ingo ...
Stefan G. Weichinger schrieb: Robert Schetterer schrieb: if you get problems with sieve dovecot try http://www.woozle.org/~neale/src/pysieved/ exactly the same behavior: ingo complains driver not in transaction state ... Seems as if ingo fails to even contact port 2000 ... any idea on how to debug ingo itself? Stefan there is somewhere in the horde doku how to setup verbose php debug logging sorry i couldnt remember where , but i used it allready during testing -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
[Dovecot] problems compiling dovecot-1.2.2 on solaris 10
if test $dot_seen = no; then \ make $target-am || exit 1; \ fi; test -z $fail make: Fatal error: Command failed for target `all-recursive' Current working directory /scratch/jawelsh/src/dovecot-1.2.2/src *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='src doc'; for subdir in $list; do \ echo Making $target in $subdir; \ if test $subdir = .; then \ dot_seen=yes; \ local_target=$target-am; \ else \ local_target=$target; \ fi; \ (cd $subdir make $local_target) \ || eval $failcom; \ done; \ if test $dot_seen = no; then \ make $target-am || exit 1; \ fi; test -z $fail make: Fatal error: Command failed for target `all-recursive' Current working directory /scratch/jawelsh/src/dovecot-1.2.2 *** Error code 1 make: Fatal error: Command failed for target `all' [house-7]$ this is with gcc-4.1.1 any ideas? Jason
Re: [Dovecot] problem with disable_plaintext_auth
On Qua, 29 Jul 2009, Olivier Nicole wrote: Hi, I am using dovecot with postfix for authentication. Everything (TLS/SSL, authentication) is working fine, except that when I set: disable_plaintext_auth = yes I still can authenticate with plain text on a no TLS/SSL session: 20 mail2.cs.ait.ac.th ESMTP Postfix (2.6.2) EHLO [192.41.170.57] 250-mail2.cs.ait.ac.th 250-PIPELINING 250-SIZE 1024 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN AUTH PLAIN 235 2.7.0 Authentication successful disable_plaintext_auth affects logging in to dovecot IMAP/POP3 server. This is a SMTP session with Postfix, you'll have to configure Postfix not to allow plain text authentication before STARTTLS. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br
[Dovecot] authn_name and authz_name differ: not supported
Hello, I'm trying to authenticate using GSSAPI, but getting this in dovecot.log authn_name and authz_name differ: not supported. What is actually trying to say me? I've remeber once encounter this problem but it get away silently. I'm using Mozilla Thunderbird 3 beta 3 and Dovecot 1.0.15
Re: [Dovecot] STARTTLS problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 29 Jul 2009, Рачков Сергей wrote: I have a problem with STARTTLS, with imaps all ok. Do you have a Cisco Firewall/IDS or a software firewall running between your client and Dovecot? If so, try to disable it for a test. Some firewalls don't understand that after STARTTLS they have to stop listening / checking the connection. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSnBdRXWSIuGy1ktrAQJQeQgAmivfQZS9CeH33e5NPFnJ7yWCRvkI99VL L6qKPBHQO144BjvHpHOaqms7trKUBYSmOClF3M7AB13S9WMlnVK596VYpD0QvBlS rNghpX2rE6oboEXpQ4Zf2iuvogYuf3wN0vGTE6W5EdbZf025a3nUH3kjY7z04qXe RBsz1dJrpXPGarGa0f9/JU3zmLVf0RZwKLnd8bxQ8cuFFgttinxnfi+8MP9+QmsY qLDixog1DPhg18txVxTUW9NuTtTbr73u3StGnSEzCwkwvPYrGW+iCrLn/PuW2Fnr u6XgTiRbmWoJZUuxaElKlaSN6mufALL+NcKbRteB161DrquDZxZvwA== =Zfuc -END PGP SIGNATURE-
Re: [Dovecot] Stuck with dovecot-sieve and horde-ingo ...
Stefan G. Weichinger schrieb: Robert Schetterer schrieb: Stefan G. Weichinger schrieb: Robert Schetterer schrieb: if you get problems with sieve dovecot try http://www.woozle.org/~neale/src/pysieved/ exactly the same behavior: ingo complains driver not in transaction state ... Seems as if ingo fails to even contact port 2000 ... any idea on how to debug ingo itself? Stefan there is somewhere in the horde doku how to setup verbose php debug logging sorry i couldnt remember where , but i used it allready during testing done already, see my last mail to horde-ml ... danke ;-) i will retest tonight horde ingo sieve with latest dovecot perhaps i will see equal problems so i will report to you -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
[Dovecot] sieve rules processing
Hello list,
My question: is sieve support some kind of continue action, to explicit tell
server processing rules below current one(if current has triged)?
Situation:
I have few rules, which fileinto's to different directories. All is working
fine, but if I want redirect all my mail for some period of time to another
mailbox, I'm adding rule like this, to be processing first.
if anyof (true)
{
redirect koshi...@gmail.com;
keep;
}
Mail redirecting, but keep state store messages to INBOX. All I want - to
process other rules, which will move message to the right imap directory.
This situation also happens with vacation sieve-action.
In sieve rfc I didn't find any workaround to that actions.
Maybe someone know how to make sieve working in described way?
Re: [Dovecot] High Availability strategies
On Jul 29, 2009, at 5:39 AM, Steffen Kaiser wrote: On Mon, 27 Jul 2009, Timo Sirainen wrote: BTW. http://dovecot.org/talks/berlin-2009-07-02.pdf has a list of some possible ways to cluster Dovecot. IMO You should place all slides and conference papers online - at least I did not found them on dovecot.org ... . Some people asked me lately about how professional Dovecot is. There aren't really many yet. Slides about the couple of talks are in / talks/..
Re: [Dovecot] Some people asked me lately about how professional Dovecot is.
I purely love that kind of crap. As if presentations meant anything, as if there aren't all kinds of scholarly work about theoretical perfect world algorithms and conceptual systems that will never be implemented and are as practical and effective as wings on a pig. Please. I'm reminded of the story about how, during the American Civil War, when the North had finally, after years of ignominious defeats, gotten a general would could fight and win a battle, General Grant. A fussy old lady approached President Lincoln and complained loudly that Grant was a drunk. Lincoln blinked at the woman, then said, Ma'am, if you'll be so kind as to find out what kind of whiskey Grant drinks, I'll send a case of it to all the other generals. Dovecot Works. That's all anyone needs to know. Plus it has a towering wizard of a developer and an avid, engaged and endlessly helpful community. -- Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows Stewart Dean, Unix System Admin, Bard College, New York 12504 sd...@bard.edu voice: 845-758-7475, fax: 845-758-7035
[Dovecot] sieve redirect action
Hello Stephan, First of all, thank you for dovecot-sieve implementation. I see that you are adding X-Sieve header to all outgoing e-mail in cmd-redirect.c /* Prepend sieve version header (should not affect signatures) */ rfc2822_header_field_write(f, X-Sieve, SIEVE_IMPLEMENTATION); How do you look at adding one more header, for example X-Sieve-Forward-From: Now, when redirect action is in use - mail forwards using sendmail command line interface. The problem that there is no suitable way to know which user's script has generate redirect. Received: header may contain envelope receiver but this is valid if only 1 rcpt to: command was specified on SMTP session. This invokes problem when forwarding mail to non-local domains, breaking such things like SPF. I'd like to setup SRS for fixing this, but I don't know sender(sieve local user) mail. Adding one header with valid local user e-mail address will fix this. Google add 2 headers for this - X-Forwarded-To: and X-Forwarded-For: . What do you think about this ?
Re: [Dovecot] Some people asked me lately about how professional Dovecot is.
Amen to that! I wholeheartedly agree... Sincerely, - Wouter van der Schagt -- From: Stewart Dean sd...@bard.edu Sent: Wednesday, July 29, 2009 11:22 PM To: Steffen Kaiser skdove...@smail.inf.fh-brs.de; Timo Sirainen t...@iki.fi; Dovecot Mailing List dovecot@dovecot.org Subject: Re: [Dovecot] Some people asked me lately about how professional Dovecot is. I purely love that kind of crap. As if presentations meant anything, as if there aren't all kinds of scholarly work about theoretical perfect world algorithms and conceptual systems that will never be implemented and are as practical and effective as wings on a pig. Please. I'm reminded of the story about how, during the American Civil War, when the North had finally, after years of ignominious defeats, gotten a general would could fight and win a battle, General Grant. A fussy old lady approached President Lincoln and complained loudly that Grant was a drunk. Lincoln blinked at the woman, then said, Ma'am, if you'll be so kind as to find out what kind of whiskey Grant drinks, I'll send a case of it to all the other generals. Dovecot Works. That's all anyone needs to know. Plus it has a towering wizard of a developer and an avid, engaged and endlessly helpful community. -- Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows Stewart Dean, Unix System Admin, Bard College, New York 12504 sd...@bard.edu voice: 845-758-7475, fax: 845-758-7035
Re: [Dovecot] Some people asked me lately about how professional Dovecot is.
On Qua, 2009-07-29 at 11:22 -0400, Stewart Dean wrote: I purely love that kind of crap. As if presentations meant anything, as if there aren't all kinds of scholarly work about theoretical perfect world algorithms and conceptual systems that will never be implemented and are as practical and effective as wings on a pig. Please. I'm reminded of the story about how, during the American Civil War, when the North had finally, after years of ignominious defeats, gotten a general would could fight and win a battle, General Grant. A fussy old lady approached President Lincoln and complained loudly that Grant was a drunk. Lincoln blinked at the woman, then said, Ma'am, if you'll be so kind as to find out what kind of whiskey Grant drinks, I'll send a case of it to all the other generals. Dovecot Works. That's all anyone needs to know. Plus it has a towering wizard of a developer and an avid, engaged and endlessly helpful community. Well said. Truth is i'm for a long time trying to find out what kind of vodka Timo drinks. -- Jose Celestino SAPO.pt::Systems http://www.sapo.pt - * Progress (n.): The process through which Usenet has evolved from smart people in front of dumb terminals to dumb people in front of smart terminals. signature.asc Description: This is a digitally signed message part
[Dovecot] parameter mail_location and variables
hi i have virtual users stored in ldap server and i must to do some modifications that requiere to chage mail_location value... the solution comes to use the uid value stored in ldap server for users on mail_location parameter... i can see in http://wiki.dovecot.org/Variables that i can't do them (i uses sasl authentication) so.. ¿exist any way to get a value from ldap server and use them in mail_location parameter? thanks in advance!!! -- Salu2 ;)
Re: [Dovecot] Some people asked me lately about how professional Dovecot is.
On Jul 29, 2009, at 11:34 AM, Jose Celestino wrote: Well said. Truth is i'm for a long time trying to find out what kind of vodka Timo drinks. I don't really, except maybe http://en.wikipedia.org/wiki/Salmiakki_Koskenkorva :)
Re: [Dovecot] authn_name and authz_name differ: not supported
On 29.07.2009 18:14, Nikolay Shopik wrote: Hello, I'm trying to authenticate using GSSAPI, but getting this in dovecot.log authn_name and authz_name differ: not supported. What is actually trying to say me? I've remeber once encounter this problem but it get away silently. I'm using Mozilla Thunderbird 3 beta 3 and Dovecot 1.0.15 Problem was in username used in Thunderbird, it MUST be w/o real, so I had sho...@inblock.ru, but should be just shopik.
Re: [Dovecot] STARTTLS problem
Charles Marcus schrieb: On 7/29/2009, Steffen Kaiser (skdove...@smail.inf.fh-brs.de) wrote: Do you have a Cisco Firewall/IDS or a software firewall running between your client and Dovecot? If so, try to disable it for a test. Some firewalls don't understand that after STARTTLS they have to stop listening / checking the connection. If its a Cisco PIX, diable the 'smtp fixup' crap that breaks smtp... What has the Cisco PIX smtp fixup feature got to do with IMAP STARTTLS?
[Dovecot] %u variable to expand kerberos realm
Hi Timo, Does this intended %u isn't expanding REALM name, so I've only see user names.
Re: [Dovecot] STARTTLS problem
On 7/29/2009, Matthias Andree (matthias.and...@gmx.de) wrote: If its a Cisco PIX, diable the 'smtp fixup' crap that breaks smtp... What has the Cisco PIX smtp fixup feature got to do with IMAP STARTTLS? Obviously, nothing... ;) Sorry, wrong list (I'm on the postfix list and this is a common reply whenever CISCO is mentioned)... -- Best regards, Charles
[Dovecot] Shared mailboxes and INBOX
I'm trying to implement a shared mailbox: in other words, we have a generic email address (security@) which we want a number of users to be able to monitor. The problem I have is that users can see folders under that shared mailbox but can't see the INBOX. All the users in question have their own INBOX in their private namespace, so does this raise a conflict with monitoring another mailbox's INBOX? Configuration: # dovecot -n # 1.2.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian 5.0.2 log_timestamp: %Y-%m-%d %H:%M:%S disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: shared/ location: maildir:/home/publicfolders:INDEX=~/Maildir/public list: yes namespace: type: shared separator: / prefix: security/ location: maildir:/home/securitymailbox/Maildir:INDEX=~/Maildir/securitymailbox list: yes auth default: passdb: driver: pam userdb: driver: passwd Thanks, Keith
[Dovecot] sieve 0.1.8 raw backtrace
hi,
I had two problems with deliver / sieve.
First one is not reproducible anymore.
Im using debian unstable (amd64), often dist-upgraded, with some experimental
stuff too (wine i think).
The first basically triggered a backtrace when confronted an email with
spammassassins report headers prepended. (user_prefs: report_safe 0)
However i dont have that backtrace anymore, sorry.
The second poped up only later as i began to investigate more the first, a few
days later. Now my entire sieve script seemed broken suddenly. After some time
i narrowed it down to one offending line:
require [fileinto,regex];
if address :regex to [m-a-t...@test\\.ch,m-a-memb...@test\\.ch, \
m-a-reg...@test\\.ch,m-a-...@test\\.ch] {
fileinto Test;
stop;
}
if i remove even one of the regex tests, then this script will not make
deliver or sieve_test go panic.
here the backtrace:
2009-07-29 18:15:37 deliver(xxx): Panic: pool_data_stack_realloc(): stack
frame changed
2009-07-29 18:15:37 deliver(xxx): Error: Raw backtrace:
/usr/lib/dovecot/deliver [0x496bc2] -
/usr/lib/dovecot/deliver(default_fatal_handler+0x34) [0x496cc4] -
/usr/lib/dovecot/deliver [0x496346] - /usr/lib/dovecot/deliver [0x4a18fb] -
/usr/lib/dovecot/deliver [0x494185] -
/usr/lib/dovecot/deliver(buffer_write_zero+0xe5) [0x494a55] -
/usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so [0x7f444ca98ff2] -
/usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_match_value+0xb0)
[0x7f444ca8ea10] -
/usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_address_match+0xe3)
[0x7f444ca8e5f3] - /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so
[0x7f444ca9291b] -
/usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_interpreter_continue+0x97)
[0x7f444ca89307] -
/usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_interpreter_run+0x48)
[0x7f444ca894f8] - /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so
[0x7f444ca96716] -
/usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so(sieve_execute+0x3d)
[0x7f444ca9698d] - /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so
[0x7f444ca7dc8a] - /usr/lib/dovecot/deliver(main+0xf5e) [0x41d0fe] -
/lib/libc.so.6(__libc_start_main+0xe6) [0x7f444ceea5c6] -
/usr/lib/dovecot/deliver [0x41b029]
I hope this helps
cheers
[Dovecot] Random flags appearing on messages
Not reproducible every time, but every so often, after viewing an
unseen message, I am seeing the first non-system flag set on the
message without an intervening STORE call.
Here's an example:
2 EXAMINE XXX (QRESYNC (1165391112 78
12160:12162,12168:12171,12173,12178,12183,12191,12360,12431,12560,12762,12765,13037,13089,13094,13196,13457,13460,13495,13548,13549,13561,13590,13597,13598))
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft impflag0 impflag1)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
...
7 UID FETCH 13608 (ENVELOPE FLAGS RFC822.SIZE BODY.PEEK[HEADER.FIELDS
(LIST-POST X-PRIORITY)])
* 30 FETCH (UID 13608 FLAGS (\Recent) ...
On the next access:
2 SELECT XXX (QRESYNC (1165391112 79
12160:12162,12168:12171,12173,12178,12183,12191,12360,12431,12560,12762,12765,13037,13089,13094,13196,13457,13460,13495,13548,13549,13561,13590,13597,13598,13608))
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft impflag0 impflag1)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft
impflag0 impflag1 \*)] Flags permitted.
...
3 UID FETCH 13608 (BODY[HEADER])
* 30 FETCH (UID 13608 FLAGS (\Seen \Recent impflag0) BODY[HEADER] {2529} ...
As can be seen, impflag0 has been magically set somehow.
Stranger still, dovecot won't let you unset the flag (this might have
something to do with QRESYNC since, if I run this command without the
UNCHANGEDSINCE parameter, it will unset the flag):
4 UID STORE 13608 (UNCHANGEDSINCE 82) -FLAGS (impflag0)
4 OK Store completed.
FYI, I am using dovecot 1.2.1 on archlinux (they haven't upgraded the
package to 1.2.2 yet, but I didn't see anything in the 1.2.2 release
notes that leads me to believe this has been fixed).
michael
Re: [Dovecot] Random flags appearing on messages
On Wed, 2009-07-29 at 11:25 -0600, Michael M. Slusarz wrote: Not reproducible every time, but every so often, after viewing an unseen message, I am seeing the first non-system flag set on the message without an intervening STORE call. mbox or maildir? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Random flags appearing on messages
On Wed, 2009-07-29 at 11:25 -0600, Michael M. Slusarz wrote:
3 UID FETCH 13608 (BODY[HEADER])
* 30 FETCH (UID 13608 FLAGS (\Seen \Recent impflag0) BODY[HEADER] {2529} ...
..
FYI, I am using dovecot 1.2.1 on archlinux (they haven't upgraded the
package to 1.2.2 yet, but I didn't see anything in the 1.2.2 release
notes that leads me to believe this has been fixed).
Oh, actually it has been fixed by 1.2.2!
- Fixed corrupted index cache file errors (and perhaps others) caused
by e.g. IMAP's FETCH BODY[] command.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Random flags appearing on messages
Quoting Timo Sirainen t...@iki.fi: On Wed, 2009-07-29 at 11:25 -0600, Michael M. Slusarz wrote: Not reproducible every time, but every so often, after viewing an unseen message, I am seeing the first non-system flag set on the message without an intervening STORE call. mbox or maildir? Sorry about that omission. It's maildir.
Re: [Dovecot] Random flags appearing on messages
Quoting Timo Sirainen t...@iki.fi:
On Wed, 2009-07-29 at 11:25 -0600, Michael M. Slusarz wrote:
3 UID FETCH 13608 (BODY[HEADER])
* 30 FETCH (UID 13608 FLAGS (\Seen \Recent impflag0) BODY[HEADER] {2529} ...
..
FYI, I am using dovecot 1.2.1 on archlinux (they haven't upgraded the
package to 1.2.2 yet, but I didn't see anything in the 1.2.2 release
notes that leads me to believe this has been fixed).
Oh, actually it has been fixed by 1.2.2!
- Fixed corrupted index cache file errors (and perhaps others) caused
by e.g. IMAP's FETCH BODY[] command.
Well... please don't make your changelog messages so blatantly obvious
and I won't end up looking like a fool...
Sorry for the noise Timo.
michael
Re: [Dovecot] STARTTLS problem
It's working A lot of thanks, Steffen! My problem was a Kaspersky Internet Security. It has a network traffic control function and option check SSL connection, if this option checked - everything work, if not checked - don't work. Best regards, Sergey. - Original Message - From: Steffen Kaiser skdove...@smail.inf.fh-brs.de To: dovecot@dovecot.org Sent: Wednesday, July 29, 2009 8:31 PM Subject: Re: [Dovecot] STARTTLS problem -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 29 Jul 2009, Рачков Сергей wrote: I have a problem with STARTTLS, with imaps all ok. Do you have a Cisco Firewall/IDS or a software firewall running between your client and Dovecot? If so, try to disable it for a test. Some firewalls don't understand that after STARTTLS they have to stop listening / checking the connection. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSnBdRXWSIuGy1ktrAQJQeQgAmivfQZS9CeH33e5NPFnJ7yWCRvkI99VL L6qKPBHQO144BjvHpHOaqms7trKUBYSmOClF3M7AB13S9WMlnVK596VYpD0QvBlS rNghpX2rE6oboEXpQ4Zf2iuvogYuf3wN0vGTE6W5EdbZf025a3nUH3kjY7z04qXe RBsz1dJrpXPGarGa0f9/JU3zmLVf0RZwKLnd8bxQ8cuFFgttinxnfi+8MP9+QmsY qLDixog1DPhg18txVxTUW9NuTtTbr73u3StGnSEzCwkwvPYrGW+iCrLn/PuW2Fnr u6XgTiRbmWoJZUuxaElKlaSN6mufALL+NcKbRteB161DrquDZxZvwA== =Zfuc -END PGP SIGNATURE-
Re: [Dovecot] dovecot-1.2.2+sieve 0.1.9: sieve issues with (global?) includes
Stephan Bosch wrote: Tom Hendrikx schreef: BTW, before I fixed your bug I had the same error for the above reason. But, as you may have noticed, that error is wrong, since you are using :global. I've committed a fix for that already: http://hg.rename-it.nl/dovecot-1.2-sieve/rev/449d8ecb0f34 Executing something like this should work: Works like a charm ;) export SIEVE_GLOBAL_DIR=/var/lib/dovecot/sieve sieved ~/.dovecot.svbin I will add the means to specify configuration items at the command line in the near future. Adding above method to the man page would already suffice, I guess None the less, thanks for the quick reaction and all the hard work :) -- Regards, Tom signature.asc Description: OpenPGP digital signature
Re: [Dovecot] problems compiling dovecot-1.2.2 on solaris 10
On Wed, 2009-07-29 at 09:33 -0400, Jason Welsh wrote: if test $dot_seen = no; then \ make $target-am || exit 1; \ fi; test -z $fail make: Fatal error: Command failed for target `all-recursive' Current working directory /scratch/jawelsh/src/dovecot-1.2.2/src *** Error code 1 The following command caused the error: failcom='exit 1'; \ .. Umm. Is this from the actual 1.2.2 tarball? Did you run any autotools stuff before running configure and make? That error you have doesn't look like anything I've seen before, so I've no idea what the problem is in your system. There are two other problems in Solaris though, but neither produces the error you see. I guess you could anyway try running http://dovecot.org/nightly/dovecot-latest.tar.gz which fixes those two Solaris issues.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.2.2 released
On Wed, 2009-07-29 at 08:59 +0200, Christian Felsing wrote: I experienced a strange effect after updating from 1.2.1 to 1.2.2 with Horde. IMP 4.3.4 had problems with GnuPG handling while Dovecot 1.2.1 was installed, but IMP 4.3.3 had no problems. Now I updated to Dovecot 1.2.2 and IMP 4.3.4 is also running flawless :-) Is that an known issue ? Who knows, maybe 4.3.4 used some IMAP feature that was broken in 1.2.1. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Unable to (un)subscribe mbox with AIX, NFS and netapp filer
On Wed, 2009-07-29 at 11:04 +0200, Ralf Becker wrote:
Jul 29 10:38:27 trevi mail:err|error dovecot: IMAP(beckerr):
fchown(/u/f0/rzuser/beckerr/Mail/.subscriptions.lock, -1, -1)
failed: Invalid argument
..
I located the bug in src/lib/file-dotlock.c ... a patch is attached.
- if (fd != -1 (uid != (uid)-1 || gid != (gid_t)-1)) {
+ if (fd != -1 (uid != (uid_t)-1 || gid != (gid_t)-1)) {
Whops, thanks, committed. :)
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] sieve 0.1.8 raw backtrace
jsech...@gmx.ch schreef: hi, I had two problems with deliver / sieve. First one is not reproducible anymore. [..] 2009-07-29 18:15:37 deliver(xxx): Panic: pool_data_stack_realloc(): stack frame changed This message tells me I committed a Dovecot API crime. I thought I fixed all of these. I'll have a look. Regards, -- Stephan Bosch step...@rename-it.nl
Re: [Dovecot] problems compiling dovecot-1.2.2 on solaris 10
well, I thought I had the official tarball, but the dovecot-latest.tar.gz compiled fine.. thanks. Jason Timo Sirainen wrote: On Wed, 2009-07-29 at 09:33 -0400, Jason Welsh wrote: if test $dot_seen = no; then \ make $target-am || exit 1; \ fi; test -z $fail make: Fatal error: Command failed for target `all-recursive' Current working directory /scratch/jawelsh/src/dovecot-1.2.2/src *** Error code 1 The following command caused the error: failcom='exit 1'; \ .. Umm. Is this from the actual 1.2.2 tarball? Did you run any autotools stuff before running configure and make? That error you have doesn't look like anything I've seen before, so I've no idea what the problem is in your system. There are two other problems in Solaris though, but neither produces the error you see. I guess you could anyway try running http://dovecot.org/nightly/dovecot-latest.tar.gz which fixes those two Solaris issues.. -- |Jason Welsh ja...@monsterjam.org| | http://monsterjam.orgDSS PGP: 0x5E30CC98 | |gpg key: http://monsterjam.org/gpg/ |
Re: [Dovecot] sieve 0.1.8 raw backtrace
Stephan Bosch schreef: jsech...@gmx.ch schreef: hi, I had two problems with deliver / sieve. First one is not reproducible anymore. [..] 2009-07-29 18:15:37 deliver(xxx): Panic: pool_data_stack_realloc(): stack frame changed This message tells me I committed a Dovecot API crime. I thought I fixed all of these. I'll have a look. I've not been able to reproduce this. However, considering the panic message I've devised a fix that should solve the problem: http://hg.rename-it.nl/dovecot-1.2-sieve/rev/f316a10179f3 Regards, -- Stephan Bosch step...@rename-it.nl
Re: [Dovecot] sieve rules processing
Nikita Koshikov schreef:
Hello list,
My question: is sieve support some kind of continue action, to explicit tell
server processing rules below current one(if current has triged)?
Situation:
I have few rules, which fileinto's to different directories. All is working
fine, but if I want redirect all my mail for some period of time to another
mailbox, I'm adding rule like this, to be processing first.
if anyof (true)
{
redirect koshi...@gmail.com;
keep;
}
Mail redirecting, but keep state store messages to INBOX. All I want - to
process other rules, which will move message to the right imap directory.
This situation also happens with vacation sieve-action.
In sieve rfc I didn't find any workaround to that actions.
I am not exactly sure what you mean. Why are you providing an explicit
keep command when you want to sort the message further? I would think
the following example script does what you need:
==
require fileinto;
require copy;
# Temporary rule
if true {
# Forward a copy of all messages to gmail account
redirect :copy koshi...@gmail.com;
}
# File spam into spam folder and stop further processing
if header :contains X-spam yes {
fileinto Spam;
stop;
}
# Mailing list
if header :contains list-id ietf-mta-filters.imc.org {
fileinto Lists.Sieve;
}
# Implicit keep will store message in INBOX if it was not
# stored already by the fileinto commands above. The :copy
# argument to the redirect command prevents that command
# from cancelling the implicit keep action.
==
I hope this helps you along.
Regards,
--
Stephan Bosch
step...@rename-it.nl
Re: [Dovecot] problem with disable_plaintext_auth
Hi, I am using dovecot with postfix for authentication. Everything (TLS/SSL, authentication) is working fine, except that when I set: disable_plaintext_auth = yes I still can authenticate with plain text on a no TLS/SSL session: 20 mail2.cs.ait.ac.th ESMTP Postfix (2.6.2) EHLO [192.41.170.57] 250-mail2.cs.ait.ac.th 250-PIPELINING 250-SIZE 1024 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN AUTH PLAIN 235 2.7.0 Authentication successful disable_plaintext_auth affects logging in to dovecot IMAP/POP3 server. This is a SMTP session with Postfix, you'll have to configure Postfix not to allow plain text authentication before STARTTLS. But postfix hands the authentication task to dovecot (dovecot-auth daemon). And I am sure it does, because if I remove PLAIN from the authentication mechanism of dovecot, then the SMTP sessions with postfix will not offer AUTH PLAIN anymore. So I am confused here. Best regards, Olivier
Re: [Dovecot] problem with disable_plaintext_auth
Hi, I am using dovecot with postfix for authentication. Everything (TLS/SSL, authentication) is working fine, except that when I set: disable_plaintext_auth = yes I still can authenticate with plain text on a no TLS/SSL session: 20 mail2.cs.ait.ac.th ESMTP Postfix (2.6.2) EHLO [192.41.170.57] 250-mail2.cs.ait.ac.th 250-PIPELINING 250-SIZE 1024 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN AUTH PLAIN 235 2.7.0 Authentication successful disable_plaintext_auth affects logging in to dovecot IMAP/POP3 server. This is a SMTP session with Postfix, you'll have to configure Postfix not to allow plain text authentication before STARTTLS. But postfix hands the authentication task to dovecot (dovecot-auth daemon). And I am sure it does, because if I remove PLAIN from the authentication mechanism of dovecot, then the SMTP sessions with postfix will not offer AUTH PLAIN anymore. So I am confused here. My mistake, that is managed by postfix parameter: smtpd_tls_auth_only = yes Thank you, Olivier
[Dovecot] AutoCreate per Domain
Hello, is there a way to configure plugin autocreate per domain? Like: For domain xwz.com i want to autocreate folders: Models and Clients For domain yxw.com i want to autocreate folders: Adm and Tech Thanks.
[Dovecot] Berlin talk - video or audio available?
Thanks Timo for putting up the .pdf and .ppt files for your talk at www.dovecot.org/talks . Is there a video or audio file of it? Thanks, James.
Re: [Dovecot] Missing return-path on vacation messages
Hello, Is this ever likely to be fixed in dovecot? It was mentioned in a previous thread before: http://dovecot.org/list/dovecot/2008-December/035753.html Basically the vacation system is useless, most mail servers with anti-spam are rejecting the vacation replies because the sender isn't a valid address. This is the address that the auto replies are coming from: @domain1.com Stephen On Sun, Dec 14, 2008 at 2:21 AM, Timo Sirainen t...@iki.fi wrote: Are you sure it's because of a missing return path? Sounds more like the message MIME body is broken. I've never checked if it is.. On Sun, 2008-12-14 at 03:19 +1100, Stephen Vaughan wrote: The vacation auto reply is being rejected by spamassassin, for bad_MIME On Sun, Dec 14, 2008 at 3:17 AM, Timo Sirainen t...@iki.fi wrote: Pretty much the same thing, just replace rejection with vacation in my reply. Why do you want them to have the return path? On Sun, 2008-12-14 at 03:15 +1100, Stephen Vaughan wrote: I was talking about vacation auto-reply messages missing the return path On Sun, Dec 14, 2008 at 12:41 AM, Timo Sirainen t...@iki.fi wrote: On Wed, 2008-12-10 at 14:09 +1100, Stephen Vaughan wrote: I can see this has been discussed previously, was just wondering if it's been fixed in v1.1.x? I don't consider it a bug. Rejection messages shouldn't have a return path, otherwise they themselves may be rejected and soon you'll have a bounce loop. -- Best Regards, Stephen -- Best Regards, Stephen -- Best Regards, Stephen Sent from Sydney, Nsw, Australia
