- dovecot - dovecot.org

[Dovecot] Lost transaction log file
by Brent Clark 19 Aug '05

19 Aug '05

Hi list I seem to be getting quite a bit of this type of messages in my syslog. Aug 19 09:14:45 mail dovecot: IMAP(bclark): Lost transaction log file /home/bclark/Maildir/dovecot.index.log seq 4 Aug 19 09:14:45 mail dovecot: IMAP(bclark): Lost transaction log file /home/bclark/Maildir/dovecot.index.log seq 4 Would anyone know how I can go about fixing / understanding this. Any tips / advice would greatfully be appreciated. Kind Regards Brent Clark

2 3

[Dovecot] ( Dovecot + Postfix + MySQL + Postfixadmin )
by Pratchaya Chatuphian 19 Aug '05

19 Aug '05

( Dovecot + Postfix + MySQL + Postfixadmin + Spamassassin + Clamav + Amavisd-new ) I need help and sample how to. Anyone can help me sir ? Thank you for advance . Pratchaya

2 1

[Dovecot] compiling dovecot-lda from cvs
by Jakob Hirsch 19 Aug '05

19 Aug '05

current dovecot-lda fails to compile: deliver.c: In function 'main': deliver.c:543: error: 'script_path' undeclared (first use in this function) deliver.c:543: error: (Each undeclared identifier is reported only once deliver.c:543: error: for each function it appears in.) deliver.c:544: warning: implicit declaration of function 'stat' deliver.c:544: error: 'st' undeclared (first use in this function) make[3]: *** [deliver.o] Error 1

2 1

[Dovecot] logging beg - again
by Peter Gervai 19 Aug '05

19 Aug '05

Hello, [Old problem; if it was fixed, I cannot see it (checked Changelog, wiki, source, as much as my grepping counts). Any help appreciated.] I have been begging since 2003 to be able to trash qpopper and use dovecot, but statistical logging of dovecot has been pretty much absent. Qpopper does this: Aug 19 11:18:02 mail in.qpopper[8099]: Stats: userid 0 0 12 51773 user.example.com 193.291.612.5 [pop_updt.c:296] Which provides us with user id, user host and ip, which is fine with dovecot. Provides furthermore unread mail count and bytes, and read but undeleted mail count and bytes. This is essential to handle low-IQ user problems basically coming down to "WE CANNOT USE EMAIL FIX IT". This topic was touched several times: http://www.google.com/search?q=site:dovecot.org+logging&hl=en&lr=&start=0&s… including my original question at http://dovecot.org/list/dovecot/2003-October/002514.html someone even dropped in a patch http://dovecot.org/pipermail/dovecot/2003-June/001618.html which seem to have disappeared in the flow of time. Probably is a member of the TODO list since then, but I cannot find the exact spot. Some comments from Timo was dropped at http://dovecot.org/pipermail/dovecot/2003-May/001545.html http://dovecot.org/pipermail/dovecot/2003-September/002277.html (and reply http://dovecot.org/pipermail/dovecot/2003-September/002281.html ) http://dovecot.org/pipermail/dovecot/2003-November/002524.html So, is there any possibility to log the entry and exit statistics of a session, regarding the amount of mail? Thanks, Peter

2 1

[Dovecot] Multiple folders/fetchmail
by Andreas Jung 19 Aug '05

19 Aug '05

Hi, my emails are processed using procmail and stored the following way: /home/ajung/Maildir/new|cur|tmp /home/ajung/Maildir/Plone|new|cur|tmp /home/ajung/Maildir/Python|new|cur|tmp When I fetch my mail using fetchmail I can only get the mails from "Maildir". However I can not access other folders like "Plone" or "Python" (using fetchmail -r Plone). I tried to tweak mail_default_env but without access. So any ideas how to configure dovecot the way I need it? Thanks in advance, Andreas

2 1

[Dovecot] 1.0alpha1, multiple lock methods?
by Jeff A. Earickson 18 Aug '05

18 Aug '05

Hi, I just upgraded from test80 to 1.0alpha1. I wanted to try something new on the lock_method, so I set: lock_method = fcntl, dotlock I got syslog complaints like: IMAP(username): Unknown lock_method: fcntl, dotlock Can one specify multiple file locking mechanisms? If so, what is the syntax (and can the syntax be shown in the comments of the .conf file)? Jeff Earickson Colby College

2 1

[Dovecot] 1.0 alpha1 released
by Timo Sirainen 18 Aug '05

18 Aug '05

As promised a few days ago, 1.0.alpha1 release is now available from Dovecot web page. Changes since 1.0-test80 include only one mbox assert crashfix and removed fsync() call when writing to transaction log, making it a bit faster. I changed the version number also since 1.0-tests to 1.0.alpha. I know '-' is problematic to binary package builders, maybe the new versioning is better?

4 5

[Dovecot] Discussion of new sending protocol proposal for IMAP
by Marc Perkel 18 Aug '05

18 Aug '05

Timo, I joined the lemonade list for the new IMAP sending protocol and I mage the following suggestion about using IMAP as a front end for SMTP. The idea would be that a client could authenticate to IMAP, then ask for a tunnel to the SMTP server. - Here's my message. I thought I'd get people thinking. --------------------- OK thanks. I would clarify what I'm proposing. I looked at the current proposal and what I'm proposing might be in addition to rather than instead of the current proposal. LDELIVER as it is now offers capabilities of sending messages and forwarding attachments without downloading them, leaving more power on the server side. This is important for mobile clients with limited power on the client end. What I'm suggesting is something in addition to LDELIVER where we add SMTP-TUNNEL as a capability. This is for laptop users who have to deal with finding an outgoing smpt server and who might be behind a firewall that blocks smtp ports. What is different about my proposal is that what I'm suggesting isn't a straight pass through at the beginning. The client has to talk to IMAP, then authenticate, and then upon successfil authentication would ask for an SMTP connection to the local smtp server. At that point it is a tunneled connection. 1) This allows the IMAP ports to be used for SMTP and avoid port blocking. 2) It uses the same IMAP authentication for SMTP so outgoing SMTP nee not be configured separately. It merely acts as an authenticated condiut to get to SMTP. 3) It would in no way interfere with future advancements in SMTP technology at others were concerned about. 4) Client and server recoding would be trivial. 5) This could be used in place of SMTP-AUTH and would eliminate the need for authenticated SMTP making server smtp configuration easier. So - if you look at it as an addition then you don't have to choose between them. Stephane Maes wrote: > Marc, > > Based on the suggestions that we have received so far, we will publish > a proposed update. We are looking at smtp proxy options. > > Note that LDELIVER contributes also in supporting server side > recomposition with upload of only body / header part diffs. I am not > sure that tunneling would allow this. But I am looking into it. > > Thanks > > Stephane > > PS I still have an action item to provide the use cases / reasons / > pros of using it. I will distribute soon on the list. > _____ > Stephane H. Maes, PhD, > Director of Architecture - RTCC & Mobile, Oracle Corporation. > Ph: +1-203-300-7786 (mobile/SMS); Fax / UM: +1-650-607-6296. > e-mail: stephane.maes(a)oracle.com > IM: shmaes (AIM, Y!,Skype) or stephane_maes(a)hotmail.com (MSN Messenger) > -----Original Message----- > From: lemonade-bounces(a)ietf.org <lemonade-bounces(a)ietf.org> > To: lemonade(a)ietf.org <lemonade(a)ietf.org> > Sent: Thu Aug 18 08:41:10 2005 > Subject: [lemonade] Outside the box suggestion about Lemonade > > Hello, > > I'm Marc Perkel - and I'm new to this list. I run a span filtering > service called junkemailfiltercom and do some web hosting. > > I've read sme of the discussion about LDELIVER and I just wanted to > throw out a wild idea and see where it goes. > > The Problem: Sending email without having to separately config > outgoing SMTP so that an IMAP connection can be used especially by > moble users to send email. > > So - suppose that instead of adding something complex - why not just > establish a tunnel to SMTP over IMAP? > > Here's what I propose. The client when sending email would establish a > second IMAP connection to the server. One of the CAPABILITIES will be > SMTP-TUNNEL. After sending the command the IMAP server opens a > connection to the SMTP server and acts as a straight pipe through > until the connection is closed. > > The advantage of this is that you can take your existing SMTP code and > instead of connecting it on port 25 you connect it on port 143. Then > everything you could do with SMTP is available. You would just need to > add a smal layer to the SMTP layer to authenticate to the IMAP server > and tell it to open a tunnel to the SMTP server. On the server side > you just connect to localhost:25 or whatever you configure it to and > pass data. > > Basically what I'm suggesting is that IMAP act as a tunnel to SMTP > providing and authenticated connection using the same credentials as > the imap client uses. > > Unless I'm missing something - and I might be - seems to me this would > be dirt simple to implement and wouldn't impose any of the limitations > to the SMTP protocol that other people here are concerned about. > > Who likes this idea? > > > _______________________________________________ > lemonade mailing list > lemonade(a)ietf.org > https://www1.ietf.org/mailman/listinfo/lemonade > > > > > > -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com _______________________________________________ lemonade mailing list lemonade(a)ietf.org https://www1.ietf.org/mailman/listinfo/lemonade

1 0

[Dovecot] dovecot-lda compilation problem and feature request
by Michael Goth 18 Aug '05

18 Aug '05

Hi! I tried to compile deliver from CVS (as described in the wiki), but unfortunately make stopped with the following error: In file included from sieve_interface.h:37, from script.h:31, from addr.y:34: sieve_err.h:7:24: et/com_err.h: No such file or directory make[3]: *** [addr.o] Error 1 make[3]: Leaving directory `/usr/local/src/dovecot/dovecot-lda-CVS/src/libsieve'make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot/dovecot-lda-CVS/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot/dovecot-lda-CVS' make: *** [all] Error 2 Any suggestions how to fix this? And a second question about deliver: Is it possible to use a system wide default sieve script which applies to all users that do not have their own sieve script? That would be a great feature to easily set up (and maintain) some defaults for virus/spam filtering. Maildrop does it like this ;-) Thanks, Michael

3 2

[Dovecot] 2nd postgresql server to connect when 1st fail
by Krzysztof A. Adamski 18 Aug '05

18 Aug '05

I need to have mail service working even when my postgresql server will fail. In postfix i set 2 different servers and if 1st fail, postfix try to use 2nd. Is there any way to do this in dovecot? ---------------------------------------------------------------------- Zostan internetowa dziewczyna wakacji! > http://link.interia.pl/f18ac

5 10