search for: sasl_readme

...given the solid history of Postfix and Dovecot, I must be the problem! My problem statement is simply, "it should be working", but doesn't, and I don't get any announcement of "auth" when testing connections to Postfix as per directions here: http://www.postfix.org/SASL_README.html#server_test At least I haven't broken the normal functionality! I'm building a new server on the latest Fedora Core (16), but it's lacking in some hardware and won't be ready for a while, so I'm working with FC 14, running Postfix 2.5.6, and Dovecot 1.2.8. It uses the &qu...

...words of remote systems lying around on my local filesystem. It doesn't really ease my mind that the file is readable by root only, this doesn't help if my laptop's harddisk gets mounted elsewhere. Are there alternatives or better ways to do SMTP authentication? http://www.postfix.org/SASL_README.html#server_cyrus_comm says: > saslauthd can verify the SMTP client credentials by using them to log into an IMAP server So i have my mutt-client which is logged in to the remote Dovecot IMAP. Mutt uses the local MTA to send the mail. Is there some way to tell the local postfix or a local dovec...

Attempting to setup smtpd auth for Postfix using the Dovecot authorization unix socket. Some info is at: http://www.postfix.org/SASL_README.html To enable operation when Postfix is chrooted, a method from the reference above is to locate the socket at: /var/spool/postfix/private/auth To do this, I have this configuration in dovecot.conf: # listener sockets will be created by Dovecot's master process using the # settings given in...

...he local ISP server.. The problem After much searching I have not found an answer to my question. I would like the user to authenticate to be able to "send" email "through" the server.. OpenBSD uses bsdauth by default in Dovecot. After reading the Postfix http://www.postfix.org/SASL_README.html and the Dovecot Wiki http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL I have tried multiple configurations but I can't seem to get this to work.. It may be something very simple that I am missing.. All users on the Server have accounts in /etc/passwd (just no shell) Postfix - main.cf...

...lready exist in main.cf and in that case has to be extended postfix can verify login/passwords via sasl but it does not store these credentials, so you need to install saslauthd and add user/pass there or use a dovecot instance that already authenticates users for pop/imap. http://www.postfix.org/SASL_README.html https://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL Best regards Gerald > Am 09.01.2019 um 10:15 schrieb Jacky <jacky at jesstech.com>: > > Hi, > > Anyone know how to enable this SMTP AUTH feature with Postfix? > > Regards, > > Jacky > > > On...

...c04c8d9822e711e1f postfix-2.3-20051208-dovecot.patch.gz -rw-r--r-- 1 rob0 console 7287 2005-12-09 17:09 postfix-2.3-20051208-dovecot.patch.gz The original patch is here: http://dovecot.org/patches/postfix/postfix-2.2.1-dovecot-auth.patch Instructions are here (and don't forget the Postfix SASL_README too): http://dovecot.org/patches/postfix/README NB: Although my own postfix-2.3-20051208 snapshot compiled with the patch and is running, it is not tested at all. I'll try with AUTH later and see if it's working. I will not be able to test with LMTP. IIUC how this patch affects LMTP, i...

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://dovecot.org/pipermail/dovecot/attachments/20051221/643bbd8a/attachment-0001.pgp

Hi all, I just maked $SUBJECT to run. The main problem was, that in Dovecot are by default enabled only plain digest-md5 and cram-md5 authentication mechanisms. While MS Outlook knows only "LOGIN" mechanism. So, Outlook users wasn't able to use SMTP AUTH. The solution is to change a line in dovecot.conf: mechanisms = plain digest-md5 cram-md5 to: mechanisms = plain digest-md5

...cnZ== 235 Authentication successful But my problem is now that i dont know how to configure dovecot that i can login to my system with squirrelmail or something else? Dovecot should use the user added in sasldb2. I read this Howto but can find a solution for this: http://postfix.hostingzero.com/SASL_README.html I hope someone here can help me? Thx a lot Cu kami

Hi, I have compiled dovecot 1.0 and postfix 2.3 with dovecot support. here are my config sections dovecot in auth default section ---------- client { user = postfix group = postfix /path = /var/run/dovecot/auth-client mode = 0660 } postfix main.cf --------------------- smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sender_restrictions =

FreeBSD 6.1 STABLE Postfix-2.4-20061006 Dovecot-1.0.rc7 I am using 'saslauthd -a sasldb -c' for authentication with Postfix. Since Dovecot and Postfix are using the same users and passwords, I was wondering if it would be possible to use this mechanism with Dovecot also. -- Gerard "There is nothing wrong with making love with the light on. Just make sure the car door is

I'm trying to figure out if this is a bug... I'm running Postfix with Dovecot Authentication and have Amavisd-new as the front end. I fought with the install and in particular being able to send mail.... Auth failed. Hours of looking through all the config files yielded nothing... so I started Googling about. I finally found a comment at the bottom of a blog to check permissions on:

I am a student and am trying to get a mail server setup for a project. I have all of the Postfix configuration taken care of, but I am confused by the way that authentication works with Dovecot in the mix. As a user of the system, am I supposed to authenticate myself to Postfix, Dovecot, both individually, or both together? My Postfix users are stored in a PostgreSQL database, should Dovecot also

...smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = broken_sasl_auth_clients = yes 10.11.100.230 is our dovecot server. Please look at the attached doveconf.log to see my auth service configuration. I did the configuration according to the postfix SASL README. http://www.postfix.org/SASL_README.html#server_dovecot I tested the setup and everything worked fine but after 2 days i noticed these error messages in my mail.log: dovecot: auth: Error: BUG: Authentication client gave a PID 7542 of existing connection and also these messages from postfix: SASL LOGIN authentication failed: Conne...

Once again I have updated Timo's auth patch for Postfix 2.2.1 to work with a 2.3 snapshot. It applied cleanly and compiled and is running for me, but is not really tested. This is Timo's code, not mine. All I did was manually edit in the rejects from the old patch. Find it here if you're interested: http://www.nodns4.us/postfix-2.3-20051121-dovecot-auth.patch.gz md5sum:

Hi all, Apologies for the somewhat off-topic questions - I'm trying to get my head around SASL, and what it is/does. I can see that a (SMTP, IMAP etc) server can offer various authentication methods, which are pre-defined and which the client can choose from. SASL then seems to define how those work. But dovecot and cyrus-sasl both seem to offer a client-server interface, usable by eg

Sorry about the previous post, I see the subject had a typo. So here's the correct one :) Does anyone know how to configure Postfix to use SMTP authentication on a relay host? i.e. I have a Linux server, running PostFix on an ADSL line with a dynamic IP. Thus I can't just send out emails from this server but need to relay it via our ISP's SMTP server, which is very unreliable. Now

Hi all, I seem to recall mention of SASL client support either being added, but can't remember for sure. The wiki says nothing about Client support (now, or in the future)... http://wiki2.dovecot.org/Sasl So - is there support for it now? If not, is it planned for anytime soon? Thanks, -- Best regards, Charles

Hi, I'm trying to setup a new mail server where postfix 2.3-20060405 would use Dovecot's SASL and users located in LDAP. It's with dovecot-1.0-beta5. On the postfix side, I followed the SASL_README and have the following in main.cf: smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes On the dovecot side I have the following related to auth: auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain digest-md5 cram-md...

I'm trying to use Dovecot SASL with postfix 2.3.3 and when trying to send mail I get the debug output below. I don't know enough about whats going on to know where the problem is but something clearly is not right. I would send the configurations for postfix and dovecot except they are clearly talking to each other so I kinda doubt its a configuration issue. The machine can afford to be