November 2012 - dovecot

[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