similar to: Dovecot virtual and SASL with Postfix

Hi, I'm trying to allow domain-less logins for a multi-domain virtual IMAP server, and wondering if I can automatically infer the domain (value of variable %d) from the local IP (%l) or the hostname used by the client when connecting to my server. Let's say I have two host names: mail.foo.org (10.0.0.100) and mail.bar.com (10.0.0.200), with forward and reverse DNS configured to resolve A

On Fri, Feb 19, 2016 at 08:41:15AM +0100, Steffen Kaiser wrote: > >I'm trying to allow domain-less logins for a multi-domain virtual IMAP > >server, and wondering if I can automatically infer the domain (value of > >variable %d) from the local IP (%l) or the hostname used by the client > >when connecting to my server. > > > >Let's say I have two host

Hi all, actually I got a problem with the namespaces in dovecot 1.1 beta11. It occured after purging index files and resynch via imapsync. Dovecot complains about "Unknown namespace", though it worked with versions before. I cannot comfirm for 1.1beta10, but I surely know 1.1beta9 worked with these settings. Example: From Folder [INBOX/Trash] To Folder [___________] To Folder

hello list, I am attempting to sync two imap servers using the imapsync perl script. It seems handy and easy. Here's what happens when I try to do this: # # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master"). # -o smtpd_sasl_auth_enable=yes # -o

very intrigued by your solution Timo, have attempted something similar in the past to no avail. When I tried I was unable to retain the user at domain when setting the domain as extra field - protected is new to me and can't find documentation - but also doesn't work :( # cat passwd.domains 10.100.1.1:::::::domain:protected=foo.org 10.100.1.2:::::::domain:protected=bar.org # cat

Dear all, Could anybody give me some recommended open source software for wifi management? What I am looking for is a simple and basic tools, for example the software will have these kind of features : - user connect to the wifi network - user got IP from DHCP but he can't browse to anywhere at first. Instead he will redirected to a "login page" - administrator will set the

Hi All! I am working on a complete migration from an old solaris machine running Cyrus IMAP v2.3.14 and wish to migrate all users to a new ubuntu vm running Dovecot 2.0.19. What I have so far is a fully functional dovecot installation with LDAP / Dovecot SASL auth using Maildir++. My plan is to use Perdition IMAP proxy on a third host and migrate users a few at a time (see attached picture of

Did anyone set up the enviroment in dovecot with post login scripting in which imapsync does sync between two mailservers on users login (on login sync mail from old to new mailserver) is there a alternative or different approach? something like #!/bin/bash /usr/bin/imapsync --syncinternaldates --nosyncacls --authmech1 PLAIN --host1 old.server.com --user1 $USER*master --password1 master

This is probably a dumb question, but I'll ask anyway. I am currently using Postfix with Dovecot and Cyrus-SASL. I want to switch over to Dovecot SASL. The regular Dovecot user/password file is not the same as the file used by cyrus-sasl. Usewr names and passwords are different. I created a flat file that dovecot can use for SASL look-ups; however, exactly where in the Dovecot config file to

I'm trying to set up SMTP authentication on my server and am getting an authentication failed error. My client is set up to automatically select authentication method and tries CRAM_MD5. The http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL suggests "passdb pam" and "userdb passwd" -- is it possible to configure sasl authentication using a dovecot.conf like

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Attached is a patch against current CVS that adds support for the GSSAPI SASL mechanism. It was written from scratch, after reading the patch from Colin Walters against a much older version of dovecot. Other then support for the 'GSSAPI' mechanism, it contains the following changes: - - Added 'auth_krb5_keytab' option for

Posted Monday 7/25. Haven't seen a response. Trying again: --- This is a noobie question, so bear with me if it's not worded correctly: Primary Requirements: 1) I'd like to have two namespaces - one private/per-user, and one public (visible by all logged-in users). The public mailbox(s) would be used to distribute information to all users. 2) I'd like both

Greetings, Can Dovecot can handle separate authentication for receiving mail (IMAPS) and sending mail (SMTPS)? In the past, we used Dovecot IMAP for the receiving part and Cyrus SASL for the sending part. This allowed us to use two passwords with mail. Cyrus has grown too old and isn't useful anymore. Can Dovecot give us this functionality: two passwords, one for IMAP

Yes and No. It's confusing to me which is why I ask. Per my initial email my password source is PAM. It's the userdb I'm concerned about ... which dovecot is using /etc/passwd. So dovecot is getting user information from passwd file; password information from PAM. I need to add extra fields for qouta but can't add them to /etc/passwd so I have to create a passwd with the extra

We using Dovecot with LDAP. From the beginning, we using GC LDAP query with port 3268 for email accounts. For example, user1 at our-organization.org (in the USA) with "base = dc=our-organization, dc=org" works fine. But refer to this document: https://wiki2.dovecot.org/AuthDatabase/LDAP When we change the LDAP from 3268 to 389 and with TLS, the base should be changed like this:

I need to implement quota. I read as much as I could including http://wiki2.dovecot.org/HowTo/SimpleVirtualInstall But my current /etc/passwd file does not have the password in it as shown in dovecot docs ... there is an x where the password should be. I created a program that creates a passwd file in the proper format with the proper extra quota fields for all users (except it has an x where

Ive been using qmail+vpopmail+courier-imap for many years but its time to retire that server so I thought this might be an opportunity to see how I could use Postfix and Dovecot to provide the same services. Im running Dovecot 2.1.9 and Postfix 2.9.4. I have spent a few days reading through some of the docs on the wiki (there's doesn't seem to be any large overview of Dovecot concepts or

Michael Smith wrote: > Currently, "source". Other suggestions welcome. I see. I guess the current working semantics don't need anything more complicated. If the need rises to provide more complex access control, userid / password pairs could be defined in the icecast config file. e.g.: user1 / password1 allowed to connect as source /source1* user2 / password2 allowed to

Hi! I have a server with a few thousand mailboxes (for a few hundred domains) on it. The usernames are following several naming conventions: username_domain domain_username username_domain.tld username-domain domain.username The reason for this chaos is that the accounts were set up on different mailservers, some imail, some linux, some with virtualmin and some manually and

I'm trying to use virtual domains and I'm suffering a disconnect. I have two domains - foo.com and bar.com. On the filesystem, they are located at /var/mail/foo.com/ and /var/mail/bar.com/. Users are located at /var/mail/foo.com/john/, /var/mail/bar.com/jane/, etc. There are two password files with <user>:<scheme><password> entries. The scheme is {PLAIN}. They are