Directadmin BUG ?

[chiptecmm.com]

Hi there

I'm running a webserver with Directadmin, altough recently an error have been detected, imagine the following scenario.

Account A and B, are independent.

Account A user is userA

Account B user is userB

Account A decides to amke the following operation:

1.Set Catch All E-Mail
2.Selects Address radio box
3. On the text box writes the user "userB"

So userB starts receiving all garbish from userA.

This problems happens as well when userA adds an email userB@userAdomain.com on the box.

[fusionictnl]

What's the problem with this ? Offcourse you can specify any email adres for the catch-all, don't see why this is a BUG.?

[chiptecmm.com]

The bug is that, the other user that is receiving the emails (UserB) has nothing to do with the userA domain

[fusionictnl]

So no problem

If I type in an alias for spam@domain.ext to go to billgates@microsoft.com (as is possible in any mail software/cp etc.) it will deliver all spam to billgates@microsoft.com

Normaly a user will let all mail go to for example their home mail account.

[chiptecmm.com]

I thnik you won't have catched the drill yet


I'm and admin and created 2 accounts

Account A (ex, domain abc.com) and account B (ex, domain xyz.com), when you create the account you have to set the username for each one.

for account A i set the user accountA
for account B i set the user accountB

The problem is that the accountA guy has set the mail directed to accountB(user), not to an email of accountB, but for the user himself

[fusionictnl]

Yes I understand you're point (I think).

if you send a mail to accountB@userdomainAccountA.ext it delivers it to accountB ????

OR:

He just set the forwarder/catchall to: "accountB" instead of "accountb@userdomainAccountA.ext" ??

[chiptecmm.com]

It happens in both cases, in the first

if you send a mail to accountB@userdomainAccountA.ext it delivers it to accountB ????

in caso of accountB@userdomainAccountA.ext is not created in Account A, it delivers in accounB

and in the last case
He just set the forwarder/catchall to: "accountB"
it happens too

[fusionictnl]

Yes this is a normal way of wich exim handles mail.


Originally posted by chiptecmm.com
It happens in both cases, in the first

1.if you send a mail to accountB@userdomainAccountA.ext it delivers it to accountB ????

2.in caso of accountB@userdomainAccountA.ext is not created in Account A, it delivers in accounB

3.and in the last case
He just set the forwarder/catchall to: "accountB"
it happens too

1. Exim works wich mail as following (i presume):

mail to accountB@userdomainAccountA.ext
Checks wich domain: userdomainAccountA.ext
Is local so check account: accountB
Mailbox doesn't exists, check CatchAll
CatchAll doesn't exists, check local users
accountB exists as local user: deliveres to accountB

2. Same as 1 ;) ?

3. When you don't specify an @sdgsdgs.ext it's an account as accountB so it's dilivered to the local user. You also can put root in there etc.

Why do you want functionality as 3?

We'll lets say you have 2 domains and you want to set all domain of domain2 to go to domain1. You just set an catch-all to domain1 on domain2 ;)

Why 1,2 ? That's because exims routers work that way.

But if I have a catch all on my domain and there is a [user]@mailaccount.com it deliveres it to me.

You can check the following topic: http://www.directadmin.com/forum/showthread.php?s=&threadid=5495&perpage=20&pagenumber=2

[nobaloney]

Originally posted by chiptecmm.com
It happens in both cases
Exim (as do all MTAs) checks all addresses to see if they're local before attempting delivery to another server.

If you're using the exim.conf I wrote I'll be happy to attempt to debug it for you, and correct it if I've made an error.

To see if you're using my exim.conf file please check:

head /etc/exim.conf

and compare it with the top lines of the exim.conf file found here (http://www.nobaloney.net/downloads/spamblocker/DirectAdmin/).

Let me know if it is, and if so, I'll do some checking over the next few days.

Jeff