On Sun, 30 Mar 2025 07:37:38 +0200
Paul Neuwirth via Postfix-users <postfix-users@postfix.org> wrote:

> On Sat, 29 Mar 2025 10:21:53 -0400 (EDT)
> Wietse Venema via Postfix-users <postfix-users@postfix.org> wrote:
> 
> > Paul Neuwirth via Postfix-users:  
> > > On Fri, 28 Mar 2025 12:41:45 -0400 (EDT)
> > > Wietse Venema via Postfix-users <postfix-users@postfix.org> wrote:
> > >     
> > > > Paul Neuwirth via Postfix-users:    
> > > > > Hello group,
> > > > > 
> > > > > Since a few days I have massive problems with lockfiles
> > > > > blocking the mailboxes (type storage, /var/mail/user).
> > > > > don't know if it's the right list. may more concern dovecot.
> > > > > 
> > > > > postqueue is full of
> > > > > 944C223FC2    17905 Fri Mar 28 06:02:01  XXX
> > > > > (cannot update mailbox /var/mail/pane for user XXX. unable to
> > > > > create lock file /var/mail/XXX.lock: File exists) XXX      
> > > > 
> > > > That looks like a Postfix error message (*). 
> > > > 
> > > > Are you using Postfix to deliver mail, and Dovecot to read mail?
> > > > 
> > > >         Wietse
> > > > 
> > > > (*) The function dot_lockfile() produces the text "unable to
> > > > create lock file /var/mail/XXX.lock: File exists)", and the
> > > > function deliver_mailbox_file() prepends the text "cannot update
> > > > mailbox /var/mail/XXX for user XXX."
> > > > _______________________________________________    
> > > 
> > > yes, that's right
> > > 
> > > from /var/log/mail on last restart:
> > > 2025-03-29T06:24:41.124754+01:00 XXX dovecot: master: Error:
> > > fstat(/var/lib/dovecot/instances.lock) failed: No such file or
> > > directory 2025-03-29T06:24:41.125299+01:00 XXX dovecot: master:
> > > Error: file_dotlock_open(/var/lib/dovecot/instances) failed: No
> > > such file or directory
> > > 
> > > files do exists, I even made folder and files world-readable to
> > > check, they are owned by root:root
> > > 
> > > # ls -la /var/lib/dovecot/
> > > total 20
> > > drwxr-xr-x   2 root root  100 Mar 29 06:24 .
> > > drwxr-xr-x 151 root root 4096 Mar 28 21:16 ..
> > > -rw-------   1 root root    0 Feb 14  2010 auth-success
> > > -rw-r--r--   1 root root   62 Apr 16  2020 instances
> > > -rw-r--r--   1 root root    0 Mar 29 06:24 instances.lock
> > > -rw-r--r--   1 root root  211 Jan 22  2017 mounts
> > > -rw-r--r--   1 root root  230 Jan 22  2017 ssl-parameters.dat    
> > 
> > Are they looking at the *same* /var/lib/dovecot/instances.lock
> > file? If one process is chrooted or containerized, "the same"
> > pathname will resolve to different tsrgets.
> > 
> >     Wietse  
> good point.
> I already checked superficially and came to the conclusion no.
> 
> not that sure about. but doesn't seem so:
> don't find anything about chroot in postfix configs.
> the main running executable of postfix is
> /usr/lib/postfix/bin//master - but there's only a bin folder (and some
> files in /usr/lib/postfix, cwd is /var/spool/postfix
> 
> dovecot also nothing about chroot in config
> cwd and most open files is /var/run/dovecot doesn't seem to be a
> (ch)root-dir either. 

I again think I've got this solved.
Problem was allegedly very big E-Mails (10-30MiB) in the user's
mail-file.

I think that would be no issue with mbox format?
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

Reply via email to