Hi Aki,
Thank you.
The problem is solved.
in global-acls i have created the file .DEFAULT
now the Masteruser can read INBOX.
Best regards
Luda
> Am 09.04.2019 um 09:46 schrieb Ludwig Wieland :
>
> Thank you,
>
> How and where ?
>
>
> I configured only this:
> cat
> On 11 April 2019 07:57 Robust Coding via dovecot wrote:
>
>
> Hi Admin,
>
> I hope you consider reading and addressing my concern promptly.
>
> For the past few days I've been setting up a VPS with cPanel and WHM
> pre-installed on Bluehost. I want to enable push notification plugin in
Hi Admin,
I hope you consider reading and addressing my concern promptly.
For the past few days I've been setting up a VPS with cPanel and WHM
pre-installed on Bluehost. I want to enable push notification plugin in
Dovecot2.3.5. I tried OX and Lua plugins and got errors.
For using OX plugin:
On 11/04/2019 00:51, Laura Smith via dovecot wrote:
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, April 10, 2019 11:48 PM, John Fawcett via dovecot
> wrote:
>
>> On 11/04/2019 00:18, Laura Smith via dovecot wrote:
>>
>>> ‐‐‐ Original Message ‐‐‐
>>> On Wednesday, April 10, 2019
‐‐‐ Original Message ‐‐‐
On Wednesday, April 10, 2019 11:48 PM, John Fawcett via dovecot
wrote:
> On 11/04/2019 00:18, Laura Smith via dovecot wrote:
>
> > ‐‐‐ Original Message ‐‐‐
> > On Wednesday, April 10, 2019 10:24 PM, Aki Tuomi aki.tu...@open-xchange.com
> > wrote:
> >
On 11/04/2019 00:18, Laura Smith via dovecot wrote:
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, April 10, 2019 10:24 PM, Aki Tuomi
> wrote:
>
>>> On 10 April 2019 23:56 Laura Smith via dovecot < dovecot@dovecot.org> wrote:
>>>
>>> ‐‐‐ Original Message ‐‐‐
>>> On Wednesday, April
‐‐‐ Original Message ‐‐‐
On Wednesday, April 10, 2019 10:24 PM, Aki Tuomi
wrote:
> > On 10 April 2019 23:56 Laura Smith via dovecot < dovecot@dovecot.org> wrote:
> >
> > ‐‐‐ Original Message ‐‐‐
> > On Wednesday, April 10, 2019 9:14 PM, Aki Tuomi <
> >
Yes. I gave it a try here, and it seems to work. Does it give any extra
information if you include -i flag?
Aki
Yes, I had tried that, and it doesn't give much extra information, at
least to my eye, that seems to help my issue. Above the previous
output it outputs the Version, Flags,
On 10 April 2019 23:56 Laura Smith via dovecot <
dovecot@dovecot.org> wrote:
‐‐‐ Original Message ‐‐‐
On Wednesday, April 10, 2019 9:14 PM, Aki Tuomi <
aki.tu...@open-xchange.com> wrote:
‐‐‐ Original Message ‐‐‐
On Wednesday, April 10, 2019 9:14 PM, Aki Tuomi
wrote:
> > On 10 April 2019 23:13 Laura Smith via dovecot dovecot@dovecot.org wrote:
> > Sent with ProtonMail Secure Email.
> > ‐‐‐ Original Message ‐‐‐
> > On Wednesday, April 10, 2019 8:20 PM, Aki Tuomi
On 4/10/2019 1:32 AM, Aki Tuomi wrote:
On 9.4.2019 18.15, Dave wrote:
I've tried specifying an output file as well, per the script's
command line options,
but the output file is 0 bytes. Does anyone have any suggestions?
I *think* I'm
using it the way it's intended to be used, but maybe
> On 10 April 2019 23:13 Laura Smith via dovecot wrote:
>
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, April 10, 2019 8:20 PM, Aki Tuomi
> wrote:
>
> > > On 10 April 2019 22:13 Laura Smith via dovecot dovecot@dovecot.org wrote:
> > > On
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Wednesday, April 10, 2019 8:20 PM, Aki Tuomi
wrote:
> > On 10 April 2019 22:13 Laura Smith via dovecot dovecot@dovecot.org wrote:
> > On Wednesday, April 10, 2019 7:57 PM, Aki Tuomi aki.tu...@open-xchange.com
> >
> On 10 April 2019 22:13 Laura Smith via dovecot wrote:
>
>
> On Wednesday, April 10, 2019 7:57 PM, Aki Tuomi
> wrote:
>
> > > On 10 April 2019 21:26 Laura Smith via dovecot dovecot@dovecot.org wrote:
> > > ===
> > > dsync(foo...@example.com): Error: imapc(foobar.example.com:993):
> > >
On Wednesday, April 10, 2019 7:57 PM, Aki Tuomi
wrote:
> > On 10 April 2019 21:26 Laura Smith via dovecot dovecot@dovecot.org wrote:
> > ===
> > dsync(foo...@example.com): Error: imapc(foobar.example.com:993):
> > dns_lookup(foobar.example.com) failed: read(/var/run/dovecot/dns-client)
> >
> On 10 April 2019 21:26 Laura Smith via dovecot wrote:
>
>
> ===
> dsync(foo...@example.com): Error: imapc(foobar.example.com:993):
> dns_lookup(foobar.example.com) failed: read(/var/run/dovecot/dns-client)
> failed: read(size=512) failed: Connection reset by peer
>
This is dovecot's
‐‐‐ Original Message ‐‐‐
On Wednesday, April 10, 2019 1:08 PM, Michael Orlitzky via dovecot
wrote:
> On 4/10/19 6:39 AM, Dmitry Donskih via dovecot wrote:
>
> > `chmod -R 655 /etc/foobar/ssl' drops x attribute from`ssl' itself.
> > Use `chmod -R 755' or`chmod +x' or similar.
>
> Your
===
dsync(foo...@example.com): Error: imapc(foobar.example.com:993):
dns_lookup(foobar.example.com) failed: read(/var/run/dovecot/dns-client)
failed: read(size=512) failed: Connection reset by peer
dsync(foo...@example.com): Error: Failed to initialize user: imapc: Login to
foobar.example.com
On Wednesday, April 10, 2019 11:40 AM, Gerald Galster via dovecot
wrote:
> > Am 10.04.2019 um 11:59 schrieb Laura Smith via dovecot
> > :
> >
> > On Wednesday, April 10, 2019 10:52 AM, Aki Tuomi via dovecot
> > wrote:
> >
> > > On 10.4.2019 12.36, Laura Smith via dovecot wrote:
> > >
> > > >
> On 10 Apr 2019, at 11:50, Aki Tuomi via dovecot wrote:
>
>
>> On 10 April 2019 20:48 @lbutlr via dovecot wrote:
>>
>>
>> On 10 Apr 2019, at 10:43, @lbutlr via dovecot wrote:
>>> lso, the failed message strongly implies that the email was not delivered,
>>> since it happens on the
> On 10 April 2019 20:48 @lbutlr via dovecot wrote:
>
>
> On 10 Apr 2019, at 10:43, @lbutlr via dovecot wrote:
> > lso, the failed message strongly implies that the email was not delivered,
> > since it happens on the delivery log line and there is not indication in
> > the log that
On 10 Apr 2019, at 10:43, @lbutlr via dovecot wrote:
> lso, the failed message strongly implies that the email was not delivered,
> since it happens on the delivery log line and there is not indication in the
> log that delivery succeeded. However, the message is delivered. It might be
> worth
On 10 Apr 2019, at 10:55, Remo Mattei via dovecot wrote:
> This is what fixed mine
>
> service stats {
> # unix_listener stats-reader {
> # group =
> # mode = 0666
> # user =
> # }
> unix_listener stats-writer {
> group = dovecot
> mode = 0666
> user =
> }
> }
This is what fixed mine
service stats {
# unix_listener stats-reader {
# group =
# mode = 0666
# user =
# }
unix_listener stats-writer {
group = dovecot
mode = 0666
user =
}
}
> On Apr 10, 2019, at 09:43, @lbutlr via dovecot wrote:
>
> On 10 Apr 2019, at
On Wed, 10 Apr 2019 at 19:44, @lbutlr via dovecot
wrote:
> On 10 Apr 2019, at 09:06, @lbutlr via dovecot wrote:
> > Should I add
> >
> > service stats {
> > unix_listener stats-writer {
> > user = dovecot
> > }
> > unix_listener stats-reader {
> > user = dovecot
> > }
> > }
> >
>
On 10 Apr 2019, at 09:06, @lbutlr via dovecot wrote:
> Should I add
>
> service stats {
> unix_listener stats-writer {
> user = dovecot
> }
> unix_listener stats-reader {
> user = dovecot
> }
> }
>
> to my dovecot.conf file?
I did this and it appears to have fixed the issue.
On 4/4/19 6:57 PM, Peter Mogensen wrote:
>
>
> On 4/4/19 6:47 PM, dovecot-requ...@dovecot.org wrote:
>> For a typical Solr index, 60 seconds is an eternity. Most people aim
>> for query times of 100 milliseconds or less, and they often achieve
>> that goal.
>
> I'm pretty sure I get these
On Wed Apr 10 2019 11:14:29 GMT-0400 (Eastern Standard Time), @lbutlr
via dovecot wrote:
> On 10 Apr 2019, at 08:59, Tanstaafl via dovecot wrote:
>> On Wed Apr 10 2019 09:13:41 GMT-0400 (Eastern Standard Time), Luis F. V.
>> Gomes via dovecot wrote:
>>> I had a disk problem and had to reformat
On Wed, 10 Apr 2019 at 18:06, @lbutlr via dovecot
wrote:
>
>
> > On 10 Apr 2019, at 08:57, Odhiambo Washington via dovecot <
> dovecot@dovecot.org> wrote:
> >
> >
> >
> > On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot
> wrote:
> > On 10 Apr 2019, at 08:36, @lbutlr via dovecot
> wrote:
> > >
On 10 Apr 2019, at 08:59, Tanstaafl via dovecot wrote:
> On Wed Apr 10 2019 09:13:41 GMT-0400 (Eastern Standard Time), Luis F. V.
> Gomes via dovecot wrote:
>> I had a disk problem and had to reformat it. All mailboxes were backed
>> up using rsync.
>> After I restored the mailboxes, the POP
> On 10 Apr 2019, at 08:57, Odhiambo Washington via dovecot
> wrote:
>
>
>
> On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot wrote:
> On 10 Apr 2019, at 08:36, @lbutlr via dovecot wrote:
> > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den))
>
> One other detail:
On Wed Apr 10 2019 09:13:41 GMT-0400 (Eastern Standard Time), Luis F. V.
Gomes via dovecot wrote:
> I had a disk problem and had to reformat it. All mailboxes were backed
> up using rsync.
> After I restored the mailboxes, the POP clients (Thunderbird) that
> were configured to leave the
On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot
wrote:
> On 10 Apr 2019, at 08:36, @lbutlr via dovecot wrote:
> > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den))
>
> One other detail:
>
> /var/run/dovecot/stats-writer:
> 0 srw-rw 1 root dovecot 0 Apr 10
On 10 April 2019 17:49 @lbutlr via dovecot <
dovecot@dovecot.org> wrote:
On 10 Apr 2019, at 08:36, @lbutlr via dovecot <
dovecot@dovecot.org> wrote:
net_connect_unix(/var/run/dovecot/stats-writer) failed:
On 10 Apr 2019, at 08:36, @lbutlr via dovecot wrote:
> net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den))
One other detail:
/var/run/dovecot/stats-writer:
0 srw-rw 1 root dovecot 0 Apr 10 08:47 stats-writer
--
"Back off, man. I'm a scientist."
I am getting this error in logs
net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den))
and I looked around the google results and it seems to be related to using
service stats, which I am not using.
# doveconf -n | grep stat
# doveconf -n | head -3
# 2.3.5.1 (7ec6d0ade):
Hello
I had a disk problem and had to reformat it. All mailboxes were backed
up using rsync.
After I restored the mailboxes, the POP clients (Thunderbird) that
were configured to leave the messages on the mailserver for, let's
say, 30 days, didn't understand that some messages were already
On 4/10/19 6:39 AM, Dmitry Donskih via dovecot wrote:
> `chmod -R 655 /etc/foobar/ssl' drops x attribute from `ssl' itself.
> Use `chmod -R 755' or `chmod +x' or similar.
>
Your private keys should be... private. Use 750 instead.
> Am 10.04.2019 um 11:59 schrieb Laura Smith via dovecot :
>
>
> On Wednesday, April 10, 2019 10:52 AM, Aki Tuomi via dovecot
> wrote:
>
>> On 10.4.2019 12.36, Laura Smith via dovecot wrote:
>>
>>> Dovecot 2.3.3 (dcead646b)
>>> openSUSE Leap 15.0
>>> I am getting a weird error message:
>>>
`chmod -R 655 /etc/foobar/ssl' drops x attribute from `ssl' itself.
Use `chmod -R 755' or `chmod +x' or similar.
10.04.2019 12:36, Laura Smith via dovecot пишет:
> Dovecot 2.3.3 (dcead646b)
> openSUSE Leap 15.0
>
> I am getting a weird error message:
>
> Fatal: Error in configuration file
On 10.4.2019 13.33, Gerald Galster via dovecot wrote:
>
>> Am 10.04.2019 um 11:24 schrieb luckydog xf via dovecot :
>>
>> Hi, list,
>>
>> I downloaded dovecot-2.3-pigeonhole-0.5.5.tar.gz and installed it, after
>> I enabled
>>
>> #/etc/dovecot/conf.d/20-managesieve.conf
>> protocols =
> Am 10.04.2019 um 11:24 schrieb luckydog xf via dovecot :
>
> Hi, list,
>
> I downloaded dovecot-2.3-pigeonhole-0.5.5.tar.gz and installed it, after
> I enabled
>
> #/etc/dovecot/conf.d/20-managesieve.conf
> protocols = $protocols sieve
>
> it said " protocols: Unknown protocol:
On Wednesday, April 10, 2019 10:52 AM, Aki Tuomi via dovecot
wrote:
> On 10.4.2019 12.36, Laura Smith via dovecot wrote:
>
> > Dovecot 2.3.3 (dcead646b)
> > openSUSE Leap 15.0
> > I am getting a weird error message:
> > Fatal: Error in configuration file /etc/dovecot/local.conf line 16:
> >
On 10.4.2019 12.36, Laura Smith via dovecot wrote:
> Dovecot 2.3.3 (dcead646b)
> openSUSE Leap 15.0
>
> I am getting a weird error message:
>
> Fatal: Error in configuration file /etc/dovecot/local.conf line 16: ssl_cert:
> Can't open file /etc/foobar/ssl/certbot.pem: Permission denied
>
> I
Dovecot 2.3.3 (dcead646b)
openSUSE Leap 15.0
I am getting a weird error message:
Fatal: Error in configuration file /etc/dovecot/local.conf line 16: ssl_cert:
Can't open file /etc/foobar/ssl/certbot.pem: Permission denied
I have tried the following:
- chmod -R 655 /etc/foobar/ssl (/etc/foobar
Hi, list,
I downloaded dovecot-2.3-pigeonhole-0.5.5.tar.gz and installed it,
after I enabled
#/etc/dovecot/conf.d/20-managesieve.conf
protocols = $protocols sieve
it said " protocols: Unknown protocol: sieve"
What's wrong?"
Thanks,
We're in the process of upgrading Dovecot from version 2.1.17 to 2.2.27
(package Debian Stretch). We have a shared NFS storage in use by
multiple servers without Dovecot director. I've tested by connecting to
IMAP on the new server to my own mailbox. This isn't a problem. But when
the server with
On 9.4.2019 18.15, Dave wrote:
> >> I've tried specifying an output file as well, per the script's
> command line options,
> >> but the output file is 0 bytes. Does anyone have any suggestions?
> I *think* I'm
> >> using it the way it's intended to be used, but maybe I'm not?!
> >> -Dave
> >
>
48 matches
Mail list logo
