similar to: core dumps with 3.0.23c

I'm using procmail as the local delivery agent for Maildir style mailboxes. I discovered that I was able to send mail to other users but was unable to send mail to myself. Examples from verbose procmail log: **** Successful message to another user **** procmail: [24589] Fri Jun 2 15:03:34 2006 procmail: Assigning

I have users that belong to several groups. I want a logon script to be run for each of the groups to which a user belongs. For example, when I logon, I want admin.bat, users.bat, and someothergroup.bat to run. On Novell I used to use 'if Member of groupName...', but I don't know how to do this in Samba.. Thanks, Dean

When logs (e.g. /var/log/maillog) are rotated (e.g. to /var/log/maillog-YYYYMDD) is there a way via systemd or whatever to assign read permission to a specific group? Right now, for example - ls -l maillog* -rw------- 1 root root 3105240 Mar 13 22:04 maillog -rw------- 1 root root 1079031 Feb 24 04:39 maillog-20190224 -rw------- 1 root root 7237640 Mar 1 12:59 maillog-20190228 -rw------- 1

Folks-- I'm working with an old system I set up to copy files from one local directory to another. I was using rdist for this, but I would prefer to shift it over to rsync. The one thing I'm missing is the trivial ability to force the group owernship of the destination files to a specific group. A read through the manpage and various searches on the web do not turn up any helpful hints

Hi, I'm running Samba Version 3.0.25c on Solaris 10 8/07 on X86 hardware. It's successfully joined to AD. But, and there always is a but, if : * A user is a member of SomeGroup * and the share alllows SomeGroup to access it * and SomeGroup is NOT what the user has set as their Primary Group in Active Directory then * Samba will recognize that the user can access the share * but,

Thank you Kees. On Mon, 6 Nov 2023 at 09:37, Kees van Vloten via samba <samba at lists.samba.org> wrote: > I am currently running at 4.19.2 but I have run 4.18.6 and 4.18.5. I did > not experience any issues with nested group lookups, which many of the > filters rely on. Interestingly, I've now found that (on my current DCs, running 4.18.5), ldbsearch *does* seem to return the

For a new file server that doesn't really do much other than run samba, is there any advantage to quad core CPUs vs dual core? Say the two options are equivalent in price. Thanks, Mark

Hi there, I use FC5. I discovered, for an exemple, if you have a user group with 3 members (Alan, Baker, Clive), before 3.0.23c this line at smb.conf worked fine: valid users = @user But with 3.0.23c update it doesn't work anymore. You have to replace the line like this: valid users = Alan, Baker, Clive I mean, replace the "@groupname" with the complete userlist of the

Hi, I've just updated (using yum under fedora 5) to the latest version of samba and am now encountering a major problem with samba. Whenever I attempt to access shares (don't have printers or other such non disk shares) the access fails (after prompting for password, and performing some level of authentication, it notes if no password is entered that Anonymous login successful).

> Normally a group cannot 'own' files etc, Unix uses ugo permissions and > when you chown a file you would use something like this: > > chown foo:somegroup somefile > > this would make 'foo' the owner of the file and possibly allow > 'somegroup' access to it, this would depend on whatever permissions you > set with 'chmod' > > So,

Hi, I've a question about the syntax of the valid users option. Any help is greatly appreciated! Here is the Background: samba 3.0.4 Linux as Domain Member Active Directory, not in Native Mode Compiler opions: --with-winbind --with-pam --with-smbmount The goal is to authenticate via the Windows Domain and allow access via Windows groups. The syntax in my smb.conf looks like this:

I'm quite confused by this one, as I can't see how this would happen.. but after upgrading my DCs from 4.11.10 to 4.18.5, LDAP searches don't seem to work if they use the :1.2.840.113556.1.4.1941: modifier, aka LDAP_MATCHING_RULE_IN_CHAIN. (Yes, it was a fairly big version jump.. Yes, I should have upgraded much earlier.. Yes, I know 4.19.x is out now as well) Here's a search that

Op 05-11-2023 om 23:25 schreef Jonathan Hunter via samba: > I'm quite confused by this one, as I can't see how this would happen.. > but after upgrading my DCs from 4.11.10 to 4.18.5, LDAP searches don't > seem to work if they use the :1.2.840.113556.1.4.1941: modifier, aka > LDAP_MATCHING_RULE_IN_CHAIN. (Yes, it was a fairly big version jump.. > Yes, I should have

On Wed, 2023-11-22 at 17:33 +0000, Jonathan Hunter wrote: > On Wed, 22 Nov 2023 at 01:03, Andrew Bartlett < > abartlet at samba.org > > wrote: > > Are you sure that the ACLs on all the items in the chain should > > allow reading? > > It's an excellent question, thank you - I'd like to just say "Yes" > but > I will certainly check, as

Op 06-11-2023 om 14:58 schreef Jonathan Hunter: > Thank you Kees. > > On Mon, 6 Nov 2023 at 09:37, Kees van Vloten via samba > <samba at lists.samba.org> wrote: >> I am currently running at 4.19.2 but I have run 4.18.6 and 4.18.5. I did >> not experience any issues with nested group lookups, which many of the >> filters rely on. > Interestingly, I've now

Hello! It seems my struggle with Samba isn't quite over. My latest problem is exactly what you see above, followed by an attempt to core dump. This occurs upon authentication to the system. My system is part of a W2K3 domain. I looked at the Samba HOWTO, but apparently I have a system (FC5), that doesn't allow core dumps when the PID changes, since no core dumps are being created.

We had to do a few changes in this area (due to security issues) over that large number of releases, it is entirely possible there was a regression. If you have time and patience, could you back up your DC, restore into a subdirectory (on your DC or on a test box) with 4.11.10 from git, and then do a git bisect between that and 4.18.5. You can run the query locally with bin/ldbsearch -H

On Mon, 6 Nov 2023 at 14:32, Kees van Vloten <keesvanvloten at gmail.com> wrote: > > > Op 06-11-2023 om 14:58 schreef Jonathan Hunter: > > Interestingly, I've now found that (on my current DCs, running > > 4.18.5), ldbsearch *does* seem to return the expected result, but the > > same query via ldapsearch does not. > > What if you try to use starttls

Still having problems with my Samba configuration, even after upgrade to the latest FC5 samba package. Getting "Access Denied" errors when trying to connect with a member of the group "Domain Users" to the MP3s share. The W2K3 server shows that authentication was successful. I can't find any errors in the logs at all, and winbind appears to be working (I can su to the

I've just installed dovecot on my FC5 box. I tweaked the dovecot-openssl.cnf and attempted to recreate the cert but get the errors below. I see older postings about this problem on FC2. help? - e # ./mkcert.sh /etc/ssl/certs directory doesn't exist /etc/ssl/private directory doesn't exist error on line -1 of dovecot-openssl.cnf 2810:error:02001002:system library:fopen:No such