James smtp hooks and mailets can be used to achieve this.
You can even develop some custom ones if the provided ones are not enough.
On 05/11/13 18:07, Girivaraprasad Nambari wrote:
Hi Eric/Community,
Can some one please help me with this question?
Thank you for your time.
Thank you,
Giri
On Sun, Nov 3, 2013 at 11:41 PM, Girivaraprasad Nambari <
girinamb...@gmail.com> wrote:
Hi,
I understand that security involves lot of layers, but I want to
understand is James default configuration secure enough to restrict
un-authorized access? If not, what are the areas we need to configure? Is
there any documentation available?
In my view security here means (these are few I have on top of my head),
1) Without having user authentication mails shouldn't be sent out
2) Can we enforce authentication passwords are complex?
3) Is there any way we can limit out going capabilities to only certain
users?
for example, only my company admins can send emails, NOT associates. like
that.
Any help would be appreciated.
Thanks for your time.
Thank you,
Giri
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
