search for: eingangs

Hi! I am using Unix groups to control access to shared mailboxes. This works fine as long as files are not moved between mailboxes that are owned by different groups. The move operation doesn't change group ownership of the mail. Is there a way to force dovecot to e.g. inherit the ownership from the parent folder, not only for new messages bot also for messages moved from one folder to

On Fri, 8 Aug 2003, Maik Schmitt wrote: [...] > I just tried to use it with our 7960 (sip-version). > > I've set the services_url in SIPDefault.cnf to > "http://xxx.xxx.xxx.xxx/xmlservices/vm/index.php&user=1234&pin=1234" > > It didn't work with ?user=...&pin=.... cause the phone then tried to > get

Hi, i've installed dovecot on a new mailserverand try to set up some shared mailboxes. I have everiting up an runnig so far. I have 3 mboxes to be shared. I have use the following setup namespace private { separator = prefix = location = inbox = yes hidden = yes } namespace public { separator = / prefix = zentrale/ location =

...strict locking = Yes map to guest = Bad User dos filetimes = Yes create mask = 0660 preserve case = yes short preserve case = yes case sensitive =yes hide unreadable = yes [fax] browsable = yes writable = yes comment = Eingangs-Fax-Queue path = /var/spool/fax/recvq public = yes -------snipp------ I would be happy if someone on the list could tell me what's going wrong. greets Harry

...%h %m % root postexec = /opt/samba/netlogon/bye.sh %u %M %m %I %a %S & [homes] comment = Heimatverzeichnisse path = /home/%u read only = No create mask = 0700 [fax] browsable = yes create mode = 0644 writable = yes comment = Eingangs-Fax-Queue path = /var/spool/fax/recvq [rootdir] create mode = 0644 writable = yes path = / [data] browsable = yes create mode = 0644 writable = yes comment = Datenverzeichnis path = /data public = yes [homepages]...

Hello, First of all sorry for my English. I am experiencing with Samba and I have a problem. I have an old server (OLD) with Red Hat 9 and Samba 2.2.7a that is working well. Now I try to start up a new server (NEW) with Red Hat Enterprise 4 and Samba 3.0.22. If I try to connect from NEW to itself by using smbclient I got the shared resources list correctly. If I try to connect to NEW from OLD,

Hi list, I have managed to grant a specific user access to a sub-folder (sub-level 3 from the share's entry point, I think) on a Samba 4 share he/she is not allowed and not able to access in total/general. I tried 2 different ways with one of them working. I'd like to discuss why that is. For the sake of an example, let's say the share is for teaching material (exam templates,

Upgraded to Samba 4.11.2 and I?ve now too started seeing the message: get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY A lot. I modified the source in source3/locking/share_mode_lock.c a bit in order to print out the values of the service path, smb_fname & old_write_time when it fails and it seems they are all NULL? [2019/11/14 14:24:23.358441, 0]