Re: [Dovecot] Broken dovecot-uidlist files

[Ulrich Zehl]

On Mon, Feb 23, 2009 at 12:10:29PM -0500, Timo Sirainen wrote:
> On Mon, 2009-02-23 at 16:27 +0100, Ulrich Zehl wrote:
> > I did
> > 
> > # mount -o remount,actimeo=0 /srv/storage
> 
> To both servers?

There's three Dovecot servers (NFS clients), actually, and I remounted
/srv/storage on all of them.

> > > So allina modified dovecot-uidlist and soon afterwards laura probably
> > > was using a cached dovecot-uidlist and corrupted it.
> > 
> > Since the corrupted files are available for a little while (in the example,
> > it was ~ 15 minutes), will it help if I repeatedly check all
> > dovecot-uidlists and save those found to be corrupted to a special
> > directory, so that we can see what the corruption actually is?
> 
> I suppose looking at a couple of those could verify if it's really just
> NFS caching related corruption or something else.

Okay, I will post results when I have them.

[Dovecot] "dovecot-uidlist: Duplicate file entry at line" error

[Dovecot List]

This is with respect to an error that I am facing in dovecot.

The error is that is seen in logs is "Feb 23 00:04:46 mailblade1
dovecot: IMAP(USERNAME): /indexes/USERNAME/.INBOX/dovecot-uidlist:
Duplicate file entry at line 7:
1234776125.M559298P3988.s2o.qlc.co.in,S=13111,W=13470:2, (uid 94277 ->
97805)"

This error is seen for multiple users.

Once this error occurs for a user, the user downloads mails all over
again in POP3.

Please help! And let us know what can be done.

Details of our setup
--

The setup has deployed 2 servers with Dovecot using the same storage
over NFS with the following options:

* Dovecot Version: v1.1.8 on both servers
* Server1 for retrieving mails using POP and imap Access
* Server2 for Mail Delivery via postfix and dovecot as LDA
* Number of users: 2
* Number of mails Handled: 500K per day

--Note: Based on recommendation, kernel was upgraded from 2.6.18 (-
see below for details) and yet the issue persists.


Specifications of the server
---
1) Server spec used for mail Access
    OS: Linux 2.6.28 i686 CentOS release 5.2 (Final)
    kernel : 2.6.28
    /proc/sys/fs/inotify/max_user_instances = 1024
    /proc/sys/fs/epoll/max_user_instances  = 1024
    Memory : 2GB

2) Server used for Dovecot Delivery
    OS: Linux 2.6.21-1.3194.fc7 i686 Fedora release 7 (Moonshine)
    kernel : 2.6.21
    /proc/sys/fs/inotify/max_user_instances = 128
    /proc/sys/fs/epoll/max_user_instances  = NA
    Memory : 2 GB


Conf on both the system as follows =
--
# 1.1.8: /usr/local/etc/dovecot.conf
#NFS Settings
mmap_disable: yes
mail_nfs_storage: yes
mail_nfs_index: yes

#Other special settings
pop3_no_flag_updates(pop3): yes
pop3_lock_session(pop3): yes



# all the settings
base_dir: /usr/local/var/run/dovecot
log_path:
info_log_path:
log_timestamp: %b %d %H:%M:%S
syslog_facility: mail
protocols: imap pop3
listen(default): *:143
listen(imap): *:143
listen(pop3): *:110
ssl_listen:
ssl_disable: yes
ssl_ca_file:
ssl_cert_file: /etc/ssl/certs/dovecot.pem
ssl_key_file: /etc/ssl/private/dovecot.pem
ssl_key_password:
ssl_parameters_regenerate: 168
ssl_cipher_list:
ssl_cert_username_field: commonName
ssl_verify_client_cert: no
disable_plaintext_auth: no
verbose_ssl: no
shutdown_clients: yes
nfs_check: yes
version_ignore: no
login_dir: /usr/local/var/run/dovecot/login
login_executable(default): /usr/local/libexec/dovecot/imap-login
login_executable(imap): /usr/local/libexec/dovecot/imap-login
login_executable(pop3): /usr/local/libexec/dovecot/pop3-login
login_user: dovecot
login_greeting: Welcome to MailServe Popserver.
login_log_format_elements: user=<%u> method=%m rip=%r lip=%l %c
login_log_format: %$: %s
login_process_per_connection: no
login_chroot: yes
login_greeting_capability: no
login_process_size: 64
login_processes_count: 3
login_max_processes_count: 128
login_max_connections: 256
valid_chroot_dirs:
mail_chroot:
max_mail_processes: 600
mail_max_userip_connections(default): 50
mail_max_userip_connections(imap): 50
mail_max_userip_connections(pop3): 8
verbose_proctitle: yes
first_valid_uid: 99
last_valid_uid: 0
first_valid_gid: 99
last_valid_gid: 0
mail_extra_groups:
mail_access_groups:
mail_privileged_group:
mail_uid:
mail_gid:
mail_location: maildir:~/Maildir:INDEX=/indexes/%u:CONTROL=/indexes/%u
mail_cache_fields:
mail_never_cache_fields: imap.envelope
mail_cache_min_mail_count: 0
mailbox_idle_check_interval: 30
mail_debug: no
mail_full_filesystem_access: no
mail_max_keyword_length: 50
mail_save_crlf: no
mmap_disable: yes
dotlock_use_excl: yes
fsync_disable: no
mail_nfs_storage: yes
mail_nfs_index: yes
mailbox_list_index_disable: yes
lock_method: fcntl
maildir_stat_dirs: no
maildir_copy_with_hardlinks: yes
maildir_copy_preserve_filename: no
mbox_read_locks: fcntl
mbox_write_locks: dotlock fcntl
mbox_lock_timeout: 300
mbox_dotlock_change_timeout: 120
mbox_min_index_size: 0
mbox_dirty_syncs: yes
mbox_very_dirty_syncs: no
mbox_lazy_writes: yes
dbox_rotate_size: 2048
dbox_rotate_min_size: 16
dbox_rotate_days: 1
umask: 63
mail_drop_priv_before_exec: no
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/libexec/dovecot/imap
mail_executable(pop3): /usr/local/libexec/dovecot/pop3
mail_process_size: 256
mail_plugins(default): quota imap_quota
mail_plugins(imap): quota imap_quota
mail_plugins(pop3): quota
mail_plugin_dir(default): /usr/local/lib/dovecot/imap
mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3
mail_log_prefix: %Us(%u):
mail_log_max_lines_per_sec: 10
imap_max_line_length: 65536
imap_capability:
imap_client_workarounds:
imap_logout_format: bytes=%i/%o
pop3_no_flag_updates(default): no
pop3_no_flag_updates(imap): no
pop3_no_flag_updates(pop3): yes
pop3_enable_last: no
pop3_reuse_xuidl: no
pop3_lock_session(default): no
pop3_lock_session(imap): no
pop3_lock_session(pop3): yes
pop3_uidl_format: %08Xu%08Xv
pop3_client_

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Linux Advocate]

thanx timo, u were right. i am confusing things.

vmail needs to exist as a unix user (nologin priveleges) not as a virtual user.
just give ownership of the folders to vmail...  since postfix LDA doesnt need 
to acccess the folders anymore...

right? will test dovecot lda and report back.

> > 
> > Ok. but its amazing that dovecot can deliver as vmail, a user who doesnt 
> exist.how does it accomplish this?
> 
> Huh? Maybe you're confusing some concepts. Let's see..
> 
> vmail = UNIX user = typically in /etc/passwd. Postfix's pipe program looks up 
> the UID number based on the UNIX username. Typically from /etc/passwd. Then 
> it 
> sets the deliver process's UNIX UID to this number.
> 
> Dovecot deliver then reads the config file and looks up the destination 
> username 
> from dovecot-auth. Depending on your configuration, it either receives vmail 
> (which gets converted to UID) or the UID number directly. In any case it 
> notices 
> that the process's current UNIX UID is the same as the looked up UID, so it 
> does 
> nothing.
> 
> Destination username lookup is completely different from the UNIX UID, so 
> there's no need to have a "vmail" user listed in Dovecot's passdb/userdb. 
> It's 
> never looked up from there.
> 
> > [r...@fwgw vmail]# ls -l
> > 
> > drwx-- 6 postfix postfix 4096 Feb 23 18:25 mesara.biz
> > 
> > Do i need to changes the permissions on the above?
> 
> Yes. Otherwise you'll get a permission denied error.
> 
> You could always just try and see what error messages Dovecot logs. It's 
> really 
> good at giving understandable error messages, especially the latest v1.1 
> version.



  

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Timo Sirainen]

On Feb 23, 2009, at 9:35 PM, Linux Advocate wrote:

I just heard that Postfix doesn't allow you to do that (as you  
would have

noticed too). So just use vmail.


Ok. but its amazing that dovecot can deliver as vmail, a user who  
doesnt exist.how does it accomplish this?


Huh? Maybe you're confusing some concepts. Let's see..

vmail = UNIX user = typically in /etc/passwd. Postfix's pipe program  
looks up the UID number based on the UNIX username. Typically from / 
etc/passwd. Then it sets the deliver process's UNIX UID to this number.


Dovecot deliver then reads the config file and looks up the  
destination username from dovecot-auth. Depending on your  
configuration, it either receives vmail (which gets converted to UID)  
or the UID number directly. In any case it notices that the process's  
current UNIX UID is the same as the looked up UID, so it does nothing.


Destination username lookup is completely different from the UNIX UID,  
so there's no need to have a "vmail" user listed in Dovecot's passdb/ 
userdb. It's never looked up from there.



[r...@fwgw vmail]# ls -l

drwx-- 6 postfix postfix 4096 Feb 23 18:25 mesara.biz

Do i need to changes the permissions on the above?


Yes. Otherwise you'll get a permission denied error.

You could always just try and see what error messages Dovecot logs.  
It's really good at giving understandable error messages, especially  
the latest v1.1 version.

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Linux Advocate]

> >>> my  /home/vmail/ directories are owned by postfix. do i then need to make
> >> vmail a member of the group?
> >> 
> >> You could just execute Dovecot LDA using postfix user.
> >> 
> > 
> > Therefore, ( copied from dovecot wiki, http://wiki.dovecot.org/LDA/Postfix )
> > 
> > 
> > dovecot   unix  -   n   n   -   -   pipe
> >  flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f 
> ${sender} -d ${recipient}
> > 
> > 
> > I could change the user=vmail:vmail to postfix:postfix ?
> 
> 
> I just heard that Postfix doesn't allow you to do that (as you would have 
> noticed too). So just use vmail.

Ok. but its amazing that dovecot can deliver as vmail, a user who doesnt 
exist.how does it accomplish this? 

[r...@fwgw vmail]# ls -l

drwx-- 6 postfix postfix 4096 Feb 23 18:25 mesara.biz

Do i need to changes the permissions on the above?


  

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Timo Sirainen]

On Feb 23, 2009, at 9:23 PM, Linux Advocate wrote:

Timo, if we use the dovecot LDA, we do need to create a user  
"vmail" , with no

login priveleges etc?

No.

my  /home/vmail/ directories are owned by postfix. do i then need  
to make

vmail a member of the group?

You could just execute Dovecot LDA using postfix user.



Therefore, ( copied from dovecot wiki, http://wiki.dovecot.org/LDA/Postfix 
 )



dovecot   unix  -   n   n   -   -   pipe
 flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver  
-f ${sender} -d ${recipient}



I could change the user=vmail:vmail to postfix:postfix ?



I just heard that Postfix doesn't allow you to do that (as you would  
have noticed too). So just use vmail.

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Linux Advocate]

> >> 
> >>> 3. Quota Management ( Creating, enforcing, notifying ) - is it done thru
> >> dovecot or postfix or are both needed?
> >> 
> >> Depends on if you use Dovecot LDA. If not, then both.
> > 
> > Timo, if we use the dovecot LDA, we do need to create a user "vmail" , with 
> > no 
> login priveleges etc?
> 
> No.
> 
> > my  /home/vmail/ directories are owned by postfix. do i then need to make 
> vmail a member of the group?
> 
> You could just execute Dovecot LDA using postfix user.
> 

Therefore, ( copied from dovecot wiki, http://wiki.dovecot.org/LDA/Postfix )


dovecot   unix  -   n   n   -   -   pipe
  flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f 
${sender} -d ${recipient}


I could change the user=vmail:vmail to postfix:postfix ?


  

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Timo Sirainen]

On Feb 23, 2009, at 8:49 PM, Linux Advocate wrote:






On Sun, 2009-02-22 at 23:58 -0800, Linux Advocate wrote:
2. What is the benefit of using  Dovecot's SASL as compared to  
Cyrus SASL? Is

there better performance?

Probably not, but I've always hated configuring Cyrus SASL. It's  
not as

flexible and the error and debug messages are worse.

3. Quota Management ( Creating, enforcing, notifying ) - is it  
done thru

dovecot or postfix or are both needed?

Depends on if you use Dovecot LDA. If not, then both.


Timo, if we use the dovecot LDA, we do need to create a user  
"vmail" , with no login priveleges etc?


No.

my  /home/vmail/ directories are owned by postfix. do i then need to  
make vmail a member of the group?


You could just execute Dovecot LDA using postfix user.

Or will it be easier to make /home/vmail to be owned by user vmail?  
in this scenario, we need not worry about postfix access bcos its  
dovecot's LDA that is writing and reading from /home/vmail?


I'd recommend using vmail user in any case. Dovecot (LDA or IMAP or  
POP3) really doesn't need access to Postfix's private files.

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Linux Advocate]

> 
> On Sun, 2009-02-22 at 23:58 -0800, Linux Advocate wrote:
> > 2. What is the benefit of using  Dovecot's SASL as compared to Cyrus SASL? 
> > Is 
> there better performance?
> 
> Probably not, but I've always hated configuring Cyrus SASL. It's not as
> flexible and the error and debug messages are worse.
> 
> > 3. Quota Management ( Creating, enforcing, notifying ) - is it done thru 
> dovecot or postfix or are both needed?
> 
> Depends on if you use Dovecot LDA. If not, then both.

Timo, if we use the dovecot LDA, we do need to create a user "vmail" , with no 
login priveleges etc?
my  /home/vmail/ directories are owned by postfix. do i then need to make vmail 
a member of the group?

Or will it be easier to make /home/vmail to be owned by user vmail? in this 
scenario, we need not worry about postfix access bcos its dovecot's LDA that is 
writing and reading from /home/vmail?


regards,
mgomez



  

Re: [Dovecot] OT: Fixing Messages To Be RFC 2822 Compliant

[Neil]

Thank you for the suggestion.

Will this still work if I'm using the maildir format?  (Something I
should've mentioned upfront, sorry...)

On Mon, Feb 23, 2009 at 5:17 AM, Darabos Edvárd Konrád <
n...@hippy.csoma.elte.hu> wrote:

> Hi!
>
> EXAMPLES
>   ...
>  To convert a non-standard mailbox file into a standard mailbox file
> you
>  can use:
> formail -ds >new_mailbox
>
>  Or, if you have a very tolerant mailer:
> formail -a Date: -ds >new_mailbox
>   ...
>
>   These are not working based on explicit instructions. You may give them a
> try. I don't know how bad is your mbox...
>
> Bye
>
>
> Neil wrote:
>
>> Hi,
>>
>> Yeah, I'm vaguely familiar with formail, but (after reviewing the
>> literature) it doesn't seem like it can be used to identify/fix existing
>> messages (unless you already know how they're broken and give it explicit
>> instructions to fix them).
>>
>> Is there something I'm missing?
>>
>> Thanks.
>>
>> On Mon, Feb 23, 2009 at 4:24 AM, Darabos Edvárd Konrád <
>> n...@hippy.csoma.elte.hu> wrote:
>>
>>
>>
>>> Hello!
>>>
>>>  I am not sure about what you want, but I found something that maybe
>>> useful for you.
>>>  http://gd.tuwien.ac.at/linuxcommand.org/man_pages/formail1.html
>>>
>>> Bye
>>>
>>>
>>> Neil wrote:
>>>
>>>
>>>
 Soapparently I have some messages which are not RFC compliant
 sitting
 in
 my mailboxes (mostly older ones), and I have some software which is
 refusing
 to handle such messages.

 1. Does anyone know of a nice way to verify that all my messages are
 compliant/find those that aren't? (I suppose I could use the existing
 failing software, but I was hoping for something a little more
 robust...)

 2. Does anyone know of any tools that will do The Right Thing as far as
 fixing these messages are concerned?

 Googling didn't turn up much for me, but maybe I wasn't hitting the
 right
 terms ("RFC message repair", "fix email message", etc.).

 Thanks.





>>>
>>>
>>
>>
>>
>
>

Re: [Dovecot] pkgsrc-ing sieve and managesieve

[Timo Sirainen]

On Mon, 2009-02-23 at 22:55 +0100, Edgar Fuß wrote:
> I'm trying to integrate both the new sieve implementation and managesieve 
> into pkgsrc.
> 
> Managesieve seems to need some dovecot libraries that dovecot doesn't install 
> (lib-storage/libstorage.a, lib-auth/libauth.a, lib-imap/libimap.a, 
> lib-index/libindex.a, lib-mail/libmail.a, lib-charset/libcharset.a, 
> lib-dict/libdict.a and lib-charset/libcharset.a). There seems to be no 
> provision in pkgsrc for the build of a package needing the work directory of 
> the build of another package.
> 
> Would it make sense for dovecot to install those libraries?

I think the proper solution for this would be for Dovecot to install and
use libdovecot.so and libdovecot-storage.so instead of all these
small .a libraries that are only useful for people who happen to build
external Dovecot binaries themselves. But as to when those .so files
would be available .. dunno, I could still get them to v1.2 if someone
sends me a patch. :)



signature.asc
Description: This is a digitally signed message part

[Dovecot] pkgsrc-ing sieve and managesieve

[Edgar Fuß]

I'm trying to integrate both the new sieve implementation and managesieve into 
pkgsrc.

Managesieve seems to need some dovecot libraries that dovecot doesn't install 
(lib-storage/libstorage.a, lib-auth/libauth.a, lib-imap/libimap.a, 
lib-index/libindex.a, lib-mail/libmail.a, lib-charset/libcharset.a, 
lib-dict/libdict.a and lib-charset/libcharset.a). There seems to be no 
provision in pkgsrc for the build of a package needing the work directory of 
the build of another package.

Would it make sense for dovecot to install those libraries?

Re: [Dovecot] sieve-test again

[Ian P. Christian]

2009/2/23 Stephan Bosch :
> This was also an issue for `deliver -p` and this is fixed by Timo.

That's fantastic Stephan, thanks!

Re: [Dovecot] sieve-test again

[Stephan Bosch]

Ian P. Christian schreef:

2009/2/23 Ian P. Christian :

I'm not sure what it is I'm doing wrong here, perhaps my 'test' mail
is not in the format expected by sieve-test.


I don't know why I didn't figure this out from my previous mail/error.

sieve-test appears not to handle relative paths as it's 2nd param.

This works:
# sieve-test -c -d - ./sievetest `pwd`/test

This doesn't:
# sieve-test -c -d - ./sievetest ./test


Ok, this was a bug. Thanks, fixed:

http://hg.rename-it.nl/dovecot-libsieve/rev/4d642db0b754

This was also an issue for `deliver -p` and this is fixed by Timo.

Regards,

--
Stephan Bosch
step...@rename-it.nl

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Timo Sirainen]

On Mon, 2009-02-23 at 13:14 -0500, Charles Marcus wrote:
> > And having Dovecot support also client SASL would require a lot of
> > new code which isn't used by Dovecot itself anywhere.
> 
> I understand... but it would still be nice... ;) maybe a good candidate
> for the Goggle Summer of Code?

Maybe .. We're looking into the Google SoC. I can't do it alone (at
least last year the rules required at least two mentors).



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Charles Marcus]

On 2/23/2009 12:12 PM, Timo Sirainen wrote:
 2. What is the benefit of using  Dovecot's SASL as compared to
 Cyrus SASL? Is there better performance?

>>> Probably not, but I've always hated configuring Cyrus SASL. It's
>>> not as flexible and the error and debug messages are worse.

>> I agree... but the one disadvantage to dovecot sasl is it cannot be
>> used as CLIENT mechanism... is adding this capability by any chance
>> on the radar?

> Well, as a client Cyrus SASL does pretty well already.

I know, but I'd prefer not to have them both installed if possible... ;)

> And having Dovecot support also client SASL would require a lot of
> new code which isn't used by Dovecot itself anywhere.

I understand... but it would still be nice... ;) maybe a good candidate
for the Goggle Summer of Code?

-- 

Best regards,

Charles

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Stephan Bosch]

Timo Sirainen schreef:

On Mon, 2009-02-23 at 09:50 -0500, Charles Marcus wrote:

On 2/23/2009 9:21 AM, Timo Sirainen wrote:

On Sun, 2009-02-22 at 23:58 -0800, Linux Advocate wrote:

2. What is the benefit of using  Dovecot's SASL as compared to Cyrus SASL? Is 
there better performance?

Probably not, but I've always hated configuring Cyrus SASL. It's not as
flexible and the error and debug messages are worse.

I agree... but the one disadvantage to dovecot sasl is it cannot be used
as CLIENT mechanism... is adding this capability by any chance on the radar?


Well, as a client Cyrus SASL does pretty well already. And having
Dovecot support also client SASL would require a lot of new code which
isn't used by Dovecot itself anywhere.
It could however be used in the test suite somewhere, e.g. to test the 
SASL mechanisms themselves. So it would have some merit :)


Regards,

--
Stephan Bosch
step...@rename-it.nl

Re: [Dovecot] from postfix deliver to dovecot deliver

[Pascal Volk]

On 23.02.2009 09:13 Johan Hendriks wrote:
> One more question regarding this.
> All the howto's are using a seperate user for the dovecot LDA, like vmail.
> Now all my mailboxes have the userid and groupid from postfix.
> Can i use the postfix user for the dovecot LDA?
> 

Citing PIPE(8postfix):
   user=username (required)

   user=username:groupname
  Execute  the  external  command with the rights of the
  specified username.  The software refuses  to  execute
  commands  with root privileges, or with the privileges
  of the mail system owner. If groupname  is  specified,
  the  corresponding  group  ID  is  used instead of the
  group ID of username.

You may read http://wiki.dovecot.org/LDA for more details.


Regards,
Pascal

-- 
Ubuntu is an ancient African word meaning “I can’t install Debian.”
 -- unknown

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Timo Sirainen]

On Mon, 2009-02-23 at 09:50 -0500, Charles Marcus wrote:
> On 2/23/2009 9:21 AM, Timo Sirainen wrote:
> > On Sun, 2009-02-22 at 23:58 -0800, Linux Advocate wrote:
> >> 2. What is the benefit of using  Dovecot's SASL as compared to Cyrus SASL? 
> >> Is there better performance?
> > 
> > Probably not, but I've always hated configuring Cyrus SASL. It's not as
> > flexible and the error and debug messages are worse.
> 
> I agree... but the one disadvantage to dovecot sasl is it cannot be used
> as CLIENT mechanism... is adding this capability by any chance on the radar?

Well, as a client Cyrus SASL does pretty well already. And having
Dovecot support also client SASL would require a lot of new code which
isn't used by Dovecot itself anywhere.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] Broken dovecot-uidlist files

[Timo Sirainen]

On Mon, 2009-02-23 at 16:27 +0100, Ulrich Zehl wrote:
> > > On the client side, it's Linux 2.6.23.16. All attribute cache related
> > > values are at their default, as far as I can tell. The entry in fstab
> > > reads:
> > > 
> > > nfs-server:/srv/storage /srv/storage nfs 
> > > rw,nfsvers=3,hard,intr,nosuid,noexec,nodev,noatime 0 0
> > 
> > Setting actimeo=0 probably fixes this, but also probably increases the
> > load a lot. actimeo=1 might work ok and reduce how often these problems
> > happen, but not eliminate them completely.
> > 
> > Dovecot's nfs settings should avoid this problem though. You could see
> > if upgrading your kernel helps. Some kernels have somewhat broken NFS
> > code.
> 
> I did
> 
> # mount -o remount,actimeo=0 /srv/storage

To both servers?

> > So allina modified dovecot-uidlist and soon afterwards laura probably
> > was using a cached dovecot-uidlist and corrupted it.
> 
> Since the corrupted files are available for a little while (in the example,
> it was ~ 15 minutes), will it help if I repeatedly check all
> dovecot-uidlists and save those found to be corrupted to a special
> directory, so that we can see what the corruption actually is?

I suppose looking at a couple of those could verify if it's really just
NFS caching related corruption or something else.


signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] sieve-test again

[Ian P. Christian]

2009/2/23 Ian P. Christian :
> I'm not sure what it is I'm doing wrong here, perhaps my 'test' mail
> is not in the format expected by sieve-test.

I don't know why I didn't figure this out from my previous mail/error.

sieve-test appears not to handle relative paths as it's 2nd param.

This works:
# sieve-test -c -d - ./sievetest `pwd`/test

This doesn't:
# sieve-test -c -d - ./sievetest ./test

[Dovecot] lda catchall

[Stéphane Cottin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I'm using dovecot lda in a qmail / vpopmail testing environnement.

I would like to replace vpopmail lda with dovecot's one , because of
quotas , sieve filers, indexing while delivering ...

Everything is working great, except the catchall.

If I want to bounce, a first line like "# bounce-no-mailbox" in the
.qmail file works, without this line, emails to unknown addresses are
deferred and stay in the queue, because they are deliverable for qmail,
but not for dovecot lda.

How can I set a catchall email address for dovecot lda ?


thx

Stéphane Cottin

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmixCcACgkQNgQUYqHIqqvttQCfcNBLd9Qo06g5nMcrfZAwVlpv
WegAnj7jIA/XFJWmt/2jkg1sxRYKRaI7
=JTTV
-END PGP SIGNATURE-
begin:vcard
fn;quoted-printable:St=C3=A9phane Cottin
n;quoted-printable:Cottin;St=C3=A9phane
org:VIXNS
adr:;;172 avenue de toulon;Marseille;;13010;France
email;internet:stephane.cot...@vixns.com
x-mozilla-html:FALSE
url:http://www.vixns.com
version:2.1
end:vcard

Re: [Dovecot] Broken dovecot-uidlist files

[Ulrich Zehl]

On Fri, Feb 20, 2009 at 05:50:28PM -0500, Timo Sirainen wrote:
> On Tue, 2009-01-27 at 08:30 +0100, Ulrich Zehl wrote:
> > On Mon, Jan 26, 2009 at 10:02:19AM -0500, Timo Sirainen wrote:
> > > Perhaps the NFS cache flushing doesn't work then for some reason. What
> > > OS (kernel) are you using on the Dovecot servers? How big values have
> > > you set to attribute cache?
> > 
> > On the client side, it's Linux 2.6.23.16. All attribute cache related
> > values are at their default, as far as I can tell. The entry in fstab
> > reads:
> > 
> > nfs-server:/srv/storage /srv/storage nfs 
> > rw,nfsvers=3,hard,intr,nosuid,noexec,nodev,noatime 0 0
> 
> Setting actimeo=0 probably fixes this, but also probably increases the
> load a lot. actimeo=1 might work ok and reduce how often these problems
> happen, but not eliminate them completely.
> 
> Dovecot's nfs settings should avoid this problem though. You could see
> if upgrading your kernel helps. Some kernels have somewhat broken NFS
> code.

I did

# mount -o remount,actimeo=0 /srv/storage

around 9 this morning, but I'm still seeing these errors pop up. (I
verified that there are mailboxes where this happened more than once
since 10 today.)

Is it time to upgrade my kernel, or are there other options left?

> > $ grep 123...@example.net mail.log
> > Jan 27 08:00:17 allina dovecot: pop3-login: Login: 
> > user=<123...@example.net>, method=PLAIN, rip=80.x.x.x, lip=10.x.x.x
> > Jan 27 08:00:19 allina dovecot: POP3(123...@example.net): Disconnected: 
> > Logged out top=0/0, retr=1/1283428, del=0/1, size=1283408
> > Jan 27 08:00:57 laura deliver(123...@example.net): 
> > msgid=<497eb077.09.01...@ernesto>: saved mail to INBOX
> 
> So allina modified dovecot-uidlist and soon afterwards laura probably
> was using a cached dovecot-uidlist and corrupted it.

Since the corrupted files are available for a little while (in the example,
it was ~ 15 minutes), will it help if I repeatedly check all
dovecot-uidlists and save those found to be corrupted to a special
directory, so that we can see what the corruption actually is?

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Charles Marcus]

On 2/23/2009 9:21 AM, Timo Sirainen wrote:
> On Sun, 2009-02-22 at 23:58 -0800, Linux Advocate wrote:
>> 2. What is the benefit of using  Dovecot's SASL as compared to Cyrus SASL? 
>> Is there better performance?
> 
> Probably not, but I've always hated configuring Cyrus SASL. It's not as
> flexible and the error and debug messages are worse.

I agree... but the one disadvantage to dovecot sasl is it cannot be used
as CLIENT mechanism... is adding this capability by any chance on the radar?

-- 

Best regards,

Charles

Re: [Dovecot] Which email clients support SMTP/IMAP via STDIN&STDOUT of proxy command?

[Andrzej Adam Filip]

Timo Sirainen  wrote:

> On Sun, 2009-02-22 at 17:59 +0100, Andrzej Adam Filip wrote:
>> Which email clients support SMTP/IMAP via STDIN&STDOUT of proxy command?
>
> For which OS? I know at least Evolution, mutt and pine support imap
> proxy commands. No idea about SMTP.

For future readers reference:
  emacs+gnus can do it too.

~/.emacs :

'(gnus-secondary-select-methods (quote (
  (nnimap "" 
(nnimap-stream shell) 
(imap-shell-program "/usr/sbin/dovecot -c ~/.dovecot/dovecot.conf  
--exec-mail imap")

~/.gnus :
(setq sendmail-program "/sendmail")

P.S.
I use "personal configuration file".

-- 
[pl>en: Andrew] Andrzej Adam Filip : a...@onet.eu
But you shall not escape my iambics.
  -- Gaius Valerius Catullus

[Dovecot] sieve-test again

[Ian P. Christian]

I'm not sure what it is I'm doing wrong here, perhaps my 'test' mail
is not in the format expected by sieve-test.

The 'test' file is a file taken directly from a dovecot maildir - so
is in the normal format of having headers, a new line, then the body.
There is nothing exceptional about this email.

Notice how the header below is 'innocent', however it appears that the
test is ignoring this header.

# grep DSPAM-Res test
X-DSPAM-Result: Innocent

# cat sievetest
require ["regex",
"fileinto","envelope","reject","vacation","relational","comparator-i;ascii-numeric"];

if header :contains "X-DSPAM-Result" "Innocent"
{
  fileinto "moo";
  stop;
}

# sieve-test -c ./sievetest ./test

Performed actions:

  (none)

Implicit keep:

 * store message in folder: INBOX

Info: final result: success


I don't think it's this header, but rather *all* headers, as the
following check also appears to fail.

if header :contains "To" "o"
{
  fileinto "Spam";
  stop;
}


Am I mis-using the tool?

Thanks,

Ian

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Timo Sirainen]

On Sun, 2009-02-22 at 23:58 -0800, Linux Advocate wrote:
> 2. What is the benefit of using  Dovecot's SASL as compared to Cyrus SASL? Is 
> there better performance?

Probably not, but I've always hated configuring Cyrus SASL. It's not as
flexible and the error and debug messages are worse.

> 3. Quota Management ( Creating, enforcing, notifying ) - is it done thru 
> dovecot or postfix or are both needed?

Depends on if you use Dovecot LDA. If not, then both.



signature.asc
Description: This is a digitally signed message part

Re: [Dovecot] sieve-test issue

[Ian P. Christian]

2009/2/23 Ian P. Christian :
> # sieve-test -c ../../../sieve/default.sieve
> 1235038385.M765212P13483.tch-mailstore1\,S\=3927\,W\=4017\:2\,S
> Fatal: Can't open mail stream as raw
>

Running strace on this, I see it's trying to do this:

open("sieve/default.svbin.tmp", O_WRONLY|O_CREAT|O_TRUNC, 0600) = 6
lseek(6, 0, SEEK_CUR)   = 0
fstat(6, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
write(6, "\276\272\376\312\0\0\0\0\2\0\0\0"..., 12) = 12
pwrite(6, "\0\0\0\0i\0\0\0"..., 8, 44)  = 8
pwrite(6, "\10\5regex\0\0\10fileinto\0\0\10envelope\0\0\6r"..., 105, 52) = 105
pwrite(6, "\1\0\0\0$\6\0\0"..., 8, 160) = 8
pwrite(6, "\10\0\1\2\3\4\5\6\7\4\0\0\0,\5score\0\7scoredp\0\tth"...,
1572, 168) = 1572
write(6, "\0\0\0\0i\0\0\0,\0\0\0\0\0\0\0"..., 16) = 16
write(6, "\1\0\0\0$\6\0\0\240\0\0\0\0\0\0\0"..., 16) = 16
close(6)= 0
rename("sieve/default.svbin.tmp", "sieve/default.svbin") = 0
stat("/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=4096, ...}) = 0
open("/tmp/./test", O_RDONLY)   = -1 ENOENT (No such file or directory)
write(2, "Fatal: Can't open mail stream as "..., 37Fatal: Can't open
mail stream as raw
) = 37
exit_group(89)  = ?


Was fixed like this:

# sieve-test -c sieve/default.sieve ./test
Fatal: Can't open mail stream as raw

# touch /tmp/test

# sieve-test -c sieve/default.sieve ./test

Performed actions:

  (none)

Implicit keep:

 * store message in folder: INBOX

Info: final result: success



If I remove that file, it stops working. Odd :)

[Dovecot] sieve-test issue

[Ian P. Christian]

Hi all,

I'm using a build of dovecot 1.2, and I'm seeing this:

# ls -al 1235038385.M765212P13483.tch-mailstore1\,S\=3927\,W\=4017\:2\,S
-rw--- 1 mail mail 3927 2009-02-19 10:13
1235038385.M765212P13483.tch-mailstore1,S=3927,W=4017:2,S

(r...@tch-mailstore1:/mailstore/mail/domain.net/i/ian/mail/.postini/cur)
(2009-02-23 13:46:04)
# sieve-test -c ../../../sieve/default.sieve
1235038385.M765212P13483.tch-mailstore1\,S\=3927\,W\=4017\:2\,S
Fatal: Can't open mail stream as raw


Can anyone suggest what this error means?

Thanks,

Ian

Re: [Dovecot] Update on Issues

[Charles Marcus]

On 2/22/2009, Gene Steinberg (g...@macnightowl.com) wrote:
> Linux server.paracastworld.net 2.6.27.15

Ummm... I think thats a quesion for your Distro support...

Timo can't be expected to keep up with which kernel works and which
doesn't from x number of patched kernels from x # of distro's.

-- 

Best regards,

Charles

Re: [Dovecot] v1.2.beta1 released

[Sascha Wilde]

Timo Sirainen  writes:
> On Thu, 2009-02-12 at 13:10 +0100, Sascha Wilde wrote:
>> - cyrus imapd actually tries[1] to implement a variant of this
>>   possibility in that it does not allow to remove the 'a' right from the
>>   owner: 
>
> I implemented this to Dovecot now too.

Good.  :)  

I just gave it a try.  I was a little worried when I saw that I was able
to remove all admin rights from an folder by giving "a" to another user
and let this user first remove "a" from the owner and then from him self
-- fortunately the owner was still able to edit the acls (despite the
missing administrator flag.), so everything is fine:

* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE 
AUTH=PLAIN] Dovecot ready.
lo login bar secret
lo OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT 
THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS 
LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN 
CONTEXT=SEARCH ACL RIGHTS=texk ANNOTATEMORE] Logged in
li list "" "*"
* LIST (\Noselect \HasChildren) "/" "user"
* LIST (\Noselect \HasChildren) "/" "user/f...@example.com"
* LIST (\HasChildren) "/" "INBOX"
* LIST (\HasNoChildren) "/" "user/f...@example.com/test-share"
li OK List completed.
g getacl "user/f...@example.com/test-share"
* ACL "user/f...@example.com/test-share" "f...@example.com" akxeilprwtscd 
"b...@example.com" akxeilprwtscd
g OK Getacl completed.
s setacl "user/f...@example.com/test-share" "f...@example.com" -a
s OK Setacl complete.
g getacl "user/f...@example.com/test-share"
* ACL "user/f...@example.com/test-share" "f...@example.com" kxeilprwtscd 
"b...@example.com" akxeilprwtscd
g OK Getacl completed.
s setacl "user/f...@example.com/test-share" "b...@example.com" kxeilprwtscd
s OK Setacl complete.
getacl "user/f...@example.com/test-share"
getacl BAD Error in IMAP command "USER/f...@example.com/TEST-SHARE": Unknown 
command.
lo logout
* BYE Logging out
lo OK Logout completed.


* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE 
AUTH=PLAIN] Dovecot ready.
loginb foo secret
loginb BAD Error in IMAP command received by server.
lo login elf 11
lo OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT 
THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS 
LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN 
CONTEXT=SEARCH ACL RIGHTS=texk ANNOTATEMORE] Logged in
li list "" "*"
* LIST (\HasChildren) "/" "INBOX"
* LIST (\HasNoChildren) "/" "INBOX/test-share"
li OK List completed.
g getacl "INBOX/test-share"
* ACL "INBOX/test-share" "f...@example.com" kxeilprwtscd "b...@example.com" 
kxeilprwtscd
g OK Getacl completed.
s setacl "INBOX/test-share" "f...@example.com" +a
s OK Setacl complete.
g getacl "INBOX/test-share"
* ACL "INBOX/test-share" "f...@example.com" akxeilprwtscd "b...@example.com" 
kxeilprwtscd
g OK Getacl completed.


I'm not sure if every detail here is intended, but I think its an good
solution.

>> > I think the owner ACLs are usually in global ACL files, so
>> > it's probably not possible to remove or change it, only add a new
>> > user=x.
>> 
>> I think that it would be best to always map the owners user name to
>> the keyword "owner" and vice versa between the IMAP front end and the
>> acl back end.  This way user=x where x is the owners user name should
>> never appear in an dovecot-acl file.
>
> I did consider this too, but then I thought that it could cause wrong
> results in some special situations. For example if another user's
> mailbox is symlinked to your private namespace and you change your own
> rights, it really should change them and not the owner's.

I haven't thought of that.  I agree that in such cases the mapping would
fail.  However I think there are many setups where such symlink hacks are
not used (and I guess with the new shared user namespaces and IMAP ACL
front end there will be even fewer cases in which such tricks are
useful) -- so maybe this could be configure able?

>> So it boils down to the question
>> if the individual acl-files should take precedence over the global one
>> -- without having checked I assume this decision already has been made.
>
> IIRC in v1.1 mailbox ACL files take precedence, but in v1.2 globals take
> precedence. I changed it because users shouldn't be able to override
> admin's decisions.

I guess it's mainly a question if you see these global ACLs as mere
defaults (in which case it should be possible to overwrite them) or as
an administrative instrument.  I don't really have any opinion which is
more useful...  :)

Once again many thanks for putting all this into 1.2!

cheers
sascha
-- 
Sascha Wilde  OpenPGP key: 4BB86568
http://www.intevation.de/~wilde/  http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998
Geschäftsführer:   Frank Koormann,  Bernhard Reiter,  Dr. Jan-Oliver Wagner


pgpAY

Re: [Dovecot] OT: Fixing Messages To Be RFC 2822 Compliant

[Darabos Edvárd Konrád]

Hi!

EXAMPLES
   ...
  To convert a non-standard mailbox file into a standard mailbox 
file you

  can use:
 formail -ds >new_mailbox

  Or, if you have a very tolerant mailer:
 formail -a Date: -ds >new_mailbox
   ...

   These are not working based on explicit instructions. You may give 
them a try. I don't know how bad is your mbox...


Bye

Neil wrote:

Hi,

Yeah, I'm vaguely familiar with formail, but (after reviewing the
literature) it doesn't seem like it can be used to identify/fix existing
messages (unless you already know how they're broken and give it explicit
instructions to fix them).

Is there something I'm missing?

Thanks.

On Mon, Feb 23, 2009 at 4:24 AM, Darabos Edvárd Konrád <
n...@hippy.csoma.elte.hu> wrote:

  

Hello!

  I am not sure about what you want, but I found something that maybe
useful for you.
  http://gd.tuwien.ac.at/linuxcommand.org/man_pages/formail1.html

Bye


Neil wrote:



Soapparently I have some messages which are not RFC compliant sitting
in
my mailboxes (mostly older ones), and I have some software which is
refusing
to handle such messages.

1. Does anyone know of a nice way to verify that all my messages are
compliant/find those that aren't? (I suppose I could use the existing
failing software, but I was hoping for something a little more robust...)

2. Does anyone know of any tools that will do The Right Thing as far as
fixing these messages are concerned?

Googling didn't turn up much for me, but maybe I wasn't hitting the right
terms ("RFC message repair", "fix email message", etc.).

Thanks.



  



  




smime.p7s
Description: S/MIME Cryptographic Signature

Re: [Dovecot] IMAP ACLs and global ACLs in v1.2

[Sascha Wilde]

Timo Sirainen  writes:
> On Thu, 2009-01-15 at 17:48 +0100, Sascha Wilde wrote:
>> > But should it just internally convert "owner" to "username" when
>> > replying?
>> 
>> From our experience this would be a very good idea.  Many clients
>> recognize the username and handle those ACLs differently in there UI
>> (for example they don't offer them for editing).  But they don't
>> understand "owner".
>
> GETACL now converts owner to username when ACLs contain owner right, but
> no username right.

Great, thanks.  A quick test looks perfect.  :)

cheers
sascha
-- 
Sascha Wilde  OpenPGP key: 4BB86568
http://www.intevation.de/~wilde/  http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998
Geschäftsführer:   Frank Koormann,  Bernhard Reiter,  Dr. Jan-Oliver Wagner


pgpHOSauZhHxd.pgp
Description: PGP signature

Re: [Dovecot] OT: Fixing Messages To Be RFC 2822 Compliant

[Neil]

Hi,

Yeah, I'm vaguely familiar with formail, but (after reviewing the
literature) it doesn't seem like it can be used to identify/fix existing
messages (unless you already know how they're broken and give it explicit
instructions to fix them).

Is there something I'm missing?

Thanks.

On Mon, Feb 23, 2009 at 4:24 AM, Darabos Edvárd Konrád <
n...@hippy.csoma.elte.hu> wrote:

> Hello!
>
>   I am not sure about what you want, but I found something that maybe
> useful for you.
>   http://gd.tuwien.ac.at/linuxcommand.org/man_pages/formail1.html
>
> Bye
>
>
> Neil wrote:
>
>> Soapparently I have some messages which are not RFC compliant sitting
>> in
>> my mailboxes (mostly older ones), and I have some software which is
>> refusing
>> to handle such messages.
>>
>> 1. Does anyone know of a nice way to verify that all my messages are
>> compliant/find those that aren't? (I suppose I could use the existing
>> failing software, but I was hoping for something a little more robust...)
>>
>> 2. Does anyone know of any tools that will do The Right Thing as far as
>> fixing these messages are concerned?
>>
>> Googling didn't turn up much for me, but maybe I wasn't hitting the right
>> terms ("RFC message repair", "fix email message", etc.).
>>
>> Thanks.
>>
>>
>>
>
>

Re: [Dovecot] OT: Fixing Messages To Be RFC 2822 Compliant

[Darabos Edvárd Konrád]

Hello!

   I am not sure about what you want, but I found something that maybe 
useful for you.

   http://gd.tuwien.ac.at/linuxcommand.org/man_pages/formail1.html

Bye

Neil wrote:

Soapparently I have some messages which are not RFC compliant sitting in
my mailboxes (mostly older ones), and I have some software which is refusing
to handle such messages.

1. Does anyone know of a nice way to verify that all my messages are
compliant/find those that aren't? (I suppose I could use the existing
failing software, but I was hoping for something a little more robust...)

2. Does anyone know of any tools that will do The Right Thing as far as
fixing these messages are concerned?

Googling didn't turn up much for me, but maybe I wasn't hitting the right
terms ("RFC message repair", "fix email message", etc.).

Thanks.

  




smime.p7s
Description: S/MIME Cryptographic Signature

[Dovecot] OT: Fixing Messages To Be RFC 2822 Compliant

[Neil]

Soapparently I have some messages which are not RFC compliant sitting in
my mailboxes (mostly older ones), and I have some software which is refusing
to handle such messages.

1. Does anyone know of a nice way to verify that all my messages are
compliant/find those that aren't? (I suppose I could use the existing
failing software, but I was hoping for something a little more robust...)

2. Does anyone know of any tools that will do The Right Thing as far as
fixing these messages are concerned?

Googling didn't turn up much for me, but maybe I wasn't hitting the right
terms ("RFC message repair", "fix email message", etc.).

Thanks.

Re: [Dovecot] Postfix LDA vs the Dovecot LDA + other quetions

[Geert Hendrickx]

On Sun, Feb 22, 2009 at 11:58:01PM -0800, Linux Advocate wrote:
> 
> Guys , 
> 
> 1. What is the benefit of using Dovecot' LDA as compared to postfix's
> LDA? Will there be better performance?


With Dovecot's LDA, mailbox indexes are updated at mail delivery time
instead of (only) at pop3/imap login time, which should result in faster
logins when you have a lot of new mail.

And Dovecot's LDA has extra functionality, most notably Sieve support.
But if you don't use all that, Postfix' LDA works fine too.


Geert


-- 
Geert Hendrickx  -=-  g...@telenet.be  -=-  PGP: 0xC4BB9E9F
This e-mail was composed using 100% recycled spam messages!

Re: [Dovecot] dovecot auth

[ben]

You were right... I changed the %n to %Lu in the passdb file scheme and
everything is working now :-)

thx a lot

On Sun, 2009-02-22 at 13:42 +0100, Andrzej Adam Filip wrote:
> ben  wrote:
> 
> > tried %Lu, dovecot seems to still strip of the domain part before
> > looking it up in dovecot.passwd... :
> >
> >
> > dovecot.passwd :
> > ---
> > t...@testdomain.com:{plain}test123.:8:12::/opt/storage/mbox/bb107608::
> >
> > -
> > dovecot -n
> >
> > # OS: Linux 2.6.24.5-smp i686 Slackware 12.1.0 
> > [...]
> > auth default:
> >   mechanisms: plain login apop
> >   executable: /opt/dovecot/libexec/dovecot/dovecot-auth
> >   user: mail
> >   username_format: %Lu
> >   verbose: yes
> >   debug: yes
> >   debug_passwords: yes
> >   passdb:
> > driver: passwd-file
> > args: scheme=plain username_format=%n /opt/dovecot/etc/dovecot.passwd
> >   userdb:
> > driver: passwd-file
> > args: username_format=%n /opt/dovecot/etc/dovecot.passwd
> >   socket:
> > type: listen
> > master:
> >   path: /var/run/dovecot/auth-master
> >   mode: 384
> >   user: mail
> >   group: mail
> >[...]
> 
> Have you tried to change username_format for passdb and userdb *TOO*?
> You seem to overwrite "global default" in "sub sections".
> They both are set to %n - username with stripped domain.
> 
> URL(s):
> http://wiki.dovecot.org/AuthDatabase/PasswdFile
> 
> P.S.
> My experience with dovecot is limited so treat my replies as guesses
> based of "general email experience".
> 

Re: [Dovecot] from postfix deliver to dovecot deliver

[Johan Hendriks]

Johan Hendriks schreef:

Hello all.
I use dovecot in combination with postfix, postfixadmin for virtual 
users.

Deliver to the mailbox now is done by postfix
Now i want to enable quota's and therefor i need dovecot deliver.
Can i just switch to dovecot deliver?
Or must i first do some prrperations in the mailboxes.

regards

One more question regarding this.
All the howto's are using a seperate user for the dovecot LDA, like vmail.
Now all my mailboxes have the userid and groupid from postfix.
Can i use the postfix user for the dovecot LDA?

regards,

--
___
*Johan Hendriks*
*Schavemaker Transport*

Tel: +31 (0)251 229098
Fax: +31 (0)251 212016
email: j.hendr...@schavemaker.com 
web: http://www.schavemaker.com
___