Mail Queue Administration query

[DrWizzle]

Good evening!

I'm new to the admin side of DirectAdmin so go gently with me! I've been using DA for over a year as a reseller so have a real good working knowledge of it. I've now hired a VPS and decided DA would be the way to go with this. I just have a couple of questions to make sure i've set the server up right. Having a bit of an issue with mail queue for some reason.

For the purposes of this, i've called my server "server.domain.com" in the administration settings (domain is replaced with an actual .com) . I have ns0 and ns1 of this domain glued as nameservers which work fine. I was having trouble with mail the other night and found out my domain was blocked by a few big players for spam attacks so had to get those lifted as a new renter of these IP addresses. Mail delivers fine now.

So my problem is this, on the Mail Queue administration, it has tried to send regular mail to [email protected] and also [email protected]

I've tried creating a domain server.domain.com but DA refuses this. Creating a subdomain works fine. I've tried a catch all to get this mail redirected to a normal box but to no avail. I'm unable to create subdomain email addresses or pointers here as well.

Anyone able to help?

Thanks so much!!

 

[Richard G]

I've tried creating a domain server.domain.com

You shouldn't do that. If alle is correct, DA would have created a DNS entry for server.domain.com itself already. Do not create this as a subdomain this can cause issues. Only use this as hostname. So it's best to remove the subdomain first if you made that within domain.com.

So my problem is this, on the Mail Queue administration, it has tried to send regular mail to [email protected] and also [email protected]

That is logical. System messages are send to the system account. For an admin this is [email protected] which can be changed by changing your admin email (click).

Now the second one is from the system, might be firewall notices send via root. That's why you see [email protected] and also easily to fix.

Login as root via SSH.
Then edit the /etc/aliases file and on the bottom change:

# Person who should get root's mail
#root:          marc

to

# Person who should get root's mail
root:          [email protected]

Ofcourse replace [email protected] with the email address you want these mails to arrive.

Then restart exim and you should be fine.

 

[DrWizzle]

Thank you so much for the quick reply. I just want to double check i'm doing this correctly...

I created an admin email account, and edited the email in the first step as you kindly linked above. Second step i've opened /etc/aliases and am presented with this:

# Default aliases file, installed by Exim. This file contains no real aliases.
# You should edit it to taste.


# The following alias is required by the mail RFCs 2821 and 2822.
# Set it to the address of a HUMAN who deals with this system's mail problems.

# postmaster: [email protected]

# It is also common to set the following alias so that if anybody replies to a
# bounce message from this host, the reply goes to the postmaster.

# mailer-daemon: postmaster


# You should also set up an alias for messages to root, because it is not
# usually a good idea to deliver mail as root.

# root: postmaster

# It is a good idea to redirect any messages sent to system accounts so that
# they don't just get ignored. Here are some common examples:

# bin: root
# daemon: root
# ftp: root
# nobody: root
# operator: root
# uucp: root

# You should check your /etc/passwd for any others.


# Other commonly enountered aliases are:
#
# abuse:       the person dealing with network and mail abuse
# hostmaster:  the person dealing with DNS problems
# webmaster:   the person dealing with your website

####

I've unchecked the common ones below as I have those emails setup anyway, unchecked postmaster and added in the postmaster email along with the daemon one also. Do I need to do anything with the block starting bin -> uccp?

 

[Richard G]

Yours looks different then the one I have. But as long as the root mail address is in there you should be fine.
I don't know if you have to do anything with the others, they are enabled almost all by default on my Centos 7 and 8 server.

Here's mine.

#
#  Aliases in this file will NOT be expanded in the header from
#  Mail, but WILL be visible over networks or from /bin/mail.
#
#       >>>>>>>>>>      The program "newaliases" must be run after
#       >> NOTE >>      this file is updated for any changes to
#       >>>>>>>>>>      show through to sendmail.
#

# Basic system aliases -- these MUST be present.
mailer-daemon:  postmaster
postmaster:     root

# General redirections for pseudo accounts.
bin:            root
daemon:         root
adm:            root
lp:             root
sync:           root
shutdown:       root
halt:           root
mail:           root
news:           root
uucp:           root
operator:       root
games:          root
gopher:         root
ftp:            root
nobody:         root
radiusd:        root
nut:            root
dbus:           root
vcsa:           root
canna:          root
wnn:            root
rpm:            root
nscd:           root
pcap:           root
apache:         root
webalizer:      root
dovecot:        root
fax:            root
quagga:         root
radvd:          root
pvm:            root
amandabackup:           root
privoxy:        root
ident:          root
named:          root
xfs:            root
gdm:            root
mailnull:       root
postgres:       root
sshd:           root
smmsp:          root
postfix:        root
netdump:        root
ldap:           root
squid:          root
ntp:            root
mysql:          root
desktop:        root
rpcuser:        root
rpc:            root
nfsnobody:      root
ingres:         root
system:         root
toor:           root
manager:        root
dumper:         root
abuse:                root

newsadm:        news
newsadmin:      news
usenet:         news
ftpadm:         ftp
ftpadmin:       ftp
ftp-adm:        ftp
ftp-admin:      ftp
www:            webmaster
webmaster:      root
noc:            root
security:       root
hostmaster:     root
info:           postmaster
marketing:      postmaster
sales:          postmaster
support:        postmaster


# trap decode to catch security attacks
decode:         root

# Person who should get root's mail
#root:          marc
root:           [email protected]
diradmin: :blackhole:

 

[DrWizzle]

Thank you. Mine is a new install (last week) on my VPS and I decided to run Ubuntu as that's my favourite flavour of linux and the VPS won't be used for shared hosting so don't need industry graded caged accounts so mine may be a little different to yours. The crux of it all works though. I've rebooted the server and restarted exim aloing with clearing the frozen queue. I'll see what happens going forward.

I do like the way you send your diradmin to :blackhole: though

Thank you so much for your help. I'm sure this won't be the least question I ask, but hopefully won't be any more questions for a few days.

Alan.

 

[Richard G]

The crux of it all works though.

That's the most important thing, especially if you're the only one using it.

I do like the way you send your diradmin to :blackhole: though

LoL, yes, that comes from this one:

Version 1.19.2 | Directadmin Docs

DirectAdmin Knowledge Base

directadmin.com

so that's for incoming mail. Abusers were trying to send mail to diradmin which is of no use and so filter it out.

As for my help, you're welcome..
If you have more questions.... well that's what this forum is for.