Server :: Support Sasl For Postfix?
Aug 17, 2010i used yum install postfix, but i don't know it's support sasl? how to check it?
View 3 Repliesi used yum install postfix, but i don't know it's support sasl? how to check it?
View 3 RepliesI'm trying tom compile and install postfix with SASL support, but i have a error messeage when install:
#make makefiles CCARGS="-DUSE_SASL_AUTH -DUSE_CYRUS_SASL -I/usr/local/sasl2/include/sasl" AUXLIBS="-L/usr/local/sasl2/lib -lsasl2"
...
#make install
[code]....
I have Postfix up and working perfect. It receives and sends email fine with no TLS and SASL but I installed Dovecot and then generated some self signed certificates using 'openssl' and for some reason I can't send from my IMAP server. I get this in my logs:
Code:
Mar 3 11:20:45 mail dovecot: imap-login: Login: user=<carlos>, method=PLAIN, rip=10.1.1.204, lip=192.168.0.200, TLS
Mar 3 11:21:20 mail postfix/smtpd[1386]: connect from tuna.mydomain.tld[10.1.1.204]
[Code].....
Am unable to send mail from Outlook to my Postfix SMTP server.
Am getting the following in the /var/log/maillog.
Code:
Think I've pretty much followed the instructions correctly here.
[url]
Also, I looked for the PID of the smtpd and did a strace on it.
Code:
Code:
However, when I looked at the permission of this file, it should be accessible by everyone.
Code:
I have an issue where postfix is setup to use dovecot auth and as far as I know it works, if i login using telnet to the mail server i can authorize myself y providing the base64 encoded user & password. so if i can login, why cant my email clients. have tried thunderbird and evolution. this is the mail.log relavant entries for sucessful login via telnet
[Code]...
Login by pop or imap works flawlessly that what i dont get. From what i see it SHOULD be working. It it changes things, im using postfixadmin, postfix, dovecot. passwords and info stored in mysql tables. passwords are md5 encrypted. I thought that may be the issue, but that dosnt make sence.
I'm trying to expand my Courier+MySQL+Postfix+PostfixAdmin server to use SASL logins on Postfix so I can relay on my server. After following several guides I still can't get it to work: Postfix logs show the user transcript and end with "Authentication failure" but it does not tell me what told it that the login failed. The messages log show this:
Feb 19 22:48:55 sportlaan-server saslauthd[7254]: do_auth : auth failure: [user=berend] [service=smtp] [realm=mydomain.com] [mech=pam] [reason=PAM auth error] Which I don't get because I don't think it should be using PAM... I think...
The setup is similar to this one: http://www.howtoforge.org/virtual_users_postfix_courier_mailscanner_clamav_centos_p6
My SASL config has this in it:
/usr/lib/sasl2/smtpd.conf
pwcheck_method: saslauthd
log_level: 3
authdaemond_path: /var/spool/authdaemon/socket
mech_list: plain login
I'm using postfix with unix accounts for a while now and I just realized today that SASL authentication, instead of working only with the USERNAME, it also works if the username is followed by ANYDOMAIN.COM
So, let's say I have the following UNIX users: tim, mike, john. If I set the Outgoing Username:[URL]..(where whatever.com can be any name you can think of) IT WORKS, even though it shouldn't, it should only work with tim, mike and john without any domain name. Does anyone know what might cause this and what's the workaround to this problem?
distro = debian 5
when i tried to send to other domain, i will get "Relay access denied"
below are my configs
main.cf
Code:
# postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
[Code].....
I am running the following on CentOS 5.5 (Final)
dovecot 1.0.7
saslauthd 2.1.22
When I send an email via TLS I see the following log entries.
Code:
Oct 14 11:53:06 ns2 postfix/smtpd[11372]: connect from unknown[172.16.1.159]
Oct 14 11:53:06 ns2 postfix/smtpd[11372]: setting up TLS connection from unknown[172.16.1.159]
[Code]....
What I'm really curious about is there is an intial TLS connection with a 256 bit cipher, but then.. The last entry states "sasl_method=PLAIN" - so surely this is not encrypted? Or am I misunderstanding how it works?
I am re setting up a server of mine running red hat enterprise Linux server 6 and I had all of this working befor but for some reason I had troubles getting sasl to work and now when I login my smtp server I get an error stating that my username or password is incorrect though I am sure I am entering both correctly. Would anyone know what could be happening? I have been spending days on the web looking for the solution and only went from sasl not working when started as a service to this. For some reason I can't use Pam with saslauthd and had to use shadow instead of which from what I hear I get to use better methods of secure authentication with smtp
View 2 Replies View RelatedI was reading over and checking the How to section on the Wiki for Postfix TLS / SASL. I followed it completely and everything seems to be working fine however I am confused about the following section:
smtpd_tls_security_level = may
smtpd_tls_key_file = /etc/pki/tls/private/mail.example.com.key
smtpd_tls_cert_file = /etc/pki/tls/certs/mail.example.com.cert[code].....
We have CentOS 5.3 and are using sendmail for outbound emails. We are trying to switch over to authsmtp service. Authsmtp requires sendmail built with SASL suport.
How do I find out if my sendmail has been built with SASL support? If it is not, is it easy to build it with SASL support?
I installed webmin + postfix + dovecot + sasl2-bin to get a webserver running. I have fixed all the problems, but there is still one. I am totally new to sasl, so I am sorry if I made a stupid mistake.
[Code]....
Thunderbird gives the following error when trying to send mail: Sending of message failed. The message could not be sent because the connection to the SMTP server mail.virovene.org was lost in the middle of the transaction. Try again later or contact your network administrator. mail.err Apr 28 23:33:18 virovene postfix/smtpd[6264]: fatal: no SASL authentication mechanisms
I'm getting relay access denied to an email outside of my domain. It seems the passwords are authenticating because I'm not getting invalid password prompts.
### BEGIN POSTFIX CONF ###
# postconf -n
alias_maps = hash:/etc/aliases
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
mailbox_size_limit = 0
[Code].....
I for some reason can't get Cyrus-sasl to work completely. I have to manually start it via saslauthd -a show if I let it start up itself or do a service saslauthd start or restart testsaslauthd will fail. I need help getting this fixed. I tried setting /etc/sysconfig/saslauthd to shadow instead of Pam but still no luck. Also when I try to login my postfix server I get an error stating that my username or password is incorrect even though it is right and I can receive mail from dovecot.
View 2 Replies View RelatedSlackware 13 64 - full installation
Postfix from slackbuilds dot org
Dovecot from same
has anyone recompiled Postfix using the Slackbuild script, modifying the script to include support for Cyrus-SASL, OpenLDAP, and MySQL in the build, while retaining Dovecot SASL and TLS? If so I would appreciate it if they could post the CCARGS and AUXLIBS commands. I am having some difficulty getting this working.
I'm running a server with Ubuntu 10.04 and I have installed postfix and courier. The server can recieve mail and I can fetch them using POP, but when I try to send mail it doesn't work. Postfix itself can send email if i telnet from localhost and I am using my ISP as a relay because they block port 25. I'm using outlook 2007 on my client computer and it just says that the server rejects the login attempt and tells me to check my username and password. Postfix listens on port 12 as well because the client connection also has outgoing on port 25 blocked. I have tried to use telnet to connect to the server, and I can connect. This is what I get:
[Code]....
Now what? I've tried searching for the answer but all I can come up with is AUTH PLAIN or AUTH LOGIN, but I don't know what to type after that.
I have searched through piles of postfix and sendmail documentation but I'm not sure of the terminology to describe what I want to do so I'm never sure what solutions are workable. Null client, relay hosts. What I have already is a RHEL postfix server which sends and receives email. What I want to do is add a second postfix server to the network. The second server should accept only ssl smtp mail and forward it on to the main postfix server. Users shouldn't use it for normal internal sending/receiving. It's only to allow me to support ssl smtp from people working out of the office without messing about with the main postfix server. I thought a Null Client sounded likely but I don't think it will accept mail. Is it a relay host I'm trying to configure? Any pointers on configuring something to just accept secure smtp and forward?
View 1 Replies View RelatedI have been faithfully following the postfix/sasl/etc install docs from [URL] and seem to have hit a minor snag with SASL authentication for SMTP. KMail cryptically leaves me with a generic auth fail notice and tailing the mail logs gives me
[Code]...
Pam-mysql can not connect to the database and below are my configurations.
saslfinger -s Output:
root@mailbackup:/# saslfinger -s
saslfinger - postfix Cyrus sasl configuration Tue May 10 10:12:10 EAT 2011
version: 1.0.2
mode: server-side SMTP AUTH
-- basics --
Postfix: 2.7.2
System: Slackware 13.1.0
-- smtpd is linked to --libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x00007f74ebfb7000)
-- active SMTP AUTH and TLS parameters for smtpd --
-- listing of /usr/lib64/sasl2 --
-- listing of /usr/local/lib/sasl2 --
-- content of /usr/lib64/sasl2/smtpd.conf --
-- content of /usr/local/lib/sasl2/smtpd.conf --
-- active services in /etc/postfix/master.cf --
-- mechanisms on localhost --
I followed the Wiki guide for configuring my Postfix server for SASL / TLS. I don't get any errors and I assume it's working but when I try and test SASL (saslauthd), I don't get the response noted according to the Wiki and I don't understand why.
View 3 Replies View RelatedI am having some trouble with Cyrus SASL and OpenLDAP. I tried to configure OpenLDAP using SASL for all conection but I cannot map the SASL-DN to OpenLDAP's DN. Below is my configuration file, slapd.conf
[code]...
After I finished the configuration, I try to use ldapsearch tool to verify, but I cannot:
[code]...
I installed cyrus-sasl 2.1
How to deal with?
I checked relay system using IP address it working gr8, but I want to implement user based authorization in relay server. but no idea where to make changes in sendmail.mc.. and my outlook asking for password again and again..whats role of openssl in user based authentication ?
View 1 Replies View Relatedis there any HOWTO for configuring Webmin Postfix server with multiple postfix virtual hosts? Seems to be a tough challenge to set it up without any easy manual..
View 1 Replies View Relatedso i set out to change the default smtp port the server uses because my ISP blocks port 25 and i need the email to work in outlook. this morning i could receive email, but not send it. so i did some research and thought that i needed to edit the master.cf file in /etc/postfix/ by commenting out this line: smtp inet n - n - - smtpd -oand replace it with587 inet n - n - - smtpd (587 being the port i want to use)somewhere along the lines postfix server stopped running and now i cannot get it to start.if i try using SSH it crashes immediately and if i restart it in simple control panel nothing happens
View 7 Replies View RelatedI recently moved over user from an old box running postfix(v 2.0.16) over to rhel 6 running postfix (v mail_version = 2.6.6). ive tried to make sure all the files are of correct permissions and that the main.cf file is configured corectly. However there is something wrong as when i run postfix: service postfix server i get no error but when checking the status:service postfix status i get: master dead but pid file exists Looking into /var/log/mailog i find this line being the issue:
Feb 25 16:24:39 puny1 postfix/master[3517]: fatal: fifo_listen: create fifo public/pickup: Permission denied
I gather this is a file permission issue and ive tried to make sure the public folder in /var/spool/postfix is correctly set but still no avail.
I have currently configured Postfix as an SMTP server. I would preferably not use a domain name in my email address, like so: myname@[1.2.3.4]
I'm currently testing to see how other mail servers handle this kind of address. When I sent a mail with one one of my gmail accounts, I see that the mail gets rejected due to bad syntax.
It seems as though Google is giving me a RCPT TO address like so: myname@1.2.3.4 However, the postfix server rejects this address with the following error:
501 5.1.3 Bad recipient address syntax
To my best knowledge the only way to have an IP address inside an email address with to write it as a domain literal [1.2.3.4].
My question: how to configure postfix to accept myname@1.2.3.4 as well?
I have put both [1.2.3.4] and 1.2.3.4 in "mydestination" and 1.2.3.4 in "virtual_alias_domains".
It doesn't seem to work so far though.
I am setting up a cluster of servers which use Centos Directory Server for control of logins, etc and kerberos for authentication. The basic setup is working fine, I have been able to manually create accounts using the directory console and these accounts seem to work. Now what I want to do is automate the process of creating new accounts. I am writing a perl script which can be run by one of the server administrators, they supply a small number of arguments and it should create a new user in the directory server, and also create a principal in the kerberos.
I want them to be able to do this using their logged-in kerberos credentials, i.e., without having to enter and re-enter their passwords. My first attempt was to use perl modules Net::LDAP and Authen::SASL. I could not get this working so fell back to using ldap command line tools, but even these I cannot seem to get working! When using mozldap tools, as specified in the admin manual, I get the following:
$ /usr/lib64/mozldap/ldapmodify -h ldaphost.mycompany.com -D uid=eharmic,ou=mydept,dc=mycompany -o mech=GSSAPI -o authid=eharmic < ../ldapmod.txt
Bind Error: Invalid credentials
Bind Error: additional info: SASL(-14): authorization failure:
Using openldap tools I strike exactly the same problem:
$ ldapmodify -Y GSSAPI -H LDAP://ldaphost.mycompany.com -D uid=eharmic,ou=mydept,dc=mycompany -U eharmic < ../ldapmod.txt
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
additional info: SASL(-14): authorization failure:
I believe I have set up the mapping correctly:
dn: cn=MyMapping,cn=mapping,cn=sasl,cn=config
objectClass: top
objectClass: nsSaslMapping
cn: MyMapping
nsSaslMapRegexString: ^(.+)@MYCOMPANY.COM
nsSaslMapBaseDNTemplate: ou=mydept,dc=mycompany
nsSaslMapFilterTemplate: (uid=1)
It must be getting reasonably far because after doing the above I can see the LDAP service ticket in my "klist" output.
I'm trying to find out when QME2572 (Qlogic) card became support by the kernel. We have a RHEL 5.1 system that is moving to new hardware, however the kernel at this release doesn't support the new hardware, due to the Qlogic card change. I tired the Redhat KB and Bugzilla. Is there a Kernel change list etc I can search. Never really played around with the kernel too much so I'm just after some pointers for looking up this information. Offically its not supported until Redhat 5.3, I'm trying trying to research kernel info so I can tell the customer they have to upgrade.
View 3 Replies View Related