darklord1

Well-Known Member
Jul 8, 2006
58
0
156
cPanel Access Level
Root Administrator
Well basically I like :fail: for a server configuration but it wouldnt allow for postmaster and abuse e-mails to be routed correctly, I know who cares right, well I had 2 options, figure out how to make etc/valiases/domain do the trick OR make cpanel create those accounts on account creation, well Im very new and messing with cpanel is dangerous for me.

So I started trying to edit the etc/valiases/domain.com file and heres what I have in it now

postmaster || abuse: username

Well this seems to be working well, basically it allows only those 2 in and nothing that either isnt created. It does allow the normal created e-mails to work.

As Im very pleased with this, it doesnt really help me unless I know that the e-mails are getting killed completely. I dont want it to work like blackhole Id like it to work like fail so Im asking 2 things, will this work like fail and anyone know how I can code it to put this in instead of what it would normally put in?
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,465
30
473
Go on, have a guess
I got a bit lost in the last paragraph ;) IS what you want for postmaster and abuse to go to the main user account and to still use :fail: on the Default Account? If so, then you need to create an account [email protected]. If that's not it, maybe you could explain with an example.
 

darklord1

Well-Known Member
Jul 8, 2006
58
0
156
cPanel Access Level
Root Administrator
Sorry for the confusion, chirpy,

Well with my settings I have, both postmaster and abuse redirect to the main users account, and ONLY postmaster and abuse can get through. This is what I want. So heres an example.

My e-mail is [email protected]
so [email protected] works.
[email protected] works.
[email protected] works.
[email protected] does not work.

Postmaster and abuse arent created but rather redirected. so only accounts made, postmaster, and abuse e-mails work, So I am not forced to tell my clients to make a postmaster and an abuse.

I believe this stops a dictionary attack but I wanted to know how the e-mails where handled that were not routable.

Basically, the server seems to just fail on them but is this accurate?

Heres the response I get from the server.
[email protected] [~]# exim -bt [email protected]
[email protected]
<-- [email protected]
<-- [email protected]
router = virtual_user, transport = virtual_userdelivery
[email protected] [~]# exim -bt [email protected]
[email protected]
<-- [email protected]
<-- [email protected]
router = virtual_user, transport = virtual_userdelivery
[email protected] [~]# exim -bt [email protected]
[email protected]
router = virtual_user, transport = virtual_userdelivery
[email protected] [~]# exim -bt [email protected]
[email protected] is undeliverable:
Unrouteable address
[email protected] [~]# exim -bt [email protected]
[email protected] is undeliverable:
Unrouteable address
[email protected] [~]# exim -bt [email protected]
[email protected] is undeliverable:
Unrouteable address

And I managed to firgure out what file to edit to make it a static choice of what getss written.
Simply. does it completely fail or will this have the same downfall as blackhole?

I am trying my best to have a fully functional server without comprimising functionality of scripts to the point that I inconvenience my clients.
I think thats the goal of all server owners.
 
Last edited:

darklord1

Well-Known Member
Jul 8, 2006
58
0
156
cPanel Access Level
Root Administrator
HAHA I think Ive got it.

[email protected]: user
[email protected]: user
[email protected]: user
*: :fail: That user does not exist


I was using my own domain for testing previously and didnt realize that it was sending to the root account. Boy what a trip and now it does

[email protected] [~]# exim -bt [email protected]
[email protected]
<-- [email protected]
<-- [email protected]
router = localuser, transport = local_delivery
[email protected] [~]# exim -bt [email protected]
[email protected]
<-- [email protected]
<-- [email protected]
router = localuser, transport = local_delivery
[email protected] [~]# exim -bt [email protected]
[email protected]
<-- [email protected]
<-- [email protected]
router = localuser, transport = local_delivery
[email protected] [~]# exim -bt [email protected]
[email protected] is undeliverable:
That user does not exist

using one of my clients accounts as a test account, it worked flawlessly.