Slackware 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.
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 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 RelatedMy problem is to get postfix working with a smarthost, to send mails from home with dynamic IP, and which needs authentication. I did exactly the same with Slackware 12.2 (postfix 2.6.2) and it worked. Now I tried to do with 2.6.2 (actual running version is 2.7.0 with the same problem) on Slackware 13 64bit. Following error message occurs around every minute in the maillog:
[code]...
I am attempting to enable secure authentication on my homebrew AWS based mail server, by following the very excellent flurdy how-to.However I think the repositories I am attempting to use do not include this software.Oddly enough, an aptitude search finds the packages I want, however even if I copy-paste the name of the software into the install version of the command it turns up nothing.
Code:
root@cloud1:~# aptitude search sasl2-bin
i sasl2-bin - Cyrus SASL - administration programs for SASL users
[code]....
I took to yast to install ldap. I creating the CA cert, server key and server cert and specified them during the yast ldap server dialogs.
The firewall is open for ldap.
I also went through yast's ldap client ... though I didn't exactly see to anything (presuably it wrote up a configuration file somewhere).
However when trying use the basic ldap tools, like ldapwhoami. Well it doesn't connect and gives me the above error. Of coure the ldap db is unpopulated as yet, so it probably is not able to say who am at all. But ldapadd doesn't work either.
It seems to point to my SSL usage not being correct .. so I'm trying to double check that now.
I've managed to get my Fedora box authenticate to AD with NSS_LDAP module with SSL working. I would like to bring this authentication to the next step by using SASL /GSSAPI, however I find very little / no documentation exist on this topic? I was wondering does anyone know where I can get the documentation on how to setup NSS_LDAP talking to AD with SASL/GSSAPI?
View 3 Replies View RelatedI 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 used yum install postfix, but i don't know it's support sasl? how to check it?
View 3 Replies View RelatedI'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 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 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'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].....
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'm running SUSE linux Server version 11. I want to configure mail server with postfix & cyrus-imap. For that, i have read many documents in Internet by i met issues. I'm running DNS in this server & it's ok Now I cannont send mail through command line.
[Code]....
I am experiencing a Cyrus-SASL v2.1.23 and PAM authentication issue. I installed linux PAM 1.1.3 on slackware linux 13.1 x86 64bit. On installing cyrus, i am unable to find the PAM authentiaction mechanism.
root@xxxxx:/usr/local/src/cyrus-sasl-2.1.23# saslauthd -v
saslauthd 2.1.23
authentication mechanisms: getpwent rimap shadow ldap
[code]....
How can i get the PAM authentication mechanism runnning .
I 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]...
I installed RHEL 5.5 with Postfix & openldap. POSTFIX version-2.3.3 openldap-server-2.3.43-12.el5 How to combine ldap with postfix for authentication? How to compile postfix with LDAP and where is the source
View 1 Replies View RelatedFor the last couple of weeks, I can't seem to reach [URL]... Browser just times out. Here's a traceroute: [URL]...
View 10 Replies View RelatedI am going to try out a tiling wm and I have narrowed my search down to scrotwm and dwm. I installed scrotwm from slackbuilds.org but it did not show up as a selection when I ran xwmconfig? Any ideas as to why? So then I went install dwm from slackbuilds.org but saw there was only a build script for slackware 13 as opposed to 13.1 which is what I am running. So two questions for dwm, one why is there no slackbuild for 13.1, and two when I tried to use the slackbuild for 13 this also didn't show up under xwmconfig, any thoughts?
View 4 Replies View RelatedAs always, very impressive effort from Slackbuilds.org to get slackbuild scripts updated for 13.1. Thanks to all who maintain these scripts. One which does not seem to have made it to 13.1 so far is a build script for WINE. Anybody know whether this is beacuse of some problem ? Or just an oversight ? The 13.0 script is there - might be OK to just use this with 13.1 ?
View 9 Replies View RelatedGetting the hang of diff and patch, to a small extent...However, I couldn't get the slack-desc to print anything useful when running installpkg. Always had trouble with the slack-desc files.
[code].....
i keep getting this error during gecko-mediaplayer build running 1337 stable up to date. lang.sh has en us utf8 enabled, (it didn't work with en US either.
[Code]...