[Dovecot] Dovecot 2.1.16: Quota plugin compile fails: Solaris 10
Dovecot 2.1.16 fails to compile giving the following error under Solaris 10. Previously I had no problem compiling 2.1.12. The start of the config.log file contains: It was created by Dovecot configure 2.1.16, which was generated by GNU Autoconf 2.68. Invocation command line was $ ./configure ## - ## ## Platform. ## ## - ## hostname = luna uname -m = i86pc uname -r = 5.10 uname -s = SunOS uname -v = Generic_148889-01 /usr/bin/uname -p = i386 /bin/uname -X = System = SunOS Node = luna Release = 5.10 KernelID = Generic_148889-01 Machine = i86pc BusType = unknown Serial = unknown Users = unknown OEM# = 0 Origin# = 1 NumCPU = 4 /bin/arch = i86pc /usr/bin/arch -k = i86pc /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/sfw/bin PATH: /usr/local/bin PATH: /usr/bin PATH: /usr/sbin PATH: /usr/ccs/bin PATH: /opt/SUNWspro/bin PATH: /usr/ucb GCC version info: Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared Thread model: posix gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath) Making all in quota gmake[4]: Entering directory `/usr/local/src/mail/dovecot/dovecot-2.1.16/src/plugins/quota' gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../src/lib -I../../../src/lib-master -I../../../src/lib-dict -I../../../src/lib-index -I../../../src/lib-mail -I../../../src/lib-storage -I../../../src/lib-storage/index -I../../../src/lib-storage/index/maildir -I../../../src/doveadm -I/usr/local/ssl/include -I/usr/sfw/include -I/usr/local/include -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -I/usr/local/ssl/include -MT quota-status.o -MD -MP -MF .deps/quota-status.Tpo -c -o quota-status.o quota-status.c quota-status.c: In function `main': quota-status.c:200: error: `optarg' undeclared (first use in this function) quota-status.c:200: error: (Each undeclared identifier is reported only once quota-status.c:200: error: for each function it appears in.) gmake[4]: *** [quota-status.o] Error 1 gmake[4]: Leaving directory `/usr/local/src/mail/dovecot/dovecot-2.1.16/src/plugins/quota' Steve -- --- IT Systems Administrator, E-Mail:- st...@earth.ox.ac.uk Department of Earth Sciences,Tel:- +44 (0)1865 282110 Oxford University, South Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
Re: [Dovecot] Multiple Concurrent IMAP Connections For Same User
On 06/03/2011 03:45, Stan Hoeppner wrote: If you're not doing local sync with TB and you have GLODA disabled, TB is going to show you exactly what's in your Dovecot mailbox. If the message doesn't disappear from your TB view sometime after deleting it on your smartphone, then I'd say it's very likely that Dovecot didn't receive the delete and/or expunge command from the phone. Check your Dovecot logs and see what the phone is actually sending, or not sending. Both of you mentioned problems specifically WRT smartphones. It's likely the IMAP implementation in these phones is simply buggy, or your network coverage is spotty. I don't use a smartphone so I can't really say. What smartphone are you each using? Actually it doesn't matter what the second client is (it can be another copy of TB3), the important thing is that TB3 doesn't notice the change underneath it. (The programmers seem to assume that it will have exclusive access to the mailbox from what I can see.) The real mailbox does change correctly, TB3's idea of what the mailbox holds does not and it fails to check its consistency with respect to the server. Obviously there's a difference in behaviour for some reason when TB3 interacts with Cyrus IMAP as it seems not to have a problem with that IMAP server. It's almost as if TB3 expects to be informed when there has been a deletion. (TB3 will notice other status changes such as a message being read etc.) The phantom messages within TB3 will also persist between program restarts, which suggests that it's not verifying its cached message list at that point either. By the way, asking end-users to all change their client settings is not a practical solution. We need to determine why the behaviour between Dovecot and TB3 is different from Cyrus and TB3 and then either ask the TB developers to fix their code or put a work-around in Dovecot. (I may even have to be both.) Steve -- --- IT Systems Administrator, E-Mail:- st...@earth.ox.ac.uk Department of Earth Sciences,Tel:- +44 (0)1865 282110 Oxford University, South Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
Re: [Dovecot] Multiple Concurrent IMAP Connections For Same User
I know that this is a somewhat old thread but I do have some useful input. Basically, this seems to be a Thunderbird problem (or at least an interaction problem between Thunderbird and Dovecot). Before Thunderbird version 3 there wasn't a problem, the mailbox within Thunderbird would sync correctly. As of version 3 they seem to have changed their mailbox header list caching code and it gets horribly confused when mails disappear from the mailbox without it doing so. The only way to fix the view within the program is the rebuild the (Thunderbird) index. This is not the only problem TB3 has with Dovecot. Quite often if there are large attachments TB doesn't fully load the attachments (and sometimes not even the mail itself). I've found changing TBs setting so that it only uses one connection to the server rather than the default 5 helps mitigate this. I'm not sure why TB3 has such a hard time when talking to Dovecot as no other clients have any difficulty and TB2 never did. Steve P.S. Our system is a Solaris 10 x86 box running Dovecot 1.2.x with Maildir++ folders. -- --- IT Systems Administrator, E-Mail:- st...@earth.ox.ac.uk Department of Earth Sciences,Tel:- +44 (0)1865 282110 Oxford University, South Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
Re: [Dovecot] Multiple Concurrent IMAP Connections For Same User
On 05/03/2011 18:04, Stan Hoeppner wrote: I don't believe it's an issue of Tbird talking to Dovecot, and I don't believe it's a Dovecot issue. I believe it's a combination of the TB GLODA system and local folder synchronization. I recommend you disable both of these, close TB, then manually delete all local cached folder/message copies and the gloda database in the user profile, then launch TB. And never reenable local sync or GLODA. This should fix your problem. And make sure *all* IMAP clients accessing the mailbox expunge on exit, including your smart phone, etc. Turning off all caching and synchronisation makes no difference. It's the first thing I did, especially as at work the connection to the mail server is fast and the home directory for my account is a network drive. (i.e. the caching and copying of e-mail is actually *SLOWER* than direct access.) The same effect can be seen on all platforms TB3 runs upon and whether or not the users data is stored locally or on a network drive. Steve -- --- IT Systems Administrator, E-Mail:- st...@earth.ox.ac.uk Department of Earth Sciences,Tel:- +44 (0)1865 282110 Oxford University, South Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
Re: [Dovecot] Anyone successfully setup Continous Backup of mailboxes using rsync ?
CoolAtt NNA wrote: Hi All.. Am working on continous backup of mailboxes using rsync(for e.g by running rsync every 2 min) Things gets more complicated when users create Subfolders in INBOX , SENT , etc.. If anyone among you did that plz guide advise. We have a slightly different method of doing a back-up, at least of people's inboxes (which is all I archive). I've written a program, which is run by cron once a minute, which searches for messages within all the users' inboxes and then hard-links them into a backup store elsewhere on the disk. Then, once a day a reaper process runs which checks for all files in that store with only one link and have not been accessed for a set amount of time (in our case 90 days) and then deletes those files. In other words, the messages are kept for 90 days after they have been deleted or moved out of the user's inbox. I've attached the source code tar file as you or someone else may find it useful. In your case you could rsync the back-up store instead of the user's main directory structure and maybe only do it once per day. Steve -- --- IT Systems Administrator, E-Mail:- st...@earth.ox.ac.uk Department of Earth Sciences,Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK.Fax:- +44 (0)1865 272072 backupinboxes.tar.gz Description: GNU Zip compressed data
Re: [Dovecot] scalability and arhive ideas
ferna...@dfcom.com.br wrote: I´m reading the past topics related to archive and scalability of dovecot, they are all very interesting. Here, I´m using two dovecot proxies in front of five storages pairs, and we split the domain´s accounts among those servers. So, we can share the i/o load and if one server goes down only few accounts of the domain stops (not all of them). But, we began to have space problems - and the solution would be insert more and more storage servers. So I was searching for some archive solutions (hard links - at S.O level, or some dovecot extension). A friend told me that he knows an ISP that share even the mailbox of the users among many servers - this is very weird and (at same time) very interesting approach. Instead of put all messages into one maildir and this maildir into one server, this maildir (?) is spplited among many servers - so, if one servers fails the account is still acessible and they move old/big messages to a new cheap storage - archiving transparently. Surely, other than the possibility of archiving a copy in a separate location at delivery time, everything else here is better done by a high-availability clustered SAN and *not* by an application? Archival is a valuable thing to have. Being able to, on delivery, deposit a separate copy elsewhere (without necessarily indexing it etc.) allows for near-line back-up or storage where legal or corporate regulation require. (I'm currently doing this using a cron job and a program I've written which checks to see if there are any new messages in everyone's inbox Maildirs and then hard-links them into a separate directory structure once a minute. Messages which disappear from the true inbox are then kept for a further 90 days. This allows users to recover messages that they may have accidentally deleted from their inbox.) Oh, and with reference to the second paragraph... hard links only work on a single filesystem, not across multiple filesystems or servers. Steve -- --- IT Systems Administrator, E-Mail:- st...@earth.ox.ac.uk Department of Earth Sciences,Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK.Fax:- +44 (0)1865 272072
Re: [Dovecot] building a simple antispam plugin
Surely spam filtering/rejection should be done by the MTA, preferably during the SMTP protocol conversation so as to prevent the black-holing of legitimate e-mails (i.e. the sender doesn't know it's not been delivered) and the prevention of joe-job collateral spamming? It should also be noted that, at least in the UK, the act of an MTA at the final delivery mail server accepting an e-mail means that it's legally been received. Hence, any legal document which the MTA accepts has been deemed to have been legally served even if no human ever reads it. Please be careful, e-mail administration can be a legal minefield! Steve -- --- Computer Systems Administrator,E-Mail:[EMAIL PROTECTED] Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
Re: [Dovecot] Follow-up re: gcc 2.96 - Re: PATCH: compile dovecot-1.1.beta14 with gcc 2.95
Scott Silva wrote: How much longer can a system be expected to run? 8+ years at 24/7 is about a half a million hours. Drives are getting old and expensive to replace. Processors are probably slow. Energy use is high. Motherboard capacitors are probably drying up. The systems are past a safe point and are getting closer to the great e-waste pile in the sky. I retired a 13 year old DEC AlphaStation 5/266 yesterday... Legacy systems are still doing useful things. You just have to make sure that they're isolated from the outside as they can't be patched or upgraded. (e.g. newer versions of OpenSSH won't compile under Digital UNIX 4.2C) Steve P.S. For the record, the DEC box has only ever needed to be shut down for power outages and (in its early life) OS upgrades. It ran 24/7 and never had a hardware fault (and still doesn't). Now that's reliable hardware! -- --- Computer Systems Administrator,E-Mail:[EMAIL PROTECTED] Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
Re: [Dovecot] Delay on failed pw attempts
On 2 Jan 2008, at 10:43, Luigi Rosa wrote: Timo Sirainen said the following on 01/02/2008 11:39 AM: A growing delay based on remote IP address would be nice, but it would require keeping track of that information, which pretty much means that there would have to be a new separate process doing that. All of this would be so much easier to implement for v2.0 framework.. IMHO this stuff is to be handled by IDS and firewall. Unfortunately many (most) of the IDS appliances aren't tunable in this way, they merely use content signatures. Firewalls are not designed to do this at all. My experience with Cisco kit shows this to be true. You also have to remember that the people managing the firewall/IDS aren't necessarily the same people as those who run the mail services and the latter may not have a direct influence upon the former. As for if/when Dovecot should get this, well it's not imperative. It's a feature which would be very nice to have but it's not a deal breaker. Let's face it, I know of no other IMAP server systems which currently have it. In this case, if it fits better into the v2.0 framework then it's probably best to wait until then but factor such sorts of controls into the design at this early stage of development. Steve --- Computer Systems Administrator,E-Mail:[EMAIL PROTECTED] Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
Re: [Dovecot] Delay on failed pw attempts
On 1 Jan 2008, at 21:22, Timo Sirainen wrote: On Tue, 2008-01-01 at 15:59 -0500, Dean Brooks wrote: Hi, Is there a way, or can a way be added, to add an auth_failed_delay=10s style option that would put in an artificial delay after a failed password attempt? As it stands now, Dovecot seems highly vulnerable to widescale brute-force password dictionary scans. Even if it's not configurable, can a delay be hardcoded to something like, say, 10 or 15 seconds? Failed auth requests are put to a queue that's flushed every 2 seconds. So there is already a delay. I don't think it's a good idea to increase it up from 2 seconds, it just gets annoying when you type the wrong password accidentally. Although I suppose I could change the code so that it always waits 2 seconds instead of flushing all of them. Actually, a better method which would not inconvenience real users is to have an accumalative delay, i.e. the first error has a 1 second delay, the second 2 seconds, the third 4 seconds and so on. This should tar-pit any brute force attack, at least until the script kiddies just blast the server with a huge number of new connections to do the job. Steve --- Computer Systems Administrator,E-Mail:[EMAIL PROTECTED] Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
Re: [Dovecot] exim/kmail vs. dovecot
Kristian Koehntopp wrote: I am using exim via dovecot_deliver to store messages in Maildir in my $HOME. I am using kmail to retrieve stuff. Unfortunately, something in my data crashes dovecot. I was using 1.0.rc14 from opensuse, but downloaded and installed 1.0.8 from the site. Kmail doesn't use a proper version of Maildir internally, it also assumes that it's the only program accessing the files and so play fast and loose. Not only this but it also has its own index files and gets extremely confused if things change underneath it. It's really a nasty client underneath the skin. I would suggest that you deliver your e-mail elsewhere and have kmail access the folders via IMAP, even though it's not very nice to do so. (Kmail will overload the IMAP server if you're not careful.) I can tell you this from experience as I used Kmail for a number of years in a production environment until quite recently. Steve -- --- Computer Systems Administrator,E-Mail:[EMAIL PROTECTED] Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
Re: [Dovecot] dovecot-auth consumes 100% CPU time on Solaris 10
hello Mark, Mark Heitmann wrote: In my $LD_LIBRARY_PATH /usr/lib is behind /usr/local/lib (for openldap), although dovecot-auth was linked with the Solaris lib. The way that works for me is the following LDFLAGS directive to the configure command, because the --with-ldap flag has no directory option: LDFLAGS=-L/usr/local/BerkeleyDB/lib -L/usr/local/lib /usr/local/lib/libldap-2.4.so.2 Is there a smarter way to link with the right lib and ignore the solaris one? Firstly, on Solaris *NEVER* have LD_LIBRARY_PATH or LD_RUN_PATH set when compiling, it's just a whole world of pain that you don't need. Basically, the Solaris linker will forget where the libraries you linked to were if you have either of these environment variables set at link time. The runtime linker will only have its own list to fall back upon, which will be /usr/lib. Here's how to work around it:- In the LDFLAGS use: LDFLAGS=-L/usr/local/BerkeleyDB/lib -R/usr/local/BerkeleyDB/lib -L/usr/local/lib -R/usr/local/lib Now, assuming that LD_LIBRARY_PATH is not defined, the linker will store in the resulting binary the correct search path for libraries in the correct order. Steve -- --- Computer Systems Administrator,E-Mail:[EMAIL PROTECTED] Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
[Dovecot] Sieve: Conversion script for procmail recipes.
Seeing as many on this list are in the process of migrating their mailsystems not only to dovecot's IMAP/POP3 server but also using dovecot's deliver for delivering e-mail into users' folders I thought that it might be a good idea to share with you the perl script I've been labouring upon for the last few days which will translate a simple(ish) procmail recipe to an equivalent Dovecot-Sieve script. (It handles vacation pipes as well, by the way.) It may even be useful as a basis for a more fully featured translator, who knows. Whatever, if it could be put on the Wiki no doubt it will prevent the wheel being re-invented time and again. The script can be found at the following URL: http://www.earth.ox.ac.uk/~steve/sieve/procmail2sieve.pl It might be worth putting it in a contrib directory in the dovecot-sieve distribution. Steve -- --- Computer Systems Administrator,E-Mail:[EMAIL PROTECTED] Department of Earth Sciences, Tel:- +44 (0)1865 282110 University of Oxford, Parks Road, Oxford, UK. Fax:- +44 (0)1865 272072
