HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Installation/Configuration (http://www.howtoforge.com/forums/forumdisplay.php?f=16)
-   -   After Install: Mail not working and FTP strange (http://www.howtoforge.com/forums/showthread.php?t=2361)

Raffnix 2nd February 2006 22:42

After Install: Mail not working and FTP strange
 
Hello,

Today I installed ISPconfig on a new Server (Debian Sarge Basic Image, then "Perfect Install" from HowTo)
I kept the given Hostname (IP.provider.tld) and installation worked well

But after starting ISPconfig. I noticed, that in the Services overview FTP-Server was offline. Restarting didn't change anything and trying to restart on the shell returned:

proftpd restart
- warning: "ProFTPD" address/port (xx.xx.xx.xx:21) already in use by "Debian"


I ignored that and pre-configured my domains (9 Clients), which are currently still running on my old server.

Then I switched one of them (including MX) to the new server (www.mydomain.tld is working OK) an created an user (web7p1)
Maildir has been created and I can access the Mailbox with Outlook Express and Uebimail. But trying to send mail with either of them results with an error:

Code:

Feb  2 18:40:34 xx-xx-xx-xx courierpop3login: LOGIN, user=web7p1, ip=[::ffff:xx.xx.xx.xx]
Feb  2 18:40:35 xx-xx-xx-xx courierpop3login: LOGOUT, user=web7p1, ip=[::ffff:xx.xx.xx.xx], top=0, retr=0, time=1
Feb  2 18:41:57 xx-xx-xx-xx postfix/smtpd[2144]: connect from localhost[::1]
Feb  2 18:41:57 xx-xx-xx-xx postfix/smtpd[2144]: NOQUEUE: reject: RCPT from localhost[::1]: 550 <sender@somedomain.tld>: Recipient address rejected: User unknown in local recipient table; from=<web7p1@mydomain.tld> to=<sender@somedomain.tld> proto=SMTP helo=<UebiMiau>
Feb  2 18:41:57 xx-xx-xx-xx postfix/smtpd[2144]: lost connection after RCPT from localhost[::1]
Feb  2 18:41:57 xx-xx-xx-xx postfix/smtpd[2144]: disconnect from localhost[::1]
Feb  2 18:45:45 xx-xx-xx-xx postfix/smtpd[2226]: connect from myip[xx.xx.xx.xx]
Feb  2 18:45:45 xx-xx-xx-xx postfix/smtpd[2226]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
Feb  2 18:45:45 xx-xx-xx-xx postfix/smtpd[2226]: warning: myip[xx.xx.xx.xx]: SASL LOGIN authentication failed

On the other hand, connecting to the server with an FTP client works fine (despite of the first error)

If you can help me get my mail working and explain the ftp behaviour I would be glad :D

till 2nd February 2006 22:54

Quote:

Originally Posted by Raffnix
But after starting ISPconfig. I noticed, that in the Services overview FTP-Server was offline. Restarting didn't change anything and trying to restart on the shell returned:

proftpd restart
- warning: "ProFTPD" address/port (xx.xx.xx.xx:21) already in use by "Debian"

please have a look here:
http://www.howtoforge.com/forums/sho...ocketbindtight

The problem is that proftpd binds the port on all IP addresses with its default server and then cannot bind with the later defined virtual servers.

Raffnix 3rd February 2006 12:30

Well I added "SocketBindTight on" to proftpd.conf and rebooted, but that changed nothing: The message now reads:

proftpd stop
- warning: "ProFTPD" address/port (xx.xx.xx.xx:21) already in use by "FTP-Servername"
- SocketBindTight in effect, ignoring DefaultServer

and the FTP-Server-Status in ISPconfig is still "offline".

The FTP-Server is reachable by the configured user. Unfortunately the user is not restricted to his Web but able to browse the whole server.


Even worse is, that I'm still unable to send mail.

falko 3rd February 2006 13:17

Please post your /etc/proftpd.conf here.

Quote:

Originally Posted by Raffnix
Code:

Feb  2 18:45:45 xx-xx-xx-xx postfix/smtpd[2226]: connect from myip[xx.xx.xx.xx]
Feb  2 18:45:45 xx-xx-xx-xx postfix/smtpd[2226]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
Feb  2 18:45:45 xx-xx-xx-xx postfix/smtpd[2226]: warning: myip[xx.xx.xx.xx]: SASL LOGIN authentication failed


It seems as if saslauthd isn't running. Please run
Code:

/etc/init.d/saslauthd start

Raffnix 3rd February 2006 13:48

saslauthd is running (restarted it to be sure) but still sending is not possible. This is what uebimail tells me:

It was not possible to send this e-mail
SMTP Error: Recipient not accepted. Verify your relay rules


My proftpd.conf:

Code:

#
# /etc/proftpd.conf -- This is a basic ProFTPD configuration file.
# To really apply changes reload proftpd after modifications.
#

ServerName                      "Debian"
ServerType                      standalone
DeferWelcome                    off

MultilineRFC2228                on
DefaultServer                  on
ShowSymlinks                    on

TimeoutNoTransfer              600
TimeoutStalled                  600
TimeoutIdle                    1200

DisplayLogin                    welcome.msg
DisplayFirstChdir              .message
ListOptions                    "-l"

DenyFilter                      \*.*/

# Uncomment this if you are using NIS or LDAP to retrieve passwords:
#PersistentPasswd              off

# Uncomment this if you would use TLS module:
#TLSEngine                      on

# Uncomment this if you would use quota module:
#Quotas                        on

# Uncomment this if you would use ratio module:
#Ratios                        on

# Port 21 is the standard FTP port.
Port                            21

# To prevent DoS attacks, set the maximum number of child processes
# to 30.  If you need to allow more than 30 concurrent connections
# at once, simply increase this value.  Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd)
MaxInstances                    30

# Set the user and group that the server normally runs at.
User                            nobody
Group                          nogroup

# Umask 022 is a good standard umask to prevent new files and dirs
# (second parm) from being group and world writable.
Umask                          022  022
# Normally, we want files to be overwriteable.
AllowOverwrite                  on

# Delay engine reduces impact of the so-called Timing Attack described in
# http://security.lss.hr/index.php?page=details&ID=LSS-2004-10-02
# It is on by default.
#DelayEngine                    off

# A basic anonymous configuration, no upload directories.

# <Anonymous ~ftp>
#  User                                ftp
#  Group                              nogroup
#  # We want clients to be able to login with "anonymous" as well as "ftp"
#  UserAlias                  anonymous ftp
#  # Cosmetic changes, all files belongs to ftp user
#  DirFakeUser on ftp
#  DirFakeGroup on ftp
#
#  RequireValidShell          off
#
#  # Limit the maximum number of anonymous logins
#  MaxClients                  10
#
#  # We want 'welcome.msg' displayed at login, and '.message' displayed
#  # in each newly chdired directory.
#  DisplayLogin                        welcome.msg
#  DisplayFirstChdir          .message
#
#  # Limit WRITE everywhere in the anonymous chroot
#  <Directory *>
#    <Limit WRITE>
#      DenyAll
#    </Limit>
#  </Directory>
#
#  # Uncomment this if you're brave.
#  # <Directory incoming>
#  #  # Umask 022 is a good standard umask to prevent new files and dirs
#  #  # (second parm) from being group and world writable.
#  #  Umask                          022  022
#  #            <Limit READ WRITE>
#  #            DenyAll
#  #            </Limit>
#  #            <Limit STOR>
#  #            AllowAll
#  #            </Limit>
#  # </Directory>
#
# </Anonymous>

SocketBindTight on

Include /etc/proftpd_ispconfig.conf


till 3rd February 2006 14:20

Quote:

Originally Posted by Raffnix
saslauthd is running (restarted it to be sure) but still sending is not possible. This is what uebimail tells me:

It was not possible to send this e-mail
SMTP Error: Recipient not accepted. Verify your relay rules

This error is not related to saslauth.

Please post the lines that begin with:

smtpd_recipient_restrictions = ...
mynetworks = ....

from your postfix main.cf.

Raffnix 3rd February 2006 14:29

smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject _unauth_destination

mynetworks = 127.0.0.0/8

Could reject_unauth_destination be the problem?

Raffnix 3rd February 2006 15:22

Thx for the help so far.

Unfortunately I have to reset the server and reinstall everything. If I run again in this problem, I will return here. For now, the problem is "solved" ;)

Thank you anyway.

marsianman 4th February 2006 12:01

Hi, I am having the same problem.

When setting up postfix for plain text authentication (eventually to use TLS) I try to use telnet and verify that it is setup correctly. Unfortuneatly it seem to always fail authentication. I think it might be due to not knowing how to authenticate. What should be in /etc/pam.d/smtpd ?

Further details (and my config files) can be found @ http://marsianman.is-a-geek.com:8000/wp

Any help would be appreciated, thanks guys.

falko 4th February 2006 14:56

It seems as if saslauthd isn't running. Please post the output of
Code:

ps aux
Also, on your page I read this:
Quote:

I do have the server up and running though and the /etc/sasldb2 is world readable.
You don't need sasldb2 because you're using saslauthd which means your user must be in /etc/passwd and /etc/shadow and have a valid password.


All times are GMT +2. The time now is 09:44.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.