- dovecot - dovecot.org

Re: [Dovecot] Several errors
by A. van Harten 31 Jul '09

31 Jul '09

Tried that, same result. dovecot: Jul 25 00:55:41 Info: Dovecot v1.0.7 starting up dovecot: Jul 25 00:55:42 Error: Temporary failure in creating login processes, slowing down for now dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing dovecot: Jul 25 00:55:42 Info: Created login processes successfully, unstalling dovecot: Jul 25 00:55:42 Error: child 3850 (login) returned error 89 dovecot: Jul 25 00:55:42 Error: child 3851 (login) returned error 89 dovecot: Jul 25 00:55:42 Error: Temporary failure in creating login processes, slowing down for now dovecot: Jul 25 00:55:42 Error: imap-login: USER environment missing dovecot: Jul 25 00:55:42 Error: child 3852 (login) returned error 89 dovecot: Jul 25 00:55:42 Info: Created login processes successfully, unstalling [root@nestorix etc]# dovecot -n # 1.2.1: /usr/local/etc/dovecot.conf Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. # OS: Linux 2.6.18-128.2.1.el5 i686 CentOS release 5.3 (Final) ext3 base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot protocols: pop3 pop3s imap imaps ssl: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap login_executable(imap): /usr/libexec/dovecot/imap login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Havecom Mailserver ready. valid_chroot_dirs: /var/mail/vhosts mail_location: maildir:/var/mail/vhosts/%d/%n/ mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: executable: /usr/libexec/dovecot/dovecot-auth username_translation: "/$ verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/userdb socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix [root@nestorix etc]# service dovecot stop Stopping Dovecot Imap: [ OK ] [root@nestorix etc]# gedit /var/log/dovecot [root@nestorix etc]# service dovecot start Starting Dovecot Imap: [ OK ] [root@nestorix etc]# gedit /var/log/dovecot ^C [root@nestorix etc]# dovecot -n # 1.2.1: /usr/local/etc/dovecot.conf Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. Warning: There is no way to login to this server: disable_plaintext_auth=yes, ssl=no, no non-plaintext auth mechanisms. # OS: Linux 2.6.18-128.2.1.el5 i686 CentOS release 5.3 (Final) ext3 base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot protocols: pop3 pop3s imap imaps ssl: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap login_executable(imap): /usr/libexec/dovecot/imap login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Havecom Mailserver ready. valid_chroot_dirs: /var/mail/vhosts mail_location: maildir:/var/mail/vhosts/%d/%n/ mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: executable: /usr/libexec/dovecot/dovecot-auth username_translation: "/$ verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/userdb socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix [root@nestorix etc]# Albert [QUOTE] Timo Sirainen[/QUOTE] > On Sat, 2009-07-25 at 00:07 +0200, FraNL wrote: >> Running OS: CentOS 5.3 (2.6.18-128.2.1.el5) >> >> 1. >> My Linux distribution comes with Dovecot 1.0.7. After trying to make it running, I encoutnered many problems. So I decided to upgrade to 1.2.1. When running dovecot -r from CLI, it returns with version 1.2.1. But at the top of the log file it says: Info: Dovecot v1.0.7 starting up >> >> So I am not sure which version I am running. > > It means you're using some weird mix of both. Get rid of all of Dovecot v1.0 binaries (rpm -e dovecot or something) and your problems should go away. > > -- Med venlig hilsen, Met vriendelijke groeten, -- Med venlig hilsen, Met vriendelijke groeten,

4 15

Re: [Dovecot] Several errors
by A. van Harten 31 Jul '09

31 Jul '09

[QUOTE] Charles Marcus[/QUOTE] > > Who says you have to install it? Almost all the fora which are speaking of setting up a mail server tell me to install Dovecot > And who is it that you think owes you 'descent support' for free? When and where did I spoke about FREE? I never said I didn't want to pay for it!!! Please don't think for me... > That said, the support on the dovecot list is the best I've seen, even > when people get attitudes (like yours)... Attitudes? Since when is a normal business inquiry not appropriate? > If you want to learn linux, and learn how to admin a mail server, you're > expected to do some leg work yourself... no one expects you to be a > guru, but a little googling on how to change ownership of files in linux > would most likely answer this particular question. Sorry, but the answers on this mail group are written with as few words as possible - if it was written in Finnish, I'd understand just as much as I do now. Googling on a Dovecot problems results always in www.dovecot.org or one of its child sites. Always. Googling on a Linux question results always in experts-exchange. Always. > > Also, the attititude will most likely get surprising little response. If > you want to get help from someone for free, it helps to ask nicely. I don't agree. I know the way of asking isn't the most nice way - and I also apologise to them, who assisted me! But who cares if I agree with someone, who didn't assist me at all, but who only is capable of writing negatively about me? > Thats said, I wouldn't be surprised if Timo responds nicely anyway... > I've seen him respond to much worse emails than yours, and yours was > pretty bad... Pretty bad? You misunderstood me, my friend. Try to read reasonable next time. That helps! > > -- > > Best regards, > > Charles > -- Med venlig hilsen, Met vriendelijke groeten,

1 0

[Dovecot] Limiting user access
by Darvin Denmian 30 Jul '09

30 Jul '09

Hello, Is there a way to restrict clients access, for example: user1(a)domain.com -> only access pop3 user2(a)domain.com -> can access pop3 and imap in Dovecot? Thanks !!!

2 2

Re: [Dovecot] POSIX stupidity
by Timo Sirainen 30 Jul '09

30 Jul '09

On Thu, 2009-07-30 at 20:21 +0200, Remi Gacogne wrote: > Le jeudi 30 juillet 2009, Timo Sirainen a écrit : > > > > What the hell were POSIX people thinking?? This is the first syscall > > > I've seen that behaves like this, and apparently without any good > > > reason! Wonder how many other new system calls there are like this, that > > > I haven't noticed yet.. > > > > Looks like all posix_*() syscalls do that. Wonder if there are more. > > Looks like too many people were incorrectly using errno, especially in multi- > threaded context. > > From http://www.unix.org/whitepapers/reentrant.html : > > "In addition, all POSIX.1c functions avoid using errno and, instead, return > the error number directly as the function return value, with a return value of > zero indicating that no error was detected. This strategy is, in fact, being > followed on a POSIX-wide basis for all new functions. " But that doesn't solve anything, because old functions' API can't be changed. The only thing this change did was to make it more difficult for programmers to remember how functions' error handling should be done. In both APIs the success is indicated by returning 0, which makes it especially difficult to notice when it's being used wrong. If they really had to change this, it would have been much better to both set errno and return -error, that way it would have allowed also 2/3 of the old style error checks: if (posix_fallocate(..) < 0) perror() // works if (posix_fallocate(..) != 0) perror() // works if (posix_fallocate(..) == -1) perror() // doesn't work Now none of them work. I did also a quick google code search for posix_fallocate and found several other programs that handle the error wrong. And I'm sure it's only going to grow. Oh well, maybe some day gcc and libc add some features to catch at least the < 0 and == -1 usage (which would already work if posix_fallocate() had been specified to return unsigned int, not int).

1 0

[Dovecot] AIX and posix_fallocate
by Ralf Becker 30 Jul '09

30 Jul '09

Hi, AIX's implementation of posix_fallocate is a little bit, let me say, peculiar. Attached is a patch to "fix" (=work around) this. Without you'll see this in the logs: Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr): posix_fallocate() failed: File exists Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr): file_set_size() failed with mbox file /u/f0/rzuser/beckerr/Mail/Ham: File exists Funny, isn't it? This is what it should be: Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr): posix_fallocate() failed: Operation not supported on socket Jul 28 01:17:41 trevi mail:err|error dovecot: IMAP(beckerr): file_set_size() failed with mbox file /u/f0/rzuser/beckerr/Mail/Ham: Operation not supported on socket The problem is, that errno is not correcly set, when posix_fallocate returns EOPNOTSUPP (="Operation not supported on socket"). In this case the return code has to be checked rather than errno. When patched dovecot handles err==EOPNOTSUPP the same way like errno==EINVAL on Solaris. A note for all AIX Admins: Without APAR IZ48778: POSIX_FALLOCATE() FAILS WITH ERROR-25(ENOTTY) resp. IZ46961: POSIX_FALLOCATE() FAILS WITH ERROR-25(ENOTTY) APPLIES TO AIX 5300-06 you don't even get EOPNOTSUPP: posix_fallocate fails with NOTTY. So you have to install one of this fixes to make the patch work. Ralf -- ______________________________________________________________________ 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: beckerr(a)fh-trier.de Fon: +49 651 8103 499 Web: http://www.fh-trier.de/~beckerr Fax: +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) --- ./lib/file-set-size.c.org 2009-07-06 12:56:17.000000000 +0200 +++ ./lib/file-set-size.c 2009-07-06 12:54:40.000000000 +0200 @@ -43,9 +43,15 @@ #ifdef HAVE_POSIX_FALLOCATE if (posix_fallocate_supported) { - if (posix_fallocate(fd, st.st_size, size - st.st_size) == 0) + int err; + if ((err = posix_fallocate(fd, st.st_size, size - st.st_size)) == 0) return 0; + if (err == EOPNOTSUPP /* AIX */ ) { + /* Ignore this error silently. + You have to test err, because errno is not + correcly set on some versions of AIX */ + } else if (errno != EINVAL /* Solaris */) { if (!ENOSPACE(errno)) i_error("posix_fallocate() failed: %m");

4 4

[Dovecot] lock files causing time outs with Thunderbird
by CJ Keist 30 Jul '09

30 Jul '09

I have dovecot 1.1.16 running on Solaris 10. We are seeing problem with lock files taking forever to be removed after opening a email folder like Trash with several thousand messages in them. We use mbox format. All users inbox's are local to the mail server, and all other users mail folders are stored on a separate file server mounted via NFS. I see no problems with the NFS mounts. cd'ing into the mount points, listing files and viewing files a perform with now visible delays. Is there something I can do in the config file to speed things up? Here is the config file: # 1.1.16: /userM/mail-services/dovecot/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 3072). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: SunOS 5.10 sun4v base_dir: /userM/mail-services/dovecot/var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /userM/mail-services/dovecot/etc/ssl/dovecot.pem ssl_key_file: /userM/mail-services/dovecot/etc/ssl/privkey.pem ssl_parameters_regenerate: 0 ssl_cipher_list: MEDIUM:!LOW disable_plaintext_auth: no login_dir: /userM/mail-services/dovecot/var/run/dovecot/login login_executable(default): /userM/mail-services/dovecot/libexec/dovecot/imap-login login_executable(imap): /userM/mail-services/dovecot/libexec/dovecot/imap-login login_executable(pop3): /userM/mail-services/dovecot/libexec/dovecot/pop3-login login_greeting: Cyrus ready. login_max_processes_count: 1024 max_mail_processes: 1024 mail_location: mbox:~/:INBOX=/userM/mail/%u mail_debug: yes mmap_disable: yes mail_nfs_index: yes mbox_write_locks: fcntl dotlock mbox_dotlock_change_timeout: 60 mail_executable(default): /userM/mail-services/dovecot/libexec/dovecot/imap mail_executable(imap): /userM/mail-services/dovecot/libexec/dovecot/imap mail_executable(pop3): /userM/mail-services/dovecot/libexec/dovecot/pop3 mail_plugins(default): convert mail_plugins(imap): convert mail_plugins(pop3): mail_plugin_dir(default): /userM/mail-services/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /userM/mail-services/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /userM/mail-services/dovecot/lib/dovecot/pop3 auth default: mechanisms: plain login verbose: yes debug: yes worker_max_count: 1024 worker_max_request_count: 2000 passdb: driver: pam passdb: driver: passwd args: blocking=yes userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /var/lib/postfix/private/auth mode: 438 user: postfix group: postfix master: path: /userM/mail-services/dovecot/var/run/dovecot//auth-master mode: 384 plugin: convert_mail: Maildir:~/Maildir:INBOX=/userM/mail/%u -- C. J. Keist Email: cj.keist(a)colostate.edu UNIX/Network Manager Phone: 970-491-0630 Engineering Network Services Fax: 970-491-5569 College of Engineering, CSU Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness'

2 7

[Dovecot] imap, locks, and dovecot
by Mauricio Tavares 30 Jul '09

30 Jul '09

Let's say I have two computers -- a desktop and a laptop -- setup to check email on my postfix/dovecot/mailscanner box by using imap. Now, both machines use thunderbird and have a filter in that mail client to move emails that have a certain to: address (an alias, like support(a)domain.com) to a mail directory. The desktop is setup to check for mail every minute while the laptop initially is told to do the same. So, I send an email to the said address. dovecot (1.1.7) puts it in the inbox. thunderbird in one of those machines sees it and moves it to the, say, support folder. Then, another copy of the same mail is created and placed in the same folder. I then begin increasing the time the laptop waits before checking mails. Up to 5 minutes I am still having the double email issue, but if I the laptop to wait 10 minutes I only have one copy of the said email. That makes me think both clients are seeing the same email and moving it at the same time. I do not know the imap commands being used but it sure seems that there is not some kind of locking system for the mail files (I use maildir) to make sure only one program is accessing the said email. Am I correct? Is there a way around that?

1 0

[Dovecot] Filtering with Public Namespaces and Sieve Plugin
by Thomas Leuxner 30 Jul '09

30 Jul '09

Hi, after upgrading to Dovecot 1.2x including the rewritten Sieve plugin replacing 'cmusieve', messages which have formerly been filed to a "Public/Mailing-List" maildir are no longer filtered correctly. The sieve script itself is included in the user's personal-script. The messages are dropped to the INBOX rather than the "Public Namespace Maildir". Log's don't give a hint (at least to me). The documentation says the personal script should automatically fetch the include, and compile it in the users home... Debug log excerpt: ----------------- >2009-07-30 10:44:09 deliver(xxxx): Info: Namespace: type=public, prefix=Public/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=no >2009-07-30 10:44:09 deliver(xxxx): Info: maildir: data=/var/vmail/public:CONTROL=~/maildir/public:INDEX=~/maildir/public >2009-07-30 10:44:09 deliver(xxxx): Info: maildir++: root=/var/vmail/public, index=/var/vmail/leuxner.net/tlx/maildir/public, control=/var/vmail/leuxner.net/tlx/maildir/public, inbox= >2009-07-30 10:44:09 deliver(xxxx): Info: sieve: using sieve path for user's script: /var/vmail/leuxner.net/tlx/.dovecot.sieve >2009-07-30 10:44:09 deliver(xxxx): Info: sieve: opening script /var/vmail/leuxner.net/tlx/.dovecot.sieve >2009-07-30 10:44:09 deliver(xxxx): Info: sieve: executing compiled script /var/vmail/leuxner.net/tlx/.dovecot.sieve >2009-07-30 10:44:09 deliver(xxxx): Info: Namespace : Using permissions from /var/vmail/leuxner.net/tlx/maildir: mode=0750 gid=-1 >2009-07-30 10:44:09 deliver(xxxx): Info: sieve: msgid=<20090730084326.GP1111(a)jeeves.jpl.local>: stored mail into mailbox 'INBOX' Personal ".dovecot.sieve" script: ------------------------------ require ["include","copy","fileinto","vacation"]; include :global "global.sieve"; -- snip --- Global script "global.sieve" excerpt: ------------------------------------ require ["copy","fileinto"]; #Newsletters / Mailinglists if allof (address :is ["To","CC"] "dovecot(a)dovecot.org", header :contains "List-Id" "dovecot.dovecot.org") { fileinto "Public/Mailing-Lists.Dovecot"; } elsif allof (address :is "To" "dovecot-news(a)dovecot.org", header :contains "List-Id" "dovecot-news.dovecot.org") { fileinto :copy "Public/Newsletters.Dovecot"; } Thanks Thomas $ dovecot -n # 1.2.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.2 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap listen: 188.138.0.199:143 ssl_cert_file: /etc/ssl/certs/spectre_leuxner_net_2009.crt ssl_key_file: /etc/ssl/private/spectre_leuxner_net_2009.key login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_location: maildir:~/maildir mail_debug: yes maildir_copy_preserve_filename: yes mail_plugins: acl quota imap_quota fts fts_squat namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: Public/ location: maildir:/var/vmail/public:CONTROL=~/maildir/public:INDEX=~/maildir/public list: yes auth default: passdb: driver: passwd-file args: username_format=%u /var/vmail/%d/etc/passwd userdb: driver: passwd-file args: username_format=%u /var/vmail/%d/etc/passwd 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 user: vmail group: vmail plugin: acl: vfile:/var/vmail/%d/etc/acls:cache_secs=300 quota: maildir:User quota quota_rule: *:storage=1GB quota_rule2: Trash:storage=10%% fts: squat fts_squat: partial=4 full=10 sieve_global_dir: /var/vmail/%d/etc/sieve-scripts

2 2

Re: [Dovecot] AutoCreate per Domain
by Robert Schetterer 30 Jul '09

30 Jul '09

Darvin Denmian schrieb: > Thanks Robert, > > i will try this solution !!! maybe i can be done via a global sieve rule too ask the sieve gurus if that might work > > On Thu, Jul 30, 2009 at 11:44 AM, Robert > Schetterer<robert(a)schetterer.org> wrote: >> Darvin Denmian schrieb: >>> Any idea? >>> >>> On Thu, Jul 30, 2009 at 2:30 AM, Darvin Denmian<darvin.denmian(a)gmail.com> wrote: >>>> 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. >>>> >> i dont think this would be a good idea, cause there are so much >> layouts and setups thinkable >> so in fact it might be difficult to implement this >> for all thinkable cases in the plugin, in my maildrop setup >> i do some testing about folders exist, and if not create it, >> but deliver does not exec scripts right now i think >> >> but perhaps you can exec test folder scripts at login stage >> >> http://wiki.dovecot.org/PostLoginScripting >> >> that should do the job >> >> -- >> Best Regards >> >> MfG Robert Schetterer >> >> Germany/Munich/Bavaria >> -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

[Dovecot] sieve redirect action
by Nikita Koshikov 30 Jul '09

30 Jul '09

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 ?

3 2