I think I might have worked out the grouping problem locally by simply
adding (manually) the names of members of B to /etc/group, and changing the
directory ownership to the corresponding groups. Its a strange situation as
there are users in /etc/group that are not present in /etc/passwd (they are
On Wed, Sep 22, 2010 at 11:44 PM, Grant wrote:
>
> Since you are already doing everything based on AD ...
> Have the windows folks make AD security groups for your groups b c d e And
> then filter the shares using smb.conf entries like
> valid users = @ad\groupB
> write list = @ad\groupB
>
> To
On Sep 22, 2010, at 9:24 AM, Madhusudan Singh
wrote:
> Hello,
>
> Server: Ubuntu Lucid server version
> Role: Samba file server (I administer it)
> Authentication: Against a Windows AD (I do not administer it) using winbind.
> No other authentication scheme is practicable/possible - I do NOT w
This happens sometimes when a local mail server rejects a message as
spam because it contains words in a different language than used
locally. Your original post did make it to the samba list. The "spam"
message fortunately only went to the original sender (you). Someone on
the list however did
I understand neither the language nor the intent of this message. How could
the initial message possibly be spam ? Was it the use of the capital case
for the workgroup ?
2010/9/22
> Message rejected: message contains bad words.
> Message is marked as spam.
>
> De informatie uit deze e-mail (en e
Hello,
Server: Ubuntu Lucid server version
Role: Samba file server (I administer it)
Authentication: Against a Windows AD (I do not administer it) using winbind.
No other authentication scheme is practicable/possible - I do NOT want to
manage passwords locally on this machine.
LDAP: Not explicitly
