Hi Carlos,
From your processor, why not just just authenticate with a single SMTP
userId at the official server and then set the mail sender field as the
original sender in the fwded message?
But that is assuming that you have or can register such an authenticated
userId and that your 'official' server allows you to set any sender address.
Regards,
Alain
Carlos Aviles wrote:
hi,
I've looked into the mailing list archives and I didn't find anything about
the subject, so hope someone could help me with this.
I use James 2.2.0 to intercept outgoing emails. I've built a processor chain
so for every email, I extract the attachments, sign them and pack everything
again. Finally the email is sent to the proper destination.
It's actually some kind of middleware acting between users that are sending
emails and the "official" SMTP server. The thing is that the "official"
server requires authentication. Every user has it's account configuration
and the only thing I can change is the name of the smtp server, wich is now
the James server. So the email client will connect with James the same way
as with the "official" smtp server, then James will work the attachments and
send the email through the "official" server using the authentication
parameters that the client used at first.
Does anyone know if it is doable? Is there any RemoteDelivery mailet for
SMTP_AUTH? Must James have account information for every user that sends
email through it? Can I set up an unauthenticated connection between the
client and James but at the same time retrieve the authentication
information that must be used in the final delivery process?
regards,
Carlos.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
