J.Delgado ha scritto:
I would like to see if anyone has an answer about this.
My company uses James mail server and I've been learning its features and
capabilities as the time passes.
One thing that bothers me though is the way it accepts email. More recently,
our mail server has been getting hit by a lot of spam (that due to the way
we run, we cannot block) to our domains with random usernames such as
[EMAIL PROTECTED] The problem is that James allows the email to pass based
solely on the domain and does no verification as to whether the user exists.
it only does that when it attempts to deliver the email and it errors out,
throwing it in the deadletter table on our DB.
Is there a way to make James verify the username as well as the domain prior
to accepting emails? I have worked with other servers that reject an email
if the user does not exist. Can I do that with James and how?
we name this feature "fast fail". Unfortunately it is not possible in v2.3.
Also, it is not so easy to implement this feature because at smtp level
we don't yet know what addresses will be valid during the spooling
because you can have "catchall" mailets, you could have forward mailets
and more.
We implemented a similar feature in the current dev branch but limited
to check the virtualusertable. Unfortunately this is far from being
released soon and hard to be backported to v2.3
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
