Good point.
But when I try to add a user with the "user@domain" format using the
useradd command I get error...
useradd: invalid user name 'u...@domain.com'
Does this mean it's time to switch to database auth?
Here is output you requested:
# 2.0.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32
Am 02.10.2014 um 22:24 schrieb Cliff Hayes:
> Good point.
> But when I try to add a user with the "user@domain" format using the useradd
> command I get error...
> useradd: invalid user name 'u...@domain.com'
>
> Here is output you requested:
passdb {
driver = pam
}
userdb {
driver = passwd
Good point.
But when I try to add a user with the "user@domain" format using the
useradd command I get error...
useradd: invalid user name 'u...@domain.com'
Here is output you requested:
# 2.0.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 Scientific Linux release
Am 02.10.2014 um 22:13 schrieb Cliff Hayes:
> I am trying to configure a new IMAP based mail server.
> I thought I had everything correct.
> I have dovecot logging turned up and see that dovecot is processing the
> entire email address as the username like
> this...
> Oct 2 14:52:20 servername d
I am trying to configure a new IMAP based mail server.
I thought I had everything correct.
I have dovecot logging turned up and see that dovecot is processing the
entire email address as the username like this...
Oct 2 14:52:20 servername dovecot: auth: Debug:
pam(testu...@domain.com,1.2.3.4):
On Thursday, October 2, 2014, 10:22:42 AM, jjhoffart wrote:
> Hello,
> I am currently trying to setup two invocations of dovecot
> to run on a debian based server. One for director and the other a
> stock debian instance. The issue I am having is when I go to start
> the director instance
Hello,
I am currently trying to setup two invocations of dovecot to run on a
debian based server. One for director and the other a stock debian instance.
The issue I am having is when I go to start the director instance, I receive
multiple errors telling me that the listening ports are a
On 10/2/2014 9:57 AM, Teemu Huovila wrote:
> On 10/01/2014 09:43 PM, Ben Johnson wrote:
>> Ultimately, I have two questions:
>>
>> 1.) Is the nesting structure that I've employed correct? The Wiki 2 page
>> is not clear with regard to the nesting; is it correct to put the
>> "namespace" block insid
On 10/01/2014 09:43 PM, Ben Johnson wrote:
> Ultimately, I have two questions:
>
> 1.) Is the nesting structure that I've employed correct? The Wiki 2 page
> is not clear with regard to the nesting; is it correct to put the
> "namespace" block inside the "protocol imap" block, as I demonstrated ab
Steffen,
My problem was exactly what you said, the quota field in my query.
I fixed it and now is working very well.
Thank you very much.
Alfredo
- Mensagem original -
De: "Steffen Kaiser"
Para: "Alfredo Saldanha"
Cc: dovecot@dovecot.org
Enviadas: Quinta-feira, 2 de outubro de 2014 3:
On 10/02/2014 02:40 AM, Remko Lodder wrote:
> and a mail_replica = tcp:host{a,b}:12346 configuration on each host so that
> they are pointing to eachother; This seems to work fine for most accounts,
> for example: I never experienced issues with this. However, several other
> accounts (with a la
11 matches
Mail list logo