[Dovecot] ignors the configure prefix

2009-10-04 Thread vwc72283
1.2.5 is ignoring the configure -prefix switch. It you install it some place 
else with
the -prefix then I get errors all over the place becuase things are hard coded 
to use
the default and it can't find anything any more like:

Fatal: execv(/usr/local/libexec/dovecot/ssl-build-param) failed: No such file 
or directory

and

Error: Can't open configuration file /usr/local/etc/dovecot.conf: No such file 
or directory
Fatal: Invalid configuration in /usr/local/etc/dovecot.conf

and

Starting Dovecot Imap: Error: auth_executable: Can't use
/usr/local/libexec/dovecot/dovecot-auth: No such file or directory

How do I fix this?





Re: [Dovecot] ignors the configure prefix

2009-10-04 Thread Hugo Monteiro

vwc72...@voicenet.com wrote:

1.2.5 is ignoring the configure -prefix switch. It you install it some place 
else with
the -prefix then I get errors all over the place becuase things are hard coded 
to use
the default and it can't find anything any more like:

Fatal: execv(/usr/local/libexec/dovecot/ssl-build-param) failed: No such file 
or directory

and

Error: Can't open configuration file /usr/local/etc/dovecot.conf: No such file 
or directory
Fatal: Invalid configuration in /usr/local/etc/dovecot.conf

and

Starting Dovecot Imap: Error: auth_executable: Can't use
/usr/local/libexec/dovecot/dovecot-auth: No such file or directory

How do I fix this?




  



Have you tried to build the SRPM available at 
ftp://download.fedora.redhat.com/pub/fedora/linux/development/source/SRPMS/dovecot-1.2.5-2.fc12.src.rpm 
?


I do know that these are probably not the words you want to hear now, 
but i would advise you to test upgrades on a test system, deploying 
changes to the production server only after you know everything is alright.


R's,

Hugo Monteiro.

--
ci.fct.unl.pt:~# cat .signature

Hugo Monteiro
Email: hugo.monte...@fct.unl.pt
Telefone : +351 212948300 Ext.15307
Web  : http://hmonteiro.net

Centro de Informática
Faculdade de Ciências e Tecnologia da
   Universidade Nova de Lisboa
Quinta da Torre   2829-516 Caparica   Portugal
Telefone: +351 212948596   Fax: +351 212948548
www.ci.fct.unl.pt ap...@fct.unl.pt

ci.fct.unl.pt:~# _



Re: [Dovecot] Error: userdb lookup: connect(/var/run/dovecot/auth-master) failed: Permission denied

2009-10-04 Thread Jerry
On Sat, 3 Oct 2009 18:31:03 -0400
Jerry ges...@yahoo.com wrote:

[snip]

I apologize for replying to my own message. However, this problem
has gotten me totally confused. I can POP mail without any problem;
however, I cannot use Dovecot as a virtual delivery agent. I am still
receiving this error message:

Oct 04 08:08:41 deliver(u...@mydomain.net): Error: userdb lookup: 
connect(/var/run/dovecot/auth-master) failed: Permission denied

This is the file listing:

srw---   1 root  wheel   0B Oct  4 07:23 auth-master=


-- 
Jerry
ges...@yahoo.com

The only people who make love all the time are liars.

Louis Jordan


Re: [Dovecot] ignors the configure prefix

2009-10-04 Thread vwc72283

 vwc72...@voicenet.com wrote:
 1.2.5 is ignoring the configure -prefix switch. It you install it some place 
 else with
 the -prefix then I get errors all over the place becuase things are hard 
 coded to use
 the default and it can't find anything any more like:

 Fatal: execv(/usr/local/libexec/dovecot/ssl-build-param) failed: No such 
 file or
 directory

 and

 Error: Can't open configuration file /usr/local/etc/dovecot.conf: No such 
 file or
 directory
 Fatal: Invalid configuration in /usr/local/etc/dovecot.conf

 and

 Starting Dovecot Imap: Error: auth_executable: Can't use
 /usr/local/libexec/dovecot/dovecot-auth: No such file or directory

 How do I fix this?







 Have you tried to build the SRPM available at
 ftp://download.fedora.redhat.com/pub/fedora/linux/development/source/SRPMS/dovecot-1.2.5-2.fc12.src.rpm
 ?

Yes, I have tried it. There are errors in that release, at least one file fails 
the MD5
hash. Also, fc12 stuff often does not work right on el5. el5 has specific 
SElinux
policies and expects dovecot to live in a specific place (/usr). While you can 
change
where it installs with -prefix, the code its self seems to want to live at 
/usr/local
since those references don't seem to change. Now if the .spec file can fix that 
I would
be interested in how it does it, but there is too much work involved to find 
out if the
.spec author knows something I don't.


 I do know that these are probably not the words you want to hear now,
 but i would advise you to test upgrades on a test system, deploying
 changes to the production server only after you know everything is alright.

This is the test system. Well, they're VMs, I copy and flip them.


 R's,

 Hugo Monteiro.

 --
 ci.fct.unl.pt:~# cat .signature

 Hugo Monteiro
 Email  : hugo.monte...@fct.unl.pt
 Telefone : +351 212948300 Ext.15307
 Web  : http://hmonteiro.net

 Centro de Informática
 Faculdade de Ciências e Tecnologia da
  Universidade Nova de Lisboa
 Quinta da Torre   2829-516 Caparica   Portugal
 Telefone: +351 212948596   Fax: +351 212948548
 www.ci.fct.unl.pt   ap...@fct.unl.pt

 ci.fct.unl.pt:~# _








Re: [Dovecot] Another 1.2.5 imap panic

2009-10-04 Thread Chris Wakelin


Chris Wakelin wrote:
 We've had another random imap process crash. This is with the original
 1.2.5 imap (I haven't applied the patch for two processes creating an
 index simultaneously):
 
 Backtrace:

Sorry, wrong binary again (it *was* rather late at night!). Here's the
proper backtrace

 #0  0xff21fe78 in _libc_kill () from /usr/lib/libc.so.1
 #1  0xff1b5a3c in abort () from /usr/lib/libc.so.1
 #2  0xbe258 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at 
 failures.c:160
 #3  0xbeb14 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, 
 fmt=0x0, args=0xffbee9c8) at failures.c:440
 #4  0xbe414 in i_panic (format=0xe29b8 file %s: line %d (%s): assertion 
 failed: (%s)) at failures.c:207
 #5  0x5a238 in istream_raw_mbox_get_body_size (stream=0x12a250, 
 expected_body_size=18446744073709551615) at istream-raw-mbox.c:621
 #6  0x5a4d8 in istream_raw_mbox_next (stream=0x12a250, 
 expected_body_size=18428424857071839939) at istream-raw-mbox.c:665
 #7  0x5a7a0 in istream_raw_mbox_seek (stream=0x0, offset=523301) at 
 istream-raw-mbox.c:704
 #8  0x5ae58 in mbox_file_seek (mbox=0x1272a8, view=0x127c60, seq=17, 
 deleted_r=0xffbeebb7) at mbox-file.c:177
 #9  0x5c7d8 in mbox_mail_seek (mail=0x12be80) at mbox-mail.c:85
 #10 0x5cd74 in mbox_mail_init_stream (mail=0x12be80) at mbox-mail.c:276
 #11 0x5cea4 in mbox_mail_get_stream (_mail=0x128e24, hdr_size=0x0, 
 body_size=0x0, stream_r=0xffbeed8c) at mbox-mail.c:318
 #12 0x79354 in mail_get_stream (mail=0x0, hdr_size=0x0, body_size=0x0, 
 stream_r=0xffbeed8c) at mail.c:168
 #13 0x6a958 in index_mail_set_seq (_mail=0x12be80, seq=17) at 
 index-mail.c:1326
 #14 0x5ced0 in mbox_mail_set_seq (_mail=0x12be80, seq=17) at mbox-mail.c:329
 #15 0x79034 in mail_set_seq (mail=0x12be80, seq=17) at mail.c:29
 #16 0x6f864 in index_storage_search_next_nonblock (_ctx=0x12a070, 
 mail=0x12be80, tryagain_r=0xffbeefcf) at index-search.c:1296
 #17 0x7f1a0 in mailbox_search_next_nonblock (ctx=0x12a070, mail=0x12be80, 
 tryagain_r=0xffbeefcf) at mail-storage.c:770
 #18 0x7f154 in mailbox_search_next (ctx=0x12a070, mail=0x12be80) at 
 mail-storage.c:759
 #19 0x2598c in fetch_and_copy (client=0x11e8d8, destbox=0x1272a8, t=0x128c98, 
 search_args=0x1, src_uidset_r=0xffbef0f4, copy_count_r=0xffbef0f0)
 at cmd-copy.c:56
 #20 0x25c24 in cmd_copy (cmd=0x11eb60) at cmd-copy.c:145
 #21 0x2d064 in client_command_input (cmd=0x11eb60) at client.c:611
 #22 0x2cf08 in client_command_input (cmd=0x11eb60) at client.c:660
 #23 0x2d0ec in client_handle_next_command (client=0x11e8d8, 
 remove_io_r=0xffbef2d7) at client.c:701
 #24 0x2d1e0 in client_handle_input (client=0x11e8d8) at client.c:713
 #25 0x2d318 in client_input (client=0x11e8d8) at client.c:752
 #26 0xc7ea4 in io_loop_handler_run (ioloop=0x11b370) at ioloop-poll.c:203
 #27 0xc7694 in io_loop_run (ioloop=0x11b370) at ioloop.c:335
 #28 0x36e34 in main (argc=1119232, argv=0xffbef51c, envp=0xffbef52c) at 
 main.c:327

I've had another crash since with a different user but what looks like
exactly the same backtrace (except for stream numbers etc.).

Best Wishes,
Chris

-- 
--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+-
Christopher Wakelin,   c.d.wake...@reading.ac.uk
IT Services Centre, The University of Reading,  Tel: +44 (0)118 378 8439
Whiteknights, Reading, RG6 2AF, UK  Fax: +44 (0)118 975 3094


Re: [Dovecot] v1.2.5 released (managesieve updated)

2009-10-04 Thread Stephan Bosch

Timo Sirainen wrote:

http://dovecot.org/releases/1.2/dovecot-1.2.5.tar.gz
http://dovecot.org/releases/1.2/dovecot-1.2.5.tar.gz.sig


http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.5-managesieve-0.11.9.diff.gz
http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.5-managesieve-0.11.9.diff.gz.sig


Regards,

Stephan


Re: [Dovecot] v1.1.19 released (managesieve updated)

2009-10-04 Thread Stephan Bosch

Timo Sirainen wrote:

http://dovecot.org/releases/1.1/dovecot-1.1.19.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.19.tar.gz.sig


http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.19-managesieve-0.10.7.diff.gz
http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.19-managesieve-0.10.7.diff.gz.sig

Regards,

Stephan


Re: [Dovecot] sievec fails when last line is a comment without trailing \n

2009-10-04 Thread Stephan Bosch

Peter Marschall wrote:

Hi,

when switching from Dovecot 1.1 + cmusieve to Dovecot 1.2 + sieve
I stumbled upon the following problem:

My sieve files, generated with Dovecot 1.1's managesieve, did not
compile anymore with sieve's sievec.
The error message was: 
	error: end of file before end of hash comment.


Looking a bit closer I found that the last line, which was a comment,
did not have a trailing newline.
Adding a newline fixed the problem.

I do not know if Dovecot 1.2's managesieve behaves differently,
but the upgrade from cmusieve to sieve 


In the spirit of be generous in what you accept but strict in what you send,
is it possible for sievec to not throw an error in this case,
but simply compile the file.

This might help other updates from cmusieve - sieve as well.


Good suggestion:

http://hg.rename-it.nl/dovecot-1.2-sieve/rev/3c3984419921

It now triggers a warning in stead of an error.

Regards,

Stephan.


[Dovecot] Dovecot fails when vpopmail is enabled

2009-10-04 Thread Sherin George
Hello Friends,

=
-bash-3.2# dovecot --version
1.2.5
-bash-3.2# dovecot -n
# 1.2.5: /usr/local/etc/dovecot.conf
# OS: Linux 2.6.18-128.4.1.el5xen x86_64 CentOS release 5.2 (Final)
login_dir: /usr/local/var/run/dovecot/login
login_executable: /usr/local/libexec/dovecot/imap-login
lda:
  postmaster_address: postmas...@example.com
auth default:
  passdb:
driver: pam
  userdb:
driver: passwd
=


I am trying to enable vpomail support in dovecot.

I modified default dovecot conf file as given below.

===
-bash-3.2# diff /etc/dovecot.conf /etc/dovecot.conf.original
691c691
 auth_cache_size = 1000
---
 #auth_cache_size = 0
886c886
   passdb vpopmail {
---
   #passdb vpopmail {
888,890c888,890
 args = cache_key=%u%s *
   }

---
 #args =
   #}

===

I am not able to run dovecot after this.

=
-bash-3.2# /etc/init.d/dovecot restart
Stopping Dovecot Imap: [FAILED]
Starting Dovecot Imap: [  OK  ]
-bash-3.2# /etc/init.d/dovecot restart
Stopping Dovecot Imap: [FAILED]
Starting Dovecot Imap: [  OK  ]
-bash-3.2# /etc/init.d/dovecot restart
Stopping Dovecot Imap: [FAILED]
Starting Dovecot Imap: [  OK  ]
-bash-3.2#
=

Could some one please help me to find what went wrong.

--
Thanks,
Sherin


[Dovecot] Expire Plugin Configuration Question

2009-10-04 Thread Roland Roberts
I am very confused looking at the expires plugin and its configuration.  
What is confusing me the most is that it appears that I have to 
configure expiration globally, meaning, for example, that the Trash 
mailbox expiration interval is the same regardless of the user.  What I 
really am looking for is per-user configurable rules.  Those would 
obviously not be able to be in a file configuration but would have to be 
in some shared/sharable resource.  Is such a thing possible?  What I 
really want is the ability to move my expiration rules out of my email 
client and into dovecot.  That would be very useful for me since I 
access my mail from more than one host and via more than one client.


roland

--
   PGP Key ID: 66 BC 3B CD
Roland B. Roberts, PhD RL Enterprises
rol...@rlenter.com6818 Madeline Court
rol...@astrofoto.org   Brooklyn, NY 11220



Re: [Dovecot] Expire Plugin Configuration Question

2009-10-04 Thread Roland Roberts

Charles Marcus wrote:

On 10/4/2009 7:50 PM, Roland Roberts wrote:
  
I am very confused looking at the expires plugin and its configuration. 
What is confusing me the most is that it appears that I have to

configure expiration globally, meaning, for example, that the Trash
mailbox expiration interval is the same regardless of the user.  What I
really am looking for is per-user configurable rules.



Hmmm... interesting. I don't think you can use extra fields for this
now, but I wonder if it would be possible to modify expire plugin to do so?
  


Well, it's a bit disappointing to hear that it can't be done, but I'm 
not surprised since that's what I was inferring from the documentation.  
I was hoping to be able to configure a uniform expiration policy, just 
like I currently use procmail to file my mail without having to have a 
separate config for each client.


roland

--
   PGP Key ID: 66 BC 3B CD
Roland B. Roberts, PhD RL Enterprises
rol...@rlenter.com6818 Madeline Court
rol...@astrofoto.org   Brooklyn, NY 11220



Re: [Dovecot] Expire Plugin Configuration Question

2009-10-04 Thread Charles Marcus
On 10/4/2009, Roland Roberts (rol...@astrofoto.org) wrote:
 I was hoping to be able to configure a uniform expiration policy,
 just like I currently use procmail to file my mail without having to
 have a separate config for each client.

What I had said was I don't think (maybe you can) that you can do it on
a per user basis...

If by 'uniform' you mean 'global', currently all you *can* do is set a
global policy...

-- 

Best regards,

Charles


Re: [Dovecot] Expire Plugin Configuration Question

2009-10-04 Thread Roland Roberts

Charles Marcus wrote:

On 10/4/2009, Roland Roberts (rol...@astrofoto.org) wrote:
  

I was hoping to be able to configure a uniform expiration policy,
just like I currently use procmail to file my mail without having to
have a separate config for each client.



What I had said was I don't think (maybe you can) that you can do it on
a per user basis...

If by 'uniform' you mean 'global', currently all you *can* do is set a
global policy...
  


The documentation doesn't say anything about per-user which implies it 
can't be done.  I would very much like to be wrong on that.


By uniform, I don't mean global.  I mean that the policy is set (by me 
on each of my folders) once instead of once per mail client.


roland

--
   PGP Key ID: 66 BC 3B CD
Roland B. Roberts, PhD RL Enterprises
rol...@rlenter.com6818 Madeline Court
rol...@astrofoto.org   Brooklyn, NY 11220