Brian Williams
My feedback
3 results found
-
27 votes
AdminGabriel
(PM, Axigen)
responded
I understand the request, but before we schedule this, I would like to better understand the actual use case.
@All: Could you please detail your catch all usage, with a practical example, and as well as give some examples as to what kind of rules you would create (e.g. 1. conditions, 2. actions)?
Thank you,
GabrielAn error occurred while saving the comment An error occurred while saving the comment Brian Williams
commented
I don't think you understand what I was trying to say or I didn't say it very well. When using a catch-all account, the behavior that I am seeing is that emails are always going to the Inbox regardless of any rules that may exist on the server regarding the X-AxigenSpam-Level. The spammiest email in the history of the internet is always going to land in the inbox. I believe this is because when you define the catch-all account, you are required to define both the account to which the email should be redirected AND the folder into which the email should be placed.
What I think should happen is that the email should be redirected to the desired account and then let whatever rules are defined determine if the email is spam and, if so, deal with it in the appropriate manner.
I hope that clarifies the issue.
An error occurred while saving the comment Brian Williams
commented
I agree with this. However, the issue isn't that the rules aren't being run on the emails. The issue is that no matter what the filters/rules determine, the mail always gets delivered to the inbox of the catch-all account. That, I think, is a flaw in how Axigen envisions catch-all accounts. When you configure the catch-all account, you are required to define the folder where the email will be delivered. That is the problem. Rather that just delivering email to the "account" and let the rules direct it to the appropriate folder, Axigen developers are requiring that the delivery folder be specified and that specification overrides all of the other rules. That is a mistake, in my humble opinion.
Brian Williams
supported this idea
·
-
5 votesBrian Williams
shared this idea
·
-
187 votes
An error occurred while saving the comment Brian Williams
commented
While reviewing my logs for another matter, I too found that my server was under attack from someone trying a brute force attack. In this case it was the STMP service they were attacking. I have implemented fail2ban and in less than 24 hours it has blocked 10 IP addresses. It would be nice of that kind of security was built into axigen itself. Clearly there is a need.
Brian Williams
supported this idea
·
I guess I should add that this isn't solely a spam issue. As the others have pointed out, there are other types of rules that one might want to apply in addition to spam related rules. The point is that any rules that are defined are being ignored. Email goes to whatever folder is defined in the catch-all account definition and that is that.