Page MenuHomePhorge

Abuse check
AbandonedPublic

Authored by machniak on Oct 10 2022, 11:32 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, May 14, 12:02 PM
Unknown Object (File)
Sat, May 4, 12:41 PM
Unknown Object (File)
Sat, May 4, 3:07 AM
Unknown Object (File)
Fri, May 3, 6:26 PM
Unknown Object (File)
Sat, Apr 27, 6:08 AM
Unknown Object (File)
Sun, Apr 21, 5:01 PM
Unknown Object (File)
Sun, Apr 21, 5:01 PM
Unknown Object (File)
Apr 20 2024, 10:10 AM
Subscribers
Restricted Project

Details

Reviewers
None
Group Reviewers
Restricted Project

Diff Detail

Repository
rK kolab
Branch
dev/abuse-check
Lint
Lint Skipped
Unit
No Test Coverage
Build Status
Buildable 40265
Build 16292: arc lint + arc unit

Event Timeline

machniak created this revision.

The abuse check now lives externally. As a generic mechanism vanmeeuwen suggested that we may be able to install an app/Handler/Abuse.php just like we do for app/Handler/Mailbox.php, and that this might provide a suitable generic hook to run an abuse-check background job.

I have not validated that idea.

I suppose Handler::created could be used to spawn a job, not sure if it is a good solution or not.

CreateJob is already async, so I don't really see a reason to invoke another job. At least the point is to not create the mailbox/ldap record if the abuse check didn't finish yet.