Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
On October 26, 2017 at 7:10 PM tr...@skrilnetz.net wrote:
Quoting tr...@skrilnetz.net:
Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
On October 26, 2017 at 5:53 PM tr...@skrilnetz.net wrote:
Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote:
Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>:
On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote:
/dovecot: lda(www-data): Error: user www-data: Initialization
failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission
denied (euid=33(www-data) egid=33(www-data) missing +w perm:
/var/www, dir owned by 1001:1001 mode=0755//) /
I did some troubleshooting and I don't understand where
the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail
and
^^ /var/mail contains the INBOX only
sending/receiving emails is working as it always did.
mail_location is still setup to be MAIL_LOCATION =
MBOX:~/MAIL:INBOX=/VAR/MAIL/%U
Everything else is in ~/MAIL (why uppercase?)
Why is it trying a mkdir in /var/www?
Because most likely /var/www is the home directory of www-data and
you've configured to use $HOME/MAIL as base directory, which is
/var/www/mail
- -- Steffen Kaiser
I don't know where the uppercase is coming from. In the email I've
sent its lower case.
How can I fix that without changing permissions of /var/www? Where is
$HOME/MAIL configured? Why do I get this error now for the first time,
when there was no change to the system configuration?
Probably someone attempted to send email via a crappy script and
it's now trying to deliver to www-data.
first_valid_uid = 1001
last_valid_uid = 1001
also, doveconf -n would be useful.
Aki
Here is doveconf -n: https://pastebin.com/raw/s6cKwHGc
Home directory is provided by passwd userdb when present in passwd
file. to override it, use
userdb {
driver = passwd
override_fields = home=/var/mail/%Lu
}
Aki
Thanks for the quick replies.
I've checked, and the user database information is stored in
/home/user/mail/ for every user.
That works as expected without changing anything. I have still the
same question…
Why is it trying to write to /var/www when the mailbox is in
/var/mail/ and the user data in /home/user/mail/?
Ok, got it!
It's trying to deliver to user www-data and because of below line in
passwd, it attempts to create the dir in www, right?
/www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin/[1]
How can I find out with email is causing the error message?
If you are using postfix, try mailq
Aki
Resolved!
I've added an alias (/etc/aliases) to deliver mail for www-data to
user admin. I then delivered all messages by running: postqueue -f
I've checked the messages and it seems to be that a wordpress plugin
was sending to www-data.
Thanks for the help, getting me in the right direction.
Links:
--
[1]
binGUc6sbMkFg.bin
Description: PGP Public Key
Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
> On October 26, 2017 at 7:10 PM tr...@skrilnetz.net wrote:
>
>
> Quoting tr...@skrilnetz.net:
>
> > Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
> >
> >>> On October 26, 2017 at 5:53 PM tr...@skrilnetz.net wrote:
> >>>
> >>> Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
> >>>
> >>> On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote:
> >>>
> >>> Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>:
> >>>
> >>> On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote:
> >>>
> >>> /dovecot: lda(www-data): Error: user www-data: Initialization
> >>> failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission
> >>> denied (euid=33(www-data) egid=33(www-data) missing +w perm:
> >>> /var/www, dir owned by 1001:1001 mode=0755//) /
> >>>
> >>> I did some troubleshooting and I don't understand where
> >>> the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail
> >>> and
> >>>
> >>> ^^ /var/mail contains the INBOX only
> >>>
> >>> sending/receiving emails is working as it always did.
> >>>
> >>> mail_location is still setup to be MAIL_LOCATION =
> >>> MBOX:~/MAIL:INBOX=/VAR/MAIL/%U
> >>>
> >>> Everything else is in ~/MAIL (why uppercase?)
> >>>
> >>> Why is it trying a mkdir in /var/www?
> >>>
> >>> Because most likely /var/www is the home directory of www-data and
> >>> you've configured to use $HOME/MAIL as base directory, which is
> >>> /var/www/mail
> >>> - -- Steffen Kaiser
> >>>
> >>> I don't know where the uppercase is coming from. In the email I've
> >>> sent its lower case.
> >>>
> >>> How can I fix that without changing permissions of /var/www? Where is
> >>> $HOME/MAIL configured? Why do I get this error now for the first time,
> >>> when there was no change to the system configuration?
> >>>
> >>> Probably someone attempted to send email via a crappy script and
> >>> it's now trying to deliver to www-data.
> >>>
> >>> first_valid_uid = 1001
> >>> last_valid_uid = 1001
> >>>
> >>> also, doveconf -n would be useful.
> >>> Aki
> >>>
> >>> Here is doveconf -n: https://pastebin.com/raw/s6cKwHGc
> >>
> >> Home directory is provided by passwd userdb when present in passwd
> >> file. to override it, use
> >>
> >> userdb {
> >> driver = passwd
> >> override_fields = home=/var/mail/%Lu
> >> }
> >> Aki
> >
> > Thanks for the quick replies.
> > I've checked, and the user database information is stored in
> > /home/user/mail/ for every user.
> > That works as expected without changing anything. I have still the
> > same question…
> > Why is it trying to write to /var/www when the mailbox is in
> > /var/mail/ and the user data in /home/user/mail/?
> >
> >
>
> Ok, got it!
>
> It's trying to deliver to user www-data and because of below line in
> passwd, it attempts to create the dir in www, right?
>
> /www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin/
>
> How can I find out with email is causing the error message?
If you are using postfix, try mailq
Aki
Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
On October 26, 2017 at 6:40 PM tr...@skrilnetz.net wrote:
Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
On October 26, 2017 at 5:53 PM tr...@skrilnetz.net wrote:
Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote:
Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>:
On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote:
/dovecot: lda(www-data): Error: user www-data: Initialization
failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission
denied (euid=33(www-data) egid=33(www-data) missing +w perm:
/var/www, dir owned by 1001:1001 mode=0755//) /
I did some troubleshooting and I don't understand where
the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail
and
^^ /var/mail contains the INBOX only
sending/receiving emails is working as it always did.
mail_location is still setup to be MAIL_LOCATION =
MBOX:~/MAIL:INBOX=/VAR/MAIL/%U
Everything else is in ~/MAIL (why uppercase?)
Why is it trying a mkdir in /var/www?
Because most likely /var/www is the home directory of www-data and
you've configured to use $HOME/MAIL as base directory, which is
/var/www/mail
- -- Steffen Kaiser
I don't know where the uppercase is coming from. In the email I've
sent its lower case.
How can I fix that without changing permissions of /var/www? Where is
$HOME/MAIL configured? Why do I get this error now for the first time,
when there was no change to the system configuration?
Probably someone attempted to send email via a crappy script and
it's now trying to deliver to www-data.
first_valid_uid = 1001
last_valid_uid = 1001
also, doveconf -n would be useful.
Aki
Here is doveconf -n: https://pastebin.com/raw/s6cKwHGc
Home directory is provided by passwd userdb when present in passwd
file. to override it, use
userdb {
driver = passwd
override_fields = home=/var/mail/%Lu
}
Aki
Thanks for the quick replies.
I've checked, and the user database information is stored in
/home/user/mail/ for every user.
That works as expected without changing anything. I have still the
same question…
Why is it trying to write to /var/www when the mailbox is in
/var/mail/ and the user data in /home/user/mail/?
So you are saying that the home directory field, in /etc/passwd, for
user www-data is set to /home/www-data/mail ?
You should consider setting
first_valid_uid = 1000
Aki
No, it's /var/www.
It's trying to deliver to user www-data and because of below line in
passwd, it attempts to create the dir in www, right?
/www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin/[1]
How can I find out with email is causing the error message?
Links:
--
[1]
binw_vNTYbsop.bin
Description: PGP Public Key
Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
> On October 26, 2017 at 6:40 PM tr...@skrilnetz.net wrote:
>
>
> Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
>
> >> On October 26, 2017 at 5:53 PM tr...@skrilnetz.net wrote:
> >>
> >> Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
> >>
> >> On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote:
> >>
> >> Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>:
> >>
> >> On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote:
> >>
> >> /dovecot: lda(www-data): Error: user www-data: Initialization
> >> failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission
> >> denied (euid=33(www-data) egid=33(www-data) missing +w perm:
> >> /var/www, dir owned by 1001:1001 mode=0755//) /
> >>
> >> I did some troubleshooting and I don't understand where
> >> the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail
> >> and
> >>
> >> ^^ /var/mail contains the INBOX only
> >>
> >> sending/receiving emails is working as it always did.
> >>
> >> mail_location is still setup to be MAIL_LOCATION =
> >> MBOX:~/MAIL:INBOX=/VAR/MAIL/%U
> >>
> >> Everything else is in ~/MAIL (why uppercase?)
> >>
> >> Why is it trying a mkdir in /var/www?
> >>
> >> Because most likely /var/www is the home directory of www-data and
> >> you've configured to use $HOME/MAIL as base directory, which is
> >> /var/www/mail
> >> - -- Steffen Kaiser
> >>
> >> I don't know where the uppercase is coming from. In the email I've
> >> sent its lower case.
> >>
> >> How can I fix that without changing permissions of /var/www? Where is
> >> $HOME/MAIL configured? Why do I get this error now for the first time,
> >> when there was no change to the system configuration?
> >>
> >> Probably someone attempted to send email via a crappy script and
> >> it's now trying to deliver to www-data.
> >>
> >> first_valid_uid = 1001
> >> last_valid_uid = 1001
> >>
> >> also, doveconf -n would be useful.
> >> Aki
> >>
> >> Here is doveconf -n: https://pastebin.com/raw/s6cKwHGc
> >
> > Home directory is provided by passwd userdb when present in passwd
> > file. to override it, use
> >
> > userdb {
> > driver = passwd
> > override_fields = home=/var/mail/%Lu
> > }
> > Aki
>
> Thanks for the quick replies.
> I've checked, and the user database information is stored in
> /home/user/mail/ for every user.
> That works as expected without changing anything. I have still the
> same question…
> Why is it trying to write to /var/www when the mailbox is in
> /var/mail/ and the user data in /home/user/mail/?
So you are saying that the home directory field, in /etc/passwd, for user
www-data is set to /home/www-data/mail ?
You should consider setting
first_valid_uid = 1000
Aki
Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
Quoting tr...@skrilnetz.net:
Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
On October 26, 2017 at 5:53 PM tr...@skrilnetz.net wrote:
Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote:
Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>:
On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote:
/dovecot: lda(www-data): Error: user www-data: Initialization
failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission
denied (euid=33(www-data) egid=33(www-data) missing +w perm:
/var/www, dir owned by 1001:1001 mode=0755//) /
I did some troubleshooting and I don't understand where
the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail
and
^^ /var/mail contains the INBOX only
sending/receiving emails is working as it always did.
mail_location is still setup to be MAIL_LOCATION =
MBOX:~/MAIL:INBOX=/VAR/MAIL/%U
Everything else is in ~/MAIL (why uppercase?)
Why is it trying a mkdir in /var/www?
Because most likely /var/www is the home directory of www-data and
you've configured to use $HOME/MAIL as base directory, which is
/var/www/mail
- -- Steffen Kaiser
I don't know where the uppercase is coming from. In the email I've
sent its lower case.
How can I fix that without changing permissions of /var/www? Where is
$HOME/MAIL configured? Why do I get this error now for the first time,
when there was no change to the system configuration?
Probably someone attempted to send email via a crappy script and
it's now trying to deliver to www-data.
first_valid_uid = 1001
last_valid_uid = 1001
also, doveconf -n would be useful.
Aki
Here is doveconf -n: https://pastebin.com/raw/s6cKwHGc
Home directory is provided by passwd userdb when present in passwd
file. to override it, use
userdb {
driver = passwd
override_fields = home=/var/mail/%Lu
}
Aki
Thanks for the quick replies.
I've checked, and the user database information is stored in
/home/user/mail/ for every user.
That works as expected without changing anything. I have still the
same question…
Why is it trying to write to /var/www when the mailbox is in
/var/mail/ and the user data in /home/user/mail/?
Ok, got it!
It's trying to deliver to user www-data and because of below line in
passwd, it attempts to create the dir in www, right?
/www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin/
How can I find out with email is causing the error message?
binoxPkPUjIK8.bin
Description: PGP Public Key
Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
On October 26, 2017 at 5:53 PM tr...@skrilnetz.net wrote:
Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote:
Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>:
On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote:
/dovecot: lda(www-data): Error: user www-data: Initialization
failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission
denied (euid=33(www-data) egid=33(www-data) missing +w perm:
/var/www, dir owned by 1001:1001 mode=0755//) /
I did some troubleshooting and I don't understand where
the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail
and
^^ /var/mail contains the INBOX only
sending/receiving emails is working as it always did.
mail_location is still setup to be MAIL_LOCATION =
MBOX:~/MAIL:INBOX=/VAR/MAIL/%U
Everything else is in ~/MAIL (why uppercase?)
Why is it trying a mkdir in /var/www?
Because most likely /var/www is the home directory of www-data and
you've configured to use $HOME/MAIL as base directory, which is
/var/www/mail
- -- Steffen Kaiser
I don't know where the uppercase is coming from. In the email I've
sent its lower case.
How can I fix that without changing permissions of /var/www? Where is
$HOME/MAIL configured? Why do I get this error now for the first time,
when there was no change to the system configuration?
Probably someone attempted to send email via a crappy script and
it's now trying to deliver to www-data.
first_valid_uid = 1001
last_valid_uid = 1001
also, doveconf -n would be useful.
Aki
Here is doveconf -n: https://pastebin.com/raw/s6cKwHGc
Home directory is provided by passwd userdb when present in passwd
file. to override it, use
userdb {
driver = passwd
override_fields = home=/var/mail/%Lu
}
Aki
Thanks for the quick replies.
I've checked, and the user database information is stored in
/home/user/mail/ for every user.
That works as expected without changing anything. I have still the
same question…
Why is it trying to write to /var/www when the mailbox is in
/var/mail/ and the user data in /home/user/mail/?
binvQinxmzs2U.bin
Description: PGP Public Key
Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
> On October 26, 2017 at 5:53 PM tr...@skrilnetz.net wrote:
>
>
> Quoting Aki Tuomi <aki.tu...@dovecot.fi>:
>
> >> On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote:
> >>
> >> Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>:
> >>
> >> On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote:
> >>
> >> /dovecot: lda(www-data): Error: user www-data: Initialization
> >> failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission
> >> denied (euid=33(www-data) egid=33(www-data) missing +w perm:
> >> /var/www, dir owned by 1001:1001 mode=0755//) /
> >>
> >> I did some troubleshooting and I don't understand where
> >> the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail
> >> and
> >>
> >> ^^ /var/mail contains the INBOX only
> >>
> >> sending/receiving emails is working as it always did.
> >>
> >> mail_location is still setup to be MAIL_LOCATION =
> >> MBOX:~/MAIL:INBOX=/VAR/MAIL/%U
> >>
> >> Everything else is in ~/MAIL (why uppercase?)
> >>
> >> Why is it trying a mkdir in /var/www?
> >>
> >> Because most likely /var/www is the home directory of www-data and
> >> you've configured to use $HOME/MAIL as base directory, which is
> >> /var/www/mail
> >> - -- Steffen Kaiser
> >>
> >> I don't know where the uppercase is coming from. In the email I've
> >> sent its lower case.
> >>
> >> How can I fix that without changing permissions of /var/www? Where is
> >> $HOME/MAIL configured? Why do I get this error now for the first time,
> >> when there was no change to the system configuration?
> >
> > Probably someone attempted to send email via a crappy script and
> > it's now trying to deliver to www-data.
> >
> > first_valid_uid = 1001
> > last_valid_uid = 1001
> >
> > also, doveconf -n would be useful.
> > Aki
>
> Here is doveconf -n: https://pastebin.com/raw/s6cKwHGc
Home directory is provided by passwd userdb when present in passwd file. to
override it, use
userdb {
driver = passwd
override_fields = home=/var/mail/%Lu
}
Aki
Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
Quoting Aki Tuomi <aki.tu...@dovecot.fi>: On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote: Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>: On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied (euid=33(www-data) egid=33(www-data) missing +w perm: /var/www, dir owned by 1001:1001 mode=0755//) / I did some troubleshooting and I don't understand where the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail and ^^ /var/mail contains the INBOX only sending/receiving emails is working as it always did. mail_location is still setup to be MAIL_LOCATION = MBOX:~/MAIL:INBOX=/VAR/MAIL/%U Everything else is in ~/MAIL (why uppercase?) Why is it trying a mkdir in /var/www? Because most likely /var/www is the home directory of www-data and you've configured to use $HOME/MAIL as base directory, which is /var/www/mail - -- Steffen Kaiser I don't know where the uppercase is coming from. In the email I've sent its lower case. How can I fix that without changing permissions of /var/www? Where is $HOME/MAIL configured? Why do I get this error now for the first time, when there was no change to the system configuration? Probably someone attempted to send email via a crappy script and it's now trying to deliver to www-data. first_valid_uid = 1001 last_valid_uid = 1001 also, doveconf -n would be useful. Aki Here is doveconf -n: https://pastebin.com/raw/s6cKwHGc bin72LrhJdAYm.bin Description: PGP Public Key
Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
> On October 26, 2017 at 5:40 PM tr...@skrilnetz.net wrote: > > > Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>: > > > On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: > > > >> /dovecot: lda(www-data): Error: user www-data: Initialization > >> failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission > >> denied (euid=33(www-data) egid=33(www-data) missing +w perm: > >> /var/www, dir owned by 1001:1001 mode=0755//) / > >> > >> I did some troubleshooting and I don't understand where > >> the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail > >> and > > > > ^^ /var/mail contains the INBOX only > > > >> sending/receiving emails is working as it always did. > >> > >> mail_location is still setup to be MAIL_LOCATION = > >> MBOX:~/MAIL:INBOX=/VAR/MAIL/%U > > > > Everything else is in ~/MAIL (why uppercase?) > > > >> Why is it trying a mkdir in /var/www? > > > > Because most likely /var/www is the home directory of www-data and > > you've configured to use $HOME/MAIL as base directory, which is > > /var/www/mail > > - -- Steffen Kaiser > > I don't know where the uppercase is coming from. In the email I've > sent its lower case. > > How can I fix that without changing permissions of /var/www? Where is > $HOME/MAIL configured? Why do I get this error now for the first time, > when there was no change to the system configuration? Probably someone attempted to send email via a crappy script and it's now trying to deliver to www-data. first_valid_uid = 1001 last_valid_uid = 1001 also, doveconf -n would be useful. Aki
Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
Quoting Steffen Kaiser <skdove...@smail.inf.fh-brs.de>: On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied (euid=33(www-data) egid=33(www-data) missing +w perm: /var/www, dir owned by 1001:1001 mode=0755//) / I did some troubleshooting and I don't understand where the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail and ^^ /var/mail contains the INBOX only sending/receiving emails is working as it always did. mail_location is still setup to be MAIL_LOCATION = MBOX:~/MAIL:INBOX=/VAR/MAIL/%U Everything else is in ~/MAIL (why uppercase?) Why is it trying a mkdir in /var/www? Because most likely /var/www is the home directory of www-data and you've configured to use $HOME/MAIL as base directory, which is /var/www/mail - -- Steffen Kaiser I don't know where the uppercase is coming from. In the email I've sent its lower case. How can I fix that without changing permissions of /var/www? Where is $HOME/MAIL configured? Why do I get this error now for the first time, when there was no change to the system configuration? binpoICdWAM4E.bin Description: PGP Public Key
Re: Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 26 Oct 2017, tr...@skrilnetz.net wrote: /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied (euid=33(www-data) egid=33(www-data) missing +w perm: /var/www, dir owned by 1001:1001 mode=0755//) / I did some troubleshooting and I don't understand where the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail and ^^ /var/mail contains the INBOX only sending/receiving emails is working as it always did. mail_location is still setup to be MAIL_LOCATION = MBOX:~/MAIL:INBOX=/VAR/MAIL/%U Everything else is in ~/MAIL (why uppercase?) Why is it trying a mkdir in /var/www? Because most likely /var/www is the home directory of www-data and you've configured to use $HOME/MAIL as base directory, which is /var/www/mail - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEVAwUBWfHv6Hz1H7kL/d9rAQLoHwf+PL52wG8bqOJkfmBeezBdsjOGQN8fF07P 6SjI3PKSPjlo9w9yixRLjXRlGu6MEQj28KouT6bkJibCGMf2GebWX4zw1DiC/F5/ xwc3DU4ISCKUU/SfLGpJFz/1DDL77qtZcPyrpUzkIHz0O275dY912FyJxpPfJzi3 UiWRqmgtGmX6Uzsw0+XzR1zmFJ6o8wHyucxB6tPuy7U89JpRnayvUExN7rfB/Ogs C5pafiv08jq6Ie+HFNkyVowpluVaG2OXclyucGNly3XnY7FSznkKfDYYYrVvP35o jOtrqoToK7+Eg0qQFz9GBJfseI+iuHYBcmjOrBO/Sc1J1BWgDBm5lw== =Nn7R -END PGP SIGNATURE-
Initialization failed: Namespace '': mkdir(/var/www/mail) failed: Permission denied
Hi, I'm running dovecot (v 2.2.9) on ubuntu 14.04 since a long time. I did not change any configuration lately and I'm getting the below error message. /dovecot: lda(www-data): Error: user www-data: Initialization failed: Namespace '': MKDIR(/VAR/WWW/MAIL) failed: Permission denied (euid=33(www-data) egid=33(www-data) missing +w perm: /var/www, dir owned by 1001:1001 mode=0755//) / I did some troubleshooting and I don't understand where the MKDIR(/VAR/WWW/MAIL) is coming from. Mailboxes are in /var/mail and sending/receiving emails is working as it always did. mail_location is still setup to be MAIL_LOCATION = MBOX:~/MAIL:INBOX=/VAR/MAIL/%U Why is it trying a mkdir in /var/www? Any help would be appreciated. Rgs, binDkYuCVB_Uj.bin Description: PGP Public Key
Re: Initialization Failed:
Yup, that did it. For some unknown reason I thought it had it twice in the tutorial, but when I checked, it did not. :S I've taken it out and all seems to be working now. Thanks muchly. On 31/10/15 18:08, Christian Kivalo wrote: Hi, Error: user br...@myactualdomain.com: Initialization failed: Namespace '': Unknown setting: /var/mail/vmail/myactualdomain.com/brian/mail mail_location = maildir:~/Maildir:/var/mail/vmail/%d/%n/mail:LAYOUT=fs You have double "maildir:" keyword. Regards Christian
Re: Initialization Failed:
Hi, >Error: user br...@myactualdomain.com: Initialization failed: Namespace >'': Unknown setting: /var/mail/vmail/myactualdomain.com/brian/mail >mail_location = maildir:~/Maildir:/var/mail/vmail/%d/%n/mail:LAYOUT=fs You have double "maildir:" keyword. Regards Christian
Initialization Failed:
Hi dovecotters
I am trying to install dovecot on a mail server I am provisioning for
myself in AWS.
I am following an ArsTechnica guide, and at some stage in the process
the author recommends and provides instructions to configure Dovecot
(http://arstechnica.com/information-technology/2014/03/taking-e-mail-back-part-2-arming-your-server-with-postfix-dovecot/4/)
So, now I have it installed and configured (I believe the way suggested)
but when I try to connect via IMAP I am getting an error.
If I try :
root@ip-10-0-0-244:~# telnet mail.myactualdomain.com 143
Trying 127.0.0.1...
Connected to mail.myactualdomain.com.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready.
a1 LOGIN br...@myactualdomain.com plaintextpassword
* BYE Internal error occurred. Refer to server log for more information.
Connection closed by foreign host.
root@ip-10-0-0-244:~#
If I go to /var/log/syslog I can see the following lines:
Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap-login: Login:
user=<br...@myactualdomain.com>, method=PLAIN, rip=127.0.0.1,
lip=127.0.0.1, mpid=16934, secured, session=
Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap(br...@myactualdomain.com):
Error: user br...@myactualdomain.com: Initialization failed: Namespace
'': Unknown setting: /var/mail/vmail/myactualdomain.com/brian/mail
Oct 31 05:31:06 ip-10-0-0-244 dovecot: imap(br...@myactualdomain.com):
Error: Invalid user settings. Refer to server log for more information.
root@ip-10-0-0-244:~# dovecot --version
2.2.9
So, I don't know why it's giving me an error about :
Initialization failed: Namespace '': Unknown setting:
/var/mail/vmail/myactualdomain.com/brian/mail
The location is there, with the permissions with I believe the correct
permissions.
I'm a bit stuck as to where to even go from here.
Any help would be greatly appreciated.
Kind Regards
Brian
root@ip-10-0-0-244:~# dovecot -n
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-48-generic x86_64 Ubuntu 14.04.2 LTS
auth_mechanisms = plain login
auth_verbose = yes
mail_home = /var/mail/vmail/%d/%n
mail_location = maildir:~/Maildir:/var/mail/vmail/%d/%n/mail:LAYOUT=fs
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date ihave
namespace inbox {
inbox = yes
location =
mailbox Drafts {
auto = subscribe
special_use = \Drafts
}
mailbox Junk {
auto = subscribe
special_use = \Junk
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox Trash {
auto = subscribe
special_use = \Trash
}
prefix =
}
passdb {
args = username_format=%u scheme=ssha512 /etc/dovecot/passwd.db
driver = passwd-file
}
plugin {
sieve = ~/.dovecot.sieve
sieve_after = /var/mail/vmail/sieve-after
sieve_before = /var/mail/vmail/sieve-before
sieve_dir = ~/sieve
}
protocols = imap sieve
service auth {
unix_listener /var/spool/postfix/private/dovecot-auth {
group = postfix
mode = 0660
user = postfix
}
}
ssl_cert = ssl_cipher_list =
ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM
ssl_client_ca_dir = /etc/ssl/certs
ssl_key = was automatically rejected:%n%r
}
protocol imap {
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep
mail_max_userip_connections = 10
}
Re: Error: User initialization failed
On 17 Aug 2015, at 00:54, Steffen Kaiser skdove...@smail.inf.fh-brs.de
wrote:
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
default_fields = uid=vpopmail gid=vchkpw mail_location=/usr/local/virtual/%u
mail=maildir:/usr/local/virtual/%u
looks like this mail_location is confusing Dovecot. If you wanted to specify
home here, be aware that home and mail location should (aka must) be
separate directories.
No, the problem is that dovecot does not create the root directory for virtual
users.
Virtual users do not have a “home” directory.
So, when adding a virtual user I have to remember to go to /usr/local/virtual
and maildirmake u...@domain.tld for each user.
--
I listen to the wind, to the wind of my soul
Re: Error: User initialization failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 14 Aug 2015, @lbutlr wrote:
On Aug 14, 2015, at 8:51 AM, @lbutlr krem...@kreme.com wrote:
dovecot: lda(cha...@example.com): Error: User initialization failed: Namespace
'': Ambiguous mail location setting, don't know what to do with it:
/usr/local/virtual/chance@ example.com (try prefixing it with mbox: or milder:)
Here’s the dovecot -n output
$ dovecot -n
# 2.2.18: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 9.2-RELEASE-p3 i386
auth_failure_delay = 5 secs
auth_mechanisms = PLAIN LOGIN
default_process_limit = 200
disable_plaintext_auth = no
first_valid_uid = 89
login_log_format_elements = user=%u %r %m %c
mail_location = maildir:~/Maildir
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
default_fields = uid=vpopmail gid=vchkpw mail_location=/usr/local/virtual/%u
mail=maildir:/usr/local/virtual/%u
looks like this mail_location is confusing Dovecot. If you wanted to
specify home here, be aware that home and mail location should (aka
must) be separate directories.
driver = sql
}
- --
Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEVAwUBVdGFG3z1H7kL/d9rAQKL3ggAiRRLG51ri5yRZdhRW+gW3A4Q9vnxH5Pp
pOQV/VAI2gh/T0giNfUJ/K2OnMbEPJHBySFCBgcAYdKxJiSb30RO9alnu18/5q/3
XdpXAvpR9obzXaWTb6rGF8SII7VV5tmG953EEnzuqLOyQG6I/LbFznP+U9Wmenw0
+lDYbYbavcyeQBAz5IkRs20AeK6a6nK0JVClR2yvMwmm8YuYjG7UiUmk95p4rgme
qKdypCaDPsq5xJjWEYtodAVimVTEjhsbdtSGruBPycIwSP501QpGJMGlGvJMhfd6
ObafIqfyWUeVelTC9NU89e+V9PwB/i5E6ZZE2xjrzMgCgnkQWpgcAA==
=vvM8
-END PGP SIGNATURE-
Error: User initialization failed
OK, I obviously forgot something when setting up new user accounts (which I did via postfix admin to add them to the MySQL database): dovecot: lda(cha...@example.com): Error: User initialization failed: Namespace '': Ambiguous mail location setting, don't know what to do with it: /usr/local/virtual/chance@ example.com (try prefixing it with mbox: or milder:) I have lots of mysql users defined and working, but do I need to manually create the mail store for new ones? (Sorry, it’s been quite a long time since I had to add accounts). -- You start a conversation you can't even finish it You're talkin' a lot, but you're not sayin' anything When I have nothing to say, my lips are sealed Say something once, why say it again?
Re: Error: User initialization failed
On Aug 14, 2015, at 8:51 AM, @lbutlr krem...@kreme.com wrote:
dovecot: lda(cha...@example.com): Error: User initialization failed:
Namespace '': Ambiguous mail location setting, don't know what to do with it:
/usr/local/virtual/chance@ example.com (try prefixing it with mbox: or
milder:)
Here’s the dovecot -n output
$ dovecot -n
# 2.2.18: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 9.2-RELEASE-p3 i386
auth_failure_delay = 5 secs
auth_mechanisms = PLAIN LOGIN
default_process_limit = 200
disable_plaintext_auth = no
first_valid_uid = 89
login_log_format_elements = user=%u %r %m %c
mail_location = maildir:~/Maildir
mail_max_userip_connections = 90
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
auto = subscribe
special_use = \Junk
}
mailbox NotJunk {
auto = subscribe
}
mailbox Sent {
special_use = \Sent
}
mailbox Sent Messages {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
driver = pam
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocols = imap
service auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
}
service imap-login {
inet_listener imaps {
port = 993
ssl = yes
}
}
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
ssl_protocols = !SSLv2 !SSLv3
userdb {
driver = passwd
}
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
default_fields = uid=vpopmail gid=vchkpw mail_location=/usr/local/virtual/%u
mail=maildir:/usr/local/virtual/%u
driver = sql
}
--
You start a conversation you can't even finish it
You're talkin' a lot, but you're not sayin' anything
When I have nothing to say, my lips are sealed
Say something once, why say it again?
[Dovecot] postfix+dovecot+samba4+openldap: dovecot lda:Error: user sammy: Initialization failed: mail_location not set and autodetection failed
I'm trying to setup a samba4 with openchange which uses
postfix+dovecot+openldap on a ubuntu 12.04.2 system. I can send outgoing
emails but incoming emails fail. I looked up the logs and I get:
Mar 5 11:03:48 testerA dovecot: lda(sammy): Error: user sammy:
Initialization failed: mail_location not set and autodetection failed:
Mail storage autodetection failed with home=/var/mail
Mar 5 11:03:48 testerA dovecot: lda(sammy): Fatal: Invalid user
settings. Refer to server log for more information.
any idea what I am doing wrong? Any hints, pointers would be much
appreciated.
now the user is a virtual user. The /var/mail/sammy exists:
drwxr-sr-x 10 vmail vmail 4096 Mar 4 13:48 sammy
lrwxrwxrwx 1 vmail vmail5 Feb 28 12:12 Sammy - sammy
lrwxrwxrwx 1 vmail vmail5 Feb 28 12:12 sa...@abertax.com - sammy
lrwxrwxrwx 1 vmail vmail5 Feb 28 12:13 sa...@abertax.com - sammy
lrwxrwxrwx 1 vmail vmail5 Mar 1 15:05 sa...@abx.abertax.com - sammy
The dovecot configuration is:
# 2.0.19: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-38-generic x86_64 Ubuntu 12.04.2 LTS ext4
disable_plaintext_auth = no
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
log_path = /var/log/dovecot.message
log_timestamp = %Y-%m-%d %H:%M:%S
mail_debug = yes
mail_location = maildir:/var/mail/%u
mail_privileged_group = mail
passdb {
driver = pam
}
passdb {
args = /etc/dovecot/dovecot-ldap.conf
driver = ldap
}
passdb {
driver = pam
}
protocols = imap
service auth {
unix_listener auth-master {
group = vmail
mode = 0600
user = vmail
}
unix_listener auth-userdb {
user = vmail
}
user = root
}
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
userdb {
driver = passwd
}
userdb {
args = /etc/dovecot/dovecot-ldap.conf
driver = ldap
}
userdb {
driver = passwd
}
protocol lda {
hostname = abx.abertax.com
info_log_path = /var/log/dovecot.info.log
log_path = /var/log/dovecot.message
postmaster_address = postmaster@mydomain
}
protocol pop3 {
pop3_uidl_format = %08Xu%08Xv
}
and dovevot-ldap.conf:
uris = ldap://localhost:3389
dn = cn=admin,dc=mydomain
dnpass = openchange
tls = no
ldap_version = 3
base = dc=mydomain
scope = subtree
user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid
user_filter = (uid=%u)
pass_attrs = uid=user,userPassword=password
pass_filter = (uid=%u)
Thanks
Sammy
[Dovecot] lmtp (x...@mydomain.yy): Error: user x...@mydomain.yy: Initialization failed: Namespace '': mbox: mbox requires client_limit=1 for service
new Dovecot 2.0.8 installation on Opensuse 11.3 I got the error lmtp (x...@mydomain.yy): Error: user x...@mydomain.yy: Initialization failed: Namespace '': mbox: mbox requires client_limit=1 for service while trying to transfer mails by lmtp from postfix to dovecot. I googled and looked on the dovecot wiki about this client_limit issue, but no success. What's the syntax of the client_limit and where to place it? Into which config file? Inside the global namespace doesn't seems to work (error on dovecot start). -What's the side effect of this setting to my IMAP clients? Are multiple imap connections to the same mailbox still possible? Regards Birte Nauer
Re: [Dovecot] lmtp (x...@mydomain.yy): Error: user x...@mydomain.yy: Initialization failed: Namespace '': mbox: mbox requires client_limit=1 for service
Am 02.01.2011 um 21:08 schrieb G.Nau:
What's the syntax of the client_limit and where to place it? Into which
config file? Inside the global namespace doesn't seems to work (error on
dovecot start).
Guess you can tweak it here:
$ doveconf -a | grep -A 5 'service.lmtp'
service lmtp {
chroot =
client_limit = 0
drop_priv_before_exec = no
executable = lmtp
extra_groups =
-What's the side effect of this setting to my IMAP clients? Are multiple
imap connections to the same mailbox still possible?
It changes the number of concurrent deliveries allowed - or more precisely
prevents any. 'Mbox' calls for for locking issues.
Regards
Thomas
PGP.sig
Description: Signierter Teil der Nachricht
[Dovecot] Error: user Initialization failed: namespace configuration error: inbox=yes namespace missing
In my email archiving setup, no user will have an inbox (regular mail is taken care of by another system). Is it not possible to configure a dovecot setup without an inbox? /Per Jessen, Zürich
Re: [Dovecot] Error: user Initialization failed: namespace configuration error: inbox=yes namespace missing
On 5.11.2010, at 7.54, Per Jessen wrote: In my email archiving setup, no user will have an inbox (regular mail is taken care of by another system). Is it not possible to configure a dovecot setup without an inbox? No. Also many clients require INBOX to exist and would probably break if it didn't. You could just keep an empty INBOX.
