Has anyone thought about how to possibly make use of AWS SES email
receiving to accept inbound email and get it passed along into James?
With AWS SES email receiving you can have it save the actual message to
an S3 bucket and then fire off an SNS topic or Lambda function so the
question would
I had JAMES working using LDAP against ApacheDS awhile back in my
sandbox environment. The caveat I ran into was that it worked if the
address matched the actual account but it didn't handle looking up
aliases and virtual mailboxes successfully. So I began working on
re-writing the LDAP
, Jeremy T. Bouse wrote:
I've stumbled through getting JAMES up and running and talking with
ApacheDS so far. The gotcha I found in getting JAMES to acknowledge my
users in ApacheDS was to change my usersrepository from:
usersrepository name=LocalUsers
class
Looking into the code deeper before delving into trying to create a
LDAPRecipientRewriteTable class it appears that the only existing LDAP
functionality is the LDAPUserRespository which handles it's own LDAP
connection context. I could go ahead and follow that pattern and
implement the
I've stumbled through getting JAMES up and running and talking with
ApacheDS so far. The gotcha I found in getting JAMES to acknowledge my
users in ApacheDS was to change my usersrepository from:
usersrepository name=LocalUsers
