similar to: migrating mailboxes on dovecot

I am running dovecot 1.2.16 and not able to figure out an error that happens whenever I select the root of a virtual mailbox tree. At the moment I have a simple maildir store, accessed via IMAP, and have successfully added a virtual fs namespace with two subdirectories. I have created dovecot-virtual entries in the subdirs and they are working fine; they show the expected messages, etc. My

OK I finally found time to write this. (this is for dovecot 99.X and Xmail 1.X >= 1.17) (in dovecot 1.0 it'll able to auth against Xmail via a auth script. aka You'll only need to have 1 user account databases, XMAIL's YAY !!!) Steps: 1. Install Dovecot. (rpm or Source) >From Source : http://wiki.dovecot.org/CompilingSource >From RPM :

Hi, I have installed latest Dovecot 1.0.13 on a FreeBSD 6.2 with XMail (www.xmailserver.org). It works OK except one thing: error on startup. After each reboot there are lots of such error: dovecot: Mar 28 08:54:38 Error: child 916 (login) returned error 89 dovecot: Mar 28 08:54:54 Error: imap-login: No authentication sockets found When I restart dovecot by running startup script

Hello people, Well, what the subjects says :-) I have a dovecot/Horde installation and would like to know : a. How safe will I be backing up dovecot b. What folders/files to backup Let me see now; I am running dovecot v1.2.15 Here's a dump of "dovecot -n" : ---------------------------------------------------------------- [root at mailgate ~]# dovecot -n # 1.2.15:

Hello all, I have a DL360 G4 1U server that does a wonderfull job with dovecot horde, Xmail and OpenLDAP for a company and serving about 40 acouunts. The machine is wonderful. I am very happy with it. However, I am running out of disk space. It has two times 76Gb Drives in RAID1 (disk mirroring) and the capacity has reached 82%.? I am starting of getting nervous. Does anyone know of a painless

We are splitting our users into 2 domains(DOMAINA and DOMAINB (changed for security reason)). I am having problems getting users who log into their workstation on DOMAINA to access a samba share on DOMAINB. We are using W2K3 servers as our AD with LDAP. Samba shares on are CentOS5.1 servers. I Can anyone point me to some docs on how to set this up? I have been rumbling through google for the past

Hi, I have these following configurations: Active Directory 1 = DomainA.com AD1 Primary Group = Domain Users AD1 Group 1 = Linux (member: DomainB\ad2testuser1) Server joined = linux1.DomainA.com (configured Kerberos and Winbind Samba4 from sernet) Active Directory 2 = DomainB.com AD2 Primary Group = Domain Users (member: DomainB\ad2testuser1) AD2 User 1 = ad2testuser1 note: (1)

I'm setting up Samba in an environment with 2 Active Directory domains setup with a one way trust (DOMAINA -> DOMAINB). Samba is in DOMAINA. From looking at the logs (see below) it appears that winbind is having troubles getting the credentials for the domain controller in DOMAINB. I can get tickets, using kinit, for accounts in both domains. I can join DOMAINA just fine. Running

I have two domains which are on different subnets, connected by a routed OpenVPN tunnel. The domains trust each other. Domain A has the WINS server. Domain B is confused to use Domain A's WINS server. The VPN pushes the WINS server as part of its DHCP options as well. >From either domain, I am able to use smbclient to see the shares on the other domain's PDC. I have to specify -W

Hello. I need the file server to authenticate users from two domains. Of DOMAINA that the file server has joined and users of DOMAINB that maintains a trust relationship with DOMAINA. I have two domain forests (DOMAINE and DOMAINB), and a trust relationship exists between both. DOMAINA servers are running with samba version 4.5 (with CentOS 7 system) the DOMAINB server is running with windows

I noticed that smbclient worked on some solaris 11 machines but not others. The issue a slightly different version of libarchive on the machine (0.12 vs 0.13), even though I thought all machines had been patched to the same level. So I decided to recompile. When recompiling samba 4.4.7 on solaris 11 I saw the following warning Checking for header krb5.h

I have been trying off and on for some time now to get an interdomain trust relationship going between two samba pdc machines (DomainA=trusted & DomainB=trusting). Both pdc's are running on Solaris boxes and NIS is involved (I doubt there is a NIS complication just because I can use accounts on DomainA on DomainB's samba, as long as I add them using smbpasswd manually). The situation

> IMHO, for this to work you should define "idmap domains = DOMAINA > DOMAINB" and configure the idmap backend appropriately for both domains > using idmap config DOMAIN:backend/range/default etc... > > For more details see "man idmap_tdb, man idmap_ldap and man idmap_rid". > > --Sadique Hi Sadique, thanks for your response. I test it but I don't

Hello, I am running a samba/ldap PDC on domainA with winbind. It works fine as a domain controler. Samba : 3.0.21c OpenLDAP : 2.2.15 I want to add domainB as a trusted domain (ie the users of domainB would have access to the shares of domainA without another authentication). I configured this and net rpc give me this : # net rpc trustdom list Password: Trusted domains list: DomainB

Hi I have a problem with an interdomain trust where on the PDC for DomainA, everything works perfectly. getent returns local and DomainB usernames. On the PDC for DomainB, it's DomainB works fine, but getent only returns local usernames and groups, it doesn't return the usernames or groups for DomainA. wbinfo -u and wbinfo -g work fine and return all DomainA's usernames and groups.

I've pored through the documentation, wiki, lists, etc, and I can't seem to come to a concise conclusion on how to accomplish this. My specific scenario is the following. I have a samba PDC domain called domainA, and an AD domain called domainB. domainA and domainB are different named domains, and they each authenticate logins and credentials on their own turf. The users on domainA

In summary * DomainA Samba classic domain- PDC and BDC are running Samba 4.4.7. The PDC is called "SambaPDC." * DomainB Windows AD domain , level 2008, domain controller is Windows 2012 or 2012R2 (you are correct that there are not primary and backup controllers in AD) * DomainC Windows AD domain, level 2008, domain controllers are Windows 2008 I need to get

Hi there, This is most likely something very basic which I'm not seeing right now. I have a Samba-server, which is running in security = domain, and it's a member of that domain (DOMAINA). The domain is a Win2003 domain. That domain has established a trust with another domain (DOMAINB). There's a Windows terminal server TERMSRV which is a member of DOMAINA, but a user from DOMAINB

I’ve removed the following line from smb.conf: > >> winbind use default domain = Yes > Although we are using it on a different server (who has direct access to all DC’s from both domains). > And we are able to logon with credentials from a different domain. > by using "ssh -l DOMAINA+username SERVER02" > >> We now come to the domain ranges, they must not

config smb.conf [global] realm = DOMAINB workgroup = DOMAINB security = ADS template homedir = /home/%U template shell = /bin/bash winbind expand groups = 1 winbind separator = + winbind use default domain = Yes idmap config domainb : range = 3000001 - 4000000 idmap config domainb : backend = rid idmap config domainc : range = 2000001 - 3000000 idmap config domainc : backend = rid