- dovecot - dovecot.org

[Dovecot] Mails don't get deleted after POP3
by cullinan＠rocketmail.com 09 Nov '12

09 Nov '12

Hi, there! Well, I am new to dovecot, so please be patient with me: I have a virtual server and want to setup simple mail delivery. postfix, saslauthd and dovecot basically work fine. The only open issue is, that (I guess) dovecot doesn't remove the mail when it's retrieved via pop3 from the server. It keeps sending me the same emails again and again. (The mail client (Thunderbird) is configured to remove the messages from the server - it was working already.) I guess that dovecot cannot write to some files / has problems with write permissions. But it doesn't tell me anything... Can you tell me, what configuration might be wrong or how can I enable more debugging to see what dovecot is doing after the mails got sent out via pop3? Here is the configuration: # dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.38-8-server x86_64 Ubuntu 11.04 log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 pop3s login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/pop3-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock mail_executable: /usr/lib/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/modules/pop3 auth default: passdb: driver: pam userdb: driver: passwd -----8<----- # dovecot -a # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.38-8-server x86_64 Ubuntu 11.04 base_dir: /var/run/dovecot log_path: info_log_path: log_timestamp: %Y-%m-%d %H:%M:%S syslog_facility: mail protocols: pop3 pop3s listen: * ssl_listen: ssl: yes ssl_ca_file: ssl_cert_file: /etc/ssl/certs/dovecot.pem ssl_key_file: /etc/ssl/private/dovecot.pem ssl_key_password: ssl_parameters_regenerate: 168 ssl_cipher_list: ssl_cert_username_field: commonName ssl_verify_client_cert: no disable_plaintext_auth: yes verbose_ssl: no shutdown_clients: yes nfs_check: yes version_ignore: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/pop3-login login_user: dovecot login_greeting: Dovecot ready. login_log_format_elements: user=<%u> method=%m rip=%r lip=%l %c login_log_format: %$: %s login_process_per_connection: yes login_chroot: yes login_trusted_networks: login_process_size: 64 login_processes_count: 3 login_max_processes_count: 128 login_max_connections: 256 valid_chroot_dirs: mail_chroot: max_mail_processes: 512 mail_max_userip_connections: 10 verbose_proctitle: no first_valid_uid: 500 last_valid_uid: 0 first_valid_gid: 1 last_valid_gid: 0 mail_access_groups: mail_privileged_group: mail mail_uid: mail_gid: mail_location: mail_cache_fields: mail_never_cache_fields: imap.envelope mail_cache_min_mail_count: 0 mailbox_idle_check_interval: 30 mail_debug: no mail_full_filesystem_access: no mail_max_keyword_length: 50 mail_save_crlf: no mmap_disable: no dotlock_use_excl: yes fsync_disable: no mail_nfs_storage: no mail_nfs_index: no mailbox_list_index_disable: yes lock_method: fcntl maildir_stat_dirs: no maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: no maildir_very_dirty_syncs: no mbox_read_locks: fcntl mbox_write_locks: fcntl dotlock mbox_lock_timeout: 300 mbox_dotlock_change_timeout: 120 mbox_min_index_size: 0 mbox_dirty_syncs: yes mbox_very_dirty_syncs: no mbox_lazy_writes: yes dbox_rotate_size: 2048 dbox_rotate_min_size: 16 dbox_rotate_days: 1 mail_drop_priv_before_exec: no mail_executable: /usr/lib/dovecot/pop3 mail_process_size: 256 mail_plugins: mail_plugin_dir: /usr/lib/dovecot/modules/pop3 mail_log_prefix: %Us(%u): mail_log_max_lines_per_sec: 10 imap_max_line_length: 65536 imap_capability: imap_client_workarounds: imap_logout_format: bytes=%i/%o imap_id_send: imap_id_log: imap_idle_notify_interval: 120 pop3_no_flag_updates: no pop3_enable_last: no pop3_reuse_xuidl: no pop3_save_uidl: no pop3_lock_session: no pop3_uidl_format: %08Xu%08Xv pop3_client_workarounds: pop3_logout_format: top=%t/%p, retr=%r/%b, del=%d/%m, size=%s dict_db_config: dict_process_count: 1 managesieve_max_line_length: 65536 managesieve_logout_format: bytes=%i/%o managesieve_implementation_string: dovecot auth default: mechanisms: plain realms: default_realm: cache_size: 0 cache_ttl: 3600 cache_negative_ttl: 3600 executable: /usr/lib/dovecot/dovecot-auth user: root chroot: username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ username_translation: username_format: master_user_separator: anonymous_username: anonymous krb5_keytab: gssapi_hostname: winbind_helper_path: /usr/bin/ntlm_auth failure_delay: 2 verbose: no debug: no debug_passwords: no ssl_require_client_cert: no ssl_username_from_cert: no use_winbind: no count: 1 worker_max_count: 30 process_size: 256 passdb: driver: pam args: deny: no pass: no master: no userdb: driver: passwd args: -----8<----- Please let me know if you need more. Thank you in advance! Regards, Rob

3 3

[Dovecot] Dovecot ok for port 110, but not for SSL (beginner asking)
by ycc_Swe 09 Nov '12

09 Nov '12

Hello, I just installed Dovecot. It works for plaintext autorization, port 110. It has connected with Telnet, Thunderbird and an on-line pop3 client. Telnet: +OK Dovecot ready. user nnnnn -ERR Unknown command. user nnnnn +OK pass xxxxxxxxxx +OK Logged in. stat +OK 1 1553 retr 1 +OK 1553 octets Return-path: <sssssss(a)hotmail.com> Envelope-to: nnnnnn(a)mydomain.com Delivery-date: Tue, 06 Nov 2012 12:02:28 +0100 Received: from bay0-xcvxcv-xvxcv.bay333.hotmail.com ([123.123.123.123]) by deb7.pc with esmtp (Exim 4.80) But when I try ssl (port 995) with an on-line pop3 client, it will not work: /var/log/mail.log Nov 7 02:46:55 deb7 dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=12.12.12.7, lip=123.123.123.123, TLS: Disconnected, session=<Iza75N3NlABBNykH> Nov 7 02:46:56 deb7 dovecot: pop3-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=12.12.12.7, lip=123.123.123.123, TLS: Disconnected, session=<nWTF5N3NlQBBNykH> root@deb7:~# doveconf -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-3-686-pae i686 disable_plaintext_auth = no mail_gid = mail mail_location = mbox:~/mail:INBOX=/var/mail/%u namespace inbox { inbox = yes location = prefix = } passdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap pop3" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } I know very little about mail and ssl. I have assumed that ssl will be set up "automatically" when Dovecot is installed. But maybe I have missed something here. Please give me pointers. The following two files contain ssl keys: ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem I have tried changing the ssl parameter ("yes", "required") in 10-ssl.conf but with no change except that port 110 login becomes disabled. As you can see I am a beginner with Dovecot, I hope it is still OK to ask on this mailing list. Thanks. -- View this message in context: http://dovecot.2317879.n4.nabble.com/Dovecot-ok-for-port-110-but-not-for-SS… Sent from the Dovecot mailing list archive at Nabble.com.

3 5

Re: [Dovecot] cannot update mailbox - unable to lock for exclusive access
by Stan Hoeppner 08 Nov '12

08 Nov '12

Please always reply to the list, not individuals. On 11/8/2012 4:17 AM, 1st WebDesigns wrote: > On 08/11/2012 09:23, Stan Hoeppner wrote: >> On 11/8/2012 2:29 AM, 1st WebDesigns wrote: >>> Hi there, >>> >>> We're using Dovecot version 1.0.7 and Postfix, and since upgrading our >>> Linux box we're getting this in the maillog: >> >> 1.0.7 is absolutely ancient and no longer officially supported. You >> need 1.2.x minimum, 2.x.x even better. And you say you just recently >> upgraded your Linux distro? What planet do you live on son? You're a >> few light years behind current stable software. >> >>> Nov 8 07:49:11 server1 postfix/local[27901]: 04B8E7081DA: >>> to=<xyz(a)xyz.com>, orig_to=<abc(a)abc.com>, relay=local, delay=19, >>> delays=0.07/0/0/19, dsn=4.2.0, status=deferred (cannot update mailbox >>> /var/spool/mail/abc for user abc. unable to lock for exclusive access: >>> Resource temporarily unavailable) >> >> The simple permanent fix to Postfix/Dovecot mbox locking issues is >> switching from Postfix LOCAL to Dovecot LDA for mailbox delivery. 1.0.7 >> is before my time. I do not know if LDA was available then. Upgrade >> and you'll have it, and you'll also fix other problems you're not even >> aware of yet. >> >>> Postfix is currently set to: >>> mailbox_delivery_lock = fcntl, dotlock >>> >>> Dovecot has this: >>> mbox_read_locks = fcntl >>> mbox_write_locks = fcntl dotlock >> >> LDA completely eliminates lock contention. >> >> http://wiki.dovecot.org/LDA/Postfix >> http://wiki2.dovecot.org/LDA/Postfix >> > > Thanks for your reply. We have upgraded from RHEL4 to RHEL5, so 1.0.7 > is the "stable" version that they provide RHEL 5 is also ancient, released in March 2007, over 5 years ago. The current stable release is RHEL 6.3, released in June 2012. What is the valid reason preventing you from upgrading to the 6.x distribution? The packages in general in 6.x are 5 years newer than 5.x. And given the fact that RHEL runs miles behind the bleeding edge, you're way behind the curve even with a recent RHEL distribution. You can probably find a much newer version of Dovecot in an RPM somewhere, and Postfix for that matter. But it would be better for you if you simply upgraded to RHEL 6.3. -- Stan

1 0

[Dovecot] IP/SSL configuration
by James Devine 08 Nov '12

08 Nov '12

Is there a way I can have something like the following setup: 192.168.0.2 port 110/143, with no starttls/ssl 192.168.0.3 port 110,995/143,993 with starttls/ssl 192.168.0.4 port 110,995/143,993 with starttls/ssl I am looking to setup dovecot so that some IPs will run without any notion of SSL whereas other IPs will run with with ssl/starttls available, each with its own certs

1 0

[Dovecot] pop3 exim4 dovecot
by Patrick Shirkey 08 Nov '12

08 Nov '12

Hi, I have an exim4 and dovecot system. The system has multiple accounts. Exim4 is receiving emails in the /var/mail/user files and dovecot is configured to use /home/user/mail (mbox) folder. I have one account that dovecot is not processing replies/bounces/etc... The data is being written in the /var/mail/user file by exim4 but as far as dovecot is aware there is nothing in the pop3 inbox. Can anyone suggest how I can enable dovecot to know that the data is in the /var/mail/user file and deliver it to the pop3 inbox for this account? -- Patrick Shirkey Boost Hardware Ltd

4 5

Re: [Dovecot] pop3 exim4 dovecot
by Patrick Shirkey 08 Nov '12

08 Nov '12

On Fri, November 9, 2012 1:10 am, Odhiambo Washington wrote: > On Thu, Nov 8, 2012 at 5:03 PM, Patrick Shirkey > <pshirkey(a)boosthardware.com>wrote: > >> >> On Fri, November 9, 2012 12:13 am, Odhiambo Washington wrote: >> > On Thu, Nov 8, 2012 at 11:36 AM, Patrick Shirkey >> > <pshirkey(a)boosthardware.com >> >> wrote: >> > >> >> >> >> On Thu, November 8, 2012 7:21 pm, Robert Schetterer wrote: >> >> > Am 08.11.2012 08:48, schrieb Patrick Shirkey: >> >> >> Hi, >> >> >> >> >> >> I have an exim4 and dovecot system. The system has multiple >> accounts. >> >> >> Exim4 is receiving emails in the /var/mail/user files and dovecot >> is >> >> >> configured to use /home/user/mail (mbox) folder. >> >> >> >> >> >> I have one account that dovecot is not processing >> >> replies/bounces/etc... >> >> >> The data is being written in the /var/mail/user file by exim4 but >> as >> >> far >> >> >> as dovecot is aware there is nothing in the pop3 inbox. >> >> >> >> >> >> Can anyone suggest how I can enable dovecot to know that the data >> is >> >> in >> >> >> the /var/mail/user file and deliver it to the pop3 inbox for this >> >> >> account? >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Patrick Shirkey >> >> >> Boost Hardware Ltd >> >> >> >> >> > >> >> > show logs >> >> > and config like doveconf -n >> >> > >> >> > >> >> >> >> There is nothing in the dovecot logs afaict >> >> >> >> echo "my test" | mail -s "test message" test@xxx >> >> >> >> 2012-11-08 08:34:38 1TWNZO-0000TG-8s <= root@xxx U=root P=local S=398 >> >> 2012-11-08 08:34:38 1TWNZO-0000TG-8s => xxx <test@xxx> R=local_user >> >> T=mail_spool >> >> 2012-11-08 08:34:38 1TWNZO-0000TG-8s Completed >> >> >> >> >> >> exim -bt test@xxx >> >> R: system_aliases for xxx@localhost >> >> R: userforward for xxx@localhost >> >> R: procmail for xxx@localhost >> >> R: maildrop for xxx@localhost >> >> R: lowuid_aliases for xxx@localhost (UID 1238) >> >> R: local_user for xxx@localhost >> >> xxx@localhost >> >> <-- test@xxx >> >> router = local_user, transport = mail_spool >> >> >> >> >> >> - Here's the dovecot config: >> >> >> >> # dovecot -n >> >> # 1.2.15: /etc/dovecot/dovecot.conf >> >> # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.6 >> >> log_timestamp: %Y-%m-%d %H:%M:%S >> >> protocols: pop3 pop3s >> >> listen: 127.0.0.1 >> >> login_dir: /var/run/dovecot/login >> >> login_executable: /usr/lib/dovecot/pop3-login >> >> mail_privileged_group: mail >> >> mail_location: mbox:~/mail >> >> mail_debug: yes >> >> mbox_write_locks: fcntl dotlock >> >> mail_executable: /usr/lib/dovecot/pop3 >> >> mail_plugin_dir: /usr/lib/dovecot/modules/pop3 >> >> auth default: >> >> debug: yes >> >> passdb: >> >> driver: pam >> >> userdb: >> >> driver: passwd >> >> >> >> >> >> >> > You are telling dovecot that mails are in mbox format (why you even >> use >> > mbox instead of Maildir++ beats me, but that's not what you asked for >> help >> > with) and are stored in /home/$user/mbox so go ahead at also tell Exim >> to >> > deliver to the same location! >> > If you want Exim to deliver to /var/mail/$user then change your >> > mail_location in dovecot.conf to point to this too. >> > >> > >> >> >> Thanks for your advice. I inherited this system and it is a live B2B >> system so I am trying not to break it as well as to keep it running :-) >> >> I have seen some unusual behaviour now. >> >> 1: According to my script to process the inbox for each account the pop3 >> account was empty. The code was previously working for many months. I >> thought it might be related to the missing mail_location directive >> because >> the home/xxx/mail folder was missing for the specific account that was >> having a problem so I added it as above but it didn't appear to fix the >> problem. >> > > You DO NOT need to add it manually. All you have to do is to send a test > mail to the user and the mbox will be created with the correct > permissions. > > >> >> 2: I modified it as suggested : mail_location = INBOX=/var/mail/%u >> >> That gave me an error >> >> Nov 8 13:47:03 mail dovecot: POP3(xxx): mail_location: Ambiguous mail >> location setting, don't know what to do with it: INBOX=/var/mail/xxx >> (try >> prefixing it with mbox: or maildir:) >> Nov 8 13:47:03 mail dovecot: POP3(xxx): Fatal: Namespace initialization >> failed >> > > > You must RTFM. The examples are in conf.d/10-mail.conf and they have the > following text: > > <quote> > ## Mailbox locations and namespaces > ## > > # Location for users' mailboxes. The default is empty, which means that > Dovecot > # tries to find the mailboxes automatically. This won't work if the user > # doesn't yet have any mail, so you should explicitly tell Dovecot the > full > # location. > # > # If you're using mbox, giving a path to the INBOX file (eg. /var/mail/%u) > # isn't enough. You'll also need to tell Dovecot where the other mailboxes > are > # kept. This is called the "root mail directory", and it must be the first > # path given in the mail_location setting. > # > # There are 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/wiki/Variables.txt for full list. Some examples: > # > # mail_location = maildir:~/Maildir > # mail_location = mbox:~/mail:INBOX=/var/mail/%u > # mail_location = mbox:/var/mail/%d/%1n/%n:INDEX=/var/indexes/%d/%1n/%n > # > # <doc/wiki/MailLocation.txt> > </quote> > > ... make sense? > Starting to now. My first attempt to *not* break the existing system was to try with the following: mail_location = mbox:~/mail But that didn't work so I asked here and according to your first email it seemed this config was necessary: mail_location = INBOX=/var/mail/%u But after re reading the docs it appears that *both* locations are required: mail_location = mbox:~/mail:INBOX=/var/mail/%u -- Patrick Shirkey Boost Hardware Ltd

2 1

[Dovecot] v2.2.alpha1 released
by Timo Sirainen 08 Nov '12

08 Nov '12

http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz.sig I wanted to start stabilizing v2.2 release some months ago already, but I somehow got stuck adding more and more features. Now it looks like all of the necessary API changes are done, so everything I'm planning on near future can still be added to v2.2 without major changes. The redesigned dsync hasn't had much testing yet, so avoid running it with important mails. Would be nice if people started testing and reporting any bugs. I was going to create some kind of a test suite for testing all the possible syncing combinations and also doing some random stress testing, but I haven't had time for that yet. The new dsync supports doing very fast syncs by saving the resulting state and giving it as command line parameter to the next sync. So for example doveadm sync -s "" > new-state saves the state and doveadm sync -s `cat new-state` continues from the saved state. The replicator code doesn't yet support this. * When creating home directories, the permissions are copied from the parent directory if it has setgid-bit set. For full details, see http://wiki2.dovecot.org/SharedMailboxes/Permissions * "doveadm auth" command was renamed to "doveadm auth test" * IMAP: ID command now advertises server name as Dovecot by default. It was already trivial to guess this from command replies. + Implemented IMAP MOVE and BINARY extensions + Implemented IMAP CATENATE, URLAUTH and URLAUTH=BINARY extensions (by Stephan Bosch). + Implemented IMAP NOTIFY extension. Requires mailbox_list_index=yes to be enabled. + Redesigned and rewritten dsync. The new design makes the syncing faster, more reliable and more featureful. The new dsync protocol isn't backwards compatible with old dsync versions (but is designed to be forwards compatible with future versions). + All mailbox formats now support per-user message flags for shared mailboxes by using a private index. It can be enabled by adding :INDEXPVT=<path> to mail location. This should be used instead of :INDEX also for Maildir/mbox to improve performance. + Improved mailbox list indexes. They should be usable now, although still disabled by default. + Added LAYOUT=index. The mailbox directories are created using their GUIDs in the filesystem, while the actual GUID <-> name mapping exists only in the index. + LMTP proxy: Implemented XCLIENT extension for passing remote IP address through proxy.

2 4

Re: [Dovecot] Android ICS stock client and IMAP Capability issue.
by Massimiliano Cianelli 08 Nov '12

08 Nov '12

Hi, Yes w/o prefix work as expected, try to add a prefix like courier does (eg. Inbox.) It will not work as expected. Due I'm upgrading an old installed server, I've to keep everything as much transparent I can... it includes IMAP folder and subscription. Looking at that I've encountered that issue, and analyzed for fix it (thank you open source), not everyone will want to use/use k9.. but you can be 100% sure the stock client is there. Due that Google act like BlackBerry, Microsoft,etc.. (hovewer they will not fix it soon, or really respect the rfc), it's much simple add Namespace on prelogin banner then wait or have to tell someone to install another client for that mailbox. I didn't know the history, but looking at change log seems that idle as been put back to prelogin client for some kind of compatibility with their service. Anyway, the most important reason that got me to subscribe the mailing list for write those emails, is share with the community that problem and provide a solution.. for someone in the future that have the same problem and will search on internet for a solution (like I've does.. before analyze it on my own). If the workaround will be added to the wiki or will be put in the source.. the important thing is that there is a solution simple and fast (two.. the source modify, and the configuration file) and someone can find it.. (Sarcastic) And if the mayans were right we can't wait for google to fix it :p Best Regards Sent from Galaxy Nexus Robert Schetterer <rs(a)sys4.de> ha scritto: >Am 07.11.2012 08:13, schrieb Massimiliano Cianelli: >> Hello, >> >> My phone: >> Android ics 4.1.2 on galaxy nexus. >> And yes, stock mean the default client that come with the os in IMAP mode. >> >> I already know about that configuration parameter, but it will display two time namespace in postlogin capabilities, and so I like much more to adjust the source code to fix the issue. >> >> Yes there is k9 but I didn't like it too much, I prefer the stock client and is much important to keep compatibility with stock client then user-installed client. >> >> About the issue on Google code, there is thr issue on google code... but Google is a lot slow in fixing those things. >> http://code.google.com/p/android/issues/detail?id=1811 >> >> In a few hour I'll update the issue noticing where is hidden the problem. >> >> Regards >> Sent from Galaxy Nexus > >Hi , i shortly tested this with android sdk jelly bean 4.1.1 and "my >setup" dovecot 2.1.10 with included orginal android mail app in imap mode, >,leaving IMAP prefix blank, everything works as expected, no double >shown inbox, namespace problems etc >so you might have to fit your namespace setup. >Also you might follow allready given advice from here. > >Anyway , i understand you using "stock client" >but you have to understand that the producers of mail clients >optimize their stuff fitting best in their own server structure >making money with it, therefor their motivation coding better imap code >is not very high, same case is for outlook and microsoft >however, i would say, fixing bugs is on the google site here, looks like >there is patch >at >http://code.google.com/p/android/issues/detail?id=1811 >and the issue seems long known > >i dont see any hard relation to dovecot in this case >meanwhile using k9mail seems the best way to workaround >there are lots of other bugs around android versions >over the years i dont expect google to fix them > > >> >> Robert Schetterer <rs(a)sys4.de> ha scritto: >> >>> Am 06.11.2012 07:08, schrieb Ben Morrow: >>>> At 6AM +0100 on 6/11/12 you (Massimiliano Cianelli) wrote: >>>>> Hi, >>>>> >>>>> My setup: >>>>> Dovecot 2 latest, installed to replace courrier IMAP, and off course >>>>> configured with the dot separator and all folder under INBOX.*. >>>>> >>>>> The problem: >>>>> My phone was driving me mad during the test, due that it will only >>>>> recognize Inbox. >>>>> >>>>> How found the solution: >>>>> I've started sniffing IMAP traffic on my server and ended up with one >>>>> difference: >>>>> On courier it ask for namespace, on dovecot it won't. >>>>> >>>>> I gives a better look, and noticed that courier show namespace >>>>> capability on prelogin banner, adding it too solved the problem. >>>>> >>>>> Reason: >>>>> Android ICS stock client seems do not honor the capability gived after >>>>> the login. >>>> >>>> See http://wiki2.dovecot.org/Upgrading/2.0?highlight=%28capability%29 ; >>>> you need to set imap_capability and/or get your client fixed. >>>> >>>> Ben >>>> >>> >>> Hi, first ,what is the exact meaning of >>> >>> "Android ICS stock client" >>> >>> do you mean default included email client in standard android in imap >>> mode, when yes, which version of Android , i like to test my own >>> however is there changelog/code etc at google for this behave? >>> >>> conf example >>> >>> # Override the IMAP CAPABILITY response. If the value begins with '+', >>> # add the given capabilities on top of the defaults (e.g. +XFOO XBAR). >>> #imap_capability = >>> >>> setting stuff here might be complex , or lead to trouble with other >>> clients, if setting this might fix problems ,with clients it should be >>> advised in the wiki/example-conf and/or Timo >>> >>> or the other way ,for massive used clients there should be >>> a seperate workaround section in the conf >>> >>> But fixing behave clients should be prime option anyway >>> >>> Meanwhile use K9mail in Android as best free option in imap mode servers >>> >>> Best Regards >>> MfG Robert Schetterer >>> >>> -- >>> [*] sys4 AG >>> >>> http://sys4.de, +49 (89) 30 90 46 64 >>> Franziskanerstraße 15, 81669 München >>> >>> Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 >>> Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer >>> Aufsichtsratsvorsitzender: Joerg Heidrich > > > >Best Regards >MfG Robert Schetterer > >-- >[*] sys4 AG > >http://sys4.de, +49 (89) 30 90 46 64 >Franziskanerstraße 15, 81669 München > >Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 >Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer >Aufsichtsratsvorsitzender: Joerg Heidrich

4 11

[Dovecot] dovecot-lda not correct folder
by tony.blue.mailinglist＠gmx.de 07 Nov '12

07 Nov '12

Hello, i use dovecot with maildir. The maildir-folder looks like this: vmail/mail/user1/cur vmail/mail/user1/.Sent vmail/mail/user1/.optionalfolder Procmail should put some definded mails in the "optionalfolder" My uses configuration does not do this: ... DELIVERMAIL="/usr/lib/dovecot/dovecot-lda" IMAP="$DELIVERMAIL -e -d $LOGNAME -m INBOX" ZUSATZORDNER="$DELIVERMAIL -e -d $LOGNAME -m .optionalfolder" ... dovecot-lda puts the mails for the optionalfolder always in the .cur (INBOX). What´s the correct dovecot-lda parameter to put the mails in the optionalfolder? Thank you! Tony

2 2

[Dovecot] No manpage for "doveadm fts" command
by Dave Abrahams 07 Nov '12

07 Nov '12

Just wanted to make sure this issue was registered separately from the overall confusion I'm exploring in another thread, even though I mention this there too. -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost

2 2

[Dovecot] 2.2.alpha1 (626a9df21e62): LMTP Core Dump
by Thomas Leuxner 07 Nov '12

07 Nov '12

Please find Backtrace for LMTP Core Dump below: [...] ==> /var/log/dovecot/dovecot.log <== Nov 1 11:16:14 spectre dovecot: lmtp(17245): Connect from local Nov 1 11:16:14 spectre dovecot: lmtp(17245): Fatal: master: service(lmtp): child 17245 killed with signal 11 (core dumped) ==> /var/log/mail.log <== Nov 1 11:16:14 spectre postfix/lmtp[17204]: 3Xsj4G11MrzNY: to=<tlx(a)leuxner.net>, relay=spectre.leuxner.net[private/dovecot-lmtp], delay=0.11, delays=0.06/0/0.01/0.04, dsn=4.4.2, status=deferred (lost connection with spectre.leuxner.net[private/dovecot-lmtp] while sending MAIL FROM) [...] $ gdb /usr/lib/dovecot/lmtp /tmp/core Program terminated with signal 11, Segmentation fault. #0 0x00007f6174db3d35 in mail_storage_service_lookup (ctx=0x1160640, input=0x7fff905265d0, user_r=<value optimized out>, error_r=<value optimized out>) at mail-storage-service.c:1013 1013 mail-storage-service.c: No such file or directory. in mail-storage-service.c (gdb) bt full #0 0x00007f6174db3d35 in mail_storage_service_lookup (ctx=0x1160640, input=0x7fff905265d0, user_r=<value optimized out>, error_r=<value optimized out>) at mail-storage-service.c:1013 flags = 675 user = <value optimized out> username = 0x11540b0 "tlx(a)leuxner.net" user_info = 0x1163718 user_set = <value optimized out> userdb_fields = 0x1173dd8 error = <value optimized out> reply = {uid = 0, gid = 0, home = 0x7f6175249712 "H\211\303d\213\004%\030", chroot = 0x7f6100000001 <Address 0x7f6100000001 out of bounds>, extra_fields = {arr = {buffer = 0x0, element_size = 18170192}, v = 0x0, v_modifiable = 0x0}, anonymous = 0} set_parser = 0x1167500 sets = 0x0 user_pool = 0x11705e0 temp_pool = 0x1173db0 ret = 1 #1 0x0000000000406c16 in cmd_rcpt (client=0x1161e70, args=0x116d623 "") at commands.c:545 rcpt = {address = 0x0, detail = 0x0, service_user = 0x0} input = {module = 0x40823a "lmtp", service = 0x40823a "lmtp", username = 0x11540b0 "tlx(a)leuxner.net", session_id = 0x0, local_ip = {family = 0, u = {ip6 = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0, userdb_fields = 0x0, flags_override_add = 0, flags_override_remove = 0, no_userdb_lookup = 0} address = 0x11540b0 "tlx(a)leuxner.net" username = 0x11540b0 "tlx(a)leuxner.net" detail = 0x4086a3 "" error = 0x0 ret = <value optimized out> #2 0x00000000004055fb in client_input_line (client=0x1161e70) at client.c:60 cmd = <value optimized out> args = 0x116d60f "TO:<tlx(a)leuxner.net>" #3 client_input_handle (client=0x1161e70) at client.c:113 _data_stack_cur_id = 3 output = 0x11610e8 line = <value optimized out> ret = <value optimized out> #4 0x00007f6174afd186 in io_loop_call_io (io=0x1161190) at ioloop.c:387 ioloop = 0x115c670 t_id = 2 #5 0x00007f6174afe1d7 in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:215 ctx = 0x115f4a0 event = 0x115f510 list = 0x11611e0 io = 0x11540b0 tv = {tv_sec = 299, tv_usec = 999016} msecs = <value optimized out> ret = 1 i = 0 call = false #6 0x00007f6174afd128 in io_loop_run (ioloop=0x115c670) at ioloop.c:406 No locals. #7 0x00007f6174ae6473 in master_service_run (service=0x115c510, callback=0x1173e08) at master-service.c:546 No locals. #8 0x0000000000404a06 in main (argc=1, argv=0x115c370) at main.c:122 set_roots = {0x60a8e0, 0x408e20, 0x0} service_flags = <value optimized out> storage_service_flags = 675 c = <value optimized out> [ doveconf -n ] # 2.2.alpha1 (626a9df21e62): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.6 auth_cache_size = 16 k auth_verbose = yes mail_location = mdbox:~/mdbox mail_plugins = acl quota stats namespace { list = yes location = mdbox:/var/vmail/public prefix = Public/ separator = / subscriptions = no type = public } namespace inbox { hidden = no inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = username_format=%u /var/vmail/auth.d/%d/passwd driver = passwd-file } plugin { acl = vfile:/var/vmail/conf.d/%d/acls:cache_secs=300 mail_log_events = expunge mailbox_delete quota = dict:user::file:%h/mdbox/dovecot-quota quota_rule = *:storage=1GB quota_rule2 = Trash:storage=+10%% sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/vmail/conf.d/%d/sieve stats_refresh = 30s stats_track_cmds = yes } protocols = " imap lmtp" quota_full_tempfail = yes service auth-worker { unix_listener auth-worker { user = doveauth } user = doveauth } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = doveauth } service imap-login { inet_listener imap { address = 1.2.3.4 port = 143 } inet_listener imaps { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl_ca = </etc/ssl/certs/SSL123_CA_Bundle.pem ssl_cert = </etc/ssl/certs/host_domain_tld.crt ssl_key = </etc/ssl/private/host_domain_tld.key syslog_facility = local1 userdb { args = username_format=%u /var/vmail/auth.d/%d/passwd driver = passwd-file } verbose_proctitle = yes protocol lmtp { mail_plugins = acl quota stats sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = acl quota stats imap_acl imap_quota mail_log notify imap_stats }

2 2

[Dovecot] acl and subfolder
by Laurent Foucher 07 Nov '12

07 Nov '12

hello, I'm using dovecot 2.0.16 and i would like to use acl for subfolder. The file dovecot-acl is well written in both folder test and the subfolder test/Test : cat /home/user2/Maildir/.test.Test/dovecot-acl user=user1 ilrws cat /home/user2/Maildir/.test/dovecot-acl user=user1 ilprws When user1 want to list, the folder test is well shown, but not the subfolder test/Test. This is the logs : Debug: acl: acl username = user1 imap(laurent.foucher): Debug: acl: owner = 0 Shuka-a dovecot: imap(user1): Debug: acl vfile: Global ACL directory: (none) Shuka-a dovecot: imap(user1): Debug: acl vfile: reading file /home/user2/Maildir/.test/dovecot-acl [....] imap(user1): Debug: acl: Mailbox not in dovecot-acl-list: Partages/user2/test/Test I don't userstand why the file dovecot-acl is not read from the subfolder, while user1 and user2 have the same gid and write access to the directories. Thanks for your answers. dovecot -n auth_cache_size = 512 M default_client_limit = 8400 disable_plaintext_auth = no mail_access_groups = dovecot mail_debug = yes mail_location = maildir:~/Maildir mail_plugins = acl mail_privileged_group = dovecot managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave imapflags notify namespace { inbox = yes location = prefix = separator = / type = private } namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = Partages/%%u/ separator = / subscriptions = no type = shared } passdb { args = cache_key=%u%s * driver = pam } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes.db mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } postmaster_address = postmaster(a)iut-tlse3.fr protocols = " imap sieve" service auth { client_limit = 8500 unix_listener auth-userdb { group = Personnel_IUT mode = 0666 } } service imap-login { process_limit = 4096 process_min_avail = 16 service_count = 0 vsz_limit = 256 M } service imap { process_limit = 4096 vsz_limit = 3036 M } ssl_cert = </etc/ssl/certs/cert-5383-imaps.iut-tlse3.fr.pem ssl_key = </etc/ssl/private/imaps.iut-tlse3.fr.key userdb { driver = passwd } userdb { driver = prefetch } protocol lda { info_log_path = /var/log/dovecot/dovecot-lda.log log_path = /var/log/dovecot/dovecot-lda-errors.log mail_plugins = acl sieve } protocol imap { imap_id_log = * mail_plugins = acl imap_acl listescape } -- - Laurent Foucher < I U T 'A' Paul Sabatier > laurent.foucher(a)iut-tlse3.fr Enseignant/Chargé de mission Systèmes & Réseau

2 2

[Dovecot] Auth USER lookup failed
by Angel L. Mateo 07 Nov '12

07 Nov '12

Hello, I'm running dovecot 2.1.9 and I'm trying to configure shared folders. So, as described at http://wiki2.dovecot.org/SharedMailboxes/Shared I have configured a namespace like this: namespace { type = shared separator = / prefix = shared/%%u/ location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u subscriptions = no list = yes } In one user (user1) I have configured ACLs so another one (user2) has access to a folder. Now, I want to susbscribe user2 to this folder. The problem I have is that whenever I try to list folders for this user (running thunderbird client) I get a panic and an error in the dovecot server (I have attached the complete log). The error says: Nov 6 11:58:56 myotis30 dovecot: auth: Error: userdb(user1): client doesn't have lookup permissions for this user: userdb uid (113246) doesn't match peer uid (14585) (change userdb socket permissions) Nov 6 11:58:56 myotis30 dovecot: auth: Debug: master out: FAIL#0112 Nov 6 11:58:56 myotis30 dovecot: imap(user2): Error: user user1: Auth USER lookup failed Nov 6 11:58:56 myotis30 dovecot: imap(user2): Debug: auth input: Nov 6 11:58:56 myotis30 dovecot: imap(user2): Error: Couldn't create namespace 'shared/' for user user1: userdb didn't return a home directory, but plugin setting quota used it (%h): dict:User quota::file:%h/Maildir/dovecot.quota It seems that imap process running for user2 is trying to a user lookup that fails. So I have manually tried it root@myotis30:/etc/dovecot/conf.d# sudo -u user2 doveadm user user2 userdb: user2 home : <homeDirectory> uid : 14585 gid : 404 root@myotis30:/etc/dovecot/conf.d# sudo -u user2 doveadm user user1 doveadm(user2): Error: user user1: Auth USER lookup failed doveadm(user2): Error: userdb lookup failed for user1 I have checked the socket permissions, but they are 0666 (if I'm looking the right socket): root@myotis30:/etc/dovecot/conf.d# ls -l /var/run/dovecot/auth-userdb srwxrwxrwx 1 dovecot root 0 nov 6 11:43 /var/run/dovecot/auth-userdb In fact, I have tried to put all sockets with permissions 0666 and 0777, but the error persists. Any idea? -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868889150 Fax: 868888337

2 1

[Dovecot] LDAP congestion
by Bernhard Schmidt 07 Nov '12

07 Nov '12

Hello, I've been asked to have a look at a misbehaving mail server of some colleagues today where almost all logins where failing or excessively delayed, while the LDAP database itself was pretty fast. They run Dovecot 1.2.11 (yes, I know, stoneage) against an LDAP server run by a 3rd party, auth_bind=yes (required). The problem is that this third party LDAP server delays bindResponse 3 seconds when the password is wrong. A user wanted to login every 2-3 seconds this morning with the wrong password, which effectively killed the system because the LDAP connection was mostly stalled waiting for the auth timeout. >From a previous discussion with Timo I know that bindRequests cannot be parallelized in LDAP, so the problem does not come completely unexpected. Other than removing the failure delay in the LDAP server, is there anything one can do? If there is any change in newer Dovecot versions about that please tell me so I can encourage them to upgrade, but I haven't seen anything in the changelog. Any way to get several LDAP workers/connections for passdb in parallel? Thanks, Bernhard

2 1

[Dovecot] "starting" dovecot
by Dave Abrahams 07 Nov '12

07 Nov '12

My system never issues the "dovecot start" command. I do, however, run /usr/local/libexec/dovecot/imap on port 9xxx. I talk to the server through port 9xxx and through the preauth tunnel. Is this arrangement OK? Are there some things that will only work if "dovecot" is invoked? Thanks, -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost

3 5

[Dovecot] Indexing problems
by Dave Abrahams 07 Nov '12

07 Nov '12

It looks like something is going very wrong here. Any advice? --8<---------------cut here---------------start------------->8--- $ doveadm -vvvD index '*' doveadm(dave): Debug: Loading modules from directory: /usr/local/lib/dovecot doveadm(dave): Debug: Module loaded: /usr/local/lib/dovecot/lib20_fts_plugin.so doveadm(dave): Debug: Module loaded: /usr/local/lib/dovecot/lib20_zlib_plugin.so doveadm(dave): Debug: Module loaded: /usr/local/lib/dovecot/lib21_fts_lucene_plugin.so doveadm(dave): Debug: Loading modules from directory: /usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm doveadm(dave): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: dlopen(/usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so, 10): Symbol not found: _acl_user_module Referenced from: /usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so Expected in: flat namespace in /usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so (this is usually intentional, so just ignore this message) doveadm(dave): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: dlopen(/usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so, 10): Symbol not found: _expire_set_deinit Referenced from: /usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so Expected in: flat namespace in /usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so (this is usually intentional, so just ignore this message) doveadm(dave): Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: dlopen(/usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so, 10): Symbol not found: _quota_user_module Referenced from: /usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so Expected in: flat namespace in /usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so (this is usually intentional, so just ignore this message) doveadm(dave): Debug: Module loaded: /usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib10_doveadm_zlib_plugin.so doveadm(dave): Debug: Module loaded: /usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib20_doveadm_fts_lucene_plugin.so doveadm(dave): Debug: Module loaded: /usr/local/Cellar/dovecot/2.1.9/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so doveadm(dave): Debug: Effective uid=501, gid=20, home=/Users/dave doveadm(dave): Debug: Namespace inbox: type=private, prefix=, sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:/Users/dave/Library/Data/LocalIMAP/mdbox doveadm(dave): Debug: fs: root=/Users/dave/Library/Data/LocalIMAP/mdbox, index=, control=, inbox=, alt= doveadm(dave): Debug: Namespace : Using permissions from /Users/dave/Library/Data/LocalIMAP/mdbox: mode=0700 gid=-1 doveadm(dave): Info: [Gmail].All: Cache is already up to date doveadm(dave): Info: [Gmail].All Mail: Caching mails seq=2..231746 8000/231745Assertion failed: (numDocsInStore*8 == directory->fileLength( (docStoreSegment + "." + IndexFileNames::FIELDS_INDEX_EXTENSION).c_str() )), function closeDocStore, file /tmp/clucene-gmYE/src/core/CLucene/index/DocumentsWriter.cpp, line 210. Abort trap: 6 cone:local dave$ --8<---------------cut here---------------end--------------->8--- -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost

2 1

[Dovecot] Modifying mailbox GUIDs?
by Faheem Patel 07 Nov '12

07 Nov '12

Greetings all, I can view a mailbox's GUID like so: doveadm mailbox status -u guid However, how may I *modify* a mailbox GUID? Can this be done using doveadm or some other tool? If not, how may I go about modifying the dovecot.mailbox.log (where I assume GUID data is stored)? My specific use case has to do with me wanting to modify an existing mailbox's GUID so that its messages are mirrored into a folder of the same name using "dsync mirror". (As we know, dsync utilizes GUIDs to determine mailbox uniqueness) Thanks! -- - Faheem

2 2

[Dovecot] Error: Internal quota calculation error
by Micah Anderson 07 Nov '12

07 Nov '12

Hello, I'm using 2.1.7 with seive and mysql quotas. We had an outage the other day where the database server where quotas are stored was not available for a short period of time. In dovecot land, the following types of errors occured in that scenario: Oct 26 22:19:01 grosbeak dovecot: lda(example(a)riseup.net): Error: Internal quota calculation error Oct 26 22:19:01 grosbeak dovecot: lda(example(a)riseup.net): Error: sieve: msgid=<20122132765181x.ABCCE457(a)example.com>: failed to store into mailbox 'Trash': Internal error occurred. Refer to server log for more information. [2012-10-26 22:19:01] Oct 26 22:19:01 grosbeak dovecot: lda(example(a)riseup.net): Error: sieve: script /maildir/e/example/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /maildir/e/example/.dovecot.sieve.log may reveal additional details) I expect that there would be quota calculation errors as dovecot could not reach the database server, but what worried me was the 'failed to store into mailbox' message from sieve. The 'Trash' mailbox in this particular seive script is the correct location for the message to be filed into, but the worrisome message is the 'failed with unsuccessful implicit keep'. I looked through all the message-ids that reported this error and I found that the messages were properly delivered in the end, so this might be some issue interacting between sieve, dovecot and quota and just causing a scary message that can be ignored? thanks for any information you can provide, dovecot is great! micah --

2 1

[Dovecot] backtrace for non-existant %{ldap:attr} on login
by Steffen Kaiser 07 Nov '12

07 Nov '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm fetching the user and auth data from LDAP, this is the string: pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,mailUidNumber=userdb_uid,mailGidNumber=userdb_gid,mailLocationDovecot=userdb_mail,uid=userdb_user,=userdb_quota_rule=*:bytes=%{ldap:mailQuotaBytes}, =userdb_quota_rule2=Trash:bytes=+%{ldap:mailQuotaBytesTrash} If mailQuotaBytesTrash or mailQuotaBytes is not present, the LOGIN process does not work: 1 login user pwd 1 NO [UNAVAILABLE] Temporary authentication failure. [mailsrv2:2012-10-31 08:56:51] * OK Waiting for authentication process to respond.. If I add those two attributes, the user can login successfully. dovecot-2.1.10/sbin/dovecot --version 2.1.10 (9cdeab12f3e1) The log entries: 2012-10-31 09:56:51 auth: Panic: pool_data_stack_realloc(): stack frame changed 2012-10-31 09:56:51 auth: Error: Raw backtrace: /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(+0x4857a) [0x7f2c0528c57a] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(+0x485c6) [0x7f2c0528c5c6] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f2c0525feaf] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(+0x58f2e) [0x7f2c0529cf2e] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(+0x442f5) [0x7f2c052882f5] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(buffer_get_space_unsafe+0x68) [0x7f2c05288728] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(str_vprintfa+0x6d) [0x7f2c052a796d] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(str_printfa+0x88) [0x7f2c052a7ac8] -> dovecot2.1/auth [0 wait, 1 passdb, 0 userdb]() [0x42682e] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(var_expand_with_funcs+0x6fb) [0x7f2c052ac48b] -> dovecot2.1/auth [0 wait, 1 passdb, 0 userdb](db_ldap_result_iterate_next+0x12f) [0x42734f] -> dovecot2.1/auth [0 wait, 1 passdb, 0 userdb]() [0x428974] -> dovecot2.1/auth [0 wait, 1 passdb, 0 userdb]() [0x428f5f] -> dovecot2.1/auth [0 wait, 1 passdb, 0 userdb]() [0x4282a1] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f2c05298756] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9f) [0x7f2c0529978f] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f2c052986f8] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f2c052840d3] -> dovecot2.1/auth [0 wait, 1 passdb, 0 userdb](main+0x376) [0x41bba6] -> /lib/libc.so.6(__libc_start_main+0xfd) [0x7f2c04449c8d] -> dovecot2.1/auth [0 wait, 1 passdb, 0 userdb]() [0x40cf89] 2012-10-31 09:56:51 auth: Fatal: master: service(auth): child 15865 killed with signal 6 (core dumps disabled) 2012-10-31 09:56:51 imap-login: Warning: Auth connection closed with 1 pending requests (max 0 secs, pid=15869, EOF) - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUJDqe2oxLS8a3A9mAQI+YQf/Qd4IIeM35Hmmpl1IMcQwJFK4854G5Dku yK+GsWhE2gxI6KaLO6DSI/kpN79qhQRkHsUAHzoPiZ7kQpZprNaEP/CIPkTzw//i HyC2Odpfa8fWUOqtH5Cp6X5spF6hQa4mmQyzgXguF9bdjZkNu4vQ78wRuQGG4eHi BOkNL0b93DsN3NSIoXDpiAiJn1aleTLe7mYkfsGewjb+AN+FpR4hLbf32yRRn8J0 Fkn8agEijixGMXEBD4ZprTbX9NbUr92YPfRycMnA2A00MUUlv/iKlqXRpMLafRjL bnHL/QE80xHoKKJUR96/RjruciIolAtlyYvhTU9ibRpLYm5Hcd9bZg== =iPvg -----END PGP SIGNATURE-----

2 1

[Dovecot] copymail deleted
by Christian Rößner 07 Nov '12

07 Nov '12

Hi, I had enabled an option in dovecot. mail_attachment_dir = /var/mail/virtual/copymail/attachments After a while I checked /var/mail/virtual and did some cleanup. I did not remember that copymail was specified in dovecot and erased it. Oct 30 10:56:05 mx0 dovecot: imap(hidden): Error: file_istream.stat(/var/mail/virtual/copymail/attachments/6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a0400002cb72ff6) failed: No such file or directory Oct 30 10:56:05 mx0 dovecot: imap(hidden): Error: istream-concat: Failed to get size of stream /var/mail/virtual/copymail/attachments/6a/50/6a506530265ef7c9feb396410eaf6946036e9a79-b034401e794009503a0400002cb72ff6 Oct 30 10:56:05 mx0 dovecot: imap(hidden): Error: read() failed: Invalid argument (FETCH for mailbox INBOX UID 196) Oct 30 10:56:05 mx0 dovecot: imap(hidden): Disconnected: Internal error occurred. Refer to server log for more information. [2012-10-30 10:56:05] in=150 out=950 I have Bacula and have restored most of the stuff, but obviously not all files. That is not too important. But I do not know, how to tell dovecot that it may "forget" about files that produce a "No such file or directory" error. Can I do some "rescan/rebuild" in dovecot? Kind regards -Christian Rößner -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich

2 5

[Dovecot] how to best import Evolution/Thunderbird mail into dovecot?
by Christoph Anton Mitterer 07 Nov '12

07 Nov '12

Hi. I'm migrating all my mail archive (some 60 GB) from Evolution (which is really a broken piece of software) into dovecot. Now I face the problem how to do this best... Evolution (which is still a old 2.32.x version) itself uses mbox files, in a special hierarchical structure to allow subfolders and that like. It also stores it's own status info in X-Evolution and X-Evolution-Source mail headers. Unfortunately,... much of the mail was earlier from a Thunderbird installation, which uses it's own status headers (X-Mozilla*) that were not recognised by Evolution. I have no idea which mbox subformat was always used throughout the different programs and versions... 1) Any way to check for that? To make things worse... Thunder(burden) seems to have used a modified From_ line syntax... "^From -<address> <date>$" Ideally I'd like migrate all mail into dovecot (for storage reasons again, mbox) retaining the different status flags (read, forwarded, etc.) and getting rid of the proprietary headers (of course only when they were. First thing I tried was to simply copy mail within Evolution (i.e. dragging&dropping it from the local folders to the IMAP folders from dovecot). - that preserves the status from Evolution, but doesn't restore that from Thunderbird - it clutters up the information of all From_ lines... "<address> <date>" becomes "<address of my default evolution account> <now>" - neither does it handle the special Thunderbird From_ lines - neither does it remove the Thunderbird or the X-Evolution-Source headers - if Evolution has already had corrupted index files (and this is extremely likely... as it happens even immediately during recreating all of them)... so I may loose mail So my idea was that I need a program that: - can parse all the different mbox formats (those that use the quoted ">From" style and those that use Conent-Length) - can differentiate message headers from body (so that I can drop the proprietary headers and replace them by what dovecot uses as headers) - must of course understand multiline message headers 2) Any idea for a tool like that? The meaning of the X-Evolution and X-Mozilla* headers are easy to find on the web.... so I can convert them. So I basically "just" need a tool that parses all kinds of mbox formats... allow me to drop/add headers... and spits out the rest unmodified. 3) dovecot uses some special headers like X-UID and X-IMAPD... will it create these on it's own, the first time it processes the new mbox file? I mean these headers won't be there after creation. 4) Should I drop out (during) conversion... any other mail headers.. that dovecot uses as it's own? Thanks, Chris.

6 13

Re: [Dovecot] Android ICS stock client and IMAP Capability issue.
by Massimiliano Cianelli 07 Nov '12

07 Nov '12

Hello, My phone: Android ics 4.1.2 on galaxy nexus. And yes, stock mean the default client that come with the os in IMAP mode. I already know about that configuration parameter, but it will display two time namespace in postlogin capabilities, and so I like much more to adjust the source code to fix the issue. Yes there is k9 but I didn't like it too much, I prefer the stock client and is much important to keep compatibility with stock client then user-installed client. About the issue on Google code, there is thr issue on google code... but Google is a lot slow in fixing those things. http://code.google.com/p/android/issues/detail?id=1811 In a few hour I'll update the issue noticing where is hidden the problem. Regards Sent from Galaxy Nexus Robert Schetterer <rs(a)sys4.de> ha scritto: >Am 06.11.2012 07:08, schrieb Ben Morrow: >> At 6AM +0100 on 6/11/12 you (Massimiliano Cianelli) wrote: >>> Hi, >>> >>> My setup: >>> Dovecot 2 latest, installed to replace courrier IMAP, and off course >>> configured with the dot separator and all folder under INBOX.*. >>> >>> The problem: >>> My phone was driving me mad during the test, due that it will only >>> recognize Inbox. >>> >>> How found the solution: >>> I've started sniffing IMAP traffic on my server and ended up with one >>> difference: >>> On courier it ask for namespace, on dovecot it won't. >>> >>> I gives a better look, and noticed that courier show namespace >>> capability on prelogin banner, adding it too solved the problem. >>> >>> Reason: >>> Android ICS stock client seems do not honor the capability gived after >>> the login. >> >> See http://wiki2.dovecot.org/Upgrading/2.0?highlight=%28capability%29 ; >> you need to set imap_capability and/or get your client fixed. >> >> Ben >> > >Hi, first ,what is the exact meaning of > >"Android ICS stock client" > >do you mean default included email client in standard android in imap >mode, when yes, which version of Android , i like to test my own >however is there changelog/code etc at google for this behave? > >conf example > ># Override the IMAP CAPABILITY response. If the value begins with '+', > # add the given capabilities on top of the defaults (e.g. +XFOO XBAR). > #imap_capability = > >setting stuff here might be complex , or lead to trouble with other >clients, if setting this might fix problems ,with clients it should be >advised in the wiki/example-conf and/or Timo > >or the other way ,for massive used clients there should be >a seperate workaround section in the conf > >But fixing behave clients should be prime option anyway > >Meanwhile use K9mail in Android as best free option in imap mode servers > >Best Regards >MfG Robert Schetterer > >-- >[*] sys4 AG > >http://sys4.de, +49 (89) 30 90 46 64 >Franziskanerstraße 15, 81669 München > >Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 >Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer >Aufsichtsratsvorsitzender: Joerg Heidrich

2 1

[Dovecot] LMTP benefit vs LDA
by Davide 07 Nov '12

07 Nov '12

Hi to all, my question is what is benefit implementing LMTP service replacing LDA i have dovecot 2.1.8 with vpoipmail+qmail and about 500 users now i'm using LDA and i'm interested on LMTP service. Thanks in advance -- */Davide Marchi /Teorema Ferrara Srl /(Tel: /**/+39 0532 783161)/**/ (Fax: +/**/39 0532 783368/**/)/**//**/ /**//**/Davide.Marchi(a)mail.cgilfe.it <mailto:davide.marchi@mail.cgilfe.it?subject=Info> /CONFIDENZIALITA’ *** Questo messaggio, inclusi gli eventuali allegati, è indirizzato solo ai destinatari e può contenere informazioni riservate e confidenziali. Se avete ricevuto il messaggio senza esserne un destinatario, siete pregati di non utilizzare, copiare o distribuire questo messaggio o i suoi allegati. Se avete ricevuto il messaggio per errore, siete pregati di cancellarlo dal vostro sistema, assieme a tutti gli allegati, e di informare immediatamente il mittente,sia ai sensi dell'art. 616 c.p., sia ai sensi del DL n. 196/03. *CONFIDENTIALITY*** This message and any attachments are intended only for the use of the addressee(s) and may contain information that is privileged and/or confidential. If the reader of the message is not the intended recipient(s) or an authorized representative of the intended recipient(s), please do not use, copy, distribute this email or its attachments or take action based on them. If you have received this communication in error, please notify us immediately by email and delete the message and any attachments from your system. *Teorema FerraraSrl - Via Spronello, 7 - 44121 Ferrara Italia - P. IVA 01244490387** P**S**tampa questo messaggio solo se veramente necessario, pensa alla natura! - Please consider whether it is necessary to print this e-mail*

4 4

[Dovecot] sieve
by Christian Rößner 06 Nov '12

06 Nov '12

Hi, is there a sieve option that can reject a mail directly without creating a new mail and sending that out? I know about reject "Reject message goes here"; but I am looking for a mechanism that can reject Mail. Postfix can use reject_unverified_recipient to connect to LMTP and ask if a mail would successfully be enqueued and will return the status gotten from the LMTP server if not. Chances are high that the mechanism would work, too, if Dovecot would know about the sieve rule, while getting a connection on LMTP. Does Dovecot know all rules at this point or is sieve handled after the mail has already been accepted? Kind regards -Christian Rößner -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich

8 10

[Dovecot] doveadm import doesn't work
by Andreas Thomsen 06 Nov '12

06 Nov '12

Hello, we are running dovecot 2.0.4 on openSuse 11.2. mailboxes are in mdbox-format on local filesystem. we had a powerfailure resulting in many corrupted files and i had to restore some mailboxes. as descibed in wiki, i tried : doveadm import -u <username> mdbox:/path/to/backup/<username>/mdbox INBOX all or doveadm import -u <username> mdbox:/path/to/backup/<username>/mdbox mdbox:/path/to/mailbox/<username>/mdbox all all i get is : usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] altmove [-u <user>|-A] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] <search query> fetch [-u <user>|-A] <fields> <search query> force-resync [-u <user>|-A] <mailbox> help <cmd> kick [-a <anvil socket path>] [-f] <user mask>[|]<ip/bits> log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [<ip/bits>] purge [-u <user>|-A] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] quota get|recalc reload search [-u <user>|-A] <search query> stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] who [-a <anvil socket path>] [-1] [<user mask>] [<ip/bits>] any idea, whats the problem? kind regards Andreas Thomsen -- DAD Deutscher Adressdienst GmbH Alter Wall 65 20457 Hamburg Postfach 11 35 58 20435 Hamburg Deutschland Tel. 0049 (0)40 7511990 Fax 0049 (0)40 75119911 Amtsgericht Hamburg HRB 88115 Geschäftsführerin: Daniela Kunst Steuernummer 48/714/02030 Ust-IdNr. DE813739877

2 2

[Dovecot] Android ICS stock client and IMAP Capability issue.
by Massimiliano Cianelli 06 Nov '12

06 Nov '12

Hi, My setup: Dovecot 2 latest, installed to replace courrier IMAP, and off course configured with the dot separator and all folder under INBOX.*. The problem: My phone was driving me mad during the test, due that it will only recognize Inbox. How found the solution: I've started sniffing IMAP traffic on my server and ended up with one difference: On courier it ask for namespace, on dovecot it won't. I gives a better look, and noticed that courier show namespace capability on prelogin banner, adding it too solved the problem. Reason: Android ICS stock client seems do not honor the capability gived after the login. Request: Maybe is possible to put namespace capability in prelogin banner for the next version? That will solve trouble with a setup like the mine and android stock email client. Thank you, Best regards Sent from Galaxy Nexus

3 2

[Dovecot] Security precautions for remote clients
by Roman Gelfand 06 Nov '12

06 Nov '12

Where can I find something like remote client secure dovecot best practices or, perhaps, if there is not many, if you could list major configuration/setup points. Thanks in advance

2 1

[Dovecot] Quota
by Christian Rößner 05 Nov '12

05 Nov '12

Hi, is it possible to ask Dovecot for a users quota by talking to the Dovecot server over TCP? I know about doveadm quota -u <user>, but I would like to know, if I can query for that over a network connection (on the Postfix ML they suggested writing a policy service that checks quota. Postfix is not always on the same server as Dovecot is). Does the LMTP protocol give that information somehow? I am not so familiar with LMTP. Or some Unix-Socket to query that could also be configured as inet_listener? Thanks in advance -Christian Rößner -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich

3 5

[Dovecot] maildir S= and W=
by Christoph Anton Mitterer 05 Nov '12

05 Nov '12

Hi. Even new mails delivered by my MDA don't get the ,S= and ,W= fields set... (but when I "upload" a mail via IMAP to dovecot, they are set) Is there some place in dovecot where I need to enable this? Or would it be the MDA that has to calculate and set this already when placing a file in ./new? Thanks, Chris.

2 6

Re: [Dovecot] LMTP benefit vs LDA
by Joseph Tam 04 Nov '12

04 Nov '12

Daniel Parthey writes: > Davide wrote: >> my question is what is benefit implementing LMTP service replacing >> LDA i have dovecot 2.1.8 with vpoipmail+qmail and about 500 users >> now i'm using LDA and i'm interested on LMTP service. > > with LMTP... > * you dont need to care about mail filesystem permissions > * you can use dovecot lmtp proxy and/or director > * you don't need to spawn a new process for each message One of the (potential) benefit is that a LMTP, because it can handle multiple recipients, has the ability to optimize I/O (or storage?) by using hardlinking to a single copy of a message (deduping). I don't know if Dovecot takes advantage of this in any way though. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] dovecot default service
by mican zhang 03 Nov '12

03 Nov '12

i install dovecot 2 and when i try ps auxw|grep "dovecot" i just get only 5processes, root 21861 0.0 0.0 14884 980 ? Ss 16:53 0:00 /usr/local/sbin /dovecot dovecot 21862 0.0 0.0 12740 968 ? S 16:53 0:00 dovecot/anvil root 21863 0.0 0.0 12872 1088 ? S 16:53 0:00 dovecot/log root 21865 0.0 0.0 15356 1468 ? S 16:53 0:00 dovecot/config root 21945 0.0 0.0 61148 800 pts/0 S+ 17:04 0:00 grep dovecot , my os is redhat 5.4 and i just install like ./configure make &make install i don't what's wrong?i also test on centos 6.2,and result is the same does anyone has the same issue?and what should i do to fix this?

2 3

[Dovecot] sessionid in logout line
by Aleksandar Lazic 03 Nov '12

03 Nov '12

Dear listmembers. I have the following login_log_format_elements = service=%s user=<%u> session=%{session} method=%m rip=%r lip=%l mpid=%e %c %k Maybe I have overseen the config option to add the %{session} also to the logout line. Here a example from my log: ### Nov 3 00:46:43 <HOST> dovecot: imap-login: Login: service=imap, user=<USER>, session=ETV8v4vNfwB/AAAB, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, mpid=14874, TLS, TLSv1.1 with cipher AES256-SHA (256/256 bits) zlib compression Nov 3 00:46:43 external dovecot: imap(USER): Disconnected: Logged out in=15649 out=80199 ### Thanks for help and answers. Best regards Aleks

2 2

Re: [Dovecot] dovecot dimensioning
by mancyborg＠gmail.com 02 Nov '12

02 Nov '12

Hi Javier, yes i see. Storage for now is just a 3tb sata2 hdd, so i guess that write performance is around 100 MB/s What do you think about that ? Thanks and regards, Mike On Thu, 1 Nov 2012 19:55:35 +0100 Javier de Miguel Rodriguez <javierdemiguel-ext(a)us.es> wrote: > > IMHO, fast storage is the main requirement for dovecot. > > > > El 01/11/2012, a las 16:20, "mancyborg(a)gmail.com" <mancyborg(a)gmail.com> escribió: > > > Hi All, first post here, nice to meet you :) > > > > I've been using dovecot + postfix + clamav + spamassassin for years but always with few users. > > > > Now i must build a server for 1500 users, > > they will use various email software (thunderbird, outlook, ..) > > the webmail (i'm not sure if squirrelmail or roundcube) > > and blackberry devices (with the BIS service). > > > > There will be around 1000 domains (virtual_domains) and postfix will read its users and domains from mysql. > > > > Let's say that they will send and receive around 5000 emails per hour (10K in total per hour). > > > > I was thinking to use karspersky server instead of clamav. > > > > I already have the hardware, it is a server with 4 physical cpu (Intel Xeon E5504 @ 2.00GHz) and 24 gb of ram, > > do you think it is enough ? > > > > > > Thanks for supporting, > > regards and have a nice day, > > Mike

3 3

[Dovecot] dovecot dimensioning
by mancyborg＠gmail.com 01 Nov '12

01 Nov '12

Hi All, first post here, nice to meet you :) I've been using dovecot + postfix + clamav + spamassassin for years but always with few users. Now i must build a server for 1500 users, they will use various email software (thunderbird, outlook, ..) the webmail (i'm not sure if squirrelmail or roundcube) and blackberry devices (with the BIS service). There will be around 1000 domains (virtual_domains) and postfix will read its users and domains from mysql. Let's say that they will send and receive around 5000 emails per hour (10K in total per hour). I was thinking to use karspersky server instead of clamav. I already have the hardware, it is a server with 4 physical cpu (Intel Xeon E5504 @ 2.00GHz) and 24 gb of ram, do you think it is enough ? Thanks for supporting, regards and have a nice day, Mike

1 0

Re: [Dovecot] Pigeonhole 3.3 broken against Dovecot 2.1.10
by Daniel L. Miller 01 Nov '12

01 Nov '12

On 31.10.2012 21:23, Daniel L. Miller wrote: > On 31.10.2012 21:16, Daniel L. Miller wrote: > >> On 31.10.2012 > > 04:26, Timo Sirainen wrote: > >>> I think this is a Dovecot bug, fixed > could also do this by adding -lssl -lcrypto manually to the > > installed > dovecot-config and > >> -left:#1010ff 2px solid; margin-left:5px; width:100%">I see > pto" already in the DOVECOT_SSL_LIBS section of > > /usr/local/lib/dovecot/dovecot-config. What should be changed? > > Ok - I > read the patch, and modified the LIBDOVECOT_STORAGE section accordingly. > Same comp> > >> Thought I'd see if I could guess the next fix - added the parms to LIBDOVECOT_LOGIN as well. Seems to have fixed it. Sorry for the multiple posts - it's been a long day. -- Daniel

1 0

Re: [Dovecot] Pigeonhole 3.3 broken against Dovecot 2.1.10
by Daniel L. Miller 01 Nov '12

01 Nov '12

On 31.10.2012 21:23, Daniel L. Miller wrote: > On 31.10.2012 21:16, Daniel L. Miller wrote: > >> On 31.10.2012 > > 04:26, Timo Sirainen wrote: > >>> I think this is a Dovecot bug, fixed > could also do this by adding -lssl -lcrypto manually to the > > installed > dovecot-config and > >> -left:#1010ff 2px solid; margin-left:5px; width:100%">I see > pto" already in the DOVECOT_SSL_LIBS section of > > /usr/local/lib/dovecot/dovecot-config. What should be changed? > > Ok - I > read the patch, and modified the LIBDOVECOT_STORAGE section accordingly. > Same comp> > >> I take that back - it's not exactly the same compile error. Now it references libdovecot-login.so for the undefined SSL references. -- Daniel

1 0

Re: [Dovecot] Pigeonhole 3.3 broken against Dovecot 2.1.10
by Daniel L. Miller 01 Nov '12

01 Nov '12

On 31.10.2012 21:16, Daniel L. Miller wrote: > On 31.10.2012 04:26, Timo Sirainen wrote: > >> I think this is a Dovecot bug, fixed > > by: http://hg.dovecot.org/dovecot-2.1/rev/7d931927e4ac [1][1] > >> You > > could also do this by adding -lssl -lcrypto manually to the installed > dovecot-config and running configure again for pigeonhole. > > I see "-lssl > -lcrypto" already in the DOVECOT_SSL_LIBS section of > /usr/local/lib/dovecot/dovecot-config. What should be changed? Ok - I read the patch, and modified the LIBDOVECOT_STORAGE section accordingly. Same compile error for Pigeonhole after performing a 'make clean' and 'configure'. -- Daniel Links: ------ [1] http://hg.dovecot.org/dovecot-2.1/rev/7d931927e4ac

1 0

[Dovecot] Pigeonhole 3.3 broken against Dovecot 2.1.10
by Daniel L. Miller 01 Nov '12

01 Nov '12

I'm compiling as I normally do. The config line for Dovecot is: configure --with-ldap --with-ssl --with-bzlib --with-zlib --with-stemmer --with-lucene --with-ldap followed by make & make install Then a 'configure' for Pigeonhole, followed by make, yields: libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -o .libs/sieve-dump sieve-dump.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so ../../src/lib-sieve-tool/.libs/libsieve-tool.a /usr/local/lib/dovecot/libdovecot-storage.so /usr/local/lib/dovecot/libdovecot-lda.so -L/usr/local/lib/dovecot /usr/local/lib/dovecot/libdovecot.so -lrt -Wl,-rpath -Wl,/usr/local/lib/dovecot libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -o .libs/sievec sievec.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so ../../src/lib-sieve-tool/.libs/libsieve-tool.a /usr/local/lib/dovecot/libdovecot-storage.so /usr/local/lib/dovecot/libdovecot-lda.so -L/usr/local/lib/dovecot /usr/local/lib/dovecot/libdovecot.so -lrt -Wl,-rpath -Wl,/usr/local/lib/dovecot /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `sk_new_null(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_error(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_peer_certificate(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_load_verify_locations(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_use_PrivateKey(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `DH_free(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_set_ex_data(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_set_tmp_rsa_callback(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_use_certificate(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_alert_desc_string_long(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_ex_data(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_ex_new_index(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_set_client_CA_list(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_get_ext_d2i(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_accept(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_STORE_add_cert(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSLv23_server_method(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `OBJ_txt2nid(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_write(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `sk_num(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `BIO_ctrl_get_write_guarantee(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_set_cipher_list(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `sk_push(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ERR_get_error(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_alert_type_string_long(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_COMP_get_name(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ENGINE_by_id(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `BIO_write(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `i2d_DHparams(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_NAME_ENTRY_get_data(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CIPHER_get_name(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_use_PrivateKey(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_set_info_callback(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_get_subject_name(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ENGINE_init(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ERR_clear_error(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_load_error_strings(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ENGINE_set_default_RSA(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `BIO_free(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CIPHER_get_bits(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_INFO_free(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_STORE_set_flags(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_new(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_NAME_dup(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_NAME_get_index_by_NID(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `d2i_DHparams(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_NAME_get_text_by_NID(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `OPENSSL_add_all_algorithms_noconf(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ENGINE_set_default_DSA(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ENGINE_cleanup(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_NAME_get_entry(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ASN1_STRING_type(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_library_init(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_current_cipher(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_set_cipher_list(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_connect(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ERR_error_string_n(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_STORE_CTX_get_ex_data(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_set_verify(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `BIO_new_bio_pair(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSLv23_client_method(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_use_certificate(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ASN1_STRING_length(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_get_cert_store(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_set_tmp_dh_callback(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ENGINE_set_default_ciphers(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `PEM_read_bio_PrivateKey(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `BIO_new_mem_buf(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_ex_data_X509_STORE_CTX_idx(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `sk_pop_free(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `sk_value(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `GENERAL_NAME_free(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ERR_peek_error(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_version(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `RAND_bytes(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_new(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `BIO_ctrl_pending(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_set_bio(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ASN1_STRING_data(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ENGINE_load_builtin_engines(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `PEM_read_bio_X509(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `EVP_cleanup(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_STORE_add_crl(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `BIO_read(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ENGINE_finish(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_free(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_read(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_NAME_oneline(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_free(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ERR_free_strings(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `EVP_PKEY_free(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_get_current_compression(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_verify_cert_error_string(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_CTX_ctrl(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `ERR_peek_last_error(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `RSA_generate_key(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `SSL_state_string_long(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `PEM_X509_INFO_read_bio(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `DH_generate_parameters(a)OPENSSL_1.0.0' /usr/local/lib/dovecot/libdovecot-storage.so: undefined reference to `X509_free(a)OPENSSL_1.0.0' collect2: ld returned 1 exit status make[3]: *** [sieve-dump] Error 1 make[3]: *** Waiting for unfinished jobs.... -- Daniel

3 4

[Dovecot] Out of memory/Managesieve
by Jim Knuth 31 Oct '12

31 Oct '12

Hello, I have here a problem with managesieve. With the login about webmail (roundcube) comes here in the log: --snip dovecot: managesieve-login: Fatal: pool_system_realloc(4294967296): Out of memory dovecot: managesieve-login: Fatal: master: service(managesieve-login): child 10157 returned error 83 (Out of memory (service managesieve-login { vsz_limit=1024 MB }, you may need to increase it)) --snap I've increased of 2048M and the same above. then with 4096 M happens the following --snip dovecot: managesieve-login: Panic: epoll_ctl(add, 61538840) failed: Bad file descriptor dovecot: managesieve-login: Fatal: master: service(managesieve-login): child 9777 killed with signal 6 (core dumps disabled) --snap How can one solve then this? Any ideas greatly appreciated. Thanks. -- Mit freundlichen Grüßen, with kind regards, Jim Knuth --------- Backup interessiert niemanden - Auf Restore kommt es an!

3 7

[Dovecot] IMAP proxy between Office 365 client/Sun Messaging Server
by John Dalbec 31 Oct '12

31 Oct '12

I would like to be able to migrate messages from existing end-user accounts on Sun Messaging Server to Office 365 using an administrator login and password. Unfortunately the migration tool for Office 365 doesn't support SASL AUTHENTICATE PLAIN login. The online documentation I've found suggests that I should be able to configure dovecot as an IMAP proxy and have it log in to Sun Messaging Server with AUTHENTICATE PLAIN and encode_base64("user\0admin\0adminpw") in response to a login from the Office 365 migration tool. I'd like to configure dovecot to run only the IMAP proxy if possible. I was thinking of setting all accounts to use the same (strong) password in the proxy. Would anyone be willing to share a sample configuration? Thanks, John Dalbec ellucian Luminis system administrator Youngstown State University

2 1

[Dovecot] Unable to get Managesieve working
by Cliff Dunn 31 Oct '12

31 Oct '12

I have Roundcube webmail (v. 0.8.2) running with the managesieve plugin (v. 5.1). I am able to create sieve rules without any problems in Roundcube, but incoming mail is not being processed with the rule I specify. I suspect there is something that isn't configured correctly in dovecot, but unfortunately I am unable to find a resolution online and my very limited knowledge of dovecot isn't allowing me to solve this problem on my own. I am including my dovecot config below. Please keep my knowledge level in mind when suggesting options and let me know if there is any other information I can provide to help troubleshoot the problem. Thanks for any assistance! # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.6 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps managesieve ssl_cert_file: /etc/ssl/certs/postfix.pem ssl_key_file: /etc/ssl/private/postfix.key ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:~/mail:LAYOUT=fs:INBOX=~/mail/ mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve auth default: mechanisms: plain login passdb: driver: pam passdb: driver: pam userdb: driver: passwd userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/mail/sieve

3 5

[Dovecot] Dovecot stops to work - anvil problem
by FABIO FERRARI 31 Oct '12

31 Oct '12

Hi all, we have a problem about anvil, it seems that when we have a high load the dovecot stops to work. Sometimes it is sufficient to make a dovecot reload, but sometimes we have to restart it. These are the lines related to anvil in the dovecot.log: [root@secchia ~]# grep anvil /var/log/dovecot.log | more Oct 26 11:13:55 anvil: Error: net_accept() failed: Too many open files Oct 26 11:14:32 imap-login: Error: net_connect_unix(anvil) failed: Resource temporarily unavailable Oct 26 11:14:32 imap-login: Fatal: Couldn't connect to anvil Oct 26 11:14:33 pop3-login: Error: net_connect_unix(anvil) failed: Resource temporarily unavailable Oct 26 11:14:33 pop3-login: Fatal: Couldn't connect to anvil [...] (many lines like these) Oct 26 12:01:10 pop3-login: Fatal: Couldn't connect to anvil Oct 26 12:01:18 auth: Error: read(anvil-auth-penalty) failed: Connection reset by peer Oct 26 12:01:18 auth: Error: read(anvil-auth-penalty) failed: Connection reset by peer Oct 26 12:01:18 auth: Error: net_connect_unix(anvil-auth-penalty) failed: Connection refused Oct 26 12:01:18 auth: Error: net_connect_unix(anvil-auth-penalty) failed: Connection refused Oct 26 12:01:18 auth: Error: read(anvil-auth-penalty) failed: Connection reset by peer Oct 26 12:01:18 auth: Error: net_connect_unix(anvil-auth-penalty) failed: Connection refused And this is the output of the doveconf -n: [root@secchia ~]# doveconf -n # 2.0.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-308.11.1.el5 x86_64 Red Hat Enterprise Linux Server release 5.8 (Tikanga) xfs auth_cache_size = 1024 auth_cache_ttl = 21600 s auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no hostname = mail.unimore.it info_log_path = /var/log/dovecot.log lda_mailbox_autocreate = yes log_path = /var/log/dovecot.log mail_debug = yes mail_location = maildir:/cl/mail/vhosts/sms.unimo.it/%Ln/Maildir mail_plugins = $mail_plugins quota mailbox_idle_check_interval = 60 s mbox_write_locks = fcntl namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /usr/local/etc/dovecot.masterusers driver = passwd-file master = yes } passdb { args = dovecot driver = pam } plugin { quota = maildir:User quota quota_exceeded_message = Quota exceeded (mailbox is full) quota_rule = *:storage=200MB quota_rule2 = *:messages=100000 quota_rule3 = INBOX.Trash:storage=+100M quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=85%% quota-warning 85 %u quota_warning3 = messages=95%% quota-warning 95 %u quota_warning4 = messages=80%% quota-warning 80 %u setting_name = quota } postmaster_address = postmaster(a)unimore.it quota_full_tempfail = yes service anvil { client_limit = 199999 process_limit = 199999 } service auth { client_limit = 14500 unix_listener auth-userdb { mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 } process_limit = 5000 } service imap { process_limit = 5000 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 } } service pop3 { process_limit = 1024 } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = vmail user = vmail } user = dovecot } ssl_ca = </etc/pki/tls/certs/ca_unimore_tcs.pem ssl_cert = </etc/pki/tls/certs/cert-852-mail.unimore.it-cluster.pem ssl_key = </etc/pki/tls/certs/mailcluster.key userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_ssl = yes protocol lda { mail_plugins = $mail_plugins quota } protocol imap { mail_plugins = $mail_plugins imap_quota } protocol pop3 { mail_plugins = $mail_plugins quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } [root@secchia ~]# And these are the limit settings in the OS: * soft nofile 131072 * hard nofile 131072 Have someone had the same problem? thanks in advance Fabio Ferrari

2 2

[Dovecot] lmtp out of memory - raw backtrace
by Daniel Parthey 31 Oct '12

31 Oct '12

Hi, Our setup: - 4 hosts with director and mailbox instance - delivery via director lmtp into mailbox lmtp - mailbox format: mdbox - storage on NFS - OS: Linux 2.6.32-44-server x86_64 Ubuntu 10.04.4 LTS - Dovecot 2.1.10 - Pigeonhole 0.3.3 We're getting strange "out of memory" lmtp errors/backtrace with dovecot 2.1.10 accompanied by high load caused caused by a lot of lmtp deliveries to one user. First action would be to increase vsz_limit to a higher value, but I just want to make sure there is no bug - before blindly increasing this limit. I think it should not crash and corrupt mdbox, even if memory limit is reached: Oct 29 20:14:56 10.129.3.249 dovecot: lmtp(26698, user1(a)example.org) Fatal: pool_system_realloc(16777216): Out of memory Oct 29 20:14:56 10.129.3.249 dovecot: lmtp(26698, user1(a)example.org) Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x4271a) [0x7f6dcbae971a] -> /usr/lib/dovecot/libdovecot.so.0(+0x42766) [0x7f6dcbae 9766] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f6dcbabd158] -> /usr/lib/dovecot/libdovecot.so.0(+0x53690) [0x7f6dcbafa690] -> /usr/lib/dovecot/libdovecot.so.0(+0x3e6f5) [0x7f6dcbae56f5] -> /usr/lib/dove cot/libdovecot.so.0(buffer_write+0x7c) [0x7f6dcbae5e7c] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xa8033) [0x7f6dcbdda033] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_record_map_move_to_private+0x3 c) [0x7f6dcbdda4ec] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_get_atomic_map+0x18) [0x7f6dcbde9c88] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb7cf9) [0x7f6dcbde9cf9] -> /usr/lib/dovecot/lib dovecot-storage.so.0(mail_index_sync_record+0x7e6) [0x7f6dcbdea626] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x23c) [0x7f6dcbdeae4c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_m ap+0xa8) [0x7f6dcbddc2b8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb42da) [0x7f6dcbde62da] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb458a) [0x7f6dcbde658a] -> /usr/lib/dovecot/libdovecot-storage.so.0( mail_index_sync_begin_to+0x4f) [0x7f6dcbde6ecf] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin+0x1e) [0x7f6dcbde6f4e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_map_atomic_lock+0x5e) [0x 7f6dcbd6115e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_transaction_save_commit_pre+0x46) [0x7f6dcbd64fb6] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x9d4f3) [0x7f6dcbdcf4f3] -> /usr/lib/dovecot/libdov ecot-storage.so.0(mail_index_transaction_commit_full+0x9f) [0x7f6dcbddd97f] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_transaction_commit+0x8a) [0x7f6dcbdcf18a] -> /usr/lib/dovecot/modules/lib10_quota_plug in.so(+0xba7f) [0x7f6dca4eca7f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x3d) [0x7f6d Oct 29 20:14:56 10.129.3.249 dovecot: lmtp(26698, user1(a)example.org) Fatal: master: service(lmtp): child 26698 returned error 83 (Out of memory (service lmtp { vsz_limit=256 MB }, you may need to increase it)) Oct 30 01:15:49 10.129.3.249 dovecot: lmtp(17927, user1(a)example.org) Error: mmap_anon(216690688) failed: Cannot allocate memory Oct 30 01:15:49 10.129.3.249 dovecot: lmtp(17927, user1(a)example.org) Error: mmap_anon(216690688) failed: Cannot allocate memory Oct 30 10:32:27 10.129.3.249 dovecot: mailbox: mail: imap(user1(a)example.org): <nURUbUPNBgAKgQPI>: Error: Corrupted dbox file /mail/dovecot/example.org/user1/mail/storage/m.3577 (around offset=1844402): EOF reading msg header (got 0/30 bytes) Oct 30 10:33:44 10.129.3.249 dovecot: mailbox: mail: imap(user1(a)example.org): <ZZ0pYkPN+wAKgQPp>: Error: /mail/dovecot/example.org/user1/mail/mailboxes/Lists/Cron/dbox-Mails/dovecot.index reset, view is now inconsistent Oct 30 10:33:44 10.129.3.249 dovecot: mailbox: mail: imap(user1(a)example.org): <CcYCYkPNkAAKgQPV>: Error: /mail/dovecot/example.org/user1/mail/mailboxes/Lists/postfix/dbox-Mails/dovecot.index reset, view is now inconsistent Oct 30 10:33:44 10.129.3.249 dovecot: mailbox: mail: imap(user1(a)example.org): <t+gLYkPNVQAKgQPV>: Error: /mail/dovecot/example.org/user1/mail/mailboxes/Lists/Dovecot/dbox-Mails/dovecot.index reset, view is now inconsistent Oct 30 10:33:46 10.129.3.249 dovecot: mailbox: mail: imap(user1(a)example.org): <YElVbUPNKwAKgQO/>: Error: /mail/dovecot/example.org/user1/mail/mailboxes/INBOX/dbox-Mails/dovecot.index reset, view is now inconsistent Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21404, user1(a)example.org) Error: Timeout (180s) while waiting for lock for transaction log file /mail/dovecot/example.org/user1/mail/storage/dovecot.map.index.log Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21405, user1(a)example.org) Error: Timeout (180s) while waiting for lock for transaction log file /mail/dovecot/example.org/user1/mail/storage/dovecot.map.index.log Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21410, user1(a)example.org) Error: Timeout (180s) while waiting for lock for transaction log file /mail/dovecot/example.org/user1/mail/storage/dovecot.map.index.log Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21419, user1(a)example.org) Error: Timeout (180s) while waiting for lock for transaction log file /mail/dovecot/example.org/user1/mail/storage/dovecot.map.index.log Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21404, user1(a)example.org) Error: 2ZCXNsuej1CcUwAAk4785w: sieve: mailbox: deliver: session=<session}> msgid=<201210300932.q9U9URHO029943(a)common.example-hosting.net> from=MAILER-DAEMON(a)common.example-hosting.net: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2012-10-30 10:32:59] Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21404, user1(a)example.org) Error: 2ZCXNsuej1CcUwAAk4785w: sieve: script /mail/dovecot/example.org/user1/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /mail/dovecot/example.org/user1/.dovecot.sieve.log may reveal additional details) Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21405, user1(a)example.org) Error: PFBjN8uej1CdUwAAk4785w: sieve: mailbox: deliver: session=<session}> msgid=<201210300932.q9U9URHP029943(a)common.example-hosting.net> from=MAILER-DAEMON(a)common.example-hosting.net: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2012-10-30 10:32:59] Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21410, user1(a)example.org) Error: spYhE82ej1CiUwAAk4785w: sieve: mailbox: deliver: session=<session}> msgid=<201210300932.q9U9URHQ029943(a)common.example-hosting.net> from=MAILER-DAEMON(a)common.example-hosting.net: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2012-10-30 10:33:01] Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21419, user1(a)example.org) Error: sOscMs2ej1CrUwAAk4785w: sieve: mailbox: deliver: session=<session}> msgid=<201210300932.q9U9URHS029943(a)common.example-hosting.net> from=MAILER-DAEMON(a)common.example-hosting.net: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2012-10-30 10:33:01] Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21410, user1(a)example.org) Error: spYhE82ej1CiUwAAk4785w: sieve: script /mail/dovecot/example.org/user1/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /mail/dovecot/example.org/user1/.dovecot.sieve.log may reveal additional details) Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21405, user1(a)example.org) Error: PFBjN8uej1CdUwAAk4785w: sieve: script /mail/dovecot/example.org/user1/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /mail/dovecot/example.org/user1/.dovecot.sieve.log may reveal additional details) Oct 30 10:36:16 10.129.3.249 dovecot: lmtp(21419, user1(a)example.org) Error: sOscMs2ej1CrUwAAk4785w: sieve: script /mail/dovecot/example.org/user1/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /mail/dovecot/example.org/user1/.dovecot.sieve.log may reveal additional details) Oct 30 10:36:46 10.129.3.249 dovecot: lmtp(21538, user1(a)example.org) Error: Timeout (180s) while waiting for lock for transaction log file /mail/dovecot/example.org/user1/mail/storage/dovecot.map.index.log Oct 30 10:36:46 10.129.3.249 dovecot: lmtp(21538, user1(a)example.org) Error: +jXqE+uej1AiVAAAk4785w: sieve: mailbox: deliver: session=<session}> msgid=<201210300933.q9U9URHi029943(a)common.example-hosting.net> from=MAILER-DAEMON(a)common.example-hosting.net: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2012-10-30 10:33:31] Oct 30 10:36:46 10.129.3.249 dovecot: lmtp(21538, user1(a)example.org) Error: +jXqE+uej1AiVAAAk4785w: sieve: script /mail/dovecot/example.org/user1/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /mail/dovecot/example.org/user1/.dovecot.sieve.log may reveal additional details) Oct 30 10:36:46 10.129.3.249 dovecot: lmtp(21543, user1(a)example.org) Error: Timeout (180s) while waiting for lock for transaction log file /mail/dovecot/example.org/user1/mail/storage/dovecot.map.index.log Oct 30 10:36:46 10.129.3.249 dovecot: lmtp(21543, user1(a)example.org) Error: CxDMM+uej1AnVAAAk4785w: sieve: mailbox: deliver: session=<session}> msgid=<201210300933.q9U9URHl029943(a)common.example-hosting.net> from=MAILER-DAEMON(a)common.example-hosting.net: failed to store into mailbox 'INBOX': Internal error occurred. Refer to server log for more information. [2012-10-30 10:33:31] Oct 30 10:36:46 10.129.3.249 dovecot: lmtp(21543, user1(a)example.org) Error: CxDMM+uej1AnVAAAk4785w: sieve: script /mail/dovecot/example.org/user1/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /mail/dovecot/example.org/user1/.dovecot.sieve.log may reveal additional details) Regards Daniel -- https://plus.google.com/103021802792276734820

2 1

[Dovecot] POP3 Proxy : user format not accepted
by Christian Gregoire 30 Oct '12

30 Oct '12

Hello, I want to use Dovecot as a POP3 proxy (http://wiki.dovecot.org/HowTo/ImapProxy) All is working fine on my sample platform, except that I have plenty (several thousands) of users that login using local_part#domain, instead of local_part@domain, which is an old setting on my POP3 server. And in that case, Dovecot returns 'Authentication failed'. Here is my proxy table : mysql> select * from tbl_proxy; +--------------------+-------------+--------------------+ | user | host | destuser | +--------------------+-------------+--------------------+ | christian(a)mydom.fr | 10.10.100.1 | christian(a)mydom.fr | | christian#mydom.fr | 10.10.100.1 | christian(a)mydom.fr | +--------------------+-------------+--------------------+ If I login on the Dovecot proxy with the '@' version, everything is fine : root : ~> telnet 10.10.100.24 110 Trying 10.10.100.24... Connected to 10.10.100.24 (10.10.100.24). Escape character is '^]'. +OK Dovecot ready. user christian(a)mydom.fr +OK pass azerty42 +OK christian#mydom.fr has 3 messages (3561 octets) And MySQL logs show the query : 121030 12:55:28 3 Query SELECT NULL AS password, host, destuser, 'Y' AS nologin, 'Y' AS nodelay, 'Y' AS proxy, 'Y' AS nopassword FROM tbl_proxy WHERE user = 'christian(a)mydom.fr' If I login on the Dovecot proxy with the '#' version, it fails : root : ~> telnet 10.10.100.24 110 Trying 10.10.100.24... Connected to 10.10.100.24 (10.10.100.24). Escape character is '^]'. +OK Dovecot ready. user christian#mydom.fr +OK pass azerty42 -ERR Authentication failed. And nothing shows up the the MySQL logs. If I login directly on the POP server with the same credentials, no problem : root : ~> telnet 10.10.100.1 110 Trying 10.10.100.1... Connected to 10.10.100.1 (10.10.100.1). Escape character is '^]'. +OK Welcome to POP3 Server V 2.06. Authenticate yourself. user christian#mydom.fr +OK Password required for christian#mydom.fr pass azerty42 +OK christian#mydom.fr has 3 messages (3561 octets) Any idea ? Is the '#' not internally supported in the user login by Dovecot ? Thanks in advance. Christian

2 2

[Dovecot] Dovecot does not update acl_shared_dict file
by Chris Smith 30 Oct '12

30 Oct '12

Hi all, Firstly, thanks for all your effort with this software. Much appreciated. I am having a slight issues trying to enable reading of other users mailboxes. The docs are a little sparse for those that aren't mailadmin heros, I wonder if anyone could please help me see where I am going wrong. I would like to allow some users to list and read the mailboxes of others. E.g: When User1 logs in, they are presented with a list of their own folders, and those of User2, User3, etc to which they have (e.g. read/list) access I followed the instructions on the wiki (for Version 1.X)- there are two concepts here: 1. Grant some [e.g. list/read] access on a mailbox folder to a particular user 2. Enable the acl_shared_dict to allow dovecot to track (and display to IMAP clients) the folders to which they have access. This will take the form of a BDB file: /var/lib/dovecot/shared-mailboxes.db This file can only be updated by using the SETACL command. *This is where I have the problem*. The SETACL command does nothing. No matter how hard I try, I cannot get dovecot to update this file. The only indication I have that the file exists and is readable by dovecot is the disappearance from the logs of the line: No acl_shared_dict setting - shared mailbox listing is disabled So I can see that dovecot knows the file is there because it does not complain any more. The file is there (because I created it myself, although it is empty: size = 0), and in a moment of weakness I made sure it could be updated (this will be changed back!): ls -l /var/lib/dovecot/shared-mailboxes.db -rwxrwxrwx 1 dovecot dovecot 0 2012-10-30 12:27 /var/lib/dovecot/shared-mailboxes.db But if I try to update the ACL, absolutely nothing happens: [ > command ] [ < reply ] > telnet localhost 143 < * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=CRAM-MD5] Email server > a login [User2] [pass] < a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH ACL RIGHTS=texk] Logged in > a SETACL Inbox [User 1] rl < a OK Setacl complete. At this time, in the dovecot log (with debug enabled): 2012-10-30 13:55:24 IMAP([User2]): Info: Namespace : Using permissions from /home/mailboxes/[domain]/[User1]: mode=0770 gid=-1 2012-10-30 13:55:24 IMAP([User2]): Info: acl vfile: reading file /home/mailboxes/[domain]/[User1]/dovecot-acl 2012-10-30 13:55:24 IMAP([User2]): Info: acl vfile: reading file /home/mailboxes/[domain]/[USer1]/dovecot-acl Can anyone please help me track down what I'm doing wrong here?! It's driving me mad! Thanks for your time if you've read this far!! As requested: dovecot --version 1.2.9 base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log/dovecot.info log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps imap listen: 127.0.0.1:143 ssl_listen: 37.235.54.98 ssl_cert_file: /etc/ssl/dovecot.crt ssl_key_file: /etc/ssl/private/dovecot.key login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting: Email server valid_chroot_dirs: /var/spool/vmail mail_location: maildir:/home/mailboxes/%d/%n mail_debug: yes mbox_write_locks: fcntl dotlock mail_plugins: acl imap_acl lda: postmaster_address: [ valid@ddress ] auth default: mechanisms: plain cram-md5 verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/users socket: type: listen client: path: /var/spool/postfix/private/auth-client mode: 432 user: postfix group: postfix master: path: /var/spool/postfix/private/auth-master mode: 384 user: postfix group: postfix plugin: acl: vfile acl_shared_dict: file:/var/lib/dovecot/shared-mailboxes.db acl: vfile:/etc/dovecot/acls

1 0

[Dovecot] Problem about SSL for Dovecot.
by sheng-wei.lim 30 Oct '12

30 Oct '12

Hi All, With the below setting (cropped), the ssl certificate(signed by godaddy) don’t seems to work. It will still ask me if I want to accept this certificate. I have use the same certificate for apache host and postfix it works without any prompt. dovecot version : 2.0.19 # OS: Linux 3.2.0-32-generic-pae i686 Ubuntu 12.04.1 LTS Dovecot config: ssl = required ssl_cert = </aaa/4/merged5.crt ssl_key = </certs/proximityjobs.key userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } verbose_ssl = yes protocol lda { auth_socket_path = /var/run/dovecot/auth-master lda_mailbox_autocreate = yes log_path = /var/log/sieve.log mail_plugins = quota sieve autocreate acl postmaster_address = root } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = quota imap_quota autocreate acl imap_acl } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } Best Regards, Sheng Wei

1 0

[Dovecot] Save/restore IMAP session state
by Timo Sirainen 30 Oct '12

30 Oct '12

Some future Dovecot version will have "imap-idle" processes where IDLEing IMAP connections get moved, so the system wouldn't waste so much memory for all the IDLEing imap processes. A week ago I thought I'd see how easy it would be to implement this. I got a basic proof of concept working as a "X-STATE" command. Save the state: a x-state * STATE AQDLW45QdwAAAAMAAABuAQAAAAAAAFAcffYAPHnpFctbjlDbYQAAcEmzCwAA a OK State exported. Restore the state: b x-state AQDLW45QdwAAAAMAAABuAQAAAAAAAFAcffYAPHnpFctbjlDbYQAAcEmzCwAA b OK State imported. This could also be used to implement quick session state restoring for webmails (as suggested by Michael Slusarz). For getting the imap-idle process there would have to be code that: * triggers the session saving when process is IDLEing * figures out what filesystem paths the imap-idle should be looking at (i.e. paths to selected mailbox's dovecot.index.log file and maybe for e.g. maildir new/) * send the session state string, paths and imap connection fd to imap-idle process via UNIX socket * implement the actual imap-idle process * implement a way for imap-idle process to send back the state and connection fd to restore the imap process The patch is ugly and still missing many things. Anyway I thought I'd include it here just in case someone was really eager to continue implementing it. :) I'm not sure when I'll have time for it. A full patch would probably have to have some session_save()/session_restore() functions in lib-storage API. But a quick and dirty way is possible to implement for v2.1 as well, as long as some IMAP extensions aren't used (most importantly rfc5267).

2 2

Re: [Dovecot] Changing password for users
by Joseph Tam 30 Oct '12

30 Oct '12

Ben Morrow wrote: >> Maybe replace "/usr/bin/passwd" with htpasswd? > > Try pam_pwdfile with poppwd or some other poppassd that supports PAM. That's it! I was trying to remember the name of this PAM module. >>> and is there another way other than poppassd? >> >> Write your own PHP script -- it couldn't be more than a few dozen lines >> of code for a working skeleton. Or Google "php change password htpasswd". > > It's not as simple as you seem to think. Quite apart from getting the > password-changing itself right (have you considered what happens when > two users change their passwords at the same time? when Dovecot tries to > read the password file at the same time as you are changing it? when the > system crashes when you are halfway through rewriting the password > file?), you really shouldn't be running PHP as a user with write access > to a password file (even a virtual password file) in any case. I did consider it, and you're right, it is tricky to get it absolutely right. If robusteness and security was of utmost importance, I would abandon PHP too. I was scaling the solution to the OP's technical ability and apparent size of their operation -- if poppwd passes muster, this wouldn't be too far off. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] does dovecot interpret any mail headers specially with maildir?
by Christoph Anton Mitterer 30 Oct '12

30 Oct '12

Hi. For mbox, http://wiki2.dovecot.org/MailboxFormat/mbox#Dovecot.27s_Metadata lists a numer of mail headers: - X-IMAPbase - X-IMAP - X-UID - Status - X-Status - X-Keywords - Content-Length that are treated specially by dovecot. It also suggests, that these should be stripped by the LDA (I guess in order that someone sending you such mail cannot set the status or keywords, or even "attack you" by setting a bogus Content-Length). I wondered, when using maildir, are there any headers that dovecote would treat specially, too? And which I therefore should strip? Thanks, Chris.

2 9

[Dovecot] Problems with Virtual and mail-search.c
by Levent Dane 29 Oct '12

29 Oct '12

First, I don't know why but dovecot gots this error. Oct 15 13:24:02 widder dovecot: imap(limon): Panic: file mail-search.c: line 90 (mail_search_args_init_sub): assertion failed: (arg->value.keywords == NULL) Then, when I tried to run SELECT "INBOX/Code" (UNSEEN) virtual plugin got a segfault. Oct 15 13:24:03 widder kernel: imap[22749]: segfault at 2c ip b757f8ec sp bfa3a160 error 4 in lib20_virtual_plugin.so[b7579000+d000][b74b0000+d000] I'm running gentoo with kernel 2.6.32.12. My dovecot version is 2.1.10. I applied http://hg.dovecot.org/dovecot-2.1/raw-diff/0306792cc843/src/lib-storage/mai… But still, i'm getting this problem. Thanks, Levent Dane

2 6