BoxTrapper - Ignore, White, Black list order

[jxmot]

Greetings,

There seems to be an issue with the order in which the ignore, white, and black lists are used. For example, I want this to pass through to me -

[email protected]

And in my white list -

from .+\@.+\.specificdomain\.com

The intent is to pass everything that matches through to me. However the ignore list gets in the way because apparently it's evaluated first. IMHO that is wrong. Here's the ignore list entry that's catching it -

from .+\@.+\..+\.

The intent there is to catch anything (except for what's white listed). I believe that will match things like -

[email protected].*

So if the list order was -

white
ignore
black

Then I would have received that email. The alternative is that if something is caught in the ignore list that then subsequently the white list would be checked.

If there is a way I can correct this please let me know. I've been frustrated by this issue for quite some time.

Thanks in advance!

 

[cPanelMichael]

Hello,

I've opened internal case CPANEL-15587 to report this behavior. I'll monitor this case and update this thread with more information as it becomes available.

Thank you.

 

[jxmot]

Thank you!

I'll keep monitoring this thread for the updates. If there is anything you need me to try just let me know.

jim

 

[jxmot]

@cPanelMichael Greetings,

I was just wondering if there has been any progress on CPANEL-15587.

THanks!

 

[cPanelMichael]

I was just wondering if there has been any progress on CPANEL-15587.

Hello,

There's currently no time frame on when a change to the existing behavior will make it's way into the product. I'll continue to monitor the case and update this thread with new information as it becomes available.

Thank you.

 

[jxmot]

Hello ,

There's currently no time frame on when a change to the existing behavior will make it's way into the product. I'll continue to monitor the case and update this thread with new information as it becomes available.

Thank you.

It's still a frustrating issue, 3 years later lol

So I was just wondering(again) if there has been any progress on CPANEL-15587.

 

[cPRex]

Hey there, @jxmot - let me see if I can find out more details for you on this. It might take a few days, but I'll let you know what I see.

 

[jxmot]

Thanks @cPRex !

 

[jxmot]

@cPRex Hello, it's been a "few days"... lol

So today I ran into a good example of why the order in which the ignore, white, and black lists is completely wrong.

In this example I was expecting an email from a *.org address. And due to previous spam activity .+\@.+\.org is in the ignore list. But the expected sender is in the white list ([email protected]\.org), and that message was ignored even though it was white listed.

If the list order was white, ignore, black I would have received that important message.

 

[cPRex]

Ohsnap! It has a been a few days for sure. I actually never heard back on my end either, so I'm changing up the plan a bit. I'll reply soon :D

 

[cPRex]

Alright - I looked into this and the original case was closed as this forums thread is the only report we've had about the issue. I spoke with the manager of the development team that controls email, and he did say it's something he'd like to get changed at some point, so the case has been reopened. It's just been a very low priority case for some time, so we aren't sure when there will be action taken to adjust that behavior.

I know that isn't ideal, but that's the best information I have at this point.

 

[jxmot]

Bummer. I can't believe that I'm the only one LOL

Thank you very much cpRex for following up and giving me info.

Btw, I am a software engineer with probably enough background to help in some way. Since the issue is low priorty would the manager of the development team be willing to consider some freelance assistance?

 

[cPRex]

You're welcome to submit a patch if you think you have a good workaround available! If you think you've come up with something just submit a ticket to our team and we can get the right people to review that.

 

[jxmot]

Cool. Can you direct me to the source code?

 

[cPRex]

Nope - a vast majority of our perl modules are encoded or otherwise obscured as that isn't something we make public.