> I think this is what Noel intended with his "Merger Branch"
> message to the
> server-dev list few days ago.
> I understood he is already working on the big "merging" work
> so we'll have
> un updated trunk (head) to work on.
>
Yes, I realize that ...
I am still trying to get a sense of if this
> > - I want JAMES to relay mails from my network's private
> > IP addresses.
>
> Fine. Set that subnet as authorized.
Done
> > - I want JAMES to relay mails for SMTP authenticated users
> > from everywhere.
>
> Turn on authorization.
Done
> > - I also want JAMES to automatically add an
> - I want JAMES to relay mails from my network's private
> IP addresses.
Fine. Set that subnet as authorized.
> - I want JAMES to relay mails for SMTP authenticated users
> from everywhere.
Turn on authorization.
> - I also want JAMES to automatically add an S/MIME signature
> for SMTP
> Why? The whole point is to not require it. If we want to
> assert to downstream relays that the user was authenticated,
> we don't need the SMTP AUTH to do so.
Here is my use case:
- I want JAMES to relay mails from my network's private IP addresses.
- I want JAMES to relay mails for SMTP a
> Would it be better to prompt anyway for SMTP AUTH
Why? The whole point is to not require it. If we want to assert to
downstream relays that the user was authenticated, we don't need the SMTP
AUTH to do so.
--- Noel
> > Currently a client from an athorised address is not able to get
> > authenticated: is it correct by RFC?
>
> Should be, yes. The server does not prompt for SMTP AUTH if
> the address is authorized.
Would it be better to prompt anyway for SMTP AUTH (it is not mandatory, but
only a capabilit
> Currently a client from an athorised address is not able to
> get authenticated: is it correct by RFC?
Should be, yes. The server does not prompt for SMTP AUTH if the address is
authorized.
--- Noel
-
To unsubscribe,
> I switched on the SMTP authentication.
> If I set a wrong password on MS-Outlook upon sending an
> email, james complains.
> If I turn off the smtp authentication on MS-Outlook, james
> accepts the outgoing mail.
> It doesn't make much sense ...
> I mean, if james is set to require SMTP authen
> It should insist upon authentication - unless the email is
> addressed to a domain on that server, or the sending machine
> is an authorised address.
Currently a client from an athorised address is not able to get
authenticated: is it correct by RFC?
Stefano
It should insist upon authentication - unless the email is addressed to a
domain on that server, or the sending machine is an authorised address.
Daniel.
> -Original Message-
> From: Marcello Marangio [mailto:[EMAIL PROTECTED]
> Sent: 06 April 2005 16:40
> To: James users
> Subject: authR
Hi all.
I switched on the SMTP authentication.
If I set a wrong password on MS-Outlook upon sending an email, james
complains.
If I turn off the smtp authentication on MS-Outlook, james accepts the
outgoing mail.
It doesn't make much sense ...
I mean, if james is set to require SMTP authentication
You have to use the ComponentManager to get a hold of the userstore from
within a mailet. The API is marked as deprecated but still works. Here
is an example:
protected String getMemberEmailFromUserStore(String memberName) {
String memberEmail = null;
if (memberName != null
> Intentional differences:
>
> - trunk has a released and updated version of Phoenix,
> which meant changes to lifecycle interfaces.
Will the new version run under Loom?
> - trunk has some experimental changes that won't be kept.
What changes will not be kept?
I've seen there is a lot o
13 matches
Mail list logo
