Re: [Dovecot] setting mail_home and vacation
Ben Morrow wrote: > At 12AM +0100 on 20/12/12 you (Andreas Meyer) wrote: > > Ben Morrow wrote: > > > > > Where is that user's home directory, then? (Where is its > > > .dovecot.sieve?) That is the path that mail_home should be set to. > > > > It's /var/spool/vhosts/xyz.de/archiv . It's one file, a mbox. There is no > > .dovecot.sieve. This mbox is flushed various times a day by a MUA. > > This user archiv is a virtual user and has no home directory, just a mbox. > > All Dovecot users should have a unique home directory (which needs to be > *a directory*, obviously, and shouldn't be the same as any of the > mailbox locations). See http://wiki2.dovecot.org/VirtualUsers/Home . ok, thank you, that was an important step for the mboxes we drive! > Ben Andreas
Re: [Dovecot] setting mail_home and vacation
Daniel Parthey wrote: > > > Where is that user's home directory, then? (Where is its > > > .dovecot.sieve?) That is the path that mail_home should be set to. > > > > It's /var/spool/vhosts/xyz.de/archiv . It's one file, a mbox. There is no > > .dovecot.sieve. This mbox is flushed various times a day by a MUA. > > This user archiv is a virtual user and has no home directory, just a mbox. > > Your mail_home needs to be a directory, not a file. > mbox files should be located inside a subdirectory of your mail_home. Thank you, got it! And migrated the users to the new location of the mboxes. Great! That makes everything much easier. > Regards > Daniel Andreas
[Dovecot] Antispam r49 breaks Dovecot v2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Eugene, patch 49 breaks compilation with Dovecot v2.1. Attached patch encloses the change in a #if. To feed the #if the actual Dovecot version, I've introduced an extra variable in extra.mk, but I cannot help with making the GNU configure stuff doing it right away. There will be numerous other ways to get the Dovecot version into the source ... . Maybe, Timo would add a binary version of the Dovecot version in its config.h ? In order to be able to built version-aware plugins. Regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUNLvT2oxLS8a3A9mAQIzfwgAvf7zcN9RwKD/kTmFkfx5djKd5H0dRXt8 423csD3bCU6qcOtR2MHR0ApNp07aXK84MPgIazbne41Iekqk0daoOhnPoc0mHy8u kj9EYFGVlQTKa2vcSUEu8Phddc/YHvzQba9m2Dg9P4STuJ6EcRqkhvufspERGphF Y+IY20BQc9/Flu8TIxtt6pSiIioq0WWntCGnyPP9BX90JYYO+5zAm5FnG4GH4Q0Z 44dZSKM7iP0/nMhmsraX/5alxy0mvx3ZfhO/Ktx/wd92WmLROAlicBClIZC9XCH2 6HD/ryr73DrEeEZdmwHcnmZrtWc++EJcAetfv45Fov8XagUtFJ0D4A== =G+d/ -END PGP SIGNATURE- antispam_2.1-2.2.patch.gz Description: Binary data
[Dovecot] no more backtraces in v2.1.12 (was Re: backtrace from postgres dict)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 28 Nov 2012, Steffen Kaiser wrote: with Dovecot v2.1.12 I do no get those panics anymore. 2012-11-28 10:04:41 dict: Panic: file driver-pgsql.c: line 84 (driver_pgsql_set_state): assertion failed: (state == SQL_DB_STATE_BUSY || db->cur_result == NULL) 2012-11-28 10:04:41 dict: Error: Raw backtrace: /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(+0x4857a) [0x7f91f511157a] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(+0x485c6) [0x7f91f51115c6] -> /usr/local/dovecot-2.1.10/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f91f50e4eaf] -> dovecot2.1/dict() [0x40aa36] -> dovecot2.1/dict() [0x40aa91] -> dovecot2.1/dict() [0x40bed3] -> dovecot2.1/dict() [0x409504] - -> dovecot2.1/dict(sql_db_cache_deinit+0x20) [0x408a60] -> dovecot2.1/dict(main+0x169) [0x405a59] -> /lib/libc.so.6(__libc_start_main+0xfd) [0x7f91f4b5cc8d] -> dovecot2.1/dict() [0x404bb9] 2012-11-28 10:04:41 dict: Fatal: master: service(dict): child 22923 killed with signal 6 (core not dumped) - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUNM9LGoxLS8a3A9mAQJaoQgAu5LfaqmVcdFWMF0Z+DrQvLz1xlSIP35+ cJxI7gYKh21LzpSB2iJ2DjccRUJDZRupqpIwSDLuiFYp7ORktrrO6ohieXrDM7z1 VcFO1kU2vbTYIbOloN724pSy1oFxTsec5TTi5zlL9WFjSTW2pP9oFbcSan+43ADo gUSwm69F57GIZvOGyMSb1o83JCXRI83IajtgFtcIBuTqn6TC+zMolC2rC35ElZdM EqkXMnGBKLNjxdp+hsro2i59bahzlIO4eigrRNFDTbiM8fInFen9BK40OnXkF2Ni n7kh9Zx+8EDE2ayWFKaPz0hXZbbQSXcWdkfHjc/TBV9DPk2YY7BTSw== =V/8J -END PGP SIGNATURE-
Re: [Dovecot] doveadm-lda - segfault
Timo Sirainen writes: > On Tue, 2012-12-11 at 23:15 +0100, Kamil Jońca wrote: >> #0 0x7f99d591fe6f in mail_storage_try_copy (mail=0x198dbb0, >> _ctx=0x7fff8914fc28) at mail-copy.c:56 >> 56 mail-copy.c: No such file or directory. > > raw-storage's envelope_sender is NULL. Fixed Dovecot to make sure NULL > isn't returned: http://hg.dovecot.org/dovecot-2.1/rev/579984fdb6e5 > > But I think Pigeonhole also shouldn't set it to NULL. > sieve-message.c:sieve_message_get_sender() apparently returns NULL if it > can't find anything. Elsewhere this is used when nothing else is there: > > #define DEFAULT_ENVELOPE_SENDER "MAILER-DAEMON" > > > LDA from dovecot 2:2.1.12-0~auto+10 does not segfaults. Thanks. KJ -- http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewskiej-wprowadzenie/ "Remember, extremism in the nondefense of moderation is not a virtue." -- Peter Neumann, about usenet
Re: [Dovecot] migration to dovecot pop3
On 12/19/2012 6:59 PM, Joseph Tam wrote: > Rajesh M writes: > >> i am planning to migrate from qmail pop3 to dovecot pop3 >> >> the number of users on the server is large over 5000 >> ... >> also data volume is large - over 3.5 tb -- ie many users several 1000s of >> emails in their inbox > > If you stay on the list, you might find some people here whose > mail metrics are several orders of magnitude larger than this. > >> 1) will the migration cause all the emails on the server to re-download >> ... >> 4) has anybody migrated from qmail pop3 to dovecot pop3 successfully >> without emails being downloaded again > > A proper migration will avoid this. Google is your friend > > http://lmgtfy.com/q=POP+qmail+to+dovecot+migration > > The top hits provide exactly what you're looking for. > >> 2) can dovecot be configured to allow only one download at a time - pop3 >> locking with time out setting that can be customized We migrated 5000+ from qpopper years ago. Dovecot is sooo much better on system load. Yes, locking and timeouts are in the config file. >> >> 3) can dovecot pop3 be configured so that it will allow download of >> emails >> only of the last say 15 days ie even if the same pop3 user is >> configure on >> another machine it will download only messages of the last 15 days That's not part of pop3, so no, it's not possible with dovecot alone. You could probably work out a plugin to move read mail after x days, or there may be one out there ? Or some imap robot could do it.. Ken A. Pacific.Net > I can't answer this, but if this is an attempt to prevent mass download, > the answer to 1+4 makes these questions irrelevant. > > Joseph Tam > -- Ken Anderson Pacific Internet - http://www.pacific.net Latest Pacific.Net Status - http://twitter.com/pacnetstatus
[Dovecot] Understanding Sockets
Hi, Just trying to consolidate my knowledge of Dovecot and I want to understand various things rather than just key out lines of config in dovecot.conf with the hope of it working. What I wanted to clarify is my understanding the "socket listen" section of the config file. From my limited understanding, this section details how other processes can access the userdb defined in Dovecot. The master socket is used for "internal" processes which is mainly dovecot-lda so that when Dovecot receives mail it knows where to deliver it and client is defined for "external" processes, for example Postfix who would use the info to determine if a user existed. Would you say this is a fair (albeit) dumbed down!!) synopsis of sockets and their purpose? Thanks in advance! Tim
Re: [Dovecot] Understanding Sockets
At 10PM + on 20/12/12 Tim Smith wrote: > > Just trying to consolidate my knowledge of Dovecot and I want to > understand various things rather than just key out lines of config in > dovecot.conf with the hope of it working. > > What I wanted to clarify is my understanding the "socket listen" section > of the config file. From my limited understanding, this section details > how other processes can access the userdb defined in Dovecot. The master > socket is used for "internal" processes which is mainly dovecot-lda so > that when Dovecot receives mail it knows where to deliver it and client > is defined for "external" processes, for example Postfix who would use > the info to determine if a user existed. Would you say this is a fair > (albeit) dumbed down!!) synopsis of sockets and their purpose? Your mention of 'socket listen' and 'master' auth sockets suggests you are using Dovecot 1.x. That description is pretty-much correct for 1.x, however you should upgrade to 2.x as soon as you reasonably can, since 1.x is no longer supported. See http://wiki2.dovecot.org/Services#auth for a description of the socket types available with Dovecot 2. [The statement there that 'client' sockets can safely be exposed to the entire world, including over inet sockets, is not entirely true. AFAIK there is no rate limiting, so an exposed 'client' socket is a password oracle and should therefore be somewhat protected. The risk is approximately equivalent to an unshadowed password file, with the encrypted passwords exposed.] Ben
