similar to: Log reopen broken in 2.2.33?

Displaying 20 results from an estimated 3000 matches similar to: "Log reopen broken in 2.2.33?"

2017 Nov 07
1
Log reopen broken in 2.2.33?
On 07.11.2017 08:54, Aki Tuomi wrote: > > On 06.11.2017 23:31, David Zambonini wrote: >> Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? >> >> Using the same config that I've had for the past 10 or so point >> releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, >> but with 2.2.33 (and .1 and .2) no new logfiles are
2017 Nov 07
0
Log reopen broken in 2.2.33?
On 06.11.2017 23:31, David Zambonini wrote: > Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? > > Using the same config that I've had for the past 10 or so point > releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, > but with 2.2.33 (and .1 and .2) no new logfiles are created, file > descriptors still have the original files open and
2017 Dec 14
1
doveadm log reopen not works with 2.2.33
Hi, after the upgrade from dovecot 2.2.32 to 2.2.33 we notice that the /var/log/director/director.log was empty and the log are write in the logrotate file es. /var/log/director/director.log-20171201. Log path is dovecot is: log_path = /var/log/director/director.log Logrotate configuration is: /var/log/director/director.log { ? daily ? rotate 31 ? missingok ? notifempty ? compress ?
2017 Nov 01
2
Bug: lmtp proxy does not quote local parts with spaces
Hi again, I've not heard anything further regarding this bug, so I've had a look at the code. To restate the bug in a more precise way: LMTP in dovecot treats external RFC822 email addresses in the envelope recipient and internal usernames as almost identical/interchangeable. This is incorrect and leads to issues when attempting to use director as an LMTP proxy to proxy to recipients
2017 Nov 07
1
Dovecot auth error
On 07/11/2017 14:18, Mathieu R. wrote: > Maybe i got no answer because there is an error which seem obvious in my > logs : > > Nov 4 20:57:55 vps81550 dovecot: auth: Fatal: sql: driver not set in > configuration file /etc/dovecot/dovecot-sql.conf.ext This might sound silly, but in your doveconf you have: passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } Yet
2017 Oct 23
2
Pigeonhole vacation and envelope extension recipient addresses
I have a situation where my LMTP RCPT TO: goes to a mailbox user account that does not reflect either the final (through aliasing) or envelope email address. SMTP RCPT TO: (envelope-local-part at envelope-domain) Final Recipient: (final-local-part at final-domain) LMTP RCPT TO: (mailbox-local-part at mailbox-domain) I'd like to use the final recipient as the vacation address, but also
2017 Oct 05
2
dovecot: master: Warning: Sent SIGKILL to 100 imap-login processes
Hi, I am using Dovecot 2.2.32 (dfbe293d4) I noticed lots of messages like: dovecot: master: Warning: Sent SIGKILL to 100 imap-login processes in /var/log/maillog I commented out "process_limit" service imap { # Most of the memory goes to mmap()ing files. You may need to increase this # limit if you have huge mailboxes. #vsz_limit = $default_vsz_limit # Max. number of IMAP
2017 Oct 26
2
Bug: lmtp proxy does not quote local parts with spaces
On 26/10/2017 18:38, Alexander Dalloz wrote: > Am 26.10.2017 um 12:20 schrieb David Zambonini: >> >> There seems to be a bug with RFC822 processing in ltmp proxying that >> doesn't >> quote local parts that, for example, contain spaces. > > Newer related RFCs are RFC 5321 and 5322. Typo, meant to say RFC2822, which they still supercede, not that the
2017 Oct 13
3
v2.2.33 released
try with 2.2.33.1 ---Aki TuomiDovecot oy -------- Original message --------From: Odhiambo Washington <odhiambo at gmail.com> Date: 13/10/2017 10:42 (GMT+02:00) To: Dovecot Mailing List <dovecot at dovecot.org> Cc: dovecot-news at dovecot.org Subject: Re: v2.2.33 released On 10 October 2017 at 18:28, Timo Sirainen <tss at iki.fi> wrote: >
2009 Nov 20
2
can R scripts detect signals sent by the task scheduler ?
In general, is it possible to run R scripts through cron jobs ? Is it possible to make the script detect the system interrupt, save its current status and then exit so that next time it is rescheduled it can pick up from where it left ? Examples, if any, are more then welcome. Thank you in advance, Maura tutti i telefonini TIM! [[alternative HTML version deleted]]
2017 Nov 03
0
Bug: lmtp proxy does not quote local parts with spaces
Hi, Sorry, we're in a bit of a v2.3 merge frenzy. Much of the LMTP code will be replaced in v2.3, but I'll give the? older code a look as well. This can take a while though. Regards, Stephan. Op 1-11-2017 om 18:34 schreef David Zambonini: > Hi again, > > I've not heard anything further regarding this bug, so I've had a look at the code. > > To restate the bug
2017 Oct 30
0
Bug: lmtp proxy does not quote local parts with spaces
On 26/10/2017 19:33, David Zambonini wrote: > On 26/10/2017 18:38, Alexander Dalloz wrote: >> Am 26.10.2017 um 12:20 schrieb David Zambonini: >>> >>> There seems to be a bug with RFC822 processing in ltmp proxying that >>> doesn't >>> quote local parts that, for example, contain spaces. >> >> Newer related RFCs are RFC 5321 and 5322.
2006 Sep 20
3
Spinning mongrels and SIGUSR1
First off: Our clusters are LVS balanced Apache 2.2.3 + mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 + memcached / gem memcache_client + gem rails 1.1.6 on debian boxen, and a pgcluster backend. On 2 of our deployed clusters, we are getting the "spinning mongrel" problem. As the clusters are very low volume right now, it takes days to collect a spinner, making it
2017 Nov 03
1
Bug: lmtp proxy does not quote local parts with spaces
On 03/11/2017 11:48, Stephan Bosch wrote: > Hi, > > Sorry, we're in a bit of a v2.3 merge frenzy. Much of the LMTP code will be > replaced in v2.3, but I'll give the? older code a look as well. > > This can take a while though. Thank you very much for getting back to me, I can appreciate it can get hectic, and I don't wish to appear ungrateful, I wholeheartedly
2017 Oct 10
1
v2.2.33 released
https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz.sig We're getting close to the last v2.2.x releases. Hopefully we'll have the first v2.3 beta releases out soon. * doveadm director commands wait for the changes to be visible in the whole ring before they return. This is especially useful in testing. * Environments listed
2017 Oct 10
1
v2.2.33 released
https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz.sig We're getting close to the last v2.2.x releases. Hopefully we'll have the first v2.3 beta releases out soon. * doveadm director commands wait for the changes to be visible in the whole ring before they return. This is especially useful in testing. * Environments listed
2002 Feb 08
3
SCP Problem with OpenSSH 3.0.2p1 linux->solaris
Hello, i am experiencing scp hangs. This command is executed: system("/usr/bin/scp -v -v -v -C root\@$ip:$LOG_DIR_CLIENT$SYSTEM_LOG"."_transfer $LOG_DIR_SERVER$SYSTEM_LOG-$ip >$SSH_STEP3_LOG 2>&1"); from within a perl script.
2017 Oct 26
2
Bug: lmtp proxy does not quote local parts with spaces
There seems to be a bug with RFC822 processing in ltmp proxying that doesn't quote local parts that, for example, contain spaces. director config: director_username_hash = %Ln lmtp_proxy = yes recipient_delimiter = + protocol lmtp { auth_socket_path = director-userdb auth_username_chars = auth_username_format = %Ln passdb {
2017 Oct 11
1
dovecot-2.2.33 bug report
Hello there, dovecot-2.2.33/src/lib/str-find.c:86]: (warning) Calling 'sizeof' on 'sizeof' Source code is ctx = p_malloc(pool, MALLOC_ADD(sizeof(struct str_find_context), MALLOC_MULTIPLY(sizeof(ctx->goodtab[0]), key_len))); Regards David Binderman
2002 Sep 05
7
sshd and SIGKILL
On command: #kill -9 `cat /var/run/sshd.pid` sshd leave pid file ! sshd.c code: =============== .... /* * Arrange to restart on SIGHUP. The handler needs * listen_sock. */ signal(SIGHUP, sighup_handler); signal(SIGTERM, sigterm_handler); signal(SIGQUIT, sigterm_handler); .... =============== Missing line is : signal(SIGKILL, sigterm_handler);