similar to: SASL Support

I am looking for a way for sendmail to ALLOW auth by IP and not user name (its a closed network) or even SKIP invalid auth ? Is that even possible ? Jerry

Centos 5.x again... Is there a way to limit port access on a per-user basis? My practical goal is to limit, who is allowed to use SMTP AUTH in Sendmail. Any possible solutions appreciated... Obviously, limiting by ip will not work, since the very purpose of SMTP AUTH is to enable mail relaying for trusted users from *anywhere*. - Jussi -- Jussi Hirvi * Green Spot Topeliuksenkatu 15 C * 00250

I was playing with SASL authentication a bit today and I wasn't able to get libvirt to authenticate against PAM (or anything else except the sasldb, although I didn't try Kerberos). Does anybody know off the top of their head what mechanisms/password check options work? I'm trying to figure out if I'm attempting the impossible. Dave

I'm trying to set up imap resources in kmail, and from the logs it looks as though I have to set up sasldb. I've found some documentation, but it seems that I need to know whether I'm using sasl or sasl2. How can I tell? I seem to have several packages installed that are returned with I query yum, and both versions get mentions. Anne

Hello List. I'm cross posting this from svn-users, as I'm not sure whether this is an CentOS specific issue. Perhaps someone here has an idea of what's going on? ----------------------------- I got a fresh install of CentOS 5.2 x32, svnserve, version 1.5.5 (r34862), here is my svnserve.conf file [general] anon-access = none auth-access = write realm = isf [sasl] use-sasl = true

Code which supports cyrus SASL library (src/auth/mech-cyrus-sasl2.c) is broken. Following is the workaround patch for Dovecot Rel 0.99.11, and it worked fine on FreeBSD 4.10 BOX. It will not work with current development version. Application for that version might not be so difficult. Recently I found the CVS log which appeals that cyrus SASL support is discontinued. It's very sad. Regards

I have mail server on CentOS 4.1. Sasl authorization for SMTP is enabled. Thunderbird sends mail, but Outlook get an error 554, Relay access denied, error number 0x800CCC79 Outlook has a login and password for SMTP enabled. It is strange, because there is no any sign of authorize in maillog when Outlook try to send mail. -- ____________________________________________________________________ D

Hi, so sendmail can use only cyrus-sasl ? ok, thank you >Mario Pavlov wrote: >> I was wondering if I can make sendmail use dovecot's SASL >> implementation...maybe I should somehow compile it against dovecot's >> SASL ? My idea is to make sendmail and dovecot authenticate against >> one central user/password repository. Is this possible ? >>

Hi list I searched the net, but could not find something related. Is it possible to export the client socket to sendmail for smtp auth? What would be the sendmail.mc configuration for this? #client { # The client socket is generally safe to export to everyone. Typical use # is to export it to your SMTP server so it can do SMTP AUTH lookups # using it. #path =

Hi, I was wondering if I can make sendmail use dovecot's SASL implementation...maybe I should somehow compile it against dovecot's SASL ? My idea is to make sendmail and dovecot authenticate against one central user/password repository. Is this possible ? thank you. P.S. I want to use virtual users

Hello list. I have a mail server where I use Postfix+SASL. Everything works fine. Sending emails when using client (Outlook, Thunderbird or anything else) require authorization. It is OK. But on the same server there is a Squirrelmail which sends emails as a localhost. To send email in this way there is no any authorization. Besides one preson use PINE on the server... How to do that

first, thx for --with-storages=maildir second, there is a problem when user exceed their quota < status INBOX (messages) > NO Internal error [2003-05-06 15:35:56] in logfile: imap(user): Can't create directory /var/mail/user/.INBOX: Disk quota exceeded 'user' is not able to get list of messages and delete some of them :( third, in logfile: imap(user2): maildir flags

Hello list. I have a question for fail2ban for bad logins on sasl. I use sasl, sendmail and cyrus-imapd. In jail.conf I use the following syntax: [sasl-iptables] enabled = true filter = sasl backend = polling action = iptables[name=sasl, port=smtp, protocol=tcp] sendmail-whois[name=sasl, dest=my at email] logpath = /var/log/maillog maxretry = 6 and the following filter:

I've been trying to get smtp auth set up for days. All my sendmail and sasl2 stuff seems to be proper, but the user can't use the system on port 587, which is where I require authorization. Now I see where messages are in my maillog of the type: auth: pam_unix(dovecot:auth) : authentication failure ........ Why is dovecot involved in my smtp processes and how do I fix this. I've

I have setup my machine to relay through smtp.gmail.com installed cyrus-sasl-md5 cyrus-sasl-plain Added to access: AuthInfo:smtp.gmail.com "U:smmsp" "I:my accont" "P:my pass" "M:PLAIN" AuthInfo:smtp.gmail.com:587 "U:smmsp" "I:my account" "P:my pass" "M:PLAIN" Added to sendmail.mc the

Hi List, I just updated an old sendmail installation to a modern postfix/dovecot system with mysql backend. Everything works fine but SMTP-AUTH fails with some clients. The problem is, that with PLAIN (old) clients send the base64 coded form: USERNAME\0USERNAME\0PASSWORD which, as i understand dovecot interprets as MASTERUSER\0USERNAME\PASSWORD. New clients send \0USERNAME\0PASSWORD which works

Hello all, I've been googling my brains out since yesterday looking for up-to-date information on this matter, and have found information that is anywhere from 15 to 5 years old. I'd really like some information that much more up to date on the subject. Specifically configuring Sendmail SMTP authentication (_no smart host stuff_). I've got Sendmail 8.14 installed on a CentOS 7.3

Hello and good evening. Sorry for responding so late, it is midsummer and i spend as much time as possible on the outside (bicycle, mostly). (Just one more day, then 10 degrees colder!!) I Cc: Wietse Venema, because i quote a message of him. (this is "set quote-add-cc" here.) Aki Tuomi wrote in <84881193.5398.1597934431687 at appsuite-dev-gw2.open-xchange.com>: The dovecot

Hello. I am not subscribed and new here, so first of all i want to thank you for dovecot. I personally do not use it in "production" (yet), but it is my sole point of interaction for testing the little MUA i maintain for quite some years. I also have used its code for affirmation purposes. (Interesting that OAUTHBEARER treats hostname and port as optional. I currently do

Hi, I'm trying to configure a new server with dovecot 2.0 and postfix 2.6.6. My previous servers have all been dovecot 1.x. Trying to port over my previous configurations has been a real headache. Currently, I'm getting the following errors when trying to connect with: openssl s_client -starttls smtp -connect localhost:25 Aug 21 19:08:46 localhost postfix/smtpd[26252]: connect from