similar to: Samba internal dns server vs Bind

>What are you thinking to transfer the zones to ? I try to explain, why I asked the question. Now we have NT4 style Samba domain, with ldap backend, and Bind. We have two sites, they are connected through VPN. On the servers, Bind configured as master-slave. On every site, there is a master, for their own domain, and they are each others' slave. As I know, this is zone transfer. I want to

On Wed, 2019-06-19 at 15:11 +0200, Pisch Tam?s via samba wrote: > Hi, > > I set up Samba DCs for two sites. The first site is for example > domain.ourdomain.com, the second is site2.ourdomain.com. On the first > site, there will be 2 DCs, and one fileserver, on the second site > there will be one DC, and it will act as fileserver too. > Is it true that Samba's internal

Hello, Sometime when we receive a spam or virus that is detected as it, mailer daemon send a reply to the sender to inform that the message is a spam or content viruses. The problem is that the sender of the spam as something like voicemail at ourdomain.fr ( the user voicemail doesn't exist in our database ) And sometimes dovecot create the directory and store the reply 's mail...

Hi Louis, answers are inline ... On 03/24/2015 03:48 PM, L.P.H. van Belle wrote: > Realm is advices to use UPPERCASE.. not obligated. ( but very advices yes ) I changed the config to uppercase and rebooted, no change in the logfiles. > > check the following outputs and post them back in the list ( if needed anonymized ) > > hostname -i 192.168.1.235 > hostname -s the-ad-hostname

Hello, I've been trying to figure this out for some time and can't quite nail it down, despite searching the internet, and a couple of samba books. Here goes: I'm running "Version 3.4.3-3.3.1-2341-SUSE-SL11.2" of Samba on OpenSUSE 11.2. Here are some relevant excerpts from my smb.conf file: [global] ... security = ADS ... winbind separator = + ... log level = 2 ...

On 28.3.2019 22.34, Robert Kudyba via dovecot wrote: >>>>> Set >>>>> >>>>> ssl_client_ca_file=/path/to/cacert.pem to validate the certificate? >>>> >>>> Can this be the Lets Encrypt cert that we already have? In other >>>> words we have: >>>> ssl_cert = </etc/pki/dovecot/certs/dovecot.pem

I tried to synchronize the sysvol folders, on two dcs. Something went wrong since yesterday we have replication problems: One machine shows this, while the other one is happy. samba-tool drs showrepl ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=ourdomain,DC=com Default-First-Site-Name\DC03 via RPC DSA object GUID: af610e1a-9e3b-4cdd-a36b-c296d77a9479 Last attempt @

thanks for your input. Bill: deliver is just a symlink to dovecot-lda Stephan: I don't know, and and it even does not work when I use deliver -f "postmaster at ourdomain.internal" - I get the same error message. A part of the mail I got when using 2.2.23: Return-Path: <MAILER-DAEMON> Delivered-To: user1 at ourdomain.internal Received: from localhost (localhost [127.0.0.1])

This is still happening after a reboot, Fedora 28. Restarting dovecot fixes the problem. Does anyone know if it could be related to this bug report? *https://bugzilla.redhat.com/show_bug.cgi?id=103401#c130 <https://bugzilla.redhat.com/show_bug.cgi?id=103401#c130> * and suggested work around to add ports to /proc/sys/net/ipv4/ip_local_reserved_ports? Nov 8 12:21:41 ourdomain dovecot[1386]:

I am trying to configure NIS, PAM, & LDAP on a CentOS 6.2 host. I've previously installed a similar configuration on RHEL4, but CentOS now uses nss-pam-ldapd and nslcd instead of nss_ldap, so the configurations are a little different. Currently, local users and groups are showing up but not LDAP users. When I do a /getent passwd/ and/getent group/ I don't get LDAP users. When I do

Hi, there is a recommendation in the Samba AD DC howto: "We do not recommend using the Domain Controller as a file Server." We have two sites. We have two Samba3 servers now with ldap on site1, and one Samba3 BDC on site2. We have ~200 users, and around 50 clients connect to the servers at the same time on site1, and around 20 clients connect to the BDC on site2. On the BDCs there are

I am installing smb 3.5 on a CentOS 6.2 host using smbldap-tools. I've previously installed a similar configuration on RHEL4 using smb 3.0 but CentOS now uses nss-pam-ldapd and nslcd instead of nss_ldap, so the configurations cannot be moved straight across. When I do a listing of a share directory that should have user and group ownership determined by LDAP, I get the uidNumbers and

Hi all, Ok, been wanting to do this for a while, and I after the Heartbleed fiasco, the boss finally agreed to let me buy some real certs... Until now, we've been using self-signed certs with the following dovecot config: ssl = required ssl_cert = </etc/ssl/ourCerts/imap.pem ssl_key = </etc/ssl/ourCerts/imap_key.pem Now, I've created new keys/certs and the CSR, got the new

We're using quite successfully a samba 4.1 AD setup authenticating user. We have on an unregular basis mails that can't be delivered because dovecot-pam fails to verify the credentials. I'm trying to debug this and set the loglevel up to 3. I can see an error message being spammed in the log files and can't figure out what causes this. I expect a configuration error somewhere

when you read. : http://www.spinics.net/lists/samba/msg111972.html says: > >That output > ; TSIG error with server: tsig verify failure >is usually only seen when the internal DNS server is running. >It's a glitch, which can be ignored atm (all dyn. updates are done OK). > so if you dont want to see that error, switch to bind9_DLZ. Greetz, Louis

Hello, I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I have a strange problem with lda. We use bounce mails for internal users if they try to send virus/spammails. The exact same config works with 2.2.23, but not with 2.3.0. The relevant postfix/master.cf part: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail

Ady, I had not previously tried three slashes, but have now. No difference unfortunately. I've also tried using the web server on the same machine as the PXE server and using 'http://127.0.0.1/Software/Util1.iso' as the URL, again to no avail. It appears not to be able to connect to anything via http or https. Presumably it uses network settings (such as the gateway) provided by the

Hello, I am running Debian testing x64 and have manually installed the 6.03pre17 deb packages for extlinux, pxelinux, syslinux, syslinux-common, syslinux-stuff and syslinux-utils. I have a working tftpd-hpa 5.2-18 PXE system and can boot PCs to it. All .c32 binaries, gpxelinux.0 and memdisk are from the Debian packages and everything works except for http/https sources of ISOs. I have tried both

Hello, I'm running a few tests here with two locations. site1: server-site1.gsg.local subnet 192.168.200.0/24 site2: server-site2.gsg.local subnet 192.168.190.0/24 both are connected via VPN. I migrated an samba3 domain at server-site1 it gets Default-First-Site-Name assigned. Then I joined the new samba4 domain withe server-site2. Both servers work and i can join and access them with

>From searching the web, I found that many people have encountered this problem. The fixes the suggested don't seem to work for me... My smb.conf file looks like this [global] workgroup = OURDOMAIN security = ADS realm = OURDOMAIN.com password server = OURSERVER encrypt passwords = yes add user script = /usr/sbin/useradd %u hosts allow = 192.168.X. 127. winbind uid = 10000-20000 winbind