Re: [Dovecot] Convert plugin mbox to maildir has no effect
On Tue, 10 Apr 2007 17:58:03 +0200 guenther wrote: > On Tue, 2007-04-10 at 17:06 +0300, Timo Sirainen wrote: > > On Sun, 2007-04-08 at 23:26 +0200, Frank Elsner wrote: > > > Apr 8 23:13:36 seymour dovecot: IMAP(migrant): Mailbox conversion: > > > Couldn't create mailbox directory .gnome2_private > > > > Maildir uses "." as hierarchy separator, so this filename is invalid. > > I'm not sure if convert_skip_broken_mailboxes=yes should just cause > > these to be ignored, but for now it doesn't.. > > Just spotted the above error message (deleted previous posts already), > and it strikes me as seriously odd. > > Dots in mbox file names are usually embedded (as in "dovecot.org"), > where it makes sense, as opposed to beginning with a dot. Even worse, > this particular name is kind of weird for a mail folder... > > However, this name is well known to me: > > [EMAIL PROTECTED] ~]$ ls -ld .gnome2_private > drwx-- 2 guenther users 4096 Jul 21 2005 .gnome2_private/ Me Too :-) > I'd check where the Maildir data actually is being created and what > files are being attempted to convert. Almost looks like the Maildir dirs > are being created in the users $HOME... No, dovecot.conf contains mail_location = maildir:/home/%u/MailDir ... convert_mail = mbox:/home/%u:INBOX=/var/spool/mail/%u convert_skip_broken_mailboxes = yes --Frank Elsner
Re: [Dovecot] rc31 -> "deferring operation: binding"
Ben Beuchler wrote: I installed a virgin install of OpenLDAP 2.3.32 directly on the mail server, copied over my LDAP database, pointed Dovecot at it, and started it up. I immediately started getting the same log entries: Some ideas from the peanut gallery here -- if you run 'ldd dovecot-auth', what openldap library is it linked into? Have you tried compiling dovecot against this new 2.3.32 openldap install? cliff:~ root# egrep -v '(^$|^#)' /opt/dovecot/etc/dovecot-ldap.conf ldap_version = 3 Have you tried binding as version 2, just to see what happens? -te -- Troy Engel | Systems Engineer Fluid Inc. | http://www.fluid.com
Re: [Dovecot] WebmAdmin for DoveCot
Azher Amin wrote: Hi, I am using Dovecot with Sendmail in my environment. So far I am doing manual operations like adding new users, aliases, setting quota etc. Is there any WebAdmin interface that works with 'Dovecot and Sendmail' and can help in above tasks, plz suggest. You might get most of the way with Webmin, but most systems differ so that you'd probably be happier if you 'rolled your own' out of the available peices: pam, saslauthd, pam-mysql, mysql, postgres, ldap, and your favorite programming/scripting languages. Ken Anderson Pacific.Net Regards -Azher
[Dovecot] WebmAdmin for DoveCot
Hi, I am using Dovecot with Sendmail in my environment. So far I am doing manual operations like adding new users, aliases, setting quota etc. Is there any WebAdmin interface that works with 'Dovecot and Sendmail' and can help in above tasks, plz suggest. Regards -Azher -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Re: [Dovecot] rc31 -> "deferring operation: binding"
The really frustrating thing, of course, is that I really have no proof whatsoever that the occasional auth failures (all authentication attempts hang until Dovecot is restarted) have anything to do with the Sorry; cut myself off. The really frustrating thing, of course, is that I really have no proof whatsoever that the occasional auth failures (all authentication attempts hang until Dovecot is restarted) have anything to do with the deferred binding issue. -Ben
Re: [Dovecot] rc31 -> "deferring operation: binding"
On 4/10/07, Timo Sirainen <[EMAIL PROTECTED]> wrote: On 10.4.2007, at 4.04, Ben Beuchler wrote: > As I understand it, the new auth_bind code is extremely careful about > flushing all pending operations before attempting to perform the > authentication bind. If that's the case, any idea why OpenLDAP is > deferring the binding operations so frequently? So far it hasn't > caused any login problems, but it's quite disconcerting given the > expected behavior described in the Changelog. Well, I've really no idea. I know it works for many people and I couldn't get it to break when stress testing with hundreds of connections per second. I installed a virgin install of OpenLDAP 2.3.32 directly on the mail server, copied over my LDAP database, pointed Dovecot at it, and started it up. I immediately started getting the same log entries: Apr 10 18:55:45 cliff slapd[10420]: connection_input: conn=3 deferring operation: binding I *must* be doing something wrong... Or, at least, I must be doing something a little different than the other test cases. Any thoughts? The really frustrating thing, of course, is that I really have no proof whatsoever that the occasional auth failures (all authentication attempts hang until Dovecot is restarted) have anything to do with the cliff:/usr/local/etc/openldap root# /opt/dovecot/sbin/dovecot -n # /opt/dovecot-1.0.rc31/etc/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/mcad.edu.rapidssl.crt ssl_key_file: /etc/ssl/private/mcad.edu.rapidssl.key disable_plaintext_auth: no verbose_ssl: yes shutdown_clients: no login_dir: /opt/dovecot-1.0.rc31/var/run/dovecot/login login_executable(default): /opt/dovecot-1.0.rc31/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot-1.0.rc31/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot-1.0.rc31/libexec/dovecot/pop3-login login_greeting: Line forms at the rear. login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_processes_count: 5 verbose_proctitle: yes first_valid_uid: 5000 last_valid_uid: 5000 first_valid_gid: 5000 last_valid_gid: 5000 mail_location: maildir:/mail/mcad.edu/%u/Maildir/ maildir_stat_dirs: yes maildir_copy_with_hardlinks: yes mail_executable(default): /opt/dovecot-1.0.rc31/libexec/dovecot/imap mail_executable(imap): /opt/dovecot-1.0.rc31/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot-1.0.rc31/libexec/dovecot/pop3 mail_plugin_dir(default): /opt/dovecot-1.0.rc31/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot-1.0.rc31/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot-1.0.rc31/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain login user: dovecot-auth verbose: yes debug: yes passdb: driver: ldap args: /opt/dovecot/etc/dovecot-ldap.conf userdb: driver: static args: uid=5000 gid=5000 socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: cliff:~ root# egrep -v '(^$|^#)' /opt/dovecot/etc/dovecot-ldap.conf uris = ldap://localhost auth_bind = yes ldap_version = 3 base = dc=accounts,dc=ldap,dc=mcad,dc=edu pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=mcadEmailAccount)(activePopImap=TRUE)(uid=%u)) default_pass_scheme = SSHA user_global_uid = 5000 user_global_gid = 5000
[Dovecot] Moving maildir folders between different RC dovecot machines
Is it ever necessary to delete any of the dovecot files when moving between machines from different RC versions? I read all the RC notes from RC15 to 31 and didn't see any notes about this, but wanted to be completely sure. Have some domains that I need to move from a RC15 machine to a RC29 machine. Also later this month we plan to ugprade from RC15 to Release 1.. when it is out shortly.
[Dovecot] Having a problem with mbox/inbox
Hi, I've just installed dovecot on a RHEL 4 server. I'm using postfix as my MTA. Everything seems to work well when I have a home dir for the user, but I don't like to clutter up my /home/ dir with dirs for users that will never use them (other than mail). Is there no way to just use /var/mail/user (I think in mbox format?). I have no interest at this time of using IMAP, this is purely for POP3. Thanks Nick
[Dovecot] error creating subfolders
I'm running rc31 and I've come across a weird little error in creating
subfolders that's only apparent in a specific situation. I recently
moved our entire campus from UW to dovecot, and as part of that
migration, and following the wiki, I have some namespaces:
##default namespace
namespace private {
separator = /
prefix =
inbox = yes
}
#for backwards compatibility:
namespace private {
separator = /
prefix = mail/
hidden = yes
}
namespace private {
separator = /
prefix = ~/mail/
hidden = yes
}
which absorb the typical configuration previously used wherein the
email client had the imap server folder set to "mail/" or similar, and
which still remains on most clients. All of this works perfectly fine,
and all users see their mail folders properly. Currently everyone is
still in mbox format, and as far as I can tell, users can also create
email folders without problems (ie single files in the file system
containing messages).
But one user discovered that it does not work to create folder
containers (ie directories in the filesystem) that would contain other
email folders, no matter how one appended / or checked the right box
(or having me add the tb-extra-mailbox-sep client workaround --
they're using Thunderbird). Their client config still had mail/ as the
server imap directory, and when I cleared that out, then everything
worked perfectly.
So it's a bit weird that everything works fine with the namespaces,
except the one operation of creating the subfolder.
John Harper
-
Systems Manager
Information and Instructional Technology Services
University of Toronto Scarborough
[EMAIL PROTECTED]
Re: [Dovecot] Problems with (probably) Dovecot
Hi Timo, thanks for your message. Timo Sirainen wrote: On 10.4.2007, at 23.15, Frank Neps wrote: Trying to access my messages on the server via IMAP protocol using Outlook (2000 or 2002 or 2003) leads to an error message "Invalid messageset: " (where is a changing number). No data is displayed, the headers are not updated. Squirrelmail says, that the messages are not available any more. And Thunderbird joins in with Outlook and also tells me something about an invalid messageset. For some reasons (and some messages, not all) Kontact / Kmail does not give me error message, however, my main system is not a Linux one and therefore I'd like to get that fixed, if possible. That most likely means that message UIDs are 2^31 or larger. Now what that would happen with upgrading, I've no idea, unless it was just a "happy" conincidence. What version were you upgrading to, and is it with mbox or maildir? I did not yet upgrade to Dovecot 1.0 because in the documentation it sounded as if it were not just starting an installation routine, but involves quite some work. With the thought in mind, that I have to move to a new server in the near future anyway, I wanted to avoid the upgrade. The current Dovecot version (still installed) is 0.99. I use the mbox format. Thanks, Frank
Re: [Dovecot] Problems with (probably) Dovecot
On 10.4.2007, at 23.15, Frank Neps wrote: Trying to access my messages on the server via IMAP protocol using Outlook (2000 or 2002 or 2003) leads to an error message "Invalid messageset: " (where is a changing number). No data is displayed, the headers are not updated. Squirrelmail says, that the messages are not available any more. And Thunderbird joins in with Outlook and also tells me something about an invalid messageset. For some reasons (and some messages, not all) Kontact / Kmail does not give me error message, however, my main system is not a Linux one and therefore I'd like to get that fixed, if possible. That most likely means that message UIDs are 2^31 or larger. Now what that would happen with upgrading, I've no idea, unless it was just a "happy" conincidence. What version were you upgrading to, and is it with mbox or maildir? PGP.sig Description: This is a digitally signed message part
[Dovecot] Problems with (probably) Dovecot
Hello altogether, I've got Dovecot 0.99 installed on a Suse Linux 9.2 system, together with Postfix. I need to upgrade that server in the near future to new hardware and new versions, but at the moment it would be great, if I could find the solution for the following problem without upgrading. Unfortunately I didn't find a solution in Google. The system has enough memory and disc space, it was running for about 4 or 5 years without problems now. Trying to access my messages on the server via IMAP protocol using Outlook (2000 or 2002 or 2003) leads to an error message "Invalid messageset: " (where is a changing number). No data is displayed, the headers are not updated. Squirrelmail says, that the messages are not available any more. And Thunderbird joins in with Outlook and also tells me something about an invalid messageset. For some reasons (and some messages, not all) Kontact / Kmail does not give me error message, however, my main system is not a Linux one and therefore I'd like to get that fixed, if possible. Somewhere in Google I found a note about IMAP index files, which may be corrupt and need to be rebuilt, but I didn't find any Index files, I must admit. Any idea how to solve that? Thanks in advance and best regards, Frank
Re: [Dovecot] Connection refused with auth-master afterupgradingto Dovecot 1.0 rc 28
> On 10.4.2007, at 21.33, Jason Warner wrote: > > > I still didn't get a core dump in /var/run/dovecot. Should I be > > looking > > somewhere else? That is the directory that the base_dir variable is > > set to > > in my dovecot.conf file. > > Well, another way would be to attach gdb directly into dovecot-auth > while it's still running: > > gdb attach `pidof dovecot-auth` > cont > (wait for crash) > bt full > fr 4 > p *request > > Anyway I should be able to figure out the assert by looking at the > code too. Just a bit more difficult, since a couple of minutes wasn't > enough. :) Here's the best I could do: (gdb) bt full #0 0x004b9402 in __kernel_vsyscall () No symbol table info available. #1 0x00686d40 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x00688591 in abort () from /lib/libc.so.6 No symbol table info available. #3 0x0806bb9a in i_error () No symbol table info available. #4 0x0806baac in i_panic () No symbol table info available. #5 0x080552ce in auth_request_lookup_credentials_callback () No symbol table info available. #6 0x0805f2bd in passdb_cache_init () No symbol table info available. #7 0x0805f684 in passdb_cache_init () No symbol table info available. #8 0x0805906b in db_ldap_connect () No symbol table info available. #9 0x0806ef30 in io_loop_handler_run () No symbol table info available. #10 0x0806e27c in io_loop_run () No symbol table info available. #11 0x0805a51e in main () No symbol table info available. It looks like a stack trace, but the p *request just gives "No symbol table info available" for all 11 integers. > > > I tried this with both the allow_all_users set and without it set. > > That was > > the fix though. By adding allow_all_users to my userdb static args, > > everything is running just fine. > > Only problem with that is that it doesn't know if the user exists or > not. So depending on how you've set up permissions, it's possible > that it delivers mails to unknown users as well, creating the > directories if needed.. That is a problem. I'll go back to Postfix's virtual delivery method until I don't have to use the allow_all_users flag.
Re: [Dovecot] Connection refused with auth-master afterupgradingto Dovecot 1.0 rc 28
On 10.4.2007, at 21.33, Jason Warner wrote: I still didn't get a core dump in /var/run/dovecot. Should I be looking somewhere else? That is the directory that the base_dir variable is set to in my dovecot.conf file. Well, another way would be to attach gdb directly into dovecot-auth while it's still running: gdb attach `pidof dovecot-auth` cont (wait for crash) bt full fr 4 p *request Anyway I should be able to figure out the assert by looking at the code too. Just a bit more difficult, since a couple of minutes wasn't enough. :) I tried this with both the allow_all_users set and without it set. That was the fix though. By adding allow_all_users to my userdb static args, everything is running just fine. Only problem with that is that it doesn't know if the user exists or not. So depending on how you've set up permissions, it's possible that it delivers mails to unknown users as well, creating the directories if needed.. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Connection refused with auth-master afterupgradingto Dovecot 1.0 rc 28
> > Apr 10 11:48:28 mail deliver([EMAIL PROTECTED]): setgid(999) failed: > > Operation > > not permitted > .. > > 999 is the gid of my vmail user. > .. > > dovecot unix - n n - - pipe > > flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d > > So then you should use vmail:vmail here. That did it. Thank you so much for your help. > > > I couldn't find a core dump file in the base_dir (/var/run/ > > dovecot). Is > > there a way to force a core dump? > > ulimit -c unlimited > > in the same shell before running dovecot should do it. I still didn't get a core dump in /var/run/dovecot. Should I be looking somewhere else? That is the directory that the base_dir variable is set to in my dovecot.conf file. I tried this with both the allow_all_users set and without it set. That was the fix though. By adding allow_all_users to my userdb static args, everything is running just fine.
Re: [Dovecot] Connection refused with auth-master afterupgradingto Dovecot 1.0 rc 28
On 10.4.2007, at 21.00, Jason Warner wrote: Apr 10 11:48:28 mail deliver([EMAIL PROTECTED]): setgid(999) failed: Operation not permitted .. 999 is the gid of my vmail user. .. dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d So then you should use vmail:vmail here. I couldn't find a core dump file in the base_dir (/var/run/ dovecot). Is there a way to force a core dump? ulimit -c unlimited in the same shell before running dovecot should do it. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Connection refused with auth-master afterupgradingto Dovecot 1.0 rc 28
> -Original Message- > From: Timo Sirainen [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 10, 2007 11:45 AM > To: Dovecot Mailing List > Cc: Jason Warner; 'Jason Warner' > Subject: Re: [Dovecot] Connection refused with auth-master > afterupgradingto Dovecot 1.0 rc 28 > > On 10.4.2007, at 20.35, Timo Sirainen wrote: > > > On 10.4.2007, at 20.22, Jason Warner wrote: > > > >> Apr 10 10:12:15 mail dovecot: auth(default): file auth-request.c: > >> line 474 > >> (auth_request_lookup_credentials_callback): assertion failed: > >> (request->state == AUTH_REQUEST_STATE_PASSDB) > > > > Oh. So the connection refused happens because dovecot-auth crashes. > > Now this is beginning to make sense. The easiest way to fix this is > > to add allow_all_users to userdb static's args. I'll try to figure > > out why this crash is happening. Adding allow_all_users to my userdb static args gets rid of the previous error message, but now the logs contain this message: Apr 10 11:48:28 mail deliver([EMAIL PROTECTED]): setgid(999) failed: Operation not permitted Apr 10 11:48:28 mail postfix/pipe[17576]: 95FC916872D: to=<[EMAIL PROTECTED]>, relay=dovecot, delay=0.31, delays=0.26/0.02/0/0.02, dsn=2.0.0, status=sent (delivered via dovecot service) 999 is the gid of my vmail user. > > Do you have core file in Dovecot's base_dir (/var/run/dovecot/ or / > usr/local/var/run/dovecot/ probably)? If so, could you do: > > gdb /path/to/dovecot-auth /path/to/core > bt full > fr 4 > p *request > > (I think fr 4 is correct to give a usable output for p *request, if > it just says "No symbol" try with different fr numbers. It's anyway > the one that bt full shows auth_request_lookup_credentials_callback() > being in) > I couldn't find a core dump file in the base_dir (/var/run/dovecot). Is there a way to force a core dump?
Re: [Dovecot] get userlogin for shell script
On 10.4.2007, at 20.41, Dirk Schleicher wrote: how can I get some information if a user is connect to the dovecot imap? I like to build a script what asked if there is a connect. If yes the loop until no connect an then stop dovecot. See if there exists any "imap" processes. But I think this is a bad idea. IMAP clients in general tend to be connected as long as the client is opened. I've had an IMAP connection be open for weeks. Dovecot has shutdown_clients setting. If you set it to "no" and you kill dovecot, the imap processes keep on running. Would this work for you instead? PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Connection refused with auth-master afterupgradingto Dovecot 1.0 rc 28
On 10.4.2007, at 20.35, Timo Sirainen wrote: On 10.4.2007, at 20.22, Jason Warner wrote: Apr 10 10:12:15 mail dovecot: auth(default): file auth-request.c: line 474 (auth_request_lookup_credentials_callback): assertion failed: (request->state == AUTH_REQUEST_STATE_PASSDB) Oh. So the connection refused happens because dovecot-auth crashes. Now this is beginning to make sense. The easiest way to fix this is to add allow_all_users to userdb static's args. I'll try to figure out why this crash is happening. Do you have core file in Dovecot's base_dir (/var/run/dovecot/ or / usr/local/var/run/dovecot/ probably)? If so, could you do: gdb /path/to/dovecot-auth /path/to/core bt full fr 4 p *request (I think fr 4 is correct to give a usable output for p *request, if it just says "No symbol" try with different fr numbers. It's anyway the one that bt full shows auth_request_lookup_credentials_callback() being in) PGP.sig Description: This is a digitally signed message part
[Dovecot] get userlogin for shell script
Hello, how can I get some information if a user is connect to the dovecot imap? I like to build a script what asked if there is a connect. If yes the loop until no connect an then stop dovecot. How can I do this? Thanks Dirk
Re: [Dovecot] Dovecot Assertion on mail server with POP3 and LDAP authentication
On 10.4.2007, at 20.31, Tim Alberts wrote: Apr 4 08:44:38 msi2 dovecot: auth(default): dovecot- auth: ../../../libraries/liblber/io.c:491: ber_get_next: Assertion `ber->ber_buf == ((void *)0)' failed. Apr 4 08:44:38 msi2 dovecot: auth(default): pam(secretuser, 192.168.0.200): Child process died .. passdb: driver: pam userdb: driver: passwd So you're using pam_ldap and nss_ldap. See http://wiki.dovecot.org/ AuthDatabase/Passwd So I'd suggest upgrading. Thank you for the quick response. It doesn't look like the problem I'm having though? I don't have problems with people getting other peoples email. I have problems with the Assertion errors that I mentioned. No, but it could very well be caused by the same problem. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Connection refused with auth-master afterupgradingto Dovecot 1.0 rc 28
On 10.4.2007, at 20.22, Jason Warner wrote: Apr 10 10:12:15 mail dovecot: auth(default): file auth-request.c: line 474 (auth_request_lookup_credentials_callback): assertion failed: (request->state == AUTH_REQUEST_STATE_PASSDB) Oh. So the connection refused happens because dovecot-auth crashes. Now this is beginning to make sense. The easiest way to fix this is to add allow_all_users to userdb static's args. I'll try to figure out why this crash is happening. At this point, it looks like there was a retry and the dovecot service delivers the mail, but the mail disappears into thin air. The problem is that I have a ton of mail flooding the server and errors are overwritten before I can take a look at them. I wasn't even able to compare the same mail being sent in the delivery logs because by the time I stopped the logging more mail had come into the system. A test system would be good. :) PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Dovecot Assertion on mail server with POP3 and LDAP authentication
Timo Sirainen wrote: On 10.4.2007, at 19.48, Tim Alberts wrote: Apr 4 08:44:38 msi2 dovecot: auth(default): dovecot-auth: ../../../libraries/liblber/io.c:491: ber_get_next: Assertion `ber->ber_buf == ((void *)0)' failed. Apr 4 08:44:38 msi2 dovecot: auth(default): pam(secretuser,192.168.0.200): Child process died .. passdb: driver: pam userdb: driver: passwd So you're using pam_ldap and nss_ldap. See http://wiki.dovecot.org/AuthDatabase/Passwd So I'd suggest upgrading. Thank you for the quick response. It doesn't look like the problem I'm having though? I don't have problems with people getting other peoples email. I have problems with the Assertion errors that I mentioned. I do see that Fedora has updated packages available for Fedora so I'll upgrade and see what happens.
Re: [Dovecot] Connection refused with auth-master afterupgradingto Dovecot 1.0 rc 28
> On 10.4.2007, at 19.30, Jason Warner wrote:
>
> > < write(6, "[EMAIL PROTECTED]"..., 55) = 55
> ..
> >> write(6, "[EMAIL PROTECTED]"..., 54) = 54
>
> Your original error was: "net_connect(/var/run/dovecot/auth-master)
> failed: Connection refused". However here both of them were
> successfully connected to, and this shows that the authentication
> handshake was successfully sent. So I think it wrote a different
> error message to Dovecot's logs this time.
I'm afraid that I've tampered with stuff so much on this server that things
have changed from when I originally posted.
Apr 10 10:12:14 mail postfix/smtpd[562]: A7F1B168734:
client=mail.domain.com[127.0.0.1]
Apr 10 10:12:14 mail postfix/cleanup[496]: A7F1B168734:
message-id=<[EMAIL PROTECTED]>
Apr 10 10:12:14 mail postfix/qmgr[452]: A7F1B168734: from=<[EMAIL PROTECTED]>,
size=2600, nrcpt=1 (queue active)
Apr 10 10:12:14 mail postfix/smtp[464]: E4B351686E4: to=<[EMAIL PROTECTED]>,
relay=127.0.0.1[127.0.0.1]:10024, delay=7, delays=0.22/0/0.01/6.8,
dsn=2.6.0, status=sent (250 2.6.0 Ok, id=31657-06, from MTA: 250 2.0.0 Ok:
queued as A7F1B168734)
Apr 10 10:12:15 mail dovecot: auth(default): file auth-request.c: line 474
(auth_request_lookup_credentials_callback): assertion failed:
(request->state == AUTH_REQUEST_STATE_PASSDB)
Apr 10 10:12:15 mail dovecot: auth(default): Raw backtrace: dovecot-auth
[0x806bb91] -> dovecot-auth [0x806baac] -> dovecot-auth [0x80552ce] ->
dovecot-auth [0x805f2bd] -> dovecot-auth [0x805f684] -> dovecot-auth
[0x805906b] -> dovecot-auth(io_loop_handler_run+0x110) [0x806ef30] ->
dovecot-auth(io_loop_run+0x1c) [0x806e27c] -> dovecot-auth(main+0x2fe)
[0x805a51e] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x673f2c] ->
dovecot-auth {0x8050ba1]
Apr 10 10:12:15 mail dovecot: child 31532 (auth) killed with signal 6
Apr 10 10:12:15 mail postfix/pipe[563]: A7F1B168734: to=<[EMAIL PROTECTED]>,
relay=dovecot, delay=0.75, delays=0.24/0.06/0/0.45, dsn=4.3.0,
status=deferred (temporary failure)
This looks like the auth fails due to some error, but I'm not sure what.
Apr 10 10:13:55 mail postfix/qmgr[864]: A7F1B168734: from=<[EMAIL PROTECTED]>,
size=2600, nrcpt=1 (queue active)
Apr 10 10:13:55 mail postfix/pipe[890]: A7F1B168734: to=<[EMAIL PROTECTED]>,
relay=dovecot, delay=101, delays=101/0.02/0/0.11, dsn=2.0.0, status=sent
(delivered via dovecot service)
Apr 10 10:13:55 mail postfix/qmgr[864]: A7F1B168734: removed
At this point, it looks like there was a retry and the dovecot service
delivers the mail, but the mail disappears into thin air. The problem is
that I have a ton of mail flooding the server and errors are overwritten
before I can take a look at them. I wasn't even able to compare the same
mail being sent in the delivery logs because by the time I stopped the
logging more mail had come into the system.
Re: [Dovecot] Dovecot deliver agent - dovecot.conf permissions
On 10.4.2007, at 19.56, Daniel L. Miller wrote: I started playing with deliver, and saw a permission error in the logs for dovecot.conf. Under my distro install, /etc/dovecot.conf was installed owner/group root, with only user rw rights. I added "other" read privileges and deliver is happy - is this necessary? For now, yea. Or of course if you can change its user/group to same as what runs deliver. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Connection refused with auth-master afterupgradingto Dovecot 1.0 rc 28
On 10.4.2007, at 19.30, Jason Warner wrote: < write(6, "[EMAIL PROTECTED]"..., 55) = 55 .. write(6, "[EMAIL PROTECTED]"..., 54) = 54 Your original error was: "net_connect(/var/run/dovecot/auth-master) failed: Connection refused". However here both of them were successfully connected to, and this shows that the authentication handshake was successfully sent. So I think it wrote a different error message to Dovecot's logs this time. PGP.sig Description: This is a digitally signed message part
[Dovecot] Dovecot deliver agent - dovecot.conf permissions
I started playing with deliver, and saw a permission error in the logs for dovecot.conf. Under my distro install, /etc/dovecot.conf was installed owner/group root, with only user rw rights. I added "other" read privileges and deliver is happy - is this necessary? -- Daniel
Re: [Dovecot] Dovecot Assertion on mail server with POP3 and LDAP authentication
On 10.4.2007, at 19.48, Tim Alberts wrote: Apr 4 08:44:38 msi2 dovecot: auth(default): dovecot-auth: ../../../ libraries/liblber/io.c:491: ber_get_next: Assertion `ber->ber_buf == ((void *)0)' failed. Apr 4 08:44:38 msi2 dovecot: auth(default): pam(secretuser, 192.168.0.200): Child process died .. passdb: driver: pam userdb: driver: passwd So you're using pam_ldap and nss_ldap. See http://wiki.dovecot.org/ AuthDatabase/Passwd So I'd suggest upgrading. PGP.sig Description: This is a digitally signed message part
[Dovecot] Dovecot Assertion on mail server with POP3 and LDAP authentication
Running two Fedora 6 systems with all the latest updates as of a week ago. One system is the mail server (sendmail, dovecot), the other is the master (open)LDAP server with the mail server running a slave LDAP instance. The problem I'm having is the client pop3 users are frequently being told their passwords aren't correct by their email clients (Outlook, Eudora). They try again, a couple times and eventually it works. I've seen it on my own account and when I test their accounts, occasionally it just doesn't take the password. I've only had this trouble since I implemented the LDAP authentication. Checking through the server maillog, I see the following entry: Apr 4 08:44:38 msi2 dovecot: auth(default): dovecot-auth: ../../../libraries/liblber/io.c:491: ber_get_next: Assertion `ber->ber_buf == ((void *)0)' failed. Apr 4 08:44:38 msi2 dovecot: auth(default): pam(secretuser,192.168.0.200): Child process died Apr 4 08:44:38 msi2 dovecot: auth(default): PAM: Child 14564 died with signal 6 Apr 4 08:44:38 msi2 dovecot: pop3-login: Aborted login: user=, method=PLAIN, rip=192.168.0.200, lip=192.168.0.11 This seems to point out that dovecot is the problem, but again, I didn't have this trouble until I implemented the LDAP authentication. So my question is, anyone know a solution? If not, anyone got a suggestion of where I should look for more clues or support? Or any suggestions at all? Thanks for any help. Following is the dovecot version and configuration [EMAIL PROTECTED] ~]# dovecot --version 1.0.rc15 [EMAIL PROTECTED] ~]# dovecot -n # /etc/dovecot.conf protocols: pop3 listen: login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam userdb: driver: passwd [EMAIL PROTECTED] ~]#
Re: [Dovecot] Dovecot 1.0rc30 message ownership set as root mail
Thanks for your help. I suspected as much. I use procmail as the LDA. Mel Timo Sirainen wrote: On Sun, 2007-04-08 at 13:18 -0600, Mel Llaguno wrote: I've compiled the latest release candidate of dovecot and I am encountering a strange problem when mail is delivered. I have my installation configured to use Maildir. When messages arrive, they are placed in the correct user directory, but the ownership for individual messages is set to root and the group set to mail. .. -rw--- 1 root mail 1805 2007-04-08 13:02 _AqG.VxTGGB.mjolnir:2, What delivers the mails to maildir? You're not using Dovecot LDA because Dovecot doesn't create filenames like this. So your problem really has nothing to do with Dovecot, but rather the configuration of your MTA or mail delivery agent.
Re: [Dovecot] Connection refused with auth-master afterupgradingto Dovecot 1.0 rc 28
> -Original Message-
> From: Timo Sirainen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 10, 2007 9:36 AM
> To: Jason Warner
> Cc: 'Jason Warner'; dovecot@dovecot.org
> Subject: Re: [Dovecot] Connection refused with auth-master
> afterupgradingto Dovecot 1.0 rc 28
>
> On Tue, 2007-04-10 at 09:32 -0600, Jason Warner wrote:
> > Sorry, I forgot to mention that when I tried the -d parameter, I was
> > running
> > as the vmail user and everything went just fine.
>
> I'm running out of ideas. strace could be helpful. Run:
>
> strace -o /tmp/deliver.log deliver -d ..
>
> Both as standalone and in Postfix. What's different in the log file?
Here's a diff of the two log files:
1,3c1,3
< execve("/usr/libexec/dovecot/deliver", ["/usr/libexec/dovecot/deliver",
"-d", "[EMAIL PROTECTED]"], [/* 26 vars */]) = 0
< brk(0) = 0x9cac000
< mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7f31000
---
> execve("/usr/libexec/dovecot/deliver", ["/usr/libexec/dovecot/deliver",
"-d", "[EMAIL PROTECTED]"], [/* 3 vars */]) = 0
> brk(0) = 0x8192000
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7f4b000
7c7
< mmap2(NULL, 102341, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f18000
---
> mmap2(NULL, 102341, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f32000
22,23c22,23
< mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7f17000
< set_thread_area({entry_number:-1 -> 6, base_addr:0xb7f176c0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
---
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0xb7f31000
> set_thread_area({entry_number:-1 -> 6, base_addr:0xb7f316c0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
27,30c27,30
< munmap(0xb7f18000, 102341) = 0
< time(NULL) = 1176220958
< brk(0) = 0x9cac000
< brk(0x9cd5000) = 0x9cd5000
---
> munmap(0xb7f32000, 102341) = 0
> time(NULL) = 1176221679
> brk(0) = 0x8192000
> brk(0x81bb000) = 0x81bb000
32,33c32,33
< getpid()= 31531
< gettimeofday({1176220958, 974801}, {360, 0}) = 0
---
> getpid()= 1143
> gettimeofday({1176221679, 229181}, {360, 0}) = 0
96,106c96,106
< _llseek(6, 0, 0xbfa70aa0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
< getsockname(6, {sa_family=AF_FILE, path="Ã"}, [2]) = 0
< write(6, "[EMAIL PROTECTED]"..., 55) = 55
At this line, before changing the domain, it was a partial of my domain name
< gettimeofday({1176220958, 988500}, NULL) = 0
< poll([{fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=6,
events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL, revents=POLLIN}], 2, 59986)
= 1
< gettimeofday({1176220958, 988718}, {360, 0}) = 0
< read(6, "VERSION\t1\t0\nSPID\t28471\n", 4096) = 23
< gettimeofday({1176220958, 988913}, NULL) = 0
< poll([{fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=6,
events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL, revents=POLLIN|POLLHUP}], 2,
59986) = 1
< gettimeofday({1176220959, 11220}, {360, 0}) = 0
< read(6, "", 4073) = 0
---
> _llseek(6, 0, 0xbf9345b0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
> getsockname(6, {sa_family=AF_FILE, path="^Y^H"}, [2]) = 0
> write(6, "[EMAIL PROTECTED]"..., 54) = 54
Again, it was a partial before changing the domain.
> gettimeofday({1176221679, 234529}, NULL) = 0
> poll([{fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=6,
events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL, revents=POLLIN}], 2, 59995)
= 1
> gettimeofday({1176221679, 234669}, {360, 0}) = 0
> read(6, "VERSION\t1\t0\nSPID\t1141\n", 4096) = 22
> gettimeofday({1176221679, 234825}, NULL) = 0
> poll([{fd=3, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=6,
events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL, revents=POLLIN|POLLHUP}], 2,
59995) = 1
> gettimeofday({1176221679, 242218}, {360, 0}) = 0
> read(6, "", 4074) = 0
The first file was run as the vmail user from the command line with the -d.
The second was run from Postfix.
An interesting thing about the Postfix bug is that I now get these lines in
the log:
Apr 10 10:12:14 mail postfix/smtpd[562]: A7F1B168734:
client=mail.domain.com[127.0.0.1]
Apr 10 10:12:14 mail postfix/cleanup[496]: A7F1B168734:
message-id=<[EMAIL PROTECTED]>
Apr 10 10:12:14 mail postfix/qmgr[452]: A7F1B168734: from=<[EMAIL PROTECTED]>,
size=2600, nrcpt=1 (queue active)
Apr 10 10:12:14 mail postfix/smtp[464]: E4B351686E4: to=<[EMAIL PROTECTED]>,
relay=127.0.0.1[127.0.0.1]:10024, delay=7, delays=0.22/0/0.01/6.8,
dsn=2.6.0, status=sent (250 2.6.0 Ok, id=31657-06, from MTA: 250 2.0.0 Ok:
queued as A7F1B16873
Re: [Dovecot] Convert plugin mbox to maildir has no effect
On Tue, 2007-04-10 at 17:06 +0300, Timo Sirainen wrote:
> On Sun, 2007-04-08 at 23:26 +0200, Frank Elsner wrote:
> > Apr 8 23:13:36 seymour dovecot: IMAP(migrant): Mailbox conversion:
> > Couldn't create mailbox directory .gnome2_private
>
> Maildir uses "." as hierarchy separator, so this filename is invalid.
> I'm not sure if convert_skip_broken_mailboxes=yes should just cause
> these to be ignored, but for now it doesn't..
Just spotted the above error message (deleted previous posts already),
and it strikes me as seriously odd.
Dots in mbox file names are usually embedded (as in "dovecot.org"),
where it makes sense, as opposed to beginning with a dot. Even worse,
this particular name is kind of weird for a mail folder...
However, this name is well known to me:
[EMAIL PROTECTED] ~]$ ls -ld .gnome2_private
drwx-- 2 guenther users 4096 Jul 21 2005 .gnome2_private/
I'd check where the Maildir data actually is being created and what
files are being attempted to convert. Almost looks like the Maildir dirs
are being created in the users $HOME...
guenther
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Re: [Dovecot] "TLS handshake" errors, frozen IMAP
On Tue, 2007-04-10 at 10:34 -0500, Ben Beuchler wrote: > Apr 10 09:11:36 cliff dovecot: imap-login: Disconnected: > rip=150.253.80.90, lip=150.253.10.10, TLS handshake This means that client started SSL/TLS handshake, but it wasn't finished. Why that might happen, I don't really know. verbose_ssl=yes might show something, but just as well might not. Do you have login_process_per_connection=yes? If so and if it happened to all connections, there was something wrong with the global state. Hmm. Do you see something like this in the error log: Waiting for SSL parameter file signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Connection refused with auth-master after upgradingto Dovecot 1.0 rc 28
On Tue, 2007-04-10 at 09:32 -0600, Jason Warner wrote: > Sorry, I forgot to mention that when I tried the -d parameter, I was > running > as the vmail user and everything went just fine. I'm running out of ideas. strace could be helpful. Run: strace -o /tmp/deliver.log deliver -d .. Both as standalone and in Postfix. What's different in the log file? signature.asc Description: This is a digitally signed message part
[Dovecot] "TLS handshake" errors, frozen IMAP
Another new issue has cropped up with my rc1 -> rc31 upgrade: This morning, right around the typical morning email surge, Dovecot stopped accepting new IMAP connections. I didn't get a chance to do much troubleshooting and a restart of Dovecot fixed it. The only thing I've been able to find in the logs is a bunch of entries like this one: Apr 10 09:11:36 cliff dovecot: imap-login: Disconnected: rip=150.253.80.90, lip=150.253.10.10, TLS handshake Apr 10 09:11:36 cliff dovecot: imap-login: Disconnected: rip=150.253.80.208, lip=150.253.10.10, TLS handshake Apr 10 09:11:37 cliff dovecot: imap-login: Disconnected: rip=150.253.91.156, lip=150.253.10.10, TLS handshake And a few like this: Apr 10 09:17:48 cliff dovecot: imap-login: Disconnected: Shutting down: rip=66.93.16.227, lip=150.253.10.10, TLS handshake Any idea what that might indicate? -Ben
Re: [Dovecot] Connection refused with auth-master after upgradingto Dovecot 1.0 rc 28
> -Original Message-
> From: Timo Sirainen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 10, 2007 9:24 AM
> To: Jason Warner
> Cc: 'Jason Warner'; dovecot@dovecot.org
> Subject: RE: [Dovecot] Connection refused with auth-master after
> upgradingto Dovecot 1.0 rc 28
>
> On Tue, 2007-04-10 at 09:11 -0600, Jason Warner wrote:
>
> > When I run deliver with the -d parameter, it does deliver a message to
> > the
> > intended user. I've tried just about everything I know how to do with
> > the
> > Dovecot LDA in the master.cf config file for Postfix. Here is the line
> > as it
> > stands now:
> >
> > # Dovecot LDA
> > dovecot unix - n n - - pipe
> > flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d
> > ${recipient}
>
> So what about running deliver as vmail?
>
> sudo su vmail -s /usr/libexec/dovecot/deliver -d [EMAIL PROTECTED]
>
> What OS do you use? Do you use SELinux or anything like that?
Sorry, I forgot to mention that when I tried the -d parameter, I was running
as the vmail user and everything went just fine.
We're running Fedora Core 6. I've disabled SELinux on our mail box. There
have been SELinux updates recently. I'm not sure if they would affect our
mail server with SELinux disabled.
Re: [Dovecot] Connection refused with auth-master after upgrading to Dovecot 1.0 rc 28
On Tue, 2007-04-10 at 09:11 -0600, Jason Warner wrote:
> When I run deliver with the -d parameter, it does deliver a message to
> the
> intended user. I've tried just about everything I know how to do with
> the
> Dovecot LDA in the master.cf config file for Postfix. Here is the line
> as it
> stands now:
>
> # Dovecot LDA
> dovecot unix - n n - - pipe
> flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d
> ${recipient}
So what about running deliver as vmail?
sudo su vmail -s /usr/libexec/dovecot/deliver -d [EMAIL PROTECTED]
What OS do you use? Do you use SELinux or anything like that?
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] MANAGESIEVE patch v4 for dovecot 1.0.rc28 / problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo Sirainen schrieb: > On Sun, 2007-04-08 at 16:10 +0200, Stephan Bosch wrote: >> Robert Schetterer wrote: >>> Hi,ok setui above works >>> using avelsieve squirrelmail plugin >>> with managesieve dovecot latest >>> (perhaps i shouldnt use 1.30 rc) >>> as well there may be other problems between suse and quotawarn patches ) >>> please see this just as info to help coders to debug >>> >>> following problems in logs appear >>> >>> /var/log/messages >>> >>> 9 04:51:41 suse10-2-vmware kernel: managesieve-log[2326]: segfault at >>> rip rsp 7fff8995b938 error 14 >>> >>> i have no idea where this comes from >> Hmm. That's not good.. what ever happens, dovecot(-managesieve) must >> never segfault. Maybe you could provide a core-dump. Btw, I don't really >> know what managesieve-log is supposed to be. Timo, any ideas? > > Truncated managesieve-login most likely. Unfortunately it's really > difficult to get login processes to produce core dumps. It's a lot > easier to attach gdb into it while it's still running. First set: > > login_process_per_connection = no > login_processes_count = 1 > > Then you should have only one managesieve-login process. Then attach gdb > into it: > > gdb attach `pidof managesieve-login` > cont > > Then wait for it to crash and then give "bt full" command. > >>> /var/log/dovcot.info >>> >>> dovecot: Apr 09 04:55:00 Info: IMAP([EMAIL PROTECTED]): Disconnected: >>> Logged out >>> dovecot: Apr 09 04:55:08 Info: managesieve-login: Login: >>> user=<[EMAIL PROTECTED]>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS >>> dovecot: Apr 09 04:55:08 Info: MANAGESIEVE([EMAIL PROTECTED]): Effective >>> uid=1001, gid=1001 >>> dovecot: Apr 09 04:55:08 Info: MANAGESIEVE([EMAIL PROTECTED]): sieve >>> storage: Using active sieve script path: >>> /usr/local/virtual/[EMAIL PROTECTED]//.dovecot.sieve >>> >>> ( this line looks strange to me, but it musnt be false ) >> That looks very strange. Assuming you are not using the userdb to >> specify the SIEVE path (code directly borrowed from dovecot-sieve), 'the >> problem' seems to be that the home directory of [EMAIL PROTECTED] ends >> in a /. By looking at dovecot's home_expand code I discovered this is >> not checked while expanding ~/.dovecot.sieve. However, linux/unix/POSIX >> (?) seems to be handling duplicate slashes as single ones, so it should >> work properly anyhow. But, maybe Timo is interested in making some >> cosmetic changes. :) > > I do remove extra slashes in a couple of places, but here it's easier > just to change userdb not to return the extra slashes. :) Anyway, like > you said it should cause no problems. Thx Timo, i will wait for the new managesieve patch to do more testings, perhaps version dovecot stable 1 will be out there too - -- Mit freundlichen Gruessen Best Regards Robert Schetterer https://www.schetterer.org Munich/Bavaria/Germany -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGG6pVfGH2AvR16oERAtY9AJ0T6aG4M+fu4d3fRPLRlwuMvs7liwCgiPYp Oj9jj0o/Nfv1ci++VNVu8BA= =bmSF -END PGP SIGNATURE-
Re: [Dovecot] rc31 -> "deferring operation: binding"
Is there anything else in slapd logs? I haven't been able to identify anything of consequence. For example I found this with google: http://www.openldap.org/lists/openldap-software/200507/ msg00063.html Aye, I saw that as well. Unfortunately, Howard points out that the author of that message was mistaken and, as near as I can tell, the only "solution" anyone could come up with was to upgrade. I'm already running the current stable OpenLDAP. I'll try to track down more info. -Ben
Re: [Dovecot] Connection refused with auth-master after upgrading to Dovecot 1.0 rc 28
Timo,
I really want to thank you for taking the time to look at this. I'm a newbie
with a little Linux experience, so I'm in charge of the mail server. It
makes it nice to deal with someone who really knows what they are doing.
> -Original Message-
> From: Timo Sirainen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 10, 2007 8:46 AM
> To: Jason Warner
> Cc: 'Jason Warner'; dovecot@dovecot.org
> Subject: Re: [Dovecot] Connection refused with auth-master after
> upgradingto Dovecot 1.0 rc 28
>
> On Mon, 2007-04-09 at 08:45 -0600, Jason Warner wrote:
> > > >> > Apr 2 12:56:32 mail deliver([EMAIL PROTECTED]):
> > > >> > net_connect(/var/run/dovecot/auth-master) failed: Connection
> > > >> refused
> > > >>
> > > >> Delete this file. Restart Dovecot. Does it get recreated?
> > > >
> > > > When I delete the file and restart Dovecot it is recreated.
> > >
> > > Does this then happen every time when running deliver? Does netstat
> > > show that dovecot-auth is listening in that path?
> >
> > When running deliver from the command line, I do not get the error. The
> > error only appears when deliver is run from Postfix.
>
> And you gave deliver -d parameter when running from command line? If it
> works from there but not from Postfix, then the problem has something to
> do with how deliver is started. Did you try running as the same user as
> what Postfix runs it with?
When I run deliver with the -d parameter, it does deliver a message to the
intended user. I've tried just about everything I know how to do with the
Dovecot LDA in the master.cf config file for Postfix. Here is the line as it
stands now:
# Dovecot LDA
dovecot unix - n n - - pipe
flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d
${recipient}
That line worked just fine up until the update. After some looking, we were
running 1.0 rc 15 so this step up to 28 was quite a move. Fortunately, the
mail server is working with our virtual setup, but our vacation message
setup relied on the sieve portions of the Dovecot LDA. Thanks again for
taking a look at this.
>
> > Netstat shows the following when running.
> >
> > unix 2 [ ACC ] STREAM LISTENING 255526 private/dovecot
> > unix 2 [ ACC ] STREAM LISTENING 1176428
> > /var/run/dovecot/auth-master
>
> So it should be accepting connections.
>
> > It appears that the auth-master is running. How would I check to make
> sure
> > that it is listening and responding properly to requests?
>
> There really isn't any other way than to run deliver. auth_debug=yes
> will also log something whenever deliver is run and dovecot-auth sees
> something.
Re: [Dovecot] MANAGESIEVE patch v4 for dovecot 1.0.rc28 / problems
On Sun, 2007-04-08 at 16:10 +0200, Stephan Bosch wrote: > Robert Schetterer wrote: > > Hi,ok setui above works > > using avelsieve squirrelmail plugin > > with managesieve dovecot latest > > (perhaps i shouldnt use 1.30 rc) > > as well there may be other problems between suse and quotawarn patches ) > > please see this just as info to help coders to debug > > > > following problems in logs appear > > > > /var/log/messages > > > > 9 04:51:41 suse10-2-vmware kernel: managesieve-log[2326]: segfault at > > rip rsp 7fff8995b938 error 14 > > > > i have no idea where this comes from > Hmm. That's not good.. what ever happens, dovecot(-managesieve) must > never segfault. Maybe you could provide a core-dump. Btw, I don't really > know what managesieve-log is supposed to be. Timo, any ideas? Truncated managesieve-login most likely. Unfortunately it's really difficult to get login processes to produce core dumps. It's a lot easier to attach gdb into it while it's still running. First set: login_process_per_connection = no login_processes_count = 1 Then you should have only one managesieve-login process. Then attach gdb into it: gdb attach `pidof managesieve-login` cont Then wait for it to crash and then give "bt full" command. > > /var/log/dovcot.info > > > > dovecot: Apr 09 04:55:00 Info: IMAP([EMAIL PROTECTED]): Disconnected: > > Logged out > > dovecot: Apr 09 04:55:08 Info: managesieve-login: Login: > > user=<[EMAIL PROTECTED]>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS > > dovecot: Apr 09 04:55:08 Info: MANAGESIEVE([EMAIL PROTECTED]): Effective > > uid=1001, gid=1001 > > dovecot: Apr 09 04:55:08 Info: MANAGESIEVE([EMAIL PROTECTED]): sieve > > storage: Using active sieve script path: > > /usr/local/virtual/[EMAIL PROTECTED]//.dovecot.sieve > > > > ( this line looks strange to me, but it musnt be false ) > That looks very strange. Assuming you are not using the userdb to > specify the SIEVE path (code directly borrowed from dovecot-sieve), 'the > problem' seems to be that the home directory of [EMAIL PROTECTED] ends > in a /. By looking at dovecot's home_expand code I discovered this is > not checked while expanding ~/.dovecot.sieve. However, linux/unix/POSIX > (?) seems to be handling duplicate slashes as single ones, so it should > work properly anyhow. But, maybe Timo is interested in making some > cosmetic changes. :) I do remove extra slashes in a couple of places, but here it's easier just to change userdb not to return the extra slashes. :) Anyway, like you said it should cause no problems. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] quota warning - take 2
On Wed, 2007-04-04 at 17:34 +0200, Nicolas Boullis wrote: > > > This would make it easy. That code is already written, but it's not > in > > Dovecot's CVS yet. It would be useful also in dovecot-auth. > Originally I > > was thinking about using the code to replace the waitpid() calls in > > master, but that change got a bit complex so I forgot about it then. > > OK, then I guess I should consider it when I do the porting to current > CVS HEAD. Right? Yea. > By the way, any documentation I should read about quota > setups, quota rules, and quota roots for IMAP? When I had a look at > the > quota backport for 1.0, I failed to understand how things work > together... v1.0's quota code is somewhat kludgy. Quota setup is nothing, forget that. It's already removed from CVS HEAD. I think the examples in dovecot-example.conf should help with understanding quota rules and roots: # Quota limits are set using "quota_rule" parameters, either in here or in # userdb. It's also possible to give mailbox-specific limits, for example: # quota_rule = *:storage=1048576 # quota_rule2 = Trash:storage=102400 # User has now 1GB quota, but when saving to Trash mailbox the user gets # additional 100MB. # # Multiple quota roots are also possible, for example: # quota = dict:user::proxy::quota # quota2 = dict:domain:%d:proxy::quota_domain # quota_rule = *:storage=102400 # quota2_rule = *:storage=1048576 # Gives each user their own 100MB quota and one shared 1GB quota within # the domain. > Does this mean it looks good enough for you and you have nothing to > criticize? Wow! I was mostly concerned about if the the configuration should be done like that or somehow differently. But I think it's good now. With CVS HEAD you'd have to support multiple quota roots though, so: quota_warning = .. quota_warning2 = .. quota2_warning = .. There are also some minor coding style things to keep it consistent, but I'll change them when I merge the code. And :2 needs to be removed here, it's a GCC extension: + enum quota_warning_limit_kind storage_limit_kind:2; + enum quota_warning_limit_kind count_limit_kind:2; signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Convert plugin mbox to maildir has no effect
On Tue, 10 Apr 2007 17:39:14 +0300 Timo Sirainen wrote:
> On Tue, 2007-04-10 at 16:15 +0200, Frank Elsner wrote:
> > On Tue, 10 Apr 2007 17:06:02 +0300 Timo Sirainen wrote:
> > > On Sun, 2007-04-08 at 23:26 +0200, Frank Elsner wrote:
> > > > Apr 8 23:13:36 seymour dovecot: IMAP(migrant): Mailbox conversion:
> > > > Couldn't create mailbox directory .gnome2_private
> > >
> > > Maildir uses "." as hierarchy separator, so this filename is invalid.
> > > I'm not sure if convert_skip_broken_mailboxes=yes should just cause
> > > these to be ignored, but for now it doesn't..
> >
> > Could this behaviour be changed?
>
> Won't do anything to v1.0. Maybe for v1.0.1. Anyway already implemented
> to CVS HEAD (which will become v1.1):
Thanks. I'll give it a try.
[ ... ]
> > | plugin {
> > | convert_mail = mbox:~/:INBOX=/var/mail/%u
> > | convert_skip_broken_mailboxes=yes
> >
> >
> > Currently this doesn't work :-(
>
> You mean it doesn't work because you have these dot-directories? It
> would work if you didn't have them..
Tell this to the ".gnome*" and similiar people :-)
--Frank
Re: [Dovecot] Connection refused with auth-master after upgrading to Dovecot 1.0 rc 28
On Mon, 2007-04-09 at 08:45 -0600, Jason Warner wrote: > > >> > Apr 2 12:56:32 mail deliver([EMAIL PROTECTED]): > > >> > net_connect(/var/run/dovecot/auth-master) failed: Connection > > >> refused > > >> > > >> Delete this file. Restart Dovecot. Does it get recreated? > > > > > > When I delete the file and restart Dovecot it is recreated. > > > > Does this then happen every time when running deliver? Does netstat > > show that dovecot-auth is listening in that path? > > When running deliver from the command line, I do not get the error. The > error only appears when deliver is run from Postfix. And you gave deliver -d parameter when running from command line? If it works from there but not from Postfix, then the problem has something to do with how deliver is started. Did you try running as the same user as what Postfix runs it with? > Netstat shows the following when running. > > unix 2 [ ACC ] STREAM LISTENING 255526 private/dovecot > unix 2 [ ACC ] STREAM LISTENING 1176428 > /var/run/dovecot/auth-master So it should be accepting connections. > It appears that the auth-master is running. How would I check to make sure > that it is listening and responding properly to requests? There really isn't any other way than to run deliver. auth_debug=yes will also log something whenever deliver is run and dovecot-auth sees something. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Convert plugin mbox to maildir has no effect
On Tue, 2007-04-10 at 16:15 +0200, Frank Elsner wrote:
> On Tue, 10 Apr 2007 17:06:02 +0300 Timo Sirainen wrote:
> > On Sun, 2007-04-08 at 23:26 +0200, Frank Elsner wrote:
> > > Apr 8 23:13:36 seymour dovecot: IMAP(migrant): Mailbox conversion:
> > > Couldn't create mailbox directory .gnome2_private
> >
> > Maildir uses "." as hierarchy separator, so this filename is invalid.
> > I'm not sure if convert_skip_broken_mailboxes=yes should just cause
> > these to be ignored, but for now it doesn't..
>
> Could this behaviour be changed?
Won't do anything to v1.0. Maybe for v1.0.1. Anyway already implemented
to CVS HEAD (which will become v1.1):
# Skip directories beginning with '.'
#convert_skip_dotdirs = no
# If source storage has mailbox names with destination storage's
hierarchy
# separators, replace them with this character.
#convert_alt_hierarchy_char = _
The alt hierarchy character would fix the mailbox names to work, and
skipping dotdirs would make that unnecessary.
> | plugin {
> | convert_mail = mbox:~/:INBOX=/var/mail/%u
> | convert_skip_broken_mailboxes=yes
>
>
> Currently this doesn't work :-(
You mean it doesn't work because you have these dot-directories? It
would work if you didn't have them..
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] (2) Convert plugin mbox to maildir has no effect
On Tue, 10 Apr 2007 16:15:21 +0200 Frank Elsner wrote:
> On Tue, 10 Apr 2007 17:06:02 +0300 Timo Sirainen wrote:
> > On Sun, 2007-04-08 at 23:26 +0200, Frank Elsner wrote:
> > > Apr 8 23:13:36 seymour dovecot: IMAP(migrant): Mailbox conversion:
> > > Couldn't create mailbox directory .gnome2_private
> >
> > Maildir uses "." as hierarchy separator, so this filename is invalid.
> > I'm not sure if convert_skip_broken_mailboxes=yes should just cause
> > these to be ignored, but for now it doesn't..
>
> Could this behaviour be changed?
>
> I guess it's not a rare case for installations with UW-IMAP and
> would make the switch to dovecot much more attractive :-)
And please let me add that the example in
"dovecot-1.0.rc31/doc/wiki/Plugins.Convert.txt" reads
| UW-IMAP conversion
| --
|
| If your mailboxes exist in home directory among other files, you'll need to
| use:
|
| plugin {
| convert_mail = mbox:~/:INBOX=/var/mail/%u
| convert_skip_broken_mailboxes=yes
Currently this doesn't work :-(
--Frank
Re: [Dovecot] Released 1.0.rc31
On Mon, 2007-04-09 at 09:07 -0400, Justin McAleer wrote:
> Moving the dotlock creation after a successful call to
> mail_storage_create_with_data makes everything happy, but I defer to
> you
> whether it's safe to call that before locking.
Hmm. I guess that'd work. I'm not touching v1.0 anymore, but done to CVS
HEAD: http://dovecot.org/list/dovecot-cvs/2007-April/008624.html
> Here's the diff:
Please use diff -u whenever sending diffs. The default diff format is
horrible to read.
Anyway I think it's not really correct, because this needs to be done
after locking (although it's pretty unlikely to happen):
/* just in case if another process just had converted the mailbox,
reopen the source storage */
mail_storage_destroy(&source_ns->storage);
if (mail_storage_create(source_ns, NULL, source_data, user,
src_flags, lock_method) < 0) {
/* No need for conversion anymore. */
file_dotlock_delete(&dotlock);
return 0;
}
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Convert plugin mbox to maildir has no effect
On Tue, 10 Apr 2007 17:06:02 +0300 Timo Sirainen wrote: > On Sun, 2007-04-08 at 23:26 +0200, Frank Elsner wrote: > > Apr 8 23:13:36 seymour dovecot: IMAP(migrant): Mailbox conversion: > > Couldn't create mailbox directory .gnome2_private > > Maildir uses "." as hierarchy separator, so this filename is invalid. > I'm not sure if convert_skip_broken_mailboxes=yes should just cause > these to be ignored, but for now it doesn't.. Could this behaviour be changed? I guess it's not a rare case for installations with UW-IMAP and would make the switch to dovecot much more attractive :-) Regards, Frank Elsner
Re: [Dovecot] Convert plugin mbox to maildir has no effect
On Sun, 2007-04-08 at 23:26 +0200, Frank Elsner wrote: > Apr 8 23:13:36 seymour dovecot: IMAP(migrant): Mailbox conversion: Couldn't > create mailbox directory .gnome2_private Maildir uses "." as hierarchy separator, so this filename is invalid. I'm not sure if convert_skip_broken_mailboxes=yes should just cause these to be ignored, but for now it doesn't.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.0rc30 message ownership set as root mail
On Sun, 2007-04-08 at 13:18 -0600, Mel Llaguno wrote: > I've compiled the latest release candidate of dovecot and I am > encountering a strange problem when mail is delivered. I have my > installation configured to use Maildir. When messages arrive, they > are > placed in the correct user directory, but the ownership for > individual > messages is set to root and the group set to mail. .. > -rw--- 1 root mail 1805 2007-04-08 13:02 _AqG.VxTGGB.mjolnir:2, What delivers the mails to maildir? You're not using Dovecot LDA because Dovecot doesn't create filenames like this. So your problem really has nothing to do with Dovecot, but rather the configuration of your MTA or mail delivery agent. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Deliver die if global sieve script turn on
On Tue, 2007-04-10 at 17:45 +0800, M1 wrote:
> My investigation is it happened only if:
>
> 1. global script is enable and a script file is existed.
> 2. in a virtual user environment, "@" exist in "-d" parameter ("-d
> [EMAIL PROTECTED]") is passed to deliver.
>
> There is no error if no "@" character passed to deliver or no global script
> in global script directory.
>
> If the script is put in user home directory it works fine. Only if the
> script is put in global script directory have this problem. And there is no
> .err file in global script directory.
Does deliver have permissions to write to the global directory? There
should be no difference between global and user scripts.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Deliver die if global sieve script turn on
My investigation is it happened only if:
1. global script is enable and a script file is existed.
2. in a virtual user environment, "@" exist in "-d" parameter ("-d
[EMAIL PROTECTED]") is passed to deliver.
There is no error if no "@" character passed to deliver or no global script
in global script directory.
If the script is put in user home directory it works fine. Only if the
script is put in global script directory have this problem. And there is no
.err file in global script directory.
Regards,
Steve
"Steffen Kaiser" <[EMAIL PROTECTED]> wrote in
message
news:[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 3 Apr 2007, M1 wrote:
In my installation "deliver" die if global sieve script turn on. Is there
anything I have missed? Thanks..
The error message: "input in flex scanner failed"
Your Sieve script is syntactically wrong,
require "fileinto";
if header :is ""X-DSPAM-Result" "Spam" {
^
I'd bet here, the two double quotes.
fileinto "Spam";
}
Bye,
- --
Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBRhNPLS9SORjhbDpvAQK++Af/fgcImdUHkm1bEeTtWOkxVmep+oLk2Rd/
DyC4cuY4AwMBhaoeVd9FEGVrfCM63MVH0st2y9OJKqbcBxCxodjNn2G1YMb/vuNv
JzLi6gGJVrqRjCjgZMbSf1mj3GzaNPSVBE2ebt9gF+p8AkyOdiqb1WrAW7I+qJLZ
X8datms5M8zauz6ecPRXGleA89gRD6NOIi72CQZtsi1peKPZ/+RmpfAcgaxWLRiG
1GQz6gIc9nSVPur4nPTif04nLqCAQjXk89esioPwba6FDNRvzyd4t/KRkkcLZPab
o673PYLpNLVue497mPcnFBdk0dw8fCTKq/WYSzKwWuWMHLVVjWRcMQ==
=rObG
-END PGP SIGNATURE-
Re: [Dovecot] What are the Key DC executables
On 9.4.2007, at 21.02, Stewart Dean wrote: Back a year ago, I asked what the key DC executables where that I had to bring from my compile host to the production imap server to install or upgrade DC. I was told: dovecot, dovecot.conf, dovecot-auth, imap & imap-login I recently got DC up and running unencrypted and that worked fine. Then I tried to enable SSL and the logs said I was missing /usr/ local/libexec/dovecot/ssl-build-param, which I located in the build tree under ./src/master. Is there anything else I need? I wouldn't have remembered even the ssl-build-param, but I don't think there's anything else. There are some binaries in src/util/ that may be useful sometimes. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] rc31 -> "deferring operation: binding"
On 10.4.2007, at 4.04, Ben Beuchler wrote: As I understand it, the new auth_bind code is extremely careful about flushing all pending operations before attempting to perform the authentication bind. If that's the case, any idea why OpenLDAP is deferring the binding operations so frequently? So far it hasn't caused any login problems, but it's quite disconcerting given the expected behavior described in the Changelog. Well, I've really no idea. I know it works for many people and I couldn't get it to break when stress testing with hundreds of connections per second. Is there anything else in slapd logs? For example I found this with google: http://www.openldap.org/lists/openldap-software/200507/ msg00063.html PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] /etc/passwd authentication anomalies
On 9.4.2007, at 22.21, Stewart Dean wrote: I am using the base AIX Unix authentication with NIS. There is a base /etc/password file (though the passwords are in a funny, IBM- peculiar file, /etc/security/passed) of just 18 lines...since NIS is in use, the last line is the standard for-anything-you-don't- find-here-try NIS indicator: +::0:0::: When I start up DC, I get these error massages: Apr 9 14:44:59 mercury mail:err|error dovecot: auth(default): passwd-file /etc/passwd: User root has invalid UID 0 Apr 9 14:44:59 mercury mail:err|error dovecot: auth(default): passwd-file /etc/passwd: User kmem has invalid GID 0 Apr 9 14:44:59 mercury mail:err|error dovecot: auth(default): passwd-file /etc/passwd: User ipsec has invalid GID 0 Apr 9 14:44:59 mercury mail:err|error dovecot: auth(default): passwd-file /etc/passwd: User + has invalid UID 0 So is this intentional that you're using passwd-file instead of passwd? passwd-file isn't really meant to be used to read the standard /etc/passwd and so it gives these kind of warnings at startup. If you're using this as passdb, it'll probably allow user "+" to log in with an empty password. PGP.sig Description: This is a digitally signed message part
