FTP Works with "admin", don't work with "@"

Donsje

Verified User
Joined
Apr 9, 2010
Messages
12
If I want to login on the FTP of my server:

Works:
IP: mydomein.com
User: Admin

Problem's if someone want to use FTP with "@"
IP: mydomein.com
User: user@mydomein.com

Everything with e-mail address to login don't work,
and the adress en password is correct in the Direct Admin FTP Management.
 
Is the account active? (i.e. not suspended)

Does the DNS resolve to the domain correctly?

It's a bit hard for us to help you if you don't give us the real domain ...
 
perhaps there is a problem with your DNS:

Code:
host ftp.leeriets.nl
ftp.leeriets.nl has address 255.255.255.255

255. is not a valid IP

whereas:

Code:
host leeriets.nl
leeriets.nl has address 77.243.235.120

then if I ftp to this address it works:

Code:
telnet leeriets.nl 21
Trying 77.243.235.120...
Connected to leeriets.nl.
Escape character is '^]'.
220 FTP Server ready.
USER [email protected]
331 Password required for [email protected]

so, when you connect to the ftp server -->

either:

* fix up ftp.leeriets.nl to point to the correct IP
or
* user leeriets.nl instead (i.e. without "ftp." in front).
 
Have changed and added ftp.leeriets.nl to that IP.

Mail to server: Don't work.
FTP to server: Don't work.
Admin Panel Directadmin: Alle services are running.

FTP with "admin" works, FTP with my FTP user [email protected] don't work, sending mails to my added e-mailaccount [email protected] don't work.

"Mail delivery failed: returning message to sender‏"
 
Have you checked the logs to see what it says specifically about each attempt?

I think you're going to need an experienced server administrator to log into your system and to search for specific problems.

Jeff
 
Deleted and readded DNS: 100% correct.

Then checked the logs:

FTP:

Code:
May  5 17:44:10 ** proftpd[634]: **.**.net (::ffff:*my home ip*[::ffff:*my home ip*]) - USER [email protected]: no such user found from ::ffff:*my home ip* [::ffff:*my home ip*] to ::ffff:77.243.235.120:21 
May  5 17:44:10 srvd013 proftpd[634]: srvd013.trafego.net (::ffff:*my home ip*[::ffff:*my home ip*]) - FTP session closed.

Mail:

Code:
2010-05-05 17:37:34 H=bay0-omc4-s20.bay0.hotmail.com [65.54.190.222] F=<**@hotmail.com> rejected RCPT <[email protected]>: 
2010-05-05 17:37:34 H=bay0-omc4-s20.bay0.hotmail.com [65.54.190.222] incomplete transaction (RSET) from <**@hotmail.com>

Everything without @ works, with @ don't. Thats my experience at this moment. Because admin user on ftp works great.
 
Last edited:
Hello,

Trying 77.243.235.120...
Connected to leeriets.nl.
Escape character is '^]'.
220 FTP Server ready.
That's not proftpd. You're not running our ftp daemon, hence none of our added usernames work ;)

Shut off the current ftp daemon, and start proftpd.

To check what's currently being used, use:
Code:
netstat -lnp | grep 21
This is why we recommend a "clean" OS install with no other services before installing DA ;)

John
 
Code:
 EN      2772/named
tcp        0      0 :::21                       :::*                        LIST                                                                                                                  EN      31495/proftpd: (acc
udp        0      0 0.0.0.0:642                 0.0.0.0:*   


udp        0      0 77.243.235.121:53           0.0.0.0:*                                                                                                                                                 2772/named

Is named the problem ? Unistall it?
 
So John tells you that the problem is the ftp daemon and you suggest uninstalling the named daemon as the cure. That does not make any sense.

Uninstall what ftp daemon you are running and install proftpd from the DirectAdmin site.
 
In my opinion, the easiest way to fix this is to be doing an admin backup and a clean install then admin restore - as John says DA works well on a clean install.
 
Sometimes people only have remote access and the data center may charge to do the re-install. A clean install can always be a last resort.
 
Uninstall what ftp daemon you are running and install proftpd from the DirectAdmin site.


Which of these do I need to unistall ?
I see proftpd running here.

Code:
[root@ ~]# netstat -lnp | grep 21
tcp        0      0 0.0.0.0:645                 0.0.0.0:*                   LISTEN      2159/rpc.statd
tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   LISTEN      2114/portmap
tcp        0      0 77.243.235.121:53           0.0.0.0:*                   LISTEN      2772/named
tcp        0      0 :::21                       :::*                        LISTEN      31495/proftpd: (acc
udp        0      0 0.0.0.0:642                 0.0.0.0:*                               2159/rpc.statd
udp        0      0 77.243.235.121:53           0.0.0.0:*                               2772/named
udp        0      0 0.0.0.0:111                 0.0.0.0:*                               2114/portmap
udp        0      0 0.0.0.0:639                 0.0.0.0:*                               2159/rpc.statd
unix  2      [ ACC ]     STREAM     LISTENING     10455  3097/nautilus       /tmp/orbit-root/linc-c19-0-16b05bba216b4
unix  2      [ ACC ]     STREAM     LISTENING     10478  3105/gnome-vfs-daem /tmp/orbit-root/linc-c21-0-60cfaca35a5a
unix  2      [ ACC ]     STREAM     LISTENING     11541  3219/gnome-panel    /tmp/orbit-root/linc-c93-0-435c8b5e2091b
unix  2      [ ACC ]     STREAM     LISTENING     11571  3221/wnck-applet    /tmp/orbit-root/linc-c95-0-435c8b5e90413
unix  2      [ ACC ]     STREAM     LISTENING     5842   2214/dbus-daemon    /var/run/dbus/system_bus_socket
[root@ ~]#
 
You need to uninstall proftpd and install the one from DirectAdmin.

@ranz Pepsi logo is back.
 
In my opinion, the easiest way to fix this is to be doing an admin backup and a clean install then admin restore - as John says DA works well on a clean install.
:) Glad to see your logo back.

:( Sad to see you think reinstalling a server a good solution to solve a problem with the FTP daemon. Certainly overkill.

I guess when you don't know what you're doing and can't afford to hire someone to fix it, a reinstall seems better, but surely the downtime for you and your clients is worth something?

Jeff
 
I see what you're saying, but if there's problems with ftp - what other problems are there too? It could be a long time before he irons out all the bugs. A clean install is relatively fast and painless.

He can also move the clients to another DA box ... or grab a cheap VPS and move them to there whilst he's doing the upgrade.

We've got a DA box now that is ready for OS upgrade ... and the best way to do this is to move them to a nother server whilst we perform the upgrade. The admin backup/restore feature is very reliable.
 
what other problems are there too? It could be a long time before he irons out all the bugs.

But so far its only been 1 bug and he can take 5 minutes out of his day and try to fix ftp and then if other problems start showing up then he still has the option of reinstalling everything.

Let's not do a full engine rebuild just because the spark plugs need changing.
 
I have done ./build all and then changed the proftd config in etc with the one in the template folder of DA. Now ftp works^^

getting mail also works, now only the outgoing mail of the server, in which config I can find that?

Thanks a lot for the support.
 
DirectAdmin should install a working (though not optimal) exim.conf file.

Please post the top ten lines of your /etc/exim.conf file.

Jeff
 
Code:
# Specify your host's canonical name here. This should normally be the
# fully qualified "official" name of your host. If this option is not
# set, the uname() function is called to obtain the name. In many cases
# this does the right thing and you need not set anything explicitly.

# primary_hostname =

# Specify the domain you want to be added to all unqualified addresses
# here. An unqualified address is one that does not contain an "@" character
# followed by a domain. For example, "[email protected]" is a fully qualified
# address, but the string "caesar" (i.e. just a login name) is an unqualified
# email address. Unqualified addresses are accepted only from local callers by
# default. See the receiver_unqualified_{hosts,nets} options if you want
# to permit unqualified addresses from remote sources. If this option is
# not set, the primary_hostname value is used for qualification.

# qualify_domain =

# If you want unqualified recipient addresses to be qualified with a different
# domain to unqualified sender addresses, specify the recipient domain here.
# If this option is not set, the qualify_domain value is used.

# qualify_recipient =

# the next line is required to start the smtp auth script included
# in DirectAdmin

perl_startup = do '/etc/exim.pl'

# the next line is required to start the system_filter included in
# DirectAdmin to refuse potentiallly harmful payloads in
# email messages

system_filter = /etc/system_filter.exim

# next line to allow incoming email submission port 587
# see also check_recipient second ruleset

daemon_smtp_ports = 25 : 587

# SET SOME MEANINGFUL LIMITS
# OPTIONAL MODIFICATIONS:
#  These defaults work for us; you may wish to modify them
#  for your environment

message_size_limit = 20M
smtp_receive_timeout = 5m
smtp_accept_max = 100
message_body_visible = 3000
print_topbitchars = true
deliver_queue_load_max = 5
smtp_connect_backlog = 50
split_spool_directory = yes

# ALLOW UNDERSCORE IN EMAIL DOMAIN NAME
# domains shouldn't use the underscore character "_" but some
# may.  Because John Postel, one of the architects of the Internet,
# said "Be liberal in what you accept and conservative in what you
# transmit, we choose to allow underscore in email domain names so we
# can receive email form domains which use the underscore character
# in their domain name.
# OPTIONAL MODIFICATIONS:
#  These defaults work for us; you may wish to modify them
#  for your environment

helo_allow_chars = _

# CHANGE LOGGING BEHAVIOR # We weren't happy with the default Exim logging behavior through # syslog; it didn't give us enough information.  So we turned off
# syslog behavior and changed the logging behavior to give us what we
# felt was more helpful information.  You may choose to delete or modify
# this section.
# OPTIONAL MODIFICATIONS:
#  These defaults work for us; you may wish to modify them
#  for your environment

log_selector = \
  +delivery_size \
  +sender_on_delivery \
  +received_recipients \
  +received_sender \
  +smtp_confirmation \
  +subject \
  +smtp_incomplete_transaction \
  -dnslist_defer \
  -host_lookup_failed \
  -queue_run \
  -rejected_header \
  -retry_defer \
  -skip_delivery

syslog_duplication = false

# These options specify the Access Control Lists (ACLs) that
# are used for incoming SMTP messages - after the RCPT and DATA
# commands, respectively.

acl_smtp_rcpt = check_recipient
acl_smtp_data = check_message

# define local lists

addresslist whitelist_senders = lsearch;/etc/virtual/whitelist_senders
addresslist blacklist_senders = lsearch;/etc/virtual/blacklist_senders
domainlist blacklist_domains = lsearch;/etc/virtual/blacklist_domains
domainlist whitelist_domains = lsearch;/etc/virtual/whitelist_domains
domainlist local_domains = lsearch;/etc/virtual/domains
domainlist relay_domains = lsearch;/etc/virtual/domains : localhost
domainlist use_rbl_domains = lsearch;/etc/virtual/use_rbl_domains
hostlist auth_relay_hosts = *
hostlist bad_sender_hosts = lsearch;/etc/virtual/bad_sender_hosts
hostlist bad_sender_hosts_ip = net-lsearch;/etc/virtual/bad_sender_hosts
hostlist relay_hosts = net-lsearch;/etc/virtual/pophosts
hostlist whitelist_hosts = lsearch;/etc/virtual/whitelist_hosts
hostlist whitelist_hosts_ip = net-lsearch;/etc/virtual/whitelist_hosts

# If you want to accept mail addressed to your host's literal IP address, for
# example, mail addressed to "user@[111.111.111.111]", then uncomment the
# following line, or supply the literal domain(s) as part of "local_domains"
# above. You also need to comment "forbid_domain_literals" below. This is not
# recommended for today's Internet.

# DO NOT ALLOW HOST LITERALS
# OPTIONAL MODIFICATIONS:
#  These defaults work for us; you may wish to uncomment the line 
#  below and change the allow_domain_literals line below to true
#  to allow domain literals in your environment

# local_domains_include_host_literals

# The following line prevents Exim from recognizing addresses of the form
# "user@[111.111.111.111]" that is, with a "domain literal" (an IP address)
# instead of a named domain. The RFCs still require this form, but it makes
# little sense to permit mail to be sent to specific hosts by their IP address
# in the modern Internet, and this ancient format has been used by those
# seeking to abuse hosts by using them for unwanted relaying. If you really
# do want to support domain literals, remove the following line, and see
# also the "domain_literal" router below.

allow_domain_literals = false

# No local deliveries will ever be run under the uids of these users (a colon-
# separated list). An attempt to do so gets changed so that it runs under the
# uid of "nobody" instead. This is a paranoic safety catch. Note the default
# setting means you cannot deliver mail addressed to root as if it were a
# normal user. This isn't usually a problem, as most sites have an alias for
# root that redirects such mail to a human administrator.

never_users = root

# DO HOST LOOKUP
# OPTIONAL MODIFICATIONS:
# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.

host_lookup = *

# DISALLOW IDENT CALLBACKS
# OPTIONAL MODIFICATIONS:
# Exim may be set to make RFC 1413 (ident) callbacks for all incoming SMTP
# calls. You can limit the hosts to which these calls are made, and/or change
# the timeout that is used. If you set the timeout to zero, all RFC 1413 calls
# are disabled. RFC 1413 calls are cheap and can provide useful information
# for tracing problem messages, but some hosts and firewalls have problems
# with them. This can result in a timeout instead of an immediate refused
# connection, leading to delays on starting up an SMTP session.  By default
# we disable callbacks for incoming SMTP calls.  You may change
# rfc1413_query_timeout to 30s or some other positive number of seconds to
# enable callbacks for incoming SMTP calls.

rfc1413_hosts = *
rfc1413_query_timeout = 0s

# BOUNCE MESSAGES
# OPTIONAL MODIFICATIONS:
# When Exim can neither deliver a message nor return it to sender, it
# "freezes" the delivery error message (aka "bounce message"). There are also
# other circumstances in which messages get frozen. They will stay on the
# queue forever unless one or both of the following options is set.

# This option unfreezes bounce messages after two days, tries
# once more to deliver them, and ignores any delivery failures.

ignore_bounce_errors_after = 2d

# This option cancels (removes) frozen messages that are older than five days.

timeout_frozen_after = 5d

# TRUSTED USERS
# OPTIONAL MODIFICATIONS:
# if you must add additional trusted users, do so here; continue the
# colon-delimited list

trusted_users = mail:majordomo:apache:diradmin

# SSL/TLS cert and key
tls_certificate = /etc/exim.cert
tls_privatekey = /etc/exim.key
tls_require_ciphers = ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP
tls_advertise_hosts = *
#auth_over_tls_hosts = *
 
Back
Top