Displaying 20 results from an estimated 10000 matches similar to: "users = virual + system (both with ldap backend) => Fatal: setgid(12(mail)) failed with euid=501(..."
2018 Oct 16
0
Fatal: setgid, imap connections dropped.
I'm still trying to fix this problem. Hopefully someone can help.
I've upgraded dovecot to 2.3.3
# dovecot --version
2.3.3 (dcead646b)
That didn't help.
Next I switched 10-auth.conf to use a local password file (instead of LDAP)
=======================================
# cache all authentication results for one hour
auth_cache_size = 10M
auth_cache_ttl = 1 hour
2020 Oct 13
0
Fatal: setgid from userdb lookup fails with wrong gid
Hello all,
I'm quite new as well to Dovecot, just installed it on a FreeBSD system
with Postfix and Rspamd as side apps. Things are running semi-smoothly
for all users but I do have quite a few errors in the logs :
Oct 13 19:43:56 apollo dovecot[24478]:
imap(user1)<34412><zIeI9ZCxXDmsFhZG>: Fatal: setgid(1030(user1) from
userdb lookup) failed with euid=1022(user4),
2020 Oct 14
1
Fatal: setgid from userdb lookup fails with wrong gid
Hi,
Not sure if this is it, but I used to have the same error when I started
with dovecot.
Aki's response was the following (and solved my problem).
-------------
Hi!
You can't set
service imap {
service_count = 256
}
if you are using multiple system UIDs. See
https://wiki.dovecot.org/Services#imap.2C_pop3.2C_submission.2C_managesieve
*service_count* can be changed from 1 if only a
2018 Sep 28
2
Fatal: setgid, imap connections dropped.
Hi,
I'm getting errors with my IMAP setup.
Basically, everything seems to work.
Mail is delivered nicely from Postfix to Dovecot via LMTP. Dovecot does
the authentication to LDAP (also for Postfix). Users are able to send mail
via authenticated submission (Postfix) and login into IMAP and POP.
However, IMAP connections are dropped frequently with an "ERROR:
Connection dropped by IMAP
2009 Sep 30
4
deliver: Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted
I'm calling 'deliver' from Postfix and in some cases from
Procmail.
I set this system up more than six months ago and it's been
working flawlessly until yesterday (16:52:19 local time) when
it, without any apparent reason, just stopped delivering mails!
Lots of checking and googling (I've forgot how exacly I setup
the system :), I made 'deliver' SUID and it worked
2018 Dec 04
2
Lda fatal: setgid (102 from userdb lookup) failed
Sorry if this is a nubbie question, but I?m getting:
lda(jlbrown at bordo.com.au)<4444><QFg5KRHVBBxcEQAAYBwt+A>: Fatal: setgid(102 from userdb lookup) failed with euid=501(jlbrown), gid=20(staff), egid=20(staff): Operation not permitted (This binary should probably be called with process group set to 102 instead of 20(staff))
How can I fix this?
(macOS Mojave, Dovecot 2.3.4)
2013 May 03
0
dovecot 1.2.5 Fatal: setgid(5000(vmail)) Operation not permitted
This is the error I'm getting (whenever i recieve and email):
*deliver() : Fatal: setgid(5000(vmail)) failed with euid=5000(vmail),
gid=8(mail), egid=8(mail): Operation not permitted (This binary should
probably be called with process group set to 5000(vmail) instead of 8(mail))
*
I am at loss. I have tried "everything" i could think of (besides purging
the machine and do it all
2018 Dec 04
0
Lda fatal: setgid (102 from userdb lookup) failed
On 4.12.2018 3.27, James Brown via dovecot wrote:
> Sorry if this is a nubbie question, but I?m getting:
>
> lda(jlbrown at bordo.com.au)<4444><QFg5KRHVBBxcEQAAYBwt+A>: Fatal: setgid(102 from userdb lookup) failed with euid=501(jlbrown), gid=20(staff), egid=20(staff): Operation not permitted (This binary should probably be called with process group set to 102 instead of
2012 Feb 26
1
deliver(test@[***domain_name***]): Fatal: setgid(5000) failed with ... Operation not permitted
Hi, I am relatively new to linux, and have set up my first lamp server around a month ago. The server is housed in a data centre a few miles from my house, and is working as a web server (with apache, tomcat, mysql) just fine.
I have now been trying for a week to get Postfix and Dovecot working with postfixadmin and mysql.
(below I have replaced my test domain name with [***domain_name***])
The
2008 May 17
2
expire plugin - setgid failed
Hello all,
I'm trying to get the expire plugin working, but still having issues
even with 1.1RC5.
If I run the expire tool I get the following error:
server:~# dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool
Fatal: setgid(100) failed with euid=2005, gid=0, egid=0: Operation not
permitted
Same thing with --test:
server:~# dovecot --exec-mail ext
2010 Sep 20
1
[PATCH] Fix error launching libguestfs when euid != uid
When writing to a RHEV target, virt-v2v launches the libguestfs appliance with
euid:egid = 36:36, which is required to write to an NFS target using
root_squash. Since the update to use an febootstrap cached appliance, this
causes an error on startup as the cached files are owned by root, but the cache
directory is owned by 36:36. The reason for this is that execve() resets euid
and egid to uid and
2009 May 23
2
setgid error
Hi all
Trying to setup dovecot with mysql and postfix, I have configured it
as given below. thecot user has the dovecot group as primary, and is
also a member of mail and dovecot-users. Still, it can't setgid to
dovecot-users. I tried changing the shell for the dovecot user to
something useful and chmod'ing a file to dovecot-users, and it work
well. Still, no mail comes through
2001 May 04
1
RSARhosts / Hostbased auth and euid=0 requirement
I'm not happy with ssh being setuid root. I know that the long-term goal is
to have a seperate host-key-management process, but that is a ways off.
Until then, I'd like to propose the following:
- Allow ssh to read alternate key files.
This would allow the ssh client to use keyfiles different from the ones
sshd uses. I know that this can be done now by changing the ones sshd uses,
2010 Apr 19
2
setgid failed - Not owner
Hello ALL,
I got errors on a new installation, maybe I forgot something.
The system is Solaris, Dovecot 1.2.10, Postfix 2.7.0, MySQL 5.1.25.
Can send mail with dovecot imap, but can`t retrieve the messages.
Strange, I can save and retrieve draft messages ok, files are always
with postfix:postfix ownership.
Sorry if this is newbie question, but can`t find a solution.
Syslog info:
Apr 19
2009 Nov 13
0
Dovecot setuid, setgid, permission denied Problem!
Hello! Please, help!
I have trouble with Dovecot's Deliver utility. I don't know how to avoid
errors. Let me know what additional related information do you need?
1) Its call in Exim's configure:
==========================================
local_delivery_spam_transport:
driver = pipe
command = /usr/local/libexec/dovecot/deliver -c
2002 Mar 07
0
[Bug 136] New: setgid() deemed to fail for non-suid ssh client on linux if using other than primary group
http://bugzilla.mindrot.org/show_bug.cgi?id=136
Summary: setgid() deemed to fail for non-suid ssh client on linux
if using other than primary group
Product: Portable OpenSSH
Version: 3.0.2p1
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ssh
2018 Jan 20
1
[Bug 13239] New: "rsync --times" does not keep dirs' setgid bits when user not member of setgid group
https://bugzilla.samba.org/show_bug.cgi?id=13239
Bug ID: 13239
Summary: "rsync --times" does not keep dirs' setgid bits when
user not member of setgid group
Product: rsync
Version: 3.1.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
2018 Jan 15
0
Samba 4.6.2 does not inherit setgid bit (anymore)
Somewhere between Samba 4.2.10 and 4.6.2 (came with CentOS 7 updates)
the setgid bit is not inherited anymore when making directories via my
Samba service. Everything else is still fine. With ssh direct on the
file system or sftp, i get all permissions and acls inherited nicely.
Also with Samba all acls are still just fine, except that setgid bit is
not inherited (s on the group executable
2018 Jan 04
0
Problem with --times and setgid dir when user not member of the group
When copying locally as well as remotely inside a setgid dir, the option
--times has the unwanted side effect of making the newly created
directories not have the setgid bit set, but only when the user running
rsync is not a member of the corresponding group. The extra option
--omit-dir-times prevents the loss of the setgid bit in this case.
Is this a bug as I think it is? Note that files
2018 Feb 05
0
Samba 4.6.2 does not inherit setgid bit (anymore)
Hi Lorenzo and Dale,
My setup is like Lorenzo's completely based on setgid being propagated.
The filesystem should determine the group used starting at a certain
directory. Different "root" directories have different groups, and
security is based on groups, not users.
I tried all sorts of settings combinations, alseo "force directory mode
= 2770", but none propagates