similar to: Doveadm-sync SSH practicalities

Terry Jones wrote: > The documentation is somewhat silent on this subject. If you mean https://wiki.dovecot.org/Tools/Doveadm/Sync the answers seem implicit to what's been stated. > What permissions does the SSH user need ? To be able to run the doveadm executable (or a wrapper script that eventually runs doveadm) on the remote side. > How associated does it need to be with

> If you mean https://wiki.dovecot.org/Tools/Doveadm/Sync the answers seem > implicit to what's been stated. Yes, I do mean that address, I read that page four times and was still none the wiser. <rant-mode>And to be completely frank with you, if documentation relies on "implicit" guesswork and expects the user to "read between the lines" then in my books it

Hello, Still busy with details... Considering, as in my previous example, a password_query returning '!' or NULL for the "nologin" column, depending on an account's status (suspended or not). Let's consider a suspended user "some.user". In the case of a successful authentication, one has: sh-3.2# doveadm auth test some.user goodpassword; echo $? passdb:

I use SSH-AGENT in my system, to cache SSH credentials and avoid typing my key every time I connect to a remoto host. But "doveadm sync/backup", when one of the ends is SSH accessed, doesn't use the available SSH-AGENT and forces me to type my password. -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/

Hi all, First sorry i really couldn't find it back been searching everywhere even the docs and its bit confusing. I am using # doveadm -D sync -u *@mydomain.net remote:myserver.net # which works perfect however for security reasons we now need to change the sshd port on the remote server. How do i tell doveadm to use a custom SSH port (would love to continue to use just the ssh

I am running Dovecot with system users (userdb passwd), but some of those users don't have shell accounts on the IMAP server so their shell on that machine is set to /usr/sbin/nologin. Currently I am using maildirs and this is not a problem, but I am in the process of switching to dbox which means I will need a cronjob running 'doveadm purge -A'. During testing I found that those

On Thu, 10 Jan 2019 at 16:09, Kenneth Porter <shiva at sewingwitch.com> wrote: > I updated to CentOS 7.6 and something must have changed in the base OS > setup that prevents vsftpd from allowing logins for accounts with > /sbin/nologin as their shell. I had to add that to /etc/shells so that > such > accounts could FTP again. That file is in the setup package. Did it >

--On Thursday, January 10, 2019 4:17 PM -0500 Stephen John Smoogen <smooge at gmail.com> wrote: > So I think this is a side effect of a long term argument of the security > nature of /sbin/nologin > > https://serverfault.com/questions/328395/nologin-in-etc-shells-is-dangero > us-why > https://lists.fedoraproject.org/archives/list/devel at lists.fedoraproject.o >

There's been an ongoing discussion (started by Colin Percival's recent work on nologin) about environment-poisoning attacks via "login -p". I thought I saw a way to address this, but the more I learn, the uglier this looks. Maybe some of the good folks who read freebsd-security can puzzle this one out: Problem: login -p can be used to propagate environment flags in order to

I updated to CentOS 7.6 and something must have changed in the base OS setup that prevents vsftpd from allowing logins for accounts with /sbin/nologin as their shell. I had to add that to /etc/shells so that such accounts could FTP again. That file is in the setup package. Did it include /sbin/nologin before? I don't have anything in my notes from setting up the system last year about

On Fri, 29 Mar 2019 17:21:54 +0000 Stephen via samba <samba at lists.samba.org> wrote: > Hi Rowland! > > On 29/03/2019 16:33, Rowland Penny via samba wrote > > Roll on 'Buster' ;-) 4.5.x is well EOL. > > Its not ideal I know! ;) Unfortunately I (and every other Raspberry > Pi user) is stuck with this for now since this is the default Samba > package

I need to set up some (err, a lot) of user accounts for (pop) mail and ftp access purposes. But disallow shell login access. What I can do to achieve this - and it works well - is to create a small script, thus: #!/usr/bin/tail +6 # # /etc/NOSHELL # # Login shell to prevent shell access for user accounts # ######################################################################### #

Running Dovecot 2.1.7. I'm trying to migrate from an environment with mbox files to a maildir configuration. I remove all vestiges of my maildir over in /var/mail I put my old mailboxes in ./Mail and my old inbox in ./matthew. I issue this command: doveadm sync -u matthew at matthew.at mbox:./Mail:INBOX=./matthew Initially it gave me errors about separator, so I set the separator in

Hi, Since I upgraded from 2.2.21 to 2.2.23, the user option -u seems to be ignored by doveadm sync, or at least it doesn't handle it correctly. If I run the following in the shell as user 'max': % doveadm sync -u foo at example.com -d doveadm(max): Error: User doesn't exist I get it to work if I set the USER environment variable to foo at example.com: % USER=foo at

Hi command im using command bellow on destination server rtying to make keep it in sync after initialy doing doveadm backup -R doveadm -Dv -o imapc_host=src.srv -o imapc_user=test at domain.tld -opop3c_user=test at domain.tld -o imapc_password='pass' -o pop3c_password='pass' -o mail_fsync=never -o mail_prefetch_count=20 sync -f -1 -R -u test at domain.tld imapc: Im using

Dear all, I successfully migrated hundreds of mailboxes with Dovecot 2.2.24 on OpenBSD 6.0 (amd64. Old server is OpenBSD 5.1, i386, Dovecot-2.0.17), but got error while migrating 3 mailboxes: # doveadm -o mail_fsync=never sync -1 -R -s '' -u user at domain.com imapc: dsync(user at domain.com): Panic: file mailbox-alias-plugin.c: line 77 (mailbox_symlink_exists): assertion failed: (ret

I'm no docker guru - so I'm more than a little out of my depth in this case. But clearly ssh is installed, because that's what I'm running, and the sshd allows a connect and I get a return from ls. So, it's working fine outside the container. And I only need to execute doveadm sync inside the container. [Because that's where docecot/doveadm is installed.] So, it sure

Hi, I?m migrating an old Zarafa-installation to a dovecot using mdbox and sis on Debian Jessie. To copy over the emails, I use doveadm backup on the new box - or more precisely: vmail# doveadm -v -o imapc_user=$user -o imapc_password=$pass -o imapc_host=$host -o imapc_features=rfc822.size -o imapc_port=993 -o mailbox_list_index=no -o imapc_ssl_verify=no backup -R -x "Public folders*"

Hi -- I'm used to dsync my two mailservers running 2.0.16. Today, I did upgrade one server to 2.1, and doveadm sync is throwing to following error: mail> doveadm sync -f -u test ssh vmail at remote-host.tld dsync -v -f -u test doveadm(test): Fatal: All your namespaces have a location setting. It should be empty (default mail_location) in the namespace to be converted. Same error with

+1 to that idea. Ask the same couple month before during migration from 1.x to 2.x but got no answer from someone who able to change this. On Tue, 17 Nov 2015 10:35:11 +0200 Teodor Milkov <tm at del.bg> wrote: > Hello, > > Currently doveadm tool can't be used with read-only source locations > because it's trying to create lock files. > > I'd guess lock