- dovecot - dovecot.org

[Dovecot] Dovecot hangs randomly
by Jacob Elder 15 Aug '05

15 Aug '05

I have been run into a weird problem with dovecot. We have 4 identical servers running dovecot, serving both IMAP and POP3 clients. Every few hours, clients start timing out after the PASS command. Here is what the process tree looks like at that time: 6718 ? Ss 0:00 /usr/sbin/dovecot 6719 ? S 0:00 \_ dovecot-auth 6881 ? S 0:00 | \_ dovecot-auth 6883 ? S 0:00 | \_ dovecot-auth 6890 ? S 0:00 | \_ dovecot-auth 6928 ? S 0:00 | \_ dovecot-auth 6929 ? S 0:00 | \_ dovecot-auth 6934 ? S 0:00 | \_ dovecot-auth 6936 ? S 0:00 | \_ dovecot-auth 6939 ? S 0:00 | \_ dovecot-auth 6720 ? S 0:00 \_ imap-login 6721 ? S 0:00 \_ imap-login 6722 ? S 0:00 \_ imap-login 6782 ? S 0:00 \_ pop3-login 6808 ? S 0:00 \_ pop3-login 6884 ? S 0:00 \_ pop3-login 6885 ? S 0:00 \_ pop3-login 6886 ? S 0:00 \_ pop3-login 6887 ? S 0:00 \_ pop3-login 6888 ? S 0:00 \_ pop3-login 6889 ? S 0:00 \_ pop3-login 6931 ? S 0:00 \_ pop3-login 6937 ? S 0:00 \_ pop3-login 6940 ? S 0:00 \_ pop3-login After running invoke-rc.d dovecot stop, the process tree looks like this: 6782 ? S 0:00 pop3-login 6808 ? S 0:00 pop3-login 6881 ? S 0:00 dovecot-auth 6883 ? S 0:00 dovecot-auth 6884 ? S 0:00 pop3-login 6885 ? S 0:00 pop3-login 6886 ? S 0:00 pop3-login 6887 ? S 0:00 pop3-login 6889 ? S 0:00 pop3-login 6890 ? S 0:00 dovecot-auth 6928 ? S 0:00 dovecot-auth 6929 ? S 0:00 dovecot-auth 6931 ? S 0:00 pop3-login 6934 ? S 0:00 dovecot-auth 6936 ? S 0:00 dovecot-auth 6939 ? S 0:00 dovecot-auth If I run "killall -9 dovecot-auth pop3-login; invoke-rc.d dovecot start", service resumes for a few hours. This happens both on 2.6.8 and 2.4.27. This is Debian testing, 512 MB RAM, about 20 users per server. We use libnss-ldap and libpam-ldap for all users other than root. Samba, SSH, saslauthd (for Postfix), login, etc all work as expected. There is a 5th server that is identical to the other 4 except is NOT using libpam-ldap, and dovecot does not hang on this machine. Any ideas? -- Jacob Elder

2 2

[Dovecot] Documentation
by Enrique 15 Aug '05

15 Aug '05

Hello, I have added a few questions and answers to the wiki, about stuff that caused me long hunts when trying to set up dovecot with maildir storage. Some of it I have gleaned from the source. Some of it is actually already documented, but I had not been able to spot it when I needed it. At the time of writing I had a particular advantage: I did not know, or had mostly forgotten, the peculiarities of the imap protocol. I say 'advantage', because I think that when writing documentation it is important, yet difficult, to see things from the perspective of a user that is quite ignorant, although not stupid. These need the documentation most, and they are in majority. (Some will say the "stupid" ones are in majority, but writing for them is almost futile anyway. Anyway, I doubt they are a majority; average intelligence is adequate for all normal tasks. What we often judge and condemn as "stupidity" is most often the result of a different perspective that _we_ are too limited to understand.) Since I am not yet too spoiled, and yet recently had my hands (or rather my eyes) in the source, this may be a golden opportunity to produce some more documentation. I therefore urge you to suggest what I should look at and write about. Do you have any ideas about how the documentation should be organized? some questions are not strictly dovecot or even imap questions, yet they arise quite naturally for an administrator that is migrating to dovecot or to imap in general. The existing migration documentation was not as usefull to me as it could have been because I was both migrating to imap from a non-imap solutions, and from mbox to maildir, both at the same time. That placed me in a particularly "ignorant" position. It is quite likely that much of what I write is not exactly true. I have suggested procmail as a delivery agent for maildir stores, because it is the only one I know about at the moment. I just occurred to me that I have not even checked if /bin/mail (on GNU/Linux systems) can do it. Any ideas? I have not (yet) found out anything about the CONTROL= part of the mail environment. Should I write something about it? Is it usefull for system administrators to know about it? What is it? Regards -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

9 21

[Dovecot] Binc IMAP "IMAPdir" style layout
by Martin Lucina 15 Aug '05

15 Aug '05

Hi, I'm in the process of migrating several years worth of mail to be accessible via an IMAP server. Some time ago, I evaluated both Binc IMAP and Dovecot and found Dovecot to be much faster on large folders, which is quite important to me. One thing I did not however manage to determine from the documentation on namespaces is whether or not it is possible to implement what Binc IMAP calls an "IMAPdir" style layout. IMAPdir lets me layout mailboxes in the filesystem like so: $HOME/ Maildir/ <---- users mail goes here Mail/ <---- IMAP root INBOX -> ../Maildir/ <---- (symlink) folder/ <---- some other mailbox in Maildir format folder.subfolder/ <---- '.' is the hierarchy separator folder.subfolder-2/ other-folder/ So IMAP clients subscribe to 'INBOX' and 'folder' and 'folder/subfolder' respectively. This gives me two features that I want: 1) The ability to easily access all my mail using a command line Maildir capable client such as nail, for when I'm connection over a super-slow SSH over GPRS connection. Also, I can actually see my folders (and their subfolders) without having to look for Maildir++ style names with 'ls -a' (e.g. Maildir/.subfolder/). 2) Mail folders are organized logically, unlike the standard Maildir++ layout where everything is a subfolder of 'INBOX', which strikes me as stupid. Is such a thing possible with Dovecot? Any help would be much appreciated. Thanks, -mato

6 22

[Dovecot] Plugin development
by Sebastjan Trepca 15 Aug '05

15 Aug '05

Hi, I have a few questions regarding copy and save_finish methods. How can I get a filename or processing mail from the parameters you get in that methods? How could I use the logger you use for dovecot inside my plugin? Thanks, Sebastjan

2 3

[Dovecot] migration from bincimap to dovecot (imaps)
by Andrea Riela 15 Aug '05

15 Aug '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks, I've installed dovecot 0.99.14 (last port on my freebsd system), and now I've to migrate from bincimap. My system uses qmail with vpopmail (uid/gid 89) and Maildir format. Well, now the authentication is ok, but when I try to connect to mailbox I receive an error like "IMAP command SELECT failed". My dovecot.conf: protocols = imaps imaps_listen = 192.168.17.10:993 ssl_disable = no ssl_cert_file = /var/qmail/certs/mail.nesys.it_cert.pem ssl_key_file = /var/qmail/certs/mail.nesys.it_key.pem log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log login_user = dovecot first_valid_uid = 89 last_valid_uid = 89 first_valid_gid = 89 last_valid_gid = 89 ... default_mail_env = maildir:/usr/local/vpopmail/domains/%d/%u/Maildir ... auth_userdb = vpopmail auth_passdb = vpopmail auth_user = root My Maildir directory: elessar# ls -la total 520 drwx------ 5 vpopmail vchkpw 512 Jul 11 12:40 . drwx------ 3 vpopmail vchkpw 512 Feb 7 12:10 .. - -rw------- 1 vpopmail vchkpw 23 Jul 11 10:43 .bincimap-subscribed - -rw------- 1 vpopmail vchkpw 307344 Jul 11 12:40 bincimap-cache - -rw------- 1 vpopmail vchkpw 75 Jul 11 12:39 bincimap-uidvalidity drwx------ 2 vpopmail vchkpw 190464 Jul 11 12:40 cur drwx------ 2 vpopmail vchkpw 512 Jul 11 12:39 new drwx------ 2 vpopmail vchkpw 512 Jul 11 12:18 tmp - -rw------- 1 vpopmail vchkpw 75 Jun 23 15:09 uidvalfilename I've forgotten something? Any advice will be appreciated :) Regards Andrea -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFC0k92MakHrsrHP9wRAgIrAJ9rkNALg2l/ZoJ5+YyChw5SLhXDtACgyA4T VHnceVpLb1VO9Nm5GeyLIN8= =SEHK -----END PGP SIGNATURE-----

2 5

[Dovecot] IMAP can't read inbox: istream_raw_mbox_get_body_size assertion failed
by Paul Schreiber 15 Aug '05

15 Aug '05

Yesterday, I upgraded my debian packages from 0.99.14 to 0.99.20050712-2. IMAP service has not been reliable since, and I was seeing crashes with one user. I tried deleting the user's .subscriptions and .imap folders, and forcing the client (Mac OS X's Mail.app) to redownload everything, but that resulted in an empty inbox. Here's what I have: # dpkg -l dovecot* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=====================-=====================-========================================================== ii dovecot 0.99.14-1 dummy package for upgrades to dovecot IMAP and POP3 server ii dovecot-common 0.99.20050712-2 secure mail server that supports mbox and maildir mailboxe ii dovecot-imapd 0.99.20050712-2 secure IMAP server that supports mbox and maildir mailboxe ii dovecot-pop3d 0.99.20050712-2 secure POP3 server that supports mbox and maildir mailboxe Here's what's in mail.log: Aug 13 15:09:10 sandbox dovecot: imap-login: Login: stan [70.48.39.107] Aug 13 15:09:10 sandbox dovecot: IMAP(stan): file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) Aug 13 15:09:10 sandbox dovecot: child 6748 (imap) killed with signal 6 I got a core dump. Here it is: # gdb /usr/lib/dovecot/imap core (gdb) bt full #0 0x4004d83b in raise () from /lib/tls/libc.so.6 #1 0x4004efa2 in abort () from /lib/tls/libc.so.6 #2 0x08096fcb in i_set_failure_file () #3 0x08096ac7 in i_panic () #4 0x0807070f in istream_raw_mbox_get_body_size () #5 0x0806d1de in mbox_sync_has_changed () #6 0x0806eb50 in mbox_sync () #7 0x0806f9e7 in mbox_storage_sync_init () #8 0x0805ead5 in imap_sync_nonselected () #9 0x08057508 in _cmd_select_full () #10 0x080576d1 in cmd_select () #11 0x08058bf6 in _client_input () #12 0x0809c0c1 in io_loop_handler_run () #13 0x0809b65b in io_loop_run () #14 0x080602aa in main () I downgraded to 0.99.14 and put in the old configuration file and it seems to be working now. What's going on? Paul

3 2

[Dovecot] Authentication based on client host
by Sebastjan Trepca 15 Aug '05

15 Aug '05

Hi, I am wondering if it's possible to authenticate users that come from specific IP differently then other users. I will be authenticating them by postgresql so something like this would be very useful: password_query = SELECT password from get_user('%username','%host') Is that possible? Can it be done any other way? Thanks, Sebastjan

2 2

[Dovecot] Upgraded from 0.99 to 1.0 stable on FC3
by Obantec Support 15 Aug '05

15 Aug '05

Hi I upgraded to 1.0 stable and saw this in the maillog UIDs broken with partial sync in mbox file /var/spool/mail/thejohns_brian i am using mbox files with default_mail_env = mbox:/var/spool/mail/%u Is this a problem that i should worry about? Mark

2 1

[Dovecot] hangs on dovecot test77, mutt
by Tzafrir Cohen 15 Aug '05

15 Aug '05

Hi My toy mail server runs dovecot. My client is mutt, which I use normally use a a remote screen session. I normally connect to imap locally: account-hook imap://localhost/ 'set tunnel="/usr/local/bin/imap-local"' After a long frustration from the new mail notification in 0.99, I have decided to bite the bullet and try the -test series. Ever since I have not had stable mutt sessions. Occasionally mutt hangs on the imap connection. Usually when openning a new mailbox. But sometimes even when closing an existing mailbox. Occasionally mutt will even crash (which is annoying, but certainly not a bug of dovecot). How do I debug this? -- Tzafrir Cohen | tzafrir(a)jbr.cohens.org.il | VIM is http://tzafrir.org.il | | a Mutt's tzafrir(a)cohens.org.il | | best ICQ# 16849755 | | friend

3 4

[Dovecot] dovecot update ?
by Brent Clark 14 Aug '05

14 Aug '05

Hi list Im currently run debian sarge / testing. I upgraded my dovecot this morning on my mail server this morning, and my dovecot stopped working for my mail users email clients. I told debconf to replace the dovecot.conf (Baring in mind I saved my conf file). The output I was getting was as so: ====================================================================== Aug 11 10:09:56 mail dovecot: Dovecot v1.0-test70 starting up Aug 11 10:10:21 mail dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Ilip=192.168.111.11^Irip=192.168.111.225^Iresp=AGdjaXZvbG FuaQBwYXNzd29yZA== Aug 11 10:10:21 mail dovecot: auth(default): client out: OK^I1^Iuser=gcivolani Aug 11 10:10:21 mail dovecot: auth(default): master in: REQUEST^I1^I2040^I1 Aug 11 10:10:21 mail dovecot: auth(default): master out: USER^I1^Igcivolani^Isystem_user=gcivolani^Iuid=1009^Igid=1009^Ihome=/home/gcivolani Aug 11 10:10:21 mail dovecot: imap-login: Login: gcivolani [192.168.111.225] Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): Effective uid=1009, gid=1009 Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): Namespace: type=public, prefix=Public/, sep=/, inbox=no, hidden=no, subscriptions=no Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): maildir autodetect: stat(/tmp/cur) failed: No such file or directory Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): mbox autodetect: data=/tmp Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): mbox autodetect: INBOX file: is a directory (/tmp) Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): mbox autodetect: has .imap/: stat(/tmp/.imap) failed: No such file or directory Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): mbox autodetect: has inbox: stat(/tmp/inbox) failed: No such file or directory Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): mbox autodetect: has mbox: stat(/tmp/mbox) failed: No such file or directory Aug 11 10:10:21 mail dovecot: IMAP(gcivolani): Failed to create storage for 'Public/' with data: /tmp Aug 11 10:10:21 mail dovecot: child 2052 (imap) returned error 89 Aug 11 10:10:21 mail dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Ilip=192.168.111.11^Irip=192.168.111.225^Iresp=AGdjaXZvbG FuaQBwYXNzd29yZA== Aug 11 10:10:21 mail dovecot: auth(default): client out: OK^I1^Iuser=gcivolani ======================================================================== I killed dovecot and restarted it with my old conf fike (I have attached my conf file). I then proceed by uninstalling this version of dovecot and reinstalled the previous version (still using the old conf file) On doing so I, started getting this error message in my syslog: ======================================================================== Aug 11 12:24:46 mail dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=IMAP^Ilip=192.168.111.11^Irip=192.168.111.225^Iresp=AGdjaXZvbG FuaQBwYXNzd29yZA== Aug 11 12:24:46 mail dovecot: auth(default): client out: OK^I1^Iuser=gcivolani Aug 11 12:24:46 mail dovecot: auth(default): master in: REQUEST^I115^I4435^I1 Aug 11 12:24:46 mail dovecot: auth(default): master out: USER^I115^Igcivolani^Isystem_user=gcivolani^Iuid=1009^Igid=1009^Ihome=/home/gcivolani Aug 11 12:24:46 mail dovecot: IMAP(gcivolani): Effective uid=1009, gid=1009 Aug 11 12:24:46 mail dovecot: IMAP(gcivolani): maildir: data=/home/gcivolani/Maildir Aug 11 12:24:46 mail dovecot: IMAP(gcivolani): maildir: root=/home/gcivolani/Maildir, index=/home/gcivolani/Maildir, control=, inbox= Aug 11 12:24:46 mail dovecot: imap-login: Login: gcivolani [192.168.111.225] ======================================================================== Although dovecot's port was up and running, my users still could not read or see there folders. It was only once I realised that when I copied and renamed my .subscription file to subscription, did it all work. Obviously the mistake was on myside but telling debconf to over write the conf file, but I find it a bit weid that when on killing dovecot and then restarting the with the old conf file, it still did not work. To be honest, im a bit lost as to how im going to rectify this, but I know that I want to upgrade my packages. If you can help in anyway, it would be most appreciated. Kind Regards and thanks in advance. Brent Clark ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap imaps # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = all:!low # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. login_greeting = Dovecot ready. ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). verbose_proctitle = yes # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_groups = # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. mail_debug = yes # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = #default_mail_env = maildir: #default_mail_env = maildir:%h/Maildir default_mail_env = maildir:/home/%u/Maildir # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. # 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 #} #namespace private { # separator = / # prefix = ~%u/mail/ # hidden = yes #} #namespace public { # separator = / # prefix = Public/ # location = /tmp #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. #pop3_uidl_format = %v.%u # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. #pop3_client_workarounds = } ## ## Authentication processes ## # Executable location #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds a cached # record is forced out of cache. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = yes # Even more verbose logging for debugging purposes. Shows for example SQL # queries. auth_debug = yes # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. #passdb { # args=/etc/passwd #} passdb pam { } userdb passwd { } #passdb pam { # Service name or * as parameter. * means the authenticating service name # is used, eg. pop3 or imap. #args = dovecot #args= /etc/passwd #} # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. # passdb passwd { # args= /etc/passwd # } # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. # passdb shadow { # args= /etc/shadow # } # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication #passdb checkpassword { # Path for checkpassword binary #args = #} # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } # passwd-like file with specified location #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template #userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # # args = uid=500 gid=500 home=/var/mail/%u # args = uid=500 gid=500 home=/home/%u mail=mbox:%h/mail nice=10 # #args = #} # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb passwd { # } # userdb pam { # } # socket listen { # master { # path = /var/run/dovecot/auth-master # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #}

3 2

[Dovecot] dovecot-auth: BUG: login gave a PID of existing connection
by m.durnthaler＠aon.at 14 Aug '05

14 Aug '05

hi, first of all i have to say that i´m new to dovecot and to mailinglist. i´m trying to setup my owen imap-server on fc3, but i have some trouble with dovecot. wenn i try to log in with telnet lovalhost 143 /var/log/maillog says: dovecot-auth: BUG: login gave a PID of existing connection. can someone please give me an hint or a link to solve this problem. yours, martin. ------------------------------------------- Versendet durch aonWebmail (webmail.aon.at)

3 3

[Dovecot] crash (assertion failed: (uidlist->lock_count == 1)
by Jakob Hirsch 14 Aug '05

14 Aug '05

Hi, with 1.0-test79 Aug 3 16:18:23 ymmv dovecot: IMAP(jh): file maildir-uidlist.c: line 536 (maildir_uidlist_rewrite): assertion failed: (uidlist->lock_count == 1) Aug 3 16:18:23 ymmv dovecot: child 10780 (imap) killed with signal 6 Any idea what that is? I did no special operation, just selected a mail to read with thunderbird (1.06). After restarting TB it worked.

2 3

[Dovecot] Problem with dovecot and system crashing
by Colin Kingsbury 14 Aug '05

14 Aug '05

Hi all, I am running dovecot on a linux server (FC3) in conjunction with Sendmail. My configuration is quite vanilla and I am having the following problem: occasionally (once every 3-10 days) the dovecot server will become unresponsive and attempting to access mail via pop3 will produce an error message on the client side. As best as I can tell, the dovecot process dies because if I restart it with /sbin/service dovecot restart I get [failed] on the stop and [ok] on the start. Now, here's the interesting part: within 5 minutes of this happening, the whole machine becomes completely unresponsive and requires a power-cycle to restart it. In between dovecot dying and the server going down, the other applications (apache, mysql) continue to run. Naturally, there are no messages in the syslog or the maillog and it is set to log all messages of info or higher. Any suggestions on how to attack this would be greatly appreciated. Best, -cwk.

3 4

Re: [Dovecot] Dovecot & SquirrelMail
by admin＠downend.org 14 Aug '05

14 Aug '05

aries:/etc/init.d# netstat -ltnp | grep ':143' aries:/etc/init.d# Right I found that cyrus was in the inet config uncommented and now I recieve outputs for dovecot :) As for SquirrelMail Config test: Warning: fsockopen(): unable to connect to localhost:143 in /var/www/mail/src/configtest.php on line 247 ERROR: Error connecting to IMAP server "localhost:143".Server error: (111) Connection refused Right so obiously I need to put dovecot in the inet conf any ideas what to put in? Thanks Mark Quoting Allen Parker <infowolfe(a)gmail.com>: > On 8/14/05, admin(a)downend.org <admin(a)downend.org> wrote: > > Hi I am back thought I should start a new mail... since i lost track of > > previous. Anyways, > > > > Does Dovecot require courier-authdaemon or whatever it is called to run? > > When running the following i recieve the following output should I kill > inet > > from 143 or not. > > > > aries:/etc/init.d# netstat -ltnp | grep ':143' > > tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN > > 24715/inetd > > more than likely, you should check in your distribution's inetd.conf > (under xinetd, normally /etc/xinetd.d/ is where configurations are > kept) and remove any reference to an imap server in there since you're > not launching dovecot from inetd... you should be seeing errors like > "unable to bind to port" in your syslog coming from dovecot.. (i > personally don't use inetd for launching things... but to each their > own) > > hope this helps > > > I am recieving the same response with the dovecot init file: > > > > aries:/etc/init.d# /etc/init.d/dovecot > > aries:/etc/init.d# /etc/init.d/dovecot > > > > aries:/etc/init.d# /etc/init.d/dovecot restart > > aries:/etc/init.d# > > > > > > There is no output possible because of inet? > > Any Help will be great! > > Thanks! > > > > > -- > ________________________________________ > To avoid being added to my spam filter: > 1. Utilize list replies unless otherwise requested. > 2. If you DO send me a personal email, use english. > 3. HTML isn't cute. It belongs on the web, not in my inbox. >

2 3

[Dovecot] Mailbox written with normalized headers
by Kenneth Porter 14 Aug '05

14 Aug '05

Over on the SpamAssassin list someone noted that some spam generators add leading spaces to the subject line, but it was impossible to detect this when using Dovecot for POP3 service. Some quick testing shows that dovecot-0.99.13-4.FC2 writes the mailbox back with the extra spaces in the header squeezed out. I think Dovecot should avoid reformatting headers any more than necessary to avoid interfering with spam detectors.

2 1

[Dovecot] Dovecot & SquirrelMail
by admin＠downend.org 14 Aug '05

14 Aug '05

Hi I am back thought I should start a new mail... since i lost track of previous. Anyways, Does Dovecot require courier-authdaemon or whatever it is called to run? When running the following i recieve the following output should I kill inet from 143 or not. aries:/etc/init.d# netstat -ltnp | grep ':143' tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 24715/inetd I am recieving the same response with the dovecot init file: aries:/etc/init.d# /etc/init.d/dovecot aries:/etc/init.d# /etc/init.d/dovecot aries:/etc/init.d# /etc/init.d/dovecot restart aries:/etc/init.d# There is no output possible because of inet? Any Help will be great! Thanks!

1 0

[Dovecot] debs for 1.0?
by Lorens 12 Aug '05

12 Aug '05

Hi, 0.99 is running nicely on my sarges, but I need pop3_uidl_format = %f for Courier compatibility. I can't find any debs more recent than test22 of over a year ago (those are at http://src.braincells.com/dovecot-test/) Even though google turns up http://hemma.tobbe.nu/debian/mini-dinstall/incoming/dovecot_1.0.test46-1_i3… searching for dovecot on packages.debian.org (any distribution or source) only yields 0.99.14 and 0.99.20050712. I know Jaldhar called for vounteers to take over, but I don't feel qualified... but I've managed to do away with all non-deb installations, so if I have to I'll make a .deb myself, is there maybe an already-written script to do that with dovecot? Thanks for suggestions.

4 6

[Dovecot] Dovecot & SquirrelMail HELP!
by admin＠downend.org 12 Aug '05

12 Aug '05

Hi All, I just installed Dovecot-Imap because uw-imap is awful... and Dovecot seems like a good Imap Server. Anyway I am using a Debian Server and apt-get install dovecot Seems to be working... I can telnet to port 143 and run /var/run/dovecot/login However SquirrelMail Config test cannot detect if, If anyone knows a guide to make Dovecot work with SquirrelMail please let me know... THis is quite urgent matter and need to fix this ASAP! Thanks! Mark Smith

6 12

Fwd: Re: [Dovecot] Dovecot & SquirrelMail HELP!
by admin＠downend.org 11 Aug '05

11 Aug '05

aries:/etc/postfix# netstat -ltnp | grep ':143' tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 22272/cyrmaster Well we are getting somewhere :) Just one now... Cyrus has been removed and purged off the system.. i found something about cyrus commented in postfix config, i have removed it, restarted and reloaded postfix still there aries:/etc/postfix# pidof cyrmaster 22272 aries:/etc/postfix# kill 22272 and it is still alive argg!!! Quoting Johannes Berg <johannes(a)sipsolutions.net>: > On Fri, 2005-08-12 at 02:03 +1000, admin(a)downend.org wrote: > > > > I have installed previous Imap Servers could that be it? > > > > How can I check if port 143 is being used by another imap server? > > > > > > netstat -tan|grep 143 > > > > I recieved the following output: > > > > aries:~# netstat -tan|grep 143 > > tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN > > There's something listening on 143. Run the following as root: > > netstat -ltnp | grep ':143' > > to see which process it is. > > johannes > ----- End forwarded message -----

1 0

[Dovecot] vpopmail directory permissions denied
by bclements＠io-networks.com 11 Aug '05

11 Aug '05

I've moved from a postfix setup to a qmail/vpopmail setup I've setup the dovecot.conf file for vpopmail That works fine, users can log in, but the problem is when they go to see their folders. Nothing is there. INBOX, Drafts, nothing. This is using any imap client, imp, evolution, outlook, outlook express This is using 99.14 and the latest vpopmail/qmail I looked at the directory structure and everything is there. The dovecot log file says something about permissions denied. I am using freebsd 4.10 Anybody have a clue on whats going on? -Brent ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 1

[Dovecot] Mail disappearing
by bclements＠io-networks.com 11 Aug '05

11 Aug '05

My users are complaining that their mail is dissappearing out of folders or if they go into a folder, the mail will be there one minute, the next it isn't. Anybody see this before...and if so..is there a fix? I'm running dovecot 99.11 Brent ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

11 25

[Dovecot] Need Help with Dovecot-Imapd and SquirrelMail
by admin＠downend.org 11 Aug '05

11 Aug '05

Hi All, I just installed Dovecot-Imap because uw-imap is awful... and Dovecot seems like a good Imap Server. Anyway I am usnig a Debian Server and apr-get install dovecot Seems to be working... I can telnet to it and /var/run/dovecot/login However SquirrelMail Config test cannot detect if, If anyone knows a guide to make Dovecot work with SQuirrelMail please let me know... THis is quite urgent. Thanks! Mark Smith

1 0

[Dovecot] Re: dovecot 0.99.20050712-1
by Jaldhar H. Vyas 11 Aug '05

11 Aug '05

On Sun, 24 Jul 2005, Nick Maynard wrote: > Yep - I too saw that posting on the dovecot list... sadly after I posted > to this one. I thought the best thing to do was probably to wait > quietly, but I suppose giving him a friendly poke can't do any harm > (Hello, Jaldhar!). > > Thanks all, > Apologies for the delay but I have now prepared a backport. The problem is I don't know how to upload it to backports.org but while I get that sorted out you can get the files from http://www.braincells.com/backports/ (It's not aptable, you'll have to download the packages and manually install them with dpkg -i) -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

1 0

[Dovecot] Starting Dovecot Imap [FAILED]
by hettige＠mfac.kln.ac.lk 10 Aug '05

10 Aug '05

I want to configure dovecot in FC 4. Set the "protocols = Imap Imaps Pop3 Pop3s" in dovecot.conf Test the service by giving "service dovecot start" command and finally I got "Starting Dovecot Imap [FAILED]" Can somebody explain WHY? Saman ---------------------------------------------------

4 3

[Dovecot] new inotify patch
by Johannes Berg 10 Aug '05

10 Aug '05

Hi, As discussed on IRC, the attached patch changes the notification API and fixes inotify. johannes

1 0

[Dovecot] Strange index problem
by Andrew Hutchings 09 Aug '05

09 Aug '05

Hi, OK, I have 2 servers accessing the same mailboxes via NFS (indexes on each servers local HDD). They are on a round robin connection system. I have had a mailbox (customer using Eudora for Mac and storing mail for a certain amount of days) that on one server says there are 281 messages and the other says there are 194 messages. Of course this leads to re-downloading the difference. The mails that are invisible to the second machine are not sequential, they are at random places in the mailbox. Deleting the indexed on the machine that is inconsistent seems to fix it. We seem to get this problem about once a week or 2 over 6000 mailboxes. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ Linux CDs and DVDs - http://www.linuxiso.co.uk/ Random quote 147: "The Internet? We are not interested in it" - Bill Gates, 1993

1 0

[Dovecot] Re: Problem with dovecot and system crashing
by Paul Vatta 09 Aug '05

09 Aug '05

We have experienced similar problems with version 0.99.11 that comes with Redhat Enterprise Linux 4. If I'm not wrong, it appears to be related to the number of file descripters available to the dovecot user. To abate the situation, we stop the service, kill any remaining dovecot processes (some hang around), and then restart dovecot. Sometimes it appears that the limit of connection processes isn't honoured (as defined in the conf file) so the number can spiral out of control. I hope this helps in the absense of a workaround. Let me know if there is an obvious configuration setting to remedy this.

1 0

[Dovecot] out of disk space notification
by David Weilers 09 Aug '05

09 Aug '05

Hi Dovecot readers, My server (squirrelmail) provides me with the following error-message when selecting a mailbox (trash): ERROR : Could not complete request. Query: SELECT "Trash" Reason Given: Out of disk space The user is not over quota but for some reason dovecot still thinks this to be true. Can anyone give me a hint for finding a solution for this problem. I have installed: dovecot-0.99.10.9-2.0.rh9.dag Thanks in advance.. David

3 4

[Dovecot] corrupted binary tree and index data files
by Gary Sandine 09 Aug '05

09 Aug '05

Hi. I am using dovecot 0.99.14 as an imaps server with mbox folders (in an NFS-mounted directory) in x86 Debian testing. I have searched the archives of this list and have seen other evidence of the problems I am having. I get lots of log messages like these: Jul 29 07:47:09 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/.imap/INBOX/.imap.index.tree: UID to be inserted isn't higher than existing (290 <= 291) ... Jul 29 07:47:13 HOST imap(USER): Corrupted index data file /home/USER/IMAP_MBOX_DIR/.imap/INBOX/.imap.index.data: Field 1 size points outside file (14648 / 14656) for record 290 This is from the midst of a herd of messages starting at 82 <= 144: Jul 28 08:01:31 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (82 <= 144) ... Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (143 <= 144) Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (144 <= 144) Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (92 <= 154) Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (93 <= 154) ... Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (101 <= 154) Jul 28 08:01:34 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/SUBFOLDER_DIR/.imap/MBOX2/.imap.index.tree: UID to be inserted isn't higher than existing (79 <= 80) Jul 28 08:01:34 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/SUBFOLDER_DIR/.imap/MBOX2/.imap.index.tree: UID to be inserted isn't higher than existing (80 <= 80) Jul 28 08:11:27 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (102 <= 164) ... I don't know how to reproduce this. It happens (repeatedly) for some users and seems to be independent of the number of mboxes, mbox sizes, mail client, .... I have tried deleting .imap directories, and this helps for a while, but the problem always comes back for a few users. The proposed solution for "Corrupted binary tree" or "Corrupted index data file" log messages is usually to change to a different version of dovecot. I will try that, but want to check in here first in case something obvious is happening that I don't understand. Thanks, -- Gary Sandine <gars(a)lanl.gov>

2 2

[Dovecot] Header problems
by Andrew Hutchings 08 Aug '05

08 Aug '05

Hi, I don't know if this has been covered or not as I have been out of action most of the last few weeks getting married and stuff. My query / slight problem is when I re-install an IMAP client or change client all mails that have been read so far show an empty header with the date set back to 1970 but the mails are fully readable. New mails that weren't read in a previous client show fine. Could this be something do to with me using fcntl? I am using the latest test version with Maildir boxes. I haven't got any diagnostic data of this yet, I want to make sure this isn't a common problem first. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ Linux CDs and DVDs - http://www.linuxiso.co.uk/ Random quote 114: "Both the PC industry and consumers alike would be better off with some modest limits on Microsoft's zeal." - JOHN BLACKFORD, Editor, Computer Shopper

2 2

[Dovecot] directory names - have to begin with a dot?
by Tom Alsberg 07 Aug '05

07 Aug '05

Hi there... Two questions: (1) Is there an easy way to have Dovecot recognize subdirectories that do not begin with a dot as sub-hierarchies? (2) Is there a way to have the root folder map to a certain other mbox/maildir? I want a setup like this: / -> $HOME/mbox /INBOX -> /var/spool/<username> /folder -> $HOME/mail/folder /folder/foo -> $HOME/mail/folder/foo /folder/bar -> $HOME/mail/folder/bar /folder/foo/bar -> $HOME/mail/folder/foo/bar (Assuming / as a hierarchy separator - that is, /folder/foo/bar is the IMAP folder 'bar' inside 'foo' inside 'folder') The idea is something resembling and compatible with the default behaviour of elm/pine/mutt/KMail/evolution, so a user can use both those locally and whatever IMAP client remotely in a similiar organisation... I would love some further documentation regarding the working of Dovecot's folder lookup and how to achieve different IMAP folder organisations with dovecot. I have not yet looked deep enough into the sources to understand where most of the flexibiliy stems. Cheers, -- Tom P.S. anyone checked my trivial patch for settings parsing after closing braces? -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

2 5

[Dovecot] auth_passdb using MySQL fails at starup
by Josh Joslyn 07 Aug '05

07 Aug '05

I've got dovecot v0.99.14, MySql 4.1.11 and postfix on fedora core 4. when using uxix socket I get: dovecot-auth: MySQL: Can't connect to database vmail: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13) when using tcp socket I get: dovecot-auth: MySQL: Can't connect to database vmail: Can't create TCP/IP socket (13) * the mysql.sock exists * I can connect to mysql -u vmail and select on the table mailbox * I can run mysqladmin successfully using the port or the socket As you can see below I modified the password query to be very simple. I am surprised to get the error on startup since the password query should not be executed at this point. The problem is not MySql as I am able to query all day long the the vmail database table called mailbox with the vmail user. Not sure what else I can check Dovecot error message lacks the reason it can not connect - unless the (13) means anything to anybody??? Anybody have any ideas??? dovecot.conf : . auth_assdb = mysql /etc/dovecot-mysql.conf dovecot-mysql.conf : db_host = localhost db_unix_socket = /var/lib/mysql/mysql.sock #db_port = 3306 db = vmail db_user = vmail db_passdb = temp password_query = SELECT 'test' as password from mailbox vmail.sql: create database vmail; use vmail; grant insert,select,update,delete on vmail.* to 'vmail'@'localhost' identified by 'temp'; CREATE TABLE mailbox ( user varchar(20) not null, domain varchar(30) not null, password varchar(20) not null, status char, PRIMARY KEY (user,domain) ); insert into mailbox values('someone', 'domain.org', 'secret', 'Y');

2 1

[Dovecot] Copying keyworded messages kills IMAP process(test78)
by Sebastjan Trepca 07 Aug '05

07 Aug '05

Hi, when I try to copy/move messages with keywords, IMAP process dies: dovecot: Jul 24 23:49:47 Info: imap-login: Login: user=<seba>, method=PLAIN, rip=192.168.0.192 <http://192.168.0.192>, lip=192.168.0.188<http://192.168.0.188> dovecot: Jul 24 23:49:47 Info: IMAP(seba): Effective uid=1000, gid=100 dovecot: Jul 24 23:49:47 Info: IMAP(seba): maildir: data=/home/seba/Maildir dovecot: Jul 24 23:49:47 Info: IMAP(seba): maildir: root=/home/seba/Maildir, index=/home/seba/Maildir, control=, inbox= dovecot: Jul 24 23:49:53 Error: child 22903 (imap) killed with signal 11 I'm using dovecot-test78 on Suse 9.2 with hardlink support. Regards, Sebastjan

2 1

[Dovecot] Dieing?
by Matt Juszczak 07 Aug '05

07 Aug '05

Our dovecot process died out of no where today, with no sign of reasons why. I'm running a beta from a few weeks ago of 1.0 ... are there any security vulns I should know about that might have caused this crash (someone trying something?) Thanks, Regards, Matt

2 1

[Dovecot] How is the correct "auth" method selected in 1.0-stable?
by Ben Beuchler 07 Aug '05

07 Aug '05

In the example config for 1.0-stable, I see several "auth <blah> {}" blocks. The only one uncommented is the "auth default{}" block. How does dovecot decide which one to use? If I want it to use LDAP, should I just modify the "userdb" and "passdb" entries in the "auth default" block? Or should I be using the "auth ldap" block and somehow telling dovecot to use it? Thanks! -Ben

2 1

[Dovecot] POP and IMAP at the same time
by Marc Perkel 07 Aug '05

07 Aug '05

If a user was accessing their mailbox with POP and another process accessed it with IMAP - would that create an error? Trying to track down an unusual bug.

2 1

[Dovecot] error sha1
by Alex Romijn 07 Aug '05

07 Aug '05

Hello, I have a problem. When I do 'make' it gives the following error: gcc -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o dovecot-auth auth-cache.o au th-client-connection.o auth-master-connection.o auth-module.o db-ldap.o db-sql.o db-passwd-file.o main.o mech.o mech-anonymous.o mech-plain.o mech-login.o mech- cram-md5.o mech-digest-md5.o mech-ntlm.o mech-rpa.o mech-apop.o passdb.o passdb- bsdauth.o passdb-cache.o passdb-ldap.o passdb-passwd.o passdb-passwd-file.o pass db-pam.o passdb-checkpassword.o passdb-shadow.o passdb-vpopmail.o passdb-sql.o u serdb.o userdb-ldap.o userdb-passwd.o userdb-passwd-file.o userdb-static.o userd b-vpopmail.o userdb-sql.o -Wl,--export-dynamic libpassword.a ../lib-settings/li bsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -L/usr/lib /mysql /usr/lib/mysql/libmysqlclient.a -lcrypt -lnsl -lm -lc -lnss_files -lnss_d ns -lresolv -lz -ldl /usr/lib/mysql/libmysqlclient.a(sha1.o)(.text+0x60): In function `sha1_result': : multiple definition of `sha1_result' ../lib/liblib.a(sha1.o)(.text+0x7f4):/usr/local/src/dovecot/dovecot-1.0-stable/s rc/lib/sha1.c:233: first defined here /usr/bin/ld: Warning: size of symbol `sha1_result' changed from 158 in ../lib/li blib.a(sha1.o) to 126 in ../lib/liblib.a(sha1.o) collect2: ld returned 1 exit status make[3]: *** [dovecot-auth] Error 1 make[3]: Leaving directory `/usr/local/src/dovecot/dovecot-1.0-stable/src/auth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot/dovecot-1.0-stable/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot/dovecot-1.0-stable' make: *** [all] Error 2 What is wrong? And how can I fix this? thanks, Alex

2 1

[Dovecot] what does it mean first_uid
by G�khan Alkan 07 Aug '05

07 Aug '05

i installed qmail + vpopmail + dovecot.i installed dovecot without problems.but i run telnet localhost 143 x login user password it seems to error about first_uid.and i change first_uid vpopmail_uid (89) its ok.but i dont understand first_uid.and sholud i change last_uid , first_gid ,last_guid . do you recommend it thanks everynbody ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

2 1

[Dovecot] mechanisms?
by Marc Perkel 07 Aug '05

07 Aug '05

ok - if I'm using a password/shadow file arrangement, what auth mechanisms besides "plain" should I turn on? -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 1

[Dovecot] Dovecot 1.0-test77 endless loop hang
by Todd Vierling 07 Aug '05

07 Aug '05

Client: Bynari Insight Connector 3.0.5. (http://www.bynari.net/) This is an IMAP-based plugin for Outlook that can also store Outlook collaboration objects (calendar, tasks, notes, etc.) in IMAP messages on the server side. It does not require special server extensions, and it was actually (mostly) working with 1.0-stable. Below is a rawlog dump showing what is going back and forth. After fetching the second message, the imap process pegs the CPU and sends no more data. This also triggers a bug in the Bynari product, for which I've entered a bug report too. (mmm, mutual bug triggering :) The Connector opens two simultaneous IMAP connections: one for subscription control and one for data transfer. So I've noted the log dumps. I've also checked, and Pine is having no troubles reading any of the messages in the INBOX folder. The last BODYSTRUCTURE line (with a bunch of NILs) makes me wonder if there's something wrong with the indexing. Or perhaps something is not carrying forward the requested FETCH data to the second and later messages in a multi-message fetch? I can go further to check a gdb trace or something similar, but I wanted to mention this problem here first in case it's obvious where this endless loop may be happening. Non-default config variables (all work fine with Pine): default_mail_env = maildir:%h/.maildir protocol imap { ... imap_client_workarounds = delay-newmail outlook-idle ... } ===== subscription control connection (IN) 00000002 CAPABILITY 00000003 NAMESPACE 00000004 Subscribe INBOX 00000005 LSUB "" %* 00000006 LSUB "" %* ===== subscription control connection (OUT) * OK [RAWLOG TIMESTAMP] 2005-08-01 16:49:30 * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS 00000002 OK Capability completed. * NAMESPACE (("" "/")) NIL NIL 00000003 OK Namespace completed. 00000004 OK Subscribe completed. * LSUB () "/" "INBOX" * LSUB () "/" "INBOX/Outbox" * LSUB () "/" "INBOX/Sent Items" * LSUB () "/" "INBOX/Deleted Items" * LSUB () "/" "INBOX/Calendar" * LSUB () "/" "INBOX/Contacts" * LSUB () "/" "INBOX/Journal" * LSUB () "/" "INBOX/Notes" * LSUB () "/" "INBOX/Tasks" * LSUB () "/" "INBOX/Drafts" * LSUB () "/" "INBOX/Junk E-mail" 00000005 OK Lsub completed. * LSUB () "/" "INBOX" * LSUB () "/" "INBOX/Outbox" * LSUB () "/" "INBOX/Sent Items" * LSUB () "/" "INBOX/Deleted Items" * LSUB () "/" "INBOX/Calendar" * LSUB () "/" "INBOX/Contacts" * LSUB () "/" "INBOX/Journal" * LSUB () "/" "INBOX/Notes" * LSUB () "/" "INBOX/Tasks" * LSUB () "/" "INBOX/Drafts" * LSUB () "/" "INBOX/Junk E-mail" 00000006 OK Lsub completed. ===== data connection (IN) 00000002 CAPABILITY 00000003 NAMESPACE 00000004 Subscribe INBOX 00000005 NOOP 00000006 SELECT INBOX/Contacts 00000007 UID FETCH 1:* FLAGS 00000008 NOOP 00000009 SEARCH HEADER X-Bynari-Folder-Class "" 0000000a FETCH 1 (UID ENVELOPE BODY.PEEK[HEADER.FIELDS (Date X-Priority X-Bynari-Folder-Class X-PR-CONTAINER-CLASS X-Message-Flag Received)] INTERNALDATE RFC822.SIZE FLAGS) 0000000b NOOP 0000000c SELECT INBOX 0000000d UID FETCH 1:* FLAGS 0000000e NOOP 0000000f SEARCH HEADER X-Bynari-Folder-Class "" 00000010 FETCH 1:51 (UID ENVELOPE BODY.PEEK[HEADER.FIELDS (Date X-Priority X-Bynari-Folder-Class X-PR-CONTAINER-CLASS X-Message-Flag Received)] BODYSTRUCTURE INTERNALDATE RFC822.SIZE FLAGS) ===== data connection (OUT) * OK [RAWLOG TIMESTAMP] 2005-08-01 16:49:32 * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS 00000002 OK Capability completed. * NAMESPACE (("" "/")) NIL NIL 00000003 OK Namespace completed. 00000004 OK Subscribe completed. 00000005 OK NOOP completed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 0 RECENT * OK [UIDVALIDITY 1122927796] UIDs valid * OK [UIDNEXT 2] Predicted next UID 00000006 OK [READ-WRITE] Select completed. * 1 FETCH (FLAGS (\Seen) UID 1) 00000007 OK Fetch completed. 00000008 OK NOOP completed. * SEARCH 1 00000009 OK Search completed. * 1 FETCH (UID 1 INTERNALDATE "01-Aug-2005 16:23:17 -0400" RFC822.SIZE 319 FLAGS (\Seen) ENVELOPE ("Mon, 1 Aug 2005 16:23:17 -0400 (Eastern Daylight Time)" "Hidden synchronization message" ((NIL NIL "Bynari" "MISSING_DOMAIN")) ((NIL NIL "Bynari" "MISSING_DOMAIN")) ((NIL NIL "Bynari" "MISSING_DOMAIN")) NIL NIL NIL NIL NIL) BODY[HEADER.FIELDS (DATE X-PRIORITY X-BYNARI-FOLDER-CLASS X-PR-CONTAINER-CLASS X-MESSAGE-FLAG RECEIVED)] {135} Date: Mon, 1 Aug 2005 16:23:17 -0400 (Eastern Daylight Time) X-Bynari-Folder-Class: IPF.Contact X-PR-CONTAINER-CLASS: IPF.Contact ) 0000000a OK Fetch completed. 0000000b OK NOOP completed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 522 EXISTS * 0 RECENT * OK [UNSEEN 111] First unseen. * OK [UIDVALIDITY 1122905893] UIDs valid * OK [UIDNEXT 577] Predicted next UID 0000000c OK [READ-WRITE] Select completed. * 1 FETCH (FLAGS (\Seen) UID 1) * 2 FETCH (FLAGS (\Seen) UID 2) * 3 FETCH (FLAGS (\Seen) UID 3) * 4 FETCH (FLAGS (\Seen) UID 4) * 5 FETCH (FLAGS (\Seen) UID 5) * 6 FETCH (FLAGS (\Seen) UID 6) * 7 FETCH (FLAGS (\Answered \Seen) UID 7) * 8 FETCH (FLAGS (\Seen) UID 8) * 9 FETCH (FLAGS (\Answered \Seen) UID 9) * 10 FETCH (FLAGS (\Answered \Seen) UID 10) * 11 FETCH (FLAGS (\Seen) UID 11) * 12 FETCH (FLAGS (\Seen) UID 12) * 13 FETCH (FLAGS (\Seen) UID 13) * 14 FETCH (FLAGS (\Seen) UID 14) * 15 FETCH (FLAGS (\Seen) UID 15) * 16 FETCH (FLAGS (\Seen) UID 16) * 17 FETCH (FLAGS (\Seen) UID 17) * 18 FETCH (FLAGS (\Seen) UID 18) * 19 FETCH (FLAGS (\Seen) UID 19) * 20 FETCH (FLAGS (\Seen) UID 20) * 21 FETCH (FLAGS (\Seen) UID 21) * 22 FETCH (FLAGS (\Seen) UID 22) * 23 FETCH (FLAGS (\Seen) UID 23) * 24 FETCH (FLAGS (\Seen) UID 24) * 25 FETCH (FLAGS (\Seen) UID 25) * 26 FETCH (FLAGS (\Seen) UID 26) * 27 FETCH (FLAGS (\Answered \Seen) UID 27) * 28 FETCH (FLAGS (\Seen) UID 28) * 29 FETCH (FLAGS (\Seen) UID 29) * 30 FETCH (FLAGS (\Seen) UID 30) * 31 FETCH (FLAGS (\Seen) UID 31) * 32 FETCH (FLAGS (\Seen) UID 32) * 33 FETCH (FLAGS (\Seen) UID 33) * 34 FETCH (FLAGS (\Seen) UID 34) * 35 FETCH (FLAGS (\Seen) UID 35) * 36 FETCH (FLAGS (\Seen) UID 36) * 37 FETCH (FLAGS (\Seen) UID 37) * 38 FETCH (FLAGS (\Seen) UID 38) * 39 FETCH (FLAGS (\Seen) UID 39) * 40 FETCH (FLAGS (\Seen) UID 40) * 41 FETCH (FLAGS (\Seen) UID 41) * 42 FETCH (FLAGS (\Seen) UID 42) * 43 FETCH (FLAGS (\Seen) UID 43) * 44 FETCH (FLAGS (\Seen) UID 44) * 45 FETCH (FLAGS (\Seen) UID 45) * 46 FETCH (FLAGS (\Seen) UID 46) * 47 FETCH (FLAGS (\Seen) UID 47) * 48 FETCH (FLAGS (\Seen) UID 48) * 49 FETCH (FLAGS (\Seen) UID 49) * 50 FETCH (FLAGS (\Seen) UID 50) * 51 FETCH (FLAGS (\Seen) UID 51) * 52 FETCH (FLAGS (\Seen) UID 52) * 53 FETCH (FLAGS (\Seen) UID 53) * 54 FETCH (FLAGS (\Seen) UID 54) * 55 FETCH (FLAGS (\Seen) UID 55) * 56 FETCH (FLAGS (\Seen) UID 56) * 57 FETCH (FLAGS (\Seen) UID 57) * 58 FETCH (FLAGS (\Answered \Seen) UID 58) * 59 FETCH (FLAGS (\Answered \Seen) UID 59) * 60 FETCH (FLAGS (\Seen) UID 60) * 61 FETCH (FLAGS (\Seen) UID 61) * 62 FETCH (FLAGS (\Seen) UID 62) * 63 FETCH (FLAGS (\Seen) UID 63) * 64 FETCH (FLAGS (\Seen) UID 64) * 65 FETCH (FLAGS (\Seen) UID 65) * 66 FETCH (FLAGS (\Seen) UID 66) * 67 FETCH (FLAGS (\Seen) UID 67) * 68 FETCH (FLAGS (\Seen) UID 68) * 69 FETCH (FLAGS (\Seen) UID 69) * 70 FETCH (FLAGS (\Seen) UID 70) * 71 FETCH (FLAGS (\Seen) UID 71) * 72 FETCH (FLAGS (\Seen) UID 72) * 73 FETCH (FLAGS (\Seen) UID 73) * 74 FETCH (FLAGS (\Seen) UID 74) * 75 FETCH (FLAGS (\Seen) UID 75) * 76 FETCH (FLAGS (\Seen) UID 76) * 77 FETCH (FLAGS (\Seen) UID 77) * 78 FETCH (FLAGS (\Seen) UID 78) * 79 FETCH (FLAGS (\Seen) UID 79) * 80 FETCH (FLAGS (\Seen) UID 80) * 81 FETCH (FLAGS (\Seen) UID 81) * 82 FETCH (FLAGS (\Seen) UID 82) * 83 FETCH (FLAGS (\Seen) UID 83) * 84 FETCH (FLAGS (\Seen) UID 84) * 85 FETCH (FLAGS (\Seen) UID 85) * 86 FETCH (FLAGS (\Seen) UID 86) * 87 FETCH (FLAGS (\Seen) UID 87) * 88 FETCH (FLAGS (\Seen) UID 88) * 89 FETCH (FLAGS (\Seen) UID 89) * 90 FETCH (FLAGS (\Seen) UID 90) * 91 FETCH (FLAGS (\Seen) UID 91) * 92 FETCH (FLAGS (\Seen) UID 92) * 93 FETCH (FLAGS (\Seen) UID 93) * 94 FETCH (FLAGS (\Seen) UID 94) * 95 FETCH (FLAGS (\Seen) UID 95) * 96 FETCH (FLAGS (\Seen) UID 96) * 97 FETCH (FLAGS (\Seen) UID 97) * 98 FETCH (FLAGS (\Seen) UID 98) * 99 FETCH (FLAGS (\Seen) UID 99) * 100 FETCH (FLAGS (\Seen) UID 100) * 101 FETCH (FLAGS (\Answered \Seen) UID 101) * 102 FETCH (FLAGS (\Seen) UID 102) * 103 FETCH (FLAGS (\Seen) UID 103) * 104 FETCH (FLAGS (\Seen) UID 104) * 105 FETCH (FLAGS (\Seen) UID 105) * 106 FETCH (FLAGS (\Seen) UID 106) * 107 FETCH (FLAGS (\Seen) UID 107) * 108 FETCH (FLAGS (\Seen) UID 108) * 109 FETCH (FLAGS (\Seen) UID 109) * 110 FETCH (FLAGS (\Seen) UID 110) * 111 FETCH (FLAGS () UID 111) * 112 FETCH (FLAGS () UID 112) * 113 FETCH (FLAGS () UID 113) * 114 FETCH (FLAGS () UID 114) * 115 FETCH (FLAGS () UID 115) * 116 FETCH (FLAGS () UID 116) * 117 FETCH (FLAGS (\Seen) UID 117) * 118 FETCH (FLAGS () UID 118) * 119 FETCH (FLAGS (\Seen) UID 119) * 120 FETCH (FLAGS (\Answered \Seen) UID 120) * 121 FETCH (FLAGS (\Seen) UID 121) * 122 FETCH (FLAGS (\Seen) UID 122) * 123 FETCH (FLAGS (\Seen) UID 123) * 124 FETCH (FLAGS () UID 124) * 125 FETCH (FLAGS (\Seen) UID 125) * 126 FETCH (FLAGS (\Seen) UID 126) * 127 FETCH (FLAGS (\Seen) UID 127) * 128 FETCH (FLAGS (\Seen) UID 128) * 129 FETCH (FLAGS (\Seen) UID 129) * 130 FETCH (FLAGS (\Seen) UID 130) * 131 FETCH (FLAGS (\Seen) UID 131) * 132 FETCH (FLAGS (\Seen) UID 132) * 133 FETCH (FLAGS (\Seen) UID 133) * 134 FETCH (FLAGS (\Seen) UID 134) * 135 FETCH (FLAGS (\Seen) UID 135) * 136 FETCH (FLAGS (\Seen) UID 136) * 137 FETCH (FLAGS (\Seen) UID 137) * 138 FETCH (FLAGS () UID 138) * 139 FETCH (FLAGS () UID 139) * 140 FETCH (FLAGS () UID 140) * 141 FETCH (FLAGS () UID 141) * 142 FETCH (FLAGS (\Seen) UID 142) * 143 FETCH (FLAGS (\Seen) UID 143) * 144 FETCH (FLAGS (\Answered \Seen) UID 144) * 145 FETCH (FLAGS () UID 145) * 146 FETCH (FLAGS () UID 146) * 147 FETCH (FLAGS (\Seen) UID 147) * 148 FETCH (FLAGS () UID 148) * 149 FETCH (FLAGS (\Seen) UID 149) * 150 FETCH (FLAGS () UID 150) * 151 FETCH (FLAGS (\Seen) UID 151) * 152 FETCH (FLAGS (\Seen) UID 152) * 153 FETCH (FLAGS () UID 153) * 154 FETCH (FLAGS () UID 154) * 155 FETCH (FLAGS () UID 155) * 156 FETCH (FLAGS () UID 156) * 157 FETCH (FLAGS (\Flagged) UID 157) * 158 FETCH (FLAGS () UID 158) * 159 FETCH (FLAGS () UID 159) * 160 FETCH (FLAGS () UID 160) * 161 FETCH (FLAGS () UID 161) * 162 FETCH (FLAGS () UID 162) * 163 FETCH (FLAGS () UID 163) * 164 FETCH (FLAGS (\Seen) UID 164) * 165 FETCH (FLAGS () UID 165) * 166 FETCH (FLAGS () UID 166) * 167 FETCH (FLAGS () UID 167) * 168 FETCH (FLAGS () UID 168) * 169 FETCH (FLAGS () UID 169) * 170 FETCH (FLAGS () UID 170) * 171 FETCH (FLAGS () UID 171) * 172 FETCH (FLAGS () UID 172) * 173 FETCH (FLAGS () UID 173) * 174 FETCH (FLAGS (\Seen) UID 174) * 175 FETCH (FLAGS () UID 175) * 176 FETCH (FLAGS () UID 176) * 177 FETCH (FLAGS (\Seen) UID 177) * 178 FETCH (FLAGS () UID 178) * 179 FETCH (FLAGS () UID 179) * 180 FETCH (FLAGS () UID 180) * 181 FETCH (FLAGS () UID 181) * 182 FETCH (FLAGS (\Seen) UID 182) * 183 FETCH (FLAGS (\Seen) UID 183) * 184 FETCH (FLAGS (\Seen) UID 184) * 185 FETCH (FLAGS (\Seen) UID 185) * 186 FETCH (FLAGS (\Seen) UID 186) * 187 FETCH (FLAGS () UID 187) * 188 FETCH (FLAGS () UID 188) * 189 FETCH (FLAGS () UID 189) * 190 FETCH (FLAGS () UID 190) * 191 FETCH (FLAGS (\Seen) UID 191) * 192 FETCH (FLAGS (\Seen) UID 192) * 193 FETCH (FLAGS () UID 193) * 194 FETCH (FLAGS () UID 194) * 195 FETCH (FLAGS () UID 195) * 196 FETCH (FLAGS (\Seen) UID 196) * 197 FETCH (FLAGS (\Seen) UID 197) * 198 FETCH (FLAGS () UID 198) * 199 FETCH (FLAGS () UID 199) * 200 FETCH (FLAGS () UID 200) * 201 FETCH (FLAGS (\Seen) UID 201) * 202 FETCH (FLAGS (\Seen) UID 202) * 203 FETCH (FLAGS () UID 203) * 204 FETCH (FLAGS (\Answered \Seen) UID 204) * 205 FETCH (FLAGS (\Seen) UID 205) * 206 FETCH (FLAGS () UID 206) * 207 FETCH (FLAGS (\Seen) UID 207) * 208 FETCH (FLAGS (\Seen) UID 208) * 209 FETCH (FLAGS (\Answered \Seen) UID 209) * 210 FETCH (FLAGS (\Seen) UID 210) * 211 FETCH (FLAGS (\Answered \Seen) UID 211) * 212 FETCH (FLAGS (\Seen) UID 212) * 213 FETCH (FLAGS (\Seen) UID 213) * 214 FETCH (FLAGS () UID 214) * 215 FETCH (FLAGS (\Answered \Seen) UID 215) * 216 FETCH (FLAGS (\Seen) UID 216) * 217 FETCH (FLAGS () UID 217) * 218 FETCH (FLAGS (\Answered \Seen) UID 218) * 219 FETCH (FLAGS () UID 219) * 220 FETCH (FLAGS () UID 220) * 221 FETCH (FLAGS (\Seen) UID 221) * 222 FETCH (FLAGS () UID 222) * 223 FETCH (FLAGS (\Seen) UID 223) * 224 FETCH (FLAGS (\Answered \Seen) UID 224) * 225 FETCH (FLAGS (\Seen) UID 225) * 226 FETCH (FLAGS (\Seen) UID 226) * 227 FETCH (FLAGS (\Seen) UID 227) * 228 FETCH (FLAGS () UID 228) * 229 FETCH (FLAGS (\Seen) UID 229) * 230 FETCH (FLAGS (\Seen) UID 230) * 231 FETCH (FLAGS () UID 231) * 232 FETCH (FLAGS () UID 232) * 233 FETCH (FLAGS () UID 233) * 234 FETCH (FLAGS (\Seen) UID 234) * 235 FETCH (FLAGS (\Seen) UID 235) * 236 FETCH (FLAGS (\Seen) UID 236) * 237 FETCH (FLAGS (\Seen) UID 237) * 238 FETCH (FLAGS (\Seen) UID 238) * 239 FETCH (FLAGS () UID 239) * 240 FETCH (FLAGS () UID 240) * 241 FETCH (FLAGS () UID 241) * 242 FETCH (FLAGS () UID 242) * 243 FETCH (FLAGS () UID 243) * 244 FETCH (FLAGS (\Seen) UID 244) * 245 FETCH (FLAGS (\Seen) UID 245) * 246 FETCH (FLAGS () UID 246) * 247 FETCH (FLAGS () UID 247) * 248 FETCH (FLAGS () UID 248) * 249 FETCH (FLAGS () UID 249) * 250 FETCH (FLAGS (\Seen) UID 250) * 251 FETCH (FLAGS (\Seen) UID 251) * 252 FETCH (FLAGS () UID 252) * 253 FETCH (FLAGS (\Seen) UID 253) * 254 FETCH (FLAGS () UID 254) * 255 FETCH (FLAGS () UID 255) * 256 FETCH (FLAGS (\Seen) UID 256) * 257 FETCH (FLAGS () UID 257) * 258 FETCH (FLAGS () UID 258) * 259 FETCH (FLAGS (\Seen) UID 259) * 260 FETCH (FLAGS (\Flagged \Seen) UID 260) * 261 FETCH (FLAGS () UID 261) * 262 FETCH (FLAGS () UID 262) * 263 FETCH (FLAGS () UID 263) * 264 FETCH (FLAGS () UID 264) * 265 FETCH (FLAGS () UID 265) * 266 FETCH (FLAGS (\Seen) UID 266) * 267 FETCH (FLAGS () UID 267) * 268 FETCH (FLAGS () UID 268) * 269 FETCH (FLAGS () UID 269) * 270 FETCH (FLAGS () UID 270) * 271 FETCH (FLAGS () UID 271) * 272 FETCH (FLAGS () UID 272) * 273 FETCH (FLAGS () UID 273) * 274 FETCH (FLAGS () UID 274) * 275 FETCH (FLAGS () UID 275) * 276 FETCH (FLAGS () UID 276) * 277 FETCH (FLAGS () UID 277) * 278 FETCH (FLAGS (\Seen) UID 278) * 279 FETCH (FLAGS () UID 279) * 280 FETCH (FLAGS (\Seen) UID 280) * 281 FETCH (FLAGS () UID 281) * 282 FETCH (FLAGS (\Seen) UID 282) * 283 FETCH (FLAGS () UID 283) * 284 FETCH (FLAGS (\Seen) UID 284) * 285 FETCH (FLAGS () UID 285) * 286 FETCH (FLAGS () UID 286) * 287 FETCH (FLAGS () UID 287) * 288 FETCH (FLAGS () UID 288) * 289 FETCH (FLAGS () UID 289) * 290 FETCH (FLAGS () UID 290) * 291 FETCH (FLAGS () UID 291) * 292 FETCH (FLAGS () UID 292) * 293 FETCH (FLAGS () UID 293) * 294 FETCH (FLAGS () UID 294) * 295 FETCH (FLAGS (\Seen) UID 295) * 296 FETCH (FLAGS (\Seen) UID 296) * 297 FETCH (FLAGS () UID 297) * 298 FETCH (FLAGS () UID 298) * 299 FETCH (FLAGS () UID 299) * 300 FETCH (FLAGS () UID 300) * 301 FETCH (FLAGS () UID 301) * 302 FETCH (FLAGS (\Seen) UID 302) * 303 FETCH (FLAGS (\Answered \Seen) UID 303) * 304 FETCH (FLAGS () UID 304) * 305 FETCH (FLAGS (\Seen) UID 305) * 306 FETCH (FLAGS () UID 306) * 307 FETCH (FLAGS () UID 307) * 308 FETCH (FLAGS () UID 308) * 309 FETCH (FLAGS () UID 309) * 310 FETCH (FLAGS (\Seen) UID 310) * 311 FETCH (FLAGS () UID 311) * 312 FETCH (FLAGS () UID 312) * 313 FETCH (FLAGS (\Answered \Seen) UID 313) * 314 FETCH (FLAGS () UID 314) * 315 FETCH (FLAGS (\Seen) UID 315) * 316 FETCH (FLAGS (\Seen) UID 316) * 317 FETCH (FLAGS (\Seen) UID 317) * 318 FETCH (FLAGS () UID 318) * 319 FETCH (FLAGS () UID 319) * 320 FETCH (FLAGS () UID 320) * 321 FETCH (FLAGS (\Seen) UID 321) * 322 FETCH (FLAGS () UID 322) * 323 FETCH (FLAGS () UID 323) * 324 FETCH (FLAGS (\Seen) UID 324) * 325 FETCH (FLAGS () UID 325) * 326 FETCH (FLAGS () UID 326) * 327 FETCH (FLAGS () UID 327) * 328 FETCH (FLAGS () UID 328) * 329 FETCH (FLAGS () UID 329) * 330 FETCH (FLAGS (\Seen) UID 330) * 331 FETCH (FLAGS (\Seen) UID 331) * 332 FETCH (FLAGS (\Seen) UID 332) * 333 FETCH (FLAGS () UID 333) * 334 FETCH (FLAGS (\Seen) UID 334) * 335 FETCH (FLAGS () UID 335) * 336 FETCH (FLAGS () UID 336) * 337 FETCH (FLAGS () UID 337) * 338 FETCH (FLAGS (\Seen) UID 338) * 339 FETCH (FLAGS () UID 339) * 340 FETCH (FLAGS (\Seen) UID 340) * 341 FETCH (FLAGS () UID 341) * 342 FETCH (FLAGS () UID 342) * 343 FETCH (FLAGS () UID 343) * 344 FETCH (FLAGS () UID 344) * 345 FETCH (FLAGS (\Seen) UID 345) * 346 FETCH (FLAGS () UID 346) * 347 FETCH (FLAGS () UID 347) * 348 FETCH (FLAGS () UID 348) * 349 FETCH (FLAGS () UID 349) * 350 FETCH (FLAGS () UID 350) * 351 FETCH (FLAGS () UID 351) * 352 FETCH (FLAGS () UID 352) * 353 FETCH (FLAGS () UID 353) * 354 FETCH (FLAGS (\Seen) UID 354) * 355 FETCH (FLAGS (\Seen) UID 355) * 356 FETCH (FLAGS (\Seen) UID 356) * 357 FETCH (FLAGS () UID 357) * 358 FETCH (FLAGS () UID 358) * 359 FETCH (FLAGS () UID 359) * 360 FETCH (FLAGS (\Seen) UID 360) * 361 FETCH (FLAGS () UID 361) * 362 FETCH (FLAGS (\Seen) UID 362) * 363 FETCH (FLAGS (\Seen) UID 363) * 364 FETCH (FLAGS (\Seen) UID 364) * 365 FETCH (FLAGS (\Seen) UID 365) * 366 FETCH (FLAGS (\Seen) UID 366) * 367 FETCH (FLAGS () UID 367) * 368 FETCH (FLAGS (\Seen) UID 368) * 369 FETCH (FLAGS (\Answered \Seen) UID 369) * 370 FETCH (FLAGS (\Seen) UID 370) * 371 FETCH (FLAGS (\Seen) UID 371) * 372 FETCH (FLAGS () UID 372) * 373 FETCH (FLAGS (\Seen) UID 373) * 374 FETCH (FLAGS (\Answered \Seen) UID 374) * 375 FETCH (FLAGS (\Seen) UID 375) * 376 FETCH (FLAGS (\Answered \Seen) UID 376) * 377 FETCH (FLAGS () UID 377) * 378 FETCH (FLAGS (\Answered \Seen) UID 378) * 379 FETCH (FLAGS (\Seen) UID 379) * 380 FETCH (FLAGS (\Seen) UID 380) * 381 FETCH (FLAGS () UID 381) * 382 FETCH (FLAGS (\Answered \Seen) UID 382) * 383 FETCH (FLAGS (\Seen) UID 383) * 384 FETCH (FLAGS (\Seen) UID 384) * 385 FETCH (FLAGS () UID 385) * 386 FETCH (FLAGS (\Answered \Seen) UID 386) * 387 FETCH (FLAGS (\Seen) UID 387) * 388 FETCH (FLAGS () UID 388) * 389 FETCH (FLAGS (\Seen) UID 389) * 390 FETCH (FLAGS () UID 390) * 391 FETCH (FLAGS () UID 391) * 392 FETCH (FLAGS () UID 392) * 393 FETCH (FLAGS (\Seen) UID 393) * 394 FETCH (FLAGS () UID 394) * 395 FETCH (FLAGS () UID 395) * 396 FETCH (FLAGS (\Seen) UID 396) * 397 FETCH (FLAGS (\Answered \Seen) UID 397) * 398 FETCH (FLAGS (\Seen) UID 398) * 399 FETCH (FLAGS (\Seen) UID 399) * 400 FETCH (FLAGS (\Seen) UID 400) * 401 FETCH (FLAGS () UID 401) * 402 FETCH (FLAGS () UID 402) * 403 FETCH (FLAGS (\Seen) UID 403) * 404 FETCH (FLAGS (\Seen) UID 404) * 405 FETCH (FLAGS () UID 405) * 406 FETCH (FLAGS () UID 406) * 407 FETCH (FLAGS () UID 407) * 408 FETCH (FLAGS () UID 408) * 409 FETCH (FLAGS () UID 409) * 410 FETCH (FLAGS (\Seen) UID 410) * 411 FETCH (FLAGS () UID 411) * 412 FETCH (FLAGS () UID 412) * 413 FETCH (FLAGS (\Seen) UID 413) * 414 FETCH (FLAGS (\Answered \Seen) UID 414) * 415 FETCH (FLAGS () UID 415) * 416 FETCH (FLAGS (\Seen) UID 416) * 417 FETCH (FLAGS () UID 417) * 418 FETCH (FLAGS (\Seen) UID 418) * 419 FETCH (FLAGS () UID 419) * 420 FETCH (FLAGS (\Seen) UID 420) * 421 FETCH (FLAGS (\Seen) UID 421) * 422 FETCH (FLAGS () UID 422) * 423 FETCH (FLAGS () UID 423) * 424 FETCH (FLAGS (\Seen) UID 424) * 425 FETCH (FLAGS () UID 425) * 426 FETCH (FLAGS (\Seen) UID 426) * 427 FETCH (FLAGS (\Seen) UID 427) * 428 FETCH (FLAGS (\Seen) UID 428) * 429 FETCH (FLAGS () UID 429) * 430 FETCH (FLAGS () UID 430) * 431 FETCH (FLAGS () UID 431) * 432 FETCH (FLAGS () UID 432) * 433 FETCH (FLAGS () UID 433) * 434 FETCH (FLAGS () UID 434) * 435 FETCH (FLAGS () UID 435) * 436 FETCH (FLAGS () UID 436) * 437 FETCH (FLAGS () UID 437) * 438 FETCH (FLAGS () UID 438) * 439 FETCH (FLAGS () UID 439) * 440 FETCH (FLAGS () UID 440) * 441 FETCH (FLAGS (\Seen) UID 441) * 442 FETCH (FLAGS () UID 442) * 443 FETCH (FLAGS (\Seen) UID 443) * 444 FETCH (FLAGS () UID 444) * 445 FETCH (FLAGS () UID 445) * 446 FETCH (FLAGS () UID 446) * 447 FETCH (FLAGS (\Seen) UID 447) * 448 FETCH (FLAGS (\Seen) UID 448) * 449 FETCH (FLAGS (\Seen) UID 449) * 450 FETCH (FLAGS (\Seen) UID 450) * 451 FETCH (FLAGS (\Seen) UID 451) * 452 FETCH (FLAGS () UID 452) * 453 FETCH (FLAGS () UID 453) * 454 FETCH (FLAGS () UID 454) * 455 FETCH (FLAGS () UID 455) * 456 FETCH (FLAGS () UID 456) * 457 FETCH (FLAGS (\Seen) UID 457) * 458 FETCH (FLAGS (\Answered \Seen) UID 458) * 459 FETCH (FLAGS () UID 459) * 460 FETCH (FLAGS () UID 460) * 461 FETCH (FLAGS (\Seen) UID 461) * 462 FETCH (FLAGS (\Seen) UID 462) * 463 FETCH (FLAGS (\Seen) UID 463) * 464 FETCH (FLAGS () UID 464) * 465 FETCH (FLAGS () UID 465) * 466 FETCH (FLAGS () UID 466) * 467 FETCH (FLAGS () UID 467) * 468 FETCH (FLAGS () UID 468) * 469 FETCH (FLAGS (\Seen) UID 469) * 470 FETCH (FLAGS () UID 470) * 471 FETCH (FLAGS () UID 471) * 472 FETCH (FLAGS () UID 472) * 473 FETCH (FLAGS (\Seen) UID 473) * 474 FETCH (FLAGS () UID 474) * 475 FETCH (FLAGS () UID 475) * 476 FETCH (FLAGS (\Seen) UID 476) * 477 FETCH (FLAGS (\Seen) UID 477) * 478 FETCH (FLAGS (\Seen) UID 478) * 479 FETCH (FLAGS () UID 479) * 480 FETCH (FLAGS () UID 480) * 481 FETCH (FLAGS (\Seen) UID 481) * 482 FETCH (FLAGS () UID 482) * 483 FETCH (FLAGS () UID 483) * 484 FETCH (FLAGS (\Seen) UID 484) * 485 FETCH (FLAGS () UID 485) * 486 FETCH (FLAGS (\Answered \Seen) UID 486) * 487 FETCH (FLAGS (\Seen) UID 487) * 488 FETCH (FLAGS () UID 488) * 489 FETCH (FLAGS (\Answered \Seen) UID 489) * 490 FETCH (FLAGS () UID 490) * 491 FETCH (FLAGS () UID 491) * 492 FETCH (FLAGS (\Answered \Seen) UID 492) * 493 FETCH (FLAGS (\Seen) UID 493) * 494 FETCH (FLAGS () UID 494) * 495 FETCH (FLAGS (\Seen) UID 495) * 496 FETCH (FLAGS () UID 496) * 497 FETCH (FLAGS (\Seen) UID 497) * 498 FETCH (FLAGS (\Seen) UID 498) * 499 FETCH (FLAGS (\Seen) UID 499) * 500 FETCH (FLAGS () UID 500) * 501 FETCH (FLAGS () UID 501) * 502 FETCH (FLAGS (\Answered \Seen) UID 502) * 503 FETCH (FLAGS () UID 503) * 504 FETCH (FLAGS (\Seen) UID 504) * 505 FETCH (FLAGS (\Seen) UID 505) * 506 FETCH (FLAGS (\Seen) UID 506) * 507 FETCH (FLAGS () UID 507) * 508 FETCH (FLAGS (\Seen) UID 508) * 509 FETCH (FLAGS (\Seen) UID 509) * 510 FETCH (FLAGS () UID 510) * 511 FETCH (FLAGS () UID 511) * 512 FETCH (FLAGS () UID 512) * 513 FETCH (FLAGS (\Seen) UID 513) * 514 FETCH (FLAGS () UID 514) * 515 FETCH (FLAGS (\Seen) UID 515) * 516 FETCH (FLAGS (\Answered \Seen) UID 516) * 517 FETCH (FLAGS (\Seen) UID 517) * 518 FETCH (FLAGS () UID 564) * 519 FETCH (FLAGS () UID 570) * 520 FETCH (FLAGS () UID 571) * 521 FETCH (FLAGS (\Seen) UID 572) * 522 FETCH (FLAGS () UID 576) 0000000d OK Fetch completed. 0000000e OK NOOP completed. * SEARCH 0000000f OK Search completed. * 1 FETCH (UID 1 INTERNALDATE "05-Jan-2002 06:03:50 -0500" RFC822.SIZE 1606 FLAGS (\Seen) ENVELOPE ("Sat, 5 Jan 2002 12:03:14 +0100" "further m4 change" (("Marc Espie" NIL "espie" "schutzenberger.liafa.jussieu.fr")) (("Marc Espie" NIL "espie" "schutzenberger.liafa.jussieu.fr")) ((NIL NIL "Marc.Espie" "liafa.jussieu.fr")) (("Todd Vierling" NIL "tv" "wasabisystems.com")) NIL NIL "<Pine.WNT.4.40.0111140959180.284-100000@todd>; from tv(a)wasabisystems.com on Wed, Nov 14, 2001 at 10:21:15AM -0500" "<20020105120314.A17920(a)schutzenberger.liafa.jussieu.fr>") BODY[HEADER.FIELDS (DATE X-PRIORITY X-BYNARI-FOLDER-CLASS X-PR-CONTAINER-CLASS X-MESSAGE-FLAG RECEIVED)] {769} Received: from mononoke.wasabisystems.com (lion.ninthwonder.com [151.199.66.147]) by mail.duh.org (8.11.3nb1/8.11.3/dsb-1.2a1) with ESMTP id g05B2d618330 for <tv+wasabi(a)duh.org>; Sat, 5 Jan 2002 06:02:39 -0500 (EST) Received: by mononoke.wasabisystems.com (Postfix) id 015A030709; Sat, 5 Jan 2002 06:03:17 -0500 (EST) Received: from schutzenberger.liafa.jussieu.fr (schutzenberger.liafa.jussieu.fr [132.227.81.123]) by mononoke.wasabisystems.com (Postfix) with ESMTP id 741E030706 for <tv(a)wasabisystems.com>; Sat, 5 Jan 2002 06:03:16 -0500 (EST) Received: (from espie@localhost) by schutzenberger.liafa.jussieu.fr (8.11.3/8.10.1) id g05B3Fa00656 for tv(a)wasabisystems.com; Sat, 5 Jan 2002 12:03:15 +0100 (CET) Date: Sat, 5 Jan 2002 12:03:14 +0100 BODYSTRUCTURE ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 207 3 NIL ("inline" NIL) NIL)) * 2 FETCH (UID 2 INTERNALDATE "30-Dec-2001 21:59:14 -0500" RFC822.SIZE 1083 FLAGS (\Seen) ENVELOPE ("Sun, 30 Dec 2001 19:07:28 -0800" "Registration information at I-Appliance BBS (http://www.linux-hacker.net)" ((NIL NIL "codeman" "linux-hacker.net")) ((NIL NIL "codeman" "linux-hacker.net")) ((NIL NIL "codeman" "linux-hacker.net")) ((NIL NIL "tv" "duh.org")) NIL NIL NIL "<200112310307.fBV37SV08829(a)www.linux-hacker.net>") BODY[HEADER.FIELDS (DATE X-PRIORITY X-BYNARI-FOLDER-CLASS X-PR-CONTAINER-CLASS X-MESSAGE-FLAG RECEIVED)] {376} Received: from www.linux-hacker.net (www.linux-hacker.net [12.110.32.118]) by mail.duh.org (8.11.3nb1/8.11.3/dsb-1.2a1) with ESMTP id fBV2vqg21976 for <tv(a)duh.org>; Sun, 30 Dec 2001 21:57:52 -0500 (EST) Received: (from admin@localhost) by www.linux-hacker.net (8.10.2/8.10.2) id fBV37SV08829; Sun, 30 Dec 2001 19:07:28 -0800 Date: Sun, 30 Dec 2001 19:07:28 -0800 BODYSTRUCTURE ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 470 17 NIL NIL NIL)) -- -- Todd Vierling <tv(a)duh.org> <tv(a)pobox.com> <todd(a)vierling.name>

2 2

[Dovecot] Moving folder issue
by Andrew Hutchings 07 Aug '05

07 Aug '05

Hi, My wife who has thousands of IMAP boxes keeps getting errors when moving mailboxes in Thunderbird in Windows. I am using the same server (dovecot test 77) with Thunderbird in Linux and don't see the problem. What happens is she moves the mail box and Thunderbird comes up with an error saying it can't access the old box (odd!?). It has however completed the move. The following is what I got from logging, any ideas?: in log: 1843 lsub "" "eBay.Sales - Current.Ready to post.lollipop letters.*" 1844 close 1845 rename "eBay.Sales - Current.Ready to post.lollipop letters" "eBay.Sales - Complete.lollipop letters" 1846 subscribe "eBay.Sales - Complete.lollipop letters" 1847 unsubscribe "eBay.Sales - Current.Ready to post.lollipop letters" 1848 select "eBay.Sales - Complete.lollipop letters" out log: 1843 OK Lsub completed. 1844 OK Close completed. 1845 OK Rename completed. 1846 OK Subscribe completed. 1847 OK Unsubscribe completed. 1848 NO Internal error occured. Refer to server log for more information. [2005-08-01 20:59:50] server log: Aug 1 20:59:50 sever dovecot: IMAP(natalie): stat() failed with file /home/natalie/Maildir/.eBay.Sales - Current.Ready to post.lollipop letters/dovecot.index.log: No such file or directory Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ A-Wing Internet Services - http://www.a-wing.co.uk/ Random quote 4: "Avoid the Gates of Hell. Use Linux" - Unknown

2 1

[Dovecot] Canot move messages out of my inbox
by _ 07 Aug '05

07 Aug '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm using thunderbird on top of Maildir, dovecot latest. For some weeks i cannot move messages out of the inbox folder anymore. Looking at the logfile, i see Error: child 19591 (imap) killed with signal 1 which by now is the only error i can see. I have already compared permissions on working folders with the inbox, all are the same (rwx, owner, owner). Any ideas? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2rc1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC60HQA+RTBSZx+AcRAnXEAJ9fpA4qbQaGf34fHMnMior515/LRACfYgj5 W+uOx4kJfKdKEJVckvp2Xcc= =Kezu -----END PGP SIGNATURE-----

2 1

[Dovecot] [PATCH] settings parsing section/context return bug
by Tom Alsberg 07 Aug '05

07 Aug '05

There seems to be a minor bug in the settings parsing code (as of today's dovecot-stable snapshot - 20050731) - after the closing bracket of protocol (imap/pop3) {} section, the parser still regards all options as affecting only that protocol and not globally (I have some options, protocol imap {}, protocol pop3 {}, and then some more options - now those latter options seem to only affect POP3). It seems to be solved by the attached patch. Merely that the sub-section level has to be decreased after checking that it is positive (for returning the protocol in context to ANY). Would that change (prefix to postfix decrement) break anything else? If not, can it be applied? -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

2 1

[Dovecot] 1.0 stable 20050725 assert, signal 6
by Jeff A. Earickson 07 Aug '05

07 Aug '05

Hi, I was brave enough to upgrade from UW-imap to stable 1.0 20050725 today for our IMAP service. I have seen a few of the following in my syslog: Jul 26 15:37:18 emerald dovecot: [ID 107833 mail.error] IMAP(bjkupke): file mbox -sync-update.c: line 372: assertion failed: (ctx->mail.uid == 0 || ctx->mail.uid == mail->uid) Jul 26 15:37:18 emerald dovecot: [ID 684838 mail.error] child 16755 (imap) kille d with signal 6 Only for user bjkupke; his mailbox is not corrupted when I open it with Pine. My setup: Solaris 9, configured dovecot like so: CC=cc CFLAGS="-g" CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot --with-ssl=openssl \ --with-ssldir=/opt/openssl/ssl --with-rawlog --enable-debug > configure.out Using Sunstudio 9 compiler. I can't find any core files lying around. Bug? Problem? Suggestions please? BTW, are there searchable dovecot list archives someplace? Jeff Earickson Colby College

2 1

[Dovecot] Compile trouble with mysql
by Michael Goth 06 Aug '05

06 Aug '05

Hello! I tried to compile the latest 1.0-test (79) with mysql support, but there is the following error: ... /usr/local/mysql/lib/libmysqlclient.a(sha1.o)(.text+0x5c): In function `sha1_result': : multiple definition of `sha1_result' ../lib/liblib.a(sha1.o)(.text+0x830):/usr/local/src/dovecot/dovecot-1.0-test79/src/lib/sha1.c:233: first defined here ... So 'sha1_result' is defined by mysqlclient and dovecot. This is an issue I already reported some time ago. According to a search in the list archives, it seems no one else has this problem. But there must be more people using dovecot with MySQL support. Probably this only happens with the statically linked MySQL version from mysql.org? I'd really appreciate any help on this, as I have to set up a new mail server quickly (and Courier just doesn't work the way I want it to). Thanks, Michael

2 1

[Dovecot] Help with Virtual user setup.. need pointers
by Andre Bunting 03 Aug '05

03 Aug '05

I have been reading this : http://wiki.dovecot.org/moin.cgi/DovecotPostgresql I decide to use the postgresql instead of mysql.. but now i am in problem.. I cant seem to get postfix-pgsql sasl2-bin libsasl2-modules libpam-pgsql rpms or files for the fedora core 4.. Is there anyone who is using Fedora Core 4.. and have dovecot.. with postifx running virtual users ... or is there another way besides the link ontop to do this ? Andre Bunting Information Technology Manager Integrated Telecommunication Consultants Limited Unit No.1 - Ground Floor, 23 -27 Eastern Main Road, Barataria, Trinidad, West Indies. Telephone : 675-1438 Cell: 748-8587

1 0

[Dovecot] when will the version 1.0 released ...
by wiki kaha 03 Aug '05

03 Aug '05

Hi all. I work with the version 0.99.14 on an openbsd. There are an issue with b-tree and maybe something more. I know about the 1.x-test versions but they will never be in the ports on freebsd and openbsd because of the funny title "*-test..." This looks like an RC and the half world is waiting for a release. Is there no way to release a version so that the port world can go around :) I'm looking forward. ps: great software! regards ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

1 0

[Dovecot] Default_mail_env..
by Guillermo Llenas 02 Aug '05

02 Aug '05

Hi, I 'm new to Dovecot and we are trying to do some tests in a production environment. We use mysql to authenticate and dovecot imap only. But our structure directory is something special. All of ours accounts are stored in maildir and the path is the following: For example the account pepe(a)inter.net /export/maildir/inter.net/p/e/pepe and into pepe we have cur, tmp, new. This is a problem because we cannot modify the database adding home for all users, so in the other side I played with the default_mail_env default_mail_env = maildir:/export/maildir/%d/%1u/%2u/%n:INBOX=/export/maildir/%d/%1u/%2u/%n but didn't wok out. Because imap(pepe(a)inter.net): Aug 01 18:26:04 Fatal: Failed to create storage with data: INBOX=/export/maildir/inter.net/p/pe/pepe I need only export / maildir / domain / first letter of the username / second letter / and last username Is there any way to do this ?, thanks in advance -- Guillermo Llenas Tecnología Inter.net Argentina ________________________ +54 011 6328-1500 fax 0054 11 6328-1530 www.ar.inter.net guillermo.llenas(a)team.ar.inter.net

2 2

[Dovecot] where is "pam_listfile.so" for static userdb?
by OpenMacNews 02 Aug '05

02 Aug '05

hi all, i'm setting up Dovecot on OSX to use PAM authentication against a flat_file/static userdb (tho i will _eventually_ mv to pgsql ...). iiuc, to do so i need something like: =================================== (EDITOR) /etc/pam.d/dovecot.imap auth required pam_listfile.so item=user sense=allow file=/var/dovecot/imapusers onerr=fail =================================== for a userdb listing in "/var/imapuser". all simple & good, except -- -- where's "pam_listfile.so" on OSX? % ls /usr/lib/pam/ pam_afpmount.so pam_nologin.so pam_securetty.so pam_uwtmp.so pam_deny.so pam_permit.so pam_securityserver.so pam_wheel.so pam_netinfo.so pam_rootok.so pam_unix.so do i have to grab-n-install it from somewhere? or are one of these ^ an 'equivalent' ... this _should_ be simple :-} thanks, richard

1 0

[Dovecot] Feature request - umask for index files
by Marc Perkel 02 Aug '05

02 Aug '05

I'd like a separate feature for setting umask for index and cache files differently from email files. The reason is that I'm putting indexes in a separate location and I need group create rights in directories. Otherwise what happens is that the first user creates the directories, but the second user for the domain that has a different UID gets an error. default_mail_env = mbox:/vhome/%d/home/%n:INBOX=/vhome/%d/home/%n/INBOX:INDEX=/nobackup/imap-index/%d/%n -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 2