similar to: dovecot 2.2.1: lmtp running in base_dir

On 17/04/2016 21:49, Charles Lepple wrote: > On Apr 16, 2016, at 9:08 PM, Andy R - (NUT-List) > <spinner+NUTlist at delphinidae.org.uk> wrote: >> >> It looks like you were right. I've tried building both the patch >> against the stable 2.7.4 source and using the latest source tarball >> you've just created. The builds both went fine and seem to run as

I am currently running OpenSSH 4.3. I would like to restrict the commands SFTP users can run to a list. For example, "put, get, mput, mget, mkdir, rmdir, and rm". Is this possible with OpenSSH? I have seen many posts concerning chroot'ing and the Forced Command option, but none of these solution address restricting the commands actually available inside the SFTP subsystem. Any

On 17/04/2016 00:50, Charles Lepple wrote: > [as this list does not set or alter the Reply-To header, please use "reply all". Thanks!] > >> On Apr 16, 2016, at 5:14 PM, Andy R - (NUT-List) wrote: >> >> I'm currently using the usbhid-ups driver but as the ups usb-ID isn't recognised in the udev rules I run it as root. Running usbhid-ups gives a "device

Hi I first let base_dir = with it's default value of /var/dovecot. I changed my mind and now I have doveconf -n # 2.1.17: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.4 amd64 ffs base_dir = /var/run/dovecot/ After a few days, imap clients couldn't login. Here the problem Dec 04 17:03:16 imap-login: Fatal: Corrupted SSL parameters file: /var/dovecot/ssl-parameters.dat Dec 04 17:03:16

I can also confirm this, on my own mail server since upgrading to beta1. Dovecot always makes the base_dir world-writable on startup. ----- Forwarded message from Oleg Safiullin <form@pdp-11.org.ru> ----- Date: Fri, 20 Jan 2006 07:09:17 +0600 From: Oleg Safiullin <form@pdp-11.org.ru> To: brad@openbsd.org Subject: dovecot 1.0beta1 Hi. After update dovecot to 1.0beta1 some strange

?On 2020-10-07 12:43, Alexander Dalloz wrote: > Am 07.10.2020 um 18:20 schrieb david at mmpcrofton.com: >> Any ideas on how to resolve the Userdb connect/lookup problem? My users are pinging me on Sieve support. >> Thanks, >> David > Provide a full output of "doveconf -n"? > Alexander Alexandar, Thanks and here you go. # 2.3.7.2 (3c910f64b):

Hi, I would like to disallow dovecot to read its base_dir (mode 0310). This is currently not possible, because settings_verify() in src/master/master-settings.c will "fix" the directory mode to 0750. The following patch for 1.0rc15 ignores the read bit (0444) when checking the directory permissions. Max -------------- next part -------------- A non-text attachment was scrubbed...

Hi, we are getting some core dumps with signal 6 in ltmp on a dovecot director proxy server, like this: Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Panic: file lmtp-proxy.c: line 376 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x363323d99a] ->

I wish someone could help me. I?m trying to track auth in the lmtp code. Nice code base but I?m having trouble tracking the call stack for the error Sent from my iPhone > On Oct 9, 2020, at 08:00, David Morsberger <david at mmpcrofton.com> wrote: > > ?Alexander, > > Do you see anything wrong in my config? > > David > > Sent from my iPhone > >> On

Hi, many people are having problems using SFTP with ChrootDirectory when the jail directory (or the path above) is not owned by root. The question is if chroot'ing to usual home directories can be allowed, even though they are owned by regular users. I know that this topic has been discussed on the list several times now, so I searched the list archives for posts that invalidate the

Hello list today I built dovecot 2.2.1 from sources. But I have permission problems with LDA The "normal" imap part works fine, users can login and see their boxes. deliver is called as LDA from postfix master.cf as follows << dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d

Hello, Following Jan-Frode's advise I am trying this configuration: {postfix} ---lmtp---> {director} ---lmtp---> {dovecot} so I have two dovecot instances for director/proxy and lmtp delivery on ports 1024 and 24 respectively. whilst for imap connections I can specify a pool of imap backend servers via 'director_mail_servers' it seems is not possible with lmtp. Sep 12

I am having problems with dovecot regarding base_dir: I have :: base_dir = /opt/dovecot2/var/run/ For some reason, I have to set permissions to(chmod -R 1777 /opt/dovecot2/var/) for dovecot to run properly, but when I start dovecot, I see this: [root at gw] /opt/dovecot2/etc/dovecot# less /var/log/dovecot/dovecot.log Oct 21 16:15:27 master: Warning: Killed with signal 15 (by pid=72634 uid=0

Hello, when trying to set up a migration scenario from my old mailbox-servers to my new dovecot-cluster, I get a coredump from dovecot/lmtp when proxying mail-delivery to more than one recipient on the old mailbox-server. My setup: 3 director-hosts (Debian stretch) are proxying to a pair of replicator-hosts and during migration also to the old mailbox-server. For migration the not-migrated

> On 15 June 2019 10:56 Daniel Lange via dovecot <dovecot at dovecot.org> wrote: > > > Am 15.06.19 um 00:36 schrieb Michal Krzysztofowicz via dovecot: > > Would you know if Dovecot project uses an issue tracker which is publicly available, and which I can check? > > I am not aware of public access to the Open Exchange AG / Dovecot OY > issue tracker. I guess

# 2.2.devel (c73322f): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (fac92b5) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 ==> /var/log/dovecot/dovecot.log <== Oct 15 09:50:15 nihlus dovecot: lmtp(11447): Connect from local Oct 15 09:50:15 nihlus dovecot: lmtp(tlx at leuxner.net): Panic: file lda-sieve-plugin.c: line 447 (lda_sieve_execute_scripts): assertion failed: (script !=

Hello, today I run the command "doveadm auth cache flush" for the first time. # doveadm auth cache flush doveadm(root): Error: userdb lookup: connect(/var/run/dovecotauth-master) failed: No such file or directory 0 cache entries flushed # base_dir was the only item contain 'run' and it did not end with a / So I tried to set base_dir to /var/run/dovecot/ and could now rerun

Hi Steffen, 248 is a dovecot, 202 is dovenull, both users are in theirs groups across. If I change ownership of /usr/local/dovecot to dovecot.dovecot, then dovecot is correcting it to root.root for some reason. Does it mean that dovecot should be running as root only? What does it mean / here? is it / in filesystem or it is / for dovecot in /usr/local/dovecot ? May 01 14:36:00 master:

Running CentOS 5 and Dovecot 1.2.16 Receiving error: Error: stat(/var/run/dovecot) failed: Invalid argument Fatal: Invalid configuration in /etc/dovecot.conf I've put the default dovecot.conf in place and still get the same thing. I've tried removing the /var/run/dovecot folder and letting it re-create it with no success. It creates the /var/run/dovecot folder but that is all.

Hello all... I've installed dovecot on my ISP's shell server, and am using SSH tunnelling so that I can retrieve my mbox-format mail from procmail-processed mailboxes on that server (normally I just ssh there and read them locally with pine, but now that I have a phone with an IMAP client, I wanted to be able to read it more easily there). The problem I'm having is, although it's