similar to: Errors and dovecot crashing...

I see you haven?t received an answer. Sorry people here don?t seem to have time or inclination to answer basic questions. I?ve tried. You?re better to search elsewhere. Ethon > On Oct 11, 2017, at 12:17 PM, Michael Segel <dovecot_mjs at hotmail.com <mailto:dovecot_mjs at hotmail.com>> wrote: > > Hi, > > I?ve downloaded and built dovecot from the source. >

I DID offer my help privately. And I have attempted on NUMEROUS occasions to contract somebody to help with ZERO response. So, you?ll excuse me if I have an attitude. Ethon > On Oct 15, 2017, at 11:27 PM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > Here is a simple template you can use as quick start example, and what you can expand later on, feel free to adapt your needs

Here is a simple template you can use as quick start example, and what you can expand later on, feel free to adapt your needs mail_home=/home/vmail/%Lu mail_location=sdbox:~/Mail mail_uid = vmail mail_gid = vmail passdb { driver = static args = password=pass } ssl=yes ssl_cert=<cert.pem ssl_key=<key.pem namespace { inbox = yes separator = / } ps. Ethon, this is a community

Sharing an installed copy of dovecot between several users each running a daemon within their own account (or using the same binaries for a system daemon and a user daemon) is difficult because the compile-time directory PKG_STATEDIR (typically /var/lib/dovecot) is hard-coded as the location of things like the ssl-parameters.dat file and the replicator database. Replace all these uses of

On 30/08/2019 02:52, David Walling via samba wrote: > We have been experiencing a debilitating 'bug' in samba where something is causing a flood of the messages seen below in smbstatus and the network drives ( in our case N: ) on all clients become unresponsive. In fact, the entire client becomes unresponsive, essentially making them unusable until samba is restarted. We first saw

Bonjour Markus, > - Have you checked that port 12345 as specified below is open/forwarded > and actually /used/ by dovecot (e.g., use "netstat -tulpn|grep dovecot")? Yes of course: tcp 0 0 0.0.0.0:12345 0.0.0.0:* LISTEN 22025/dovecot tcp6 0 0 :::12345 :::* LISTEN 22025/dovecot > -

I left in some of the parameters I've been testing commented out. Interestingly, we've noticed another client triggering the same type of symptoms every morning at around the same time. Those symptoms being a line 'lookup_name_smbconf for COMPUTERNAME$ failed' and a flood of failed connection attempts from the same client. The issue seemed to resolve itself after a few minutes

HI, Do you have selinux activated? Maybe the context for logrotate does not allow accessing files under /home, and the root cli is not troubled by such a limitation? Why are you storing log files under /home anyway? Note: I don't use any OS with selinux, so can't really help with fixing this an issue. Regards, Tom On 17-11-17 22:42, SH Development wrote: > So, the question is, why

So, the question is, why can I rotate the log manually, but cron returns a permission error? Do I need to tell cron to run it as sudo or something like that? Ethon > On Nov 17, 2017, at 2:29 AM, Tom Hendrikx <tom at whyscream.net <mailto:tom at whyscream.net>> wrote: > > Hi, > > > Your crontab should normally mail you error output. But you can also run > the

We have been experiencing a debilitating 'bug' in samba where something is causing a flood of the messages seen below in smbstatus and the network drives ( in our case N: ) on all clients become unresponsive. In fact, the entire client becomes unresponsive, essentially making them unusable until samba is restarted. We first saw this and connected it to the following open bug in samba

In that scenario, what actually happens? Does mail get stored? Or rejected? Or delayed? Jeff > On Jan 24, 2017, at 6:54 PM, Roger Klorese <rogerklorese at gmail.com <mailto:rogerklorese at gmail.com>> wrote: > > I'd take the opposite approach and tell them no new mail will be received until they are under quota. > On Tue, Jan 24, 2017 at 4:52 PM SH Development

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> What version are you using? </div> <div> <br> </div> <div> Aki </div> <blockquote type="cite"> <div> On 10 March 2019 00:40 SH Development via dovecot < <a

That doesn?t seem to work either. Where do I find logs for log rotation to see the reason it failed? Ethon > On Nov 16, 2017, at 7:53 PM, Bill Shirley <bill at KnoxvilleChristian.org <mailto:bill at KnoxvilleChristian.org>> wrote: > > I believe you need a 'create' statement to set the permissions. Here > is an example for mariadb: >

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> You should upgrade 2.2 first. </div> <div> <br> </div> <div> Aki </div> <blockquote type="cite"> <div> On 10 March 2019 10:45 SH Development via dovecot

I thought I read somewhere that the hostnames on replicated dovecot servers had to be different. Is this simply the hostname you specify in the config for dovecot and can this be different than the actual unix hostname? Ethon B. > On Oct 11, 2017, at 11:04 PM, Anvar Kuchkartaev <anvar at anvartay.com> wrote: > > If you are using different hostname for each server then you need

Hi, Your crontab should normally mail you error output. But you can also run the logrotate command manually, in verbose mode. Kind regards, Tom On 17-11-17 03:35, SH Development wrote: > That doesn?t seem to work either. Where do I find logs for log rotation to see the reason it failed? > > Ethon > > > >> On Nov 16, 2017, at 7:53 PM, Bill Shirley <bill at

Ok, so for lack of any other information, am I to conclude that the doveadm backup command is broken in 2.0.9? I have been through the wiki for it back and forth and cannot make it work. Yes, I need to upgrade, there is no question, but I won?t do that without a maildir backup. I would prefer to use the built-in dovecot mechanisms for that than something else. Jeff > On Mar 10, 2019, at

Shouldn't an event of this type trigger a useful warning instead of a cryptic programming error? On Thu, Dec 13, 2018 at 07:42, Timo Sirainen <tss at iki.fi> wrote: > On 13 Dec 2018, at 7.31, SH Development <listaccount at starionline.com> wrote: >> >> I have started getting these in my log. What does this mean and what do I need to do? >> >> Panic:

Please keep responses in list. rm -f /var/lib/dovecot/ssl-parameters.dat, i think it was in that dir. On 2017-02-03 17:00, Thierry wrote: > Hi, > > I have removed the '<' : > > ssl_client_ca_file = /etc/ssl/certs/GandiCA2.pem > > But now: > > doveadm: Error: Corrupted SSL parameters file in state_dir: ssl-parameters.dat - disabling SSL 360 > doveadm:

Dear Thierry, - Have you checked that port 12345 as specified below is open/forwarded and actually /used/ by dovecot (e.g., use "netstat -tulpn|grep dovecot")? - Did you retrace your steps and have you verified that synchronisation works with ssl disabled? - Did you verify your certificate files (e.g., "openssl verify -verbose -CAfile /etc/ssl/certs/GandiCA2.pem