Am 27.05.2014 16:28, schrieb Arthur Dent:
On Tue, 2014-05-27 at 16:09 +0200, Robert Schetterer wrote:
Am 27.05.2014 16:04, schrieb Arthur Dent:
On Tue, 2014-05-27 at 15:44 +0200, Robert Schetterer wrote:
Am 27.05.2014 14:56, schrieb Arthur Dent:
Hello All,
I have a Dovecot v2.2.12 installation running on a Fedora 20 box which is the mailserver for my family. This means that it is serving only 4 accounts.
I use fetchmail->procmail to feed Dovecot and I read my mail on clients such as Evolution on (another) Fedora 20 machine, iPad/iPhone or squirrelmail on the web (running on the same Fedora 20 server).
The average mail throughput for the whole family is around a couple of hundred messages per day, but each (and every) day I get between 3 and 10 of the following messages:
dovecot: imap(mark): Error: Next message unexpectedly corrupted in mbox file /home/mark/mail/MLists/Fail2Ban at 3407473: 1 Time(s)
I have googled, but with little success. What I have found seemed to suggest that removing the .index files and allowing Dovecot to rebuild them will solve this. I did: find /home -type f -name "dovecot.index.*" -exec rm -f {} \; but it has made no difference.
Can anyone help me solve this please?
at this small setup simply use maildir as format and use getmail to fetch, sieve may do sorting
see https://sys4.de/de/blog/2013/04/12/abholdienst-fur-mail/
sorry german but setup should speak for its own
getmail does also deliver into maildir directly ( without dovecot deliver ) if you dont need to sort through sieve
Well thanks - but I have been using an mbox setup for about 10 years. It is only since I upgraded to F20 that I have been experiencing this problem. I may look at switching to maildir for the future, but for now that's too big a job...
Any other ideas?
Thanks
Mark
OK - Unless I'm missing something, all that page (which I'd already read) tells me is that I may have to delete the dovecot.index file(s) - which I've don (several times). I still have the same problem. Every single day.
Anything else?
... Avoiding crashes and errors
Since the problems usually have been related to broken headers, you should be able to avoid them by filtering out all the Dovecot's internal metadata headers. This is a good idea to do in any case. If you use Dovecot LDA it does this filtering automatically
do you use dovecot lda ?
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, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein