telnet to postfix (localhost port 25) hangs
Someone
Mandrake 9.2 machine, along with cyrus-sasl (cyrus-sasl-2.1.15-4mdk).
When I try to telnet to localhost on port 25, the session hangs. Here
is what I see on the screen:
Trying 127.0.0.1...
Connected to localhost (127.0.0.1).
Escape character is '^]'.
I never see the welcome message. It just sits there until I hit the
escape character and quit the telnet session. I'm using the default
main.cf file provided with the postfix rpm installation file that came
with my Mandrake cd. This has worked for me before, so I don't
understand why it is not working now. I would appreciate any help you
can give. Thank you.
Sean Rowe
Andreas Paasch
I've had the exact same problem.
After installing the various encryption libraries and running saslauthd and
having postfix setup to use it, I encountered the exact same problem.
However, finally found the solution.
What did the trick for me here were my mynetworks, the ones postfix had to
listen on.
I initially just had default 192.168.1.0/8 .. which didn't work.
I then changed that to my exact local ip being 192.168.1.2 and then it
worked flawlessly.
I have inet_interfaces = localhost so it seems to be a combination of these
two that causes the problem.
I must have another wrong setting, but for outgoing mail only, this will do
for me.
BTW, I'm on Mandrake 9.2. as well.
Maybe this is your solution too.
HTH,
/Andreas
--
Registeret Linux user #292411
Someone
Thanks for the information, I'll try that. I've gotten it to unhang
itself (I'm thinking that it never shut down properly from the command
line, but seems to shut down ok when I do it from mandrake control
center?)
I made some changes based on the recomendations of a tuturial I found
at http://postfix.state-of-mind.de/patrick.koetter/smtpauth, that said
to add these lines:
#--------------------
# SASL SUPPORT FOR CLIENTS
# The following options set parameters needed by Postfix to enable
# Cyrus-SASL support for authentication of mail clients.
#
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain = $myhostname
broken_sasl_auth_clients = yes
...
smtpd_recipient_restrictions =
permit_sasl_authenticated,
permit_mynetworks,
check_relay_domains
#---------------------
The connection is reset now when I telnet to port 25. Not hanging
anymore, but what do you have to do to get this thing working?? I'm
going bald here....Any help is appreciated.
sean
Andreas Paasch
First of all, MCC is to long a way to go, use CommandLIne.
I have followed the same setup as you, and my system works as planned,
however, I did a seperate install of the libraries needed for
authentication, got them from www.rpmfind.net.
I assume that might be your problem, but I could be mistaken.
Make sure to get sasl2 libraries, else it won't work well on ML 9.2.
Secondly, restarting, stopping or reloading postfix is easily done as root
from commandline in ML 9.2, just issue either
service postfix restart
service postfix stop/start
service postfix reload
a lot easier ... ;-)
I don't recall the command to have saslauthd tell you which libraries are
installed, but man saslauthd might tell you that.
That's a starter ...
Someone
rpmfind.net was the way to go. I downloaded and installed each of the
libraries for sasl2, and now it works fine. Thanks a lot for the
suggestions!
sean
Andreas Paasch
Glad I could help.
Someone
> >
> > rpmfind.net was the way to go. I downloaded and installed each of the
> > libraries for sasl2, and now it works fine. Thanks a lot for the
> > suggestions!
> >
> > sean
>
> Glad I could help.
>
> /Andreas
I spoke too soon. One problem vanishes and another reapears. I can
telnet to localhost 25 no problem. I can run the command 'printf
'test@localhost\0test@localhost\0testpass' | mmencode' to get the
character string to pass to 'auth plain <>', and that works ok (though
I would like to not have to use @localhost!!). I can't get outlook to
send a message, though! Here's the error that outlook reports:
Your server has unexpectedly terminated the connection. Possible
causes for this include server problems, network problems, or a long
period of inactivity. Account: '192.168.0.3', Server: '192.168.0.3',
Protocol: SMTP, Port: 25, Secure(SSL): No, Error Number: 0x800CCC0F
I'm confused on the Secure(SSL) portion of the error message. I
didn't think I had ssl configured for smtp; i even tried to enable ssl
in outlook, but it didn't help. I tried to follow the directions in
the tutorial I mentioned above, but it seems a little outdated. If
you don't mind helping a little bit more, I could sure use it.
Thanks.
sean
Andreas Paasch
Two things.
First of all, it clearly reads "Secure(SSL): No" - notice NO, so SSL is not
used. If postfix is setup to use SSL, then your client needs SSL too, else
you won't get a connection.
Secondly, you need to have the directive for broken clients set to yes in
main.cf and you need the libraries for plain and login into your
authentication.
Reload postfix and try again.
I am far from a guru on Postfix, still have my own problems with it, however
I'll give a hand as far as I can based on what I've read around on the
issue Postfix.
Someone
I have the broken clients set to yes, and i have the libraries for
plain and login. Thanks for your help, and I understand that you're
no guru. I've been looking all over the place to understand this
better, and I've almost convinced myself to just build the thing from
the source code.
sean
Andreas Paasch
Well, as I don't use postfix in connection with a pop3/imap server, I can't
help you any further.
However, one thing crosses my mind, you do have a POP-server installed and
active in order for Outlook clients to use the mailserver, right?
Someone
Yes, I do have a pop3/imap server. The client can log in fine to
check their messages...it's just when they want to send a message that
they get the error above. Thanks for you help in getting me this far.
I really appreciate it.
sean
Andreas Paasch
Ok, then let me see if I might give some ideas on to you.
As the problem arises when clients want to sent mail, then it's related to
smtpd, not smtp.
That's where to look.
Then it's something about authentication method, eventually pop before smtp.
Canonical maybe blocking?
Some access list blocking ?
A firewall blocking ?