You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by "Jesper B. Kiær" <jb...@jezzper.dk> on 2006/01/18 09:51:50 UTC
James dead?
Hi
I think James is a great mailserver but development seems rather dead.
Does James have a future?
There is no information on future releases, visions etc. ..nothing
brgds
Jesper Kiær
http://www.jezzper.com
Re: James dead?
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Ahmed,
I think you raise a fair point although obviously you've not completely
given up on JAMES, because you still read the mailing lists...
I wonder if there is anything being done on these specific issues at the
moment, this would aid me in "fighting JAMES corner" with various
clients.
Also, it would be interesting to hear how many people are actively
working on development of JAMES at present...
Thanks for your answers.
On Wed, 2006-01-18 at 11:40 +0100, Ahmed Mohombe wrote:
> > James is not currently actively supported/sponsored by companies
> Of course there is no companies support.
> Companies need stable IMAP solutions and easy to configure server
> through GUIs not editing per telnet some strange config files.
> None of the above features are(or were) a target of JAMES.
>
> Sorry but that's the reality :(.
> In several companies I was, trying to bring JAMES, the first question was about IMAP and GUI.
> Most of these companies don't have years to wait till someone will implement it in JAMES,
> so they'll take an existing solution.
>
> Have a nice day,
>
> Ahmed.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Danny Angus <da...@gmail.com>.
On 18/01/06, Ahmed Mohombe <am...@yahoo.com> wrote:
> > James is not currently actively supported/sponsored by companies
> Of course there is no companies support.
> Companies need stable IMAP solutions and easy to configure server
> through GUIs not editing per telnet some strange config files.
> None of the above features are(or were) a target of JAMES.
James isn't actively supported by companies who might wish to devote a
little effort to realising those goals in return for no licence fees.
So James doesn't meet their requirements, not really surprising, and
nothing to apologise about.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Ahmed Mohombe <am...@yahoo.com>.
>> there are JAMES configuration tools out there.
>
>> You mean something that's not PHP, not Telnet, and
>> not cr.. (e.g. ajaconsole) ?
>
> Well, if you don't like ajaxconsole, contribute to making it better.
Sorry but there's nothing to contribute to it: the entire concept is wrong
starting with being Telnet based :).
I wanted to contribute to it, but if you look at the code you will be totally scared :).
I started to implement myself something, but the biggest problem is how to communicate
and control JAMES from a webapplication(but not with telnet :) ). I found no documentation
for it and the process is very cumbersome, with a constant try and fail :(.
> And I
> recall several users talking about webapps that dealt with JAMES, but
> personally, I don't do GUIs, so I haven't paid that much attention.
Exactly this is the problem. Sorry for being to direct, but you as one of the main
commiter, should pay *more* attention to these "small problems", but very important
for the adoption of JAMES(this wide adoption is still important for JAMES, right? :) ).
> The development list is quite active. We've got a whole bunch of new code
> and JIRA issues that we're actively working through. There are nightly
> builds for those who feel like playing with the latest and greated code.
Yes, I know, I'm watching SVN all the time but there's noting in the direction that
it's most important for the wide adoption of JAMES :( :
- IMAP
- GUI
- (and a few other, but I suppose with the change of the container, many will work out of the box).
> This is the user list, where we tend not to bother users.
I'm watching both, (like most of the users than *want* to use JAMES, but still can't ).
Ahmed.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: James dead?
Posted by "Noel J. Bergman" <no...@devtech.com>.
Ahmed Mohombe wrote:
> there are JAMES configuration tools out there.
> You mean something that's not PHP, not Telnet, and
> not cr.. (e.g. ajaconsole) ?
Well, if you don't like ajaxconsole, contribute to making it better. And I
recall several users talking about webapps that dealt with JAMES, but
personally, I don't do GUIs, so I haven't paid that much attention.
> > If anyone wanted to make a concerted effort to maintain one
> as part of JAMES, we'd be happy for it.
> No one I talked to has an idea about how do things work at
> Apache (especially JAMES).
You submit contributions via e-mail or JIRA. If the contribution is
substantial, you may be asked to submit a Software Grant or CLA. It really
isn't a whole lot more complicated than that.
> My impression and all other potential users I talked to was that
> this project is just "dragging itself" till it will totally stop.
The development list is quite active. We've got a whole bunch of new code
and JIRA issues that we're actively working through. There are nightly
builds for those who feel like playing with the latest and greated code.
This is the user list, where we tend not to bother users.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Ahmed Mohombe <am...@yahoo.com>.
>> On the GUI, you could say the same about Samba, but you're never going
>> to convince the GUI-centric hoardes of movers and shakers
> I don't know any UNIX administator worth his salt who uses a GUI to admin a
> server. Only Windows users are GUI-centric.
Sorry but small companies can't afford to have developers or admins all the time
around. Usually admins/developers are used once at install, and than a "little
more educated worker" does the rest. This is how it works in 90% of the small
companies and ignoring this won't change the situation.
> That said, there are JAMES configuration tools out there.
Really :).
You mean something that's not PHP, not Telnet, and not cr.. (e.g. ajaconsole) ?
Well if so why don't you share this valuable information with the rest of the world
hanging around here :) ?
> If anyone wanted
> to make a concerted effort to maintain one as part of JAMES, we'd be happy
> for it.
No one I talked to has an idea about how do things work at Apache(especially JAMES).
What are the process, who does what and when (or it would be supposed to), and why TF is so
complicated to make things move compared to other projects (also by Apache) ?
My impression and all other potential users I talked to was that this project is just "dragging
itself" till it will totally stop.
Even the "Feature Status" on the first page seems to be more than 3 years old.
Every time I tried to convince a manager to give JAMES a try, they look at the first page, see the
"Feature Status" and ask:
- "Uh, no IMAP?".
- "How do I administrate it?" "Can my best employee do maintain it?"
"Well, than it makes no sense for us to drop Exchange".
Ahmed.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Ahmed Mohombe <am...@yahoo.com>.
> On the GUI, you could say the same about Samba, but you're never going
> to convince the GUI-centric hoardes of movers and shakers out there if
> you can't actually show them something they have a chance of
> understanding!
Exactly: try to convince a small company manager to adopt such a software.
I tried with more, and never succeeded. Their first "argument" against non-GUI
applications is that the developer wants a "pension" there, since only the developer
will be able to use it and will be required for the smallest thing all the time.
Ahmed.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Serge Knystautas <sk...@gmail.com>.
On 1/18/06, Jesper B. Kiær <jb...@jezzper.dk> wrote:
> What are the
>
> - visions for project?
> - roadmaps
> - plans
> - ...
That's all in the wiki. The near-term changes are in JIRA's release
notes (our issue tracker), and of course mailing list archives if you
want to search a bit.
IMO James is reasonably documented compared to most open source
projects, largely because it's stabilized and hasn't had radical
changes. We do not have as much active development as other projects,
but the developer list has sustained traffic even if at low volume.
Please also note that these are surrogate indicators of a project's
quality. James is a very excellent replacement for sendmail. I would
never consider it a replacement for Exchange, but it does what it
tries to do very well. Sendmail has much more documentation and
developer traffic, but I have yet to figure out how to edit and
compile the sendmail configuration files to manage what I consider
basic smtp gateway functionality.
Maybe it's our name that causes us problems. When we say "Enterprise
Mail Server" we mean enterprise messaging like routing and logging and
transforming and processing. I think unfortunately for us, a large
number of people hear "Enterprise Mail Server" and they think we
should be able to handle imap and calendar and contacts for 20-100
people (Exchange). We do not do that (at least not until someone
contributes that).
--
Serge Knystautas
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. sergek@lokitech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Danny Angus <da...@gmail.com>.
On 19/01/06, Andrew Sykes <an...@sykesdevelopment.com> wrote:
> Would it be possible to take pieces of required functionality and UML
> diagram them (or something similar) so that those of us with a couple of
> free hours could knock a well defined class/method together and then
> simply contribute that? It seems that if there were a bunch of
> empty .java files looking something like...
Andrew, feel free to start at the top and propose stuff, then get
right in there and develop your proposal at your own pace, this
usually spurs others on to help you out.
Join the dev list and start talking about what *you* want to do.
d.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Eclipse
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
It would be good if a .classpath could be added to the repository to aid
importing into Eclipse.
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
http://www.sykesdevelopment.com
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Command Pattern Generalisation
Posted by Stefano Bagnara <ap...@bago.org>.
Andrew Sykes wrote:
> Stefano,
>
>> A more advanced task could be to generalize the Command Pattern used by
>> the SMTPHandle so that we can use it for all ours telnet/command based
>> protocols like POP3 and possibly as a base for IMAP too.
>> The command patter is easy to adopt and it allow for more flexibility
>> extensibility and a cleaner approach to the service creation/deploy.
>
> Can you give an example of the type of generalisation you had in mind?
STMPHandler could be refactored to be protocol indipendend by moving the
"mode" to the SMTPSession (or its SMTPSessions.State HashMap) and
refactoring the loop inside the handleConnection.
POP3Handler could be refactored to use the same code of the SMTPHandler
but using a different session/state/cmdhandlers.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Command Pattern Generalisation
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Stefano,
> A more advanced task could be to generalize the Command Pattern used by
> the SMTPHandle so that we can use it for all ours telnet/command based
> protocols like POP3 and possibly as a base for IMAP too.
> The command patter is easy to adopt and it allow for more flexibility
> extensibility and a cleaner approach to the service creation/deploy.
Can you give an example of the type of generalisation you had in mind?
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
http://www.sykesdevelopment.com
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: JAMES-437
Posted by Stefano Bagnara <ap...@bago.org>.
Andrew Sykes wrote:
> Stefano,
>
> Thanks for that.
A more advanced task could be to generalize the Command Pattern used by
the SMTPHandle so that we can use it for all ours telnet/command based
protocols like POP3 and possibly as a base for IMAP too.
The command patter is easy to adopt and it allow for more flexibility
extensibility and a cleaner approach to the service creation/deploy.
Stefano
> On Mon, 2006-01-23 at 16:50 +0100, Stefano Bagnara wrote:
>> Andrew Sykes wrote:
>>> Stefano,
>>>
>>> This may seem like a silly question, but what is the "state map"? Can
>>> you elaborate a bit please?
>>
>> With the new CmdHandler architecture introduced in James 2.3.0 the state
>> of the session is stored in the SMTPSession object. The single commands
>> behaviour depends on the current session state and they alter the
>> session state. For flexibility the SMTPSession contains a state HashMap
>> that can be used by commands to store arbitrary key-values pair.
>> [...]
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: JAMES-437
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Stefano,
Thanks for that.
On Mon, 2006-01-23 at 16:50 +0100, Stefano Bagnara wrote:
> Andrew Sykes wrote:
> > Stefano,
> >
> > This may seem like a silly question, but what is the "state map"? Can
> > you elaborate a bit please?
>
>
> With the new CmdHandler architecture introduced in James 2.3.0 the state
> of the session is stored in the SMTPSession object. The single commands
> behaviour depends on the current session state and they alter the
> session state. For flexibility the SMTPSession contains a state HashMap
> that can be used by commands to store arbitrary key-values pair.
>
> E.g:
> the current sender is stored in the map with the key "SENDER_ADDRESS" by
> the MailCmdHandler and used by the following commands.
>
>
> Stefano
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
http://www.sykesdevelopment.com
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: JAMES-437
Posted by Stefano Bagnara <ap...@bago.org>.
Andrew Sykes wrote:
> Stefano,
>
> This may seem like a silly question, but what is the "state map"? Can
> you elaborate a bit please?
With the new CmdHandler architecture introduced in James 2.3.0 the state
of the session is stored in the SMTPSession object. The single commands
behaviour depends on the current session state and they alter the
session state. For flexibility the SMTPSession contains a state HashMap
that can be used by commands to store arbitrary key-values pair.
E.g:
the current sender is stored in the map with the key "SENDER_ADDRESS" by
the MailCmdHandler and used by the following commands.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: JAMES-437
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Stefano,
This may seem like a silly question, but what is the "state map"? Can
you elaborate a bit please?
On Mon, 2006-01-23 at 16:19 +0100, Stefano Bagnara wrote:
> Andrew Sykes wrote:
> > Stefano,
> >
> > Were you looking for something like this?
>
> Yes, but extended to all the messages (ideally).
>
> Probably more error logs contains uncomplete messages and could be
> enhanced like this.
>
> The bug report point to that specific log as an example but also refer
> to a general approach to the logging.
>
> In that specific log you could add the log of sender and recipient, in
> many other calls to the logger we could add more contextual informations.
>
> Please keep in mind that the CmdHandlers are now modular so when you get
> a value from the state map you always have to check for null.
>
> Stefano
>
>
> > I've added this to JIRA (JAMES-437) too.
> >
> > Index: src/java/org/apache/james/smtpserver/RcptCmdHandler.java
> > ===================================================================
> > --- src/java/org/apache/james/smtpserver/RcptCmdHandler.java
> > (revision 370873)
> > +++ src/java/org/apache/james/smtpserver/RcptCmdHandler.java (working
> > copy)
> > @@ -149,7 +149,7 @@
> > if (!session.getConfigurationData().getMailServer
> > ().isLocalServer(toDomain)) {
> > responseString = "530 "+DSNStatus.getStatus
> > (DSNStatus.PERMANENT,DSNStatus.SECURITY_AUTH)+" Authentication
> > Required";
> > session.writeResponse(responseString);
> > - getLogger().error("Rejected message -
> > authentication is required for mail request");
> > + getLogger().error("Rejected message to: " +
> > recipientAddress.toInternetAddress().getAddress() + " - authentication
> > is required for mail request");
> > return;
> > }
> > } else {
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: JAMES-437
Posted by Stefano Bagnara <ap...@bago.org>.
Andrew Sykes wrote:
> Stefano,
>
> Were you looking for something like this?
Yes, but extended to all the messages (ideally).
Probably more error logs contains uncomplete messages and could be
enhanced like this.
The bug report point to that specific log as an example but also refer
to a general approach to the logging.
In that specific log you could add the log of sender and recipient, in
many other calls to the logger we could add more contextual informations.
Please keep in mind that the CmdHandlers are now modular so when you get
a value from the state map you always have to check for null.
Stefano
> I've added this to JIRA (JAMES-437) too.
>
> Index: src/java/org/apache/james/smtpserver/RcptCmdHandler.java
> ===================================================================
> --- src/java/org/apache/james/smtpserver/RcptCmdHandler.java
> (revision 370873)
> +++ src/java/org/apache/james/smtpserver/RcptCmdHandler.java (working
> copy)
> @@ -149,7 +149,7 @@
> if (!session.getConfigurationData().getMailServer
> ().isLocalServer(toDomain)) {
> responseString = "530 "+DSNStatus.getStatus
> (DSNStatus.PERMANENT,DSNStatus.SECURITY_AUTH)+" Authentication
> Required";
> session.writeResponse(responseString);
> - getLogger().error("Rejected message -
> authentication is required for mail request");
> + getLogger().error("Rejected message to: " +
> recipientAddress.toInternetAddress().getAddress() + " - authentication
> is required for mail request");
> return;
> }
> } else {
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
JAMES-437
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Stefano,
Were you looking for something like this?
I've added this to JIRA (JAMES-437) too.
Index: src/java/org/apache/james/smtpserver/RcptCmdHandler.java
===================================================================
--- src/java/org/apache/james/smtpserver/RcptCmdHandler.java
(revision 370873)
+++ src/java/org/apache/james/smtpserver/RcptCmdHandler.java (working
copy)
@@ -149,7 +149,7 @@
if (!session.getConfigurationData().getMailServer
().isLocalServer(toDomain)) {
responseString = "530 "+DSNStatus.getStatus
(DSNStatus.PERMANENT,DSNStatus.SECURITY_AUTH)+" Authentication
Required";
session.writeResponse(responseString);
- getLogger().error("Rejected message -
authentication is required for mail request");
+ getLogger().error("Rejected message to: " +
recipientAddress.toInternetAddress().getAddress() + " - authentication
is required for mail request");
return;
}
} else {
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Stefano Bagnara <ap...@bago.org>.
Andrew Sykes wrote:
> Wouldn't it be a good idea to just get stuck into moving the logging? I
> assume it's got to go sometime. Or is there any special reason why
> things have to be done in a specific order? If IIRC wraps log4j isn't
> log4j already a dependency?
Avalon logger is only a service provided via an Interface.
Every avalon container supply its own implementation to the components
requiring the logger service.
The wrapper I referred is an implementation of the Logger service on top
of log4j, so that you don't need to change your code and you can use
log4j anyway.
We currently don't depend on log4j. I would prefer to add log4j only
when we will remove the whole avalon dependency (or we will provide our
own implementation of the avalon services).
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Stefano,
As far as I can see, I've done everything I can with the logging (for
that file anyway). Unless there's something glaringly missing? This
would represent my suggestion of small incremental patches.
Wouldn't it be a good idea to just get stuck into moving the logging? I
assume it's got to go sometime. Or is there any special reason why
things have to be done in a specific order? If IIRC wraps log4j isn't
log4j already a dependency?
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
http://www.sykesdevelopment.com
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Stefano Bagnara <ap...@bago.org>.
Andrew Sykes wrote:
> Stefano,
>
> Another version of the improved logging stuff, sender and recipient are
> the only glaringly obvious pieces of info that are missing. I've added a
> method to get these rather than cluttering the code.
Please, when you stop/finish working on the logging issue post the full
patch to the JIRA issue and I will review/commit it as soon as possible.
> The logging is currently in avalon, has anyone begun work on moving this
> to something else? Perhaps log4j ;-)
There is no much difference in how they are used.
Until we use phoenix / avalon for other services we can safely use its
logger, too.
IIRC an avalon wrapper for log4j already exists but I don't see the
point in adding one more dependency right now as we can't remove avalon
anyway, yet.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Stefano,
Another version of the improved logging stuff, sender and recipient are
the only glaringly obvious pieces of info that are missing. I've added a
method to get these rather than cluttering the code.
The logging is currently in avalon, has anyone begun work on moving this
to something else? Perhaps log4j ;-)
Index: src/java/org/apache/james/smtpserver/RcptCmdHandler.java
===================================================================
--- src/java/org/apache/james/smtpserver/RcptCmdHandler.java (revision
370873)
+++ src/java/org/apache/james/smtpserver/RcptCmdHandler.java (working
copy)
@@ -37,7 +37,9 @@
*/
private final static String SENDER = "SENDER_ADDRESS"; //
Sender's email address
private final static String RCPT_LIST = "RCPT_LIST"; // The
message recipients
-
+ private MailAddress recipientAddress = null;
+ private String recipient = null;
+
/*
* handles RCPT command
*
@@ -60,7 +62,6 @@
String responseString = null;
StringBuffer responseBuffer = session.getResponseBuffer();
- String recipient = null;
if ((argument != null) && (argument.indexOf(":") > 0)) {
int colonIndex = argument.indexOf(":");
recipient = argument.substring(colonIndex + 1);
@@ -96,8 +97,8 @@
StringBuffer errorBuffer =
new StringBuffer(192)
.append("Error parsing recipient
address: ")
- .append(recipient)
- .append(": did not start and end with <
>");
+ .append("Address did not start and end
with < >")
+ .append(getContext(session));
getLogger().error(errorBuffer.toString());
}
return;
@@ -102,7 +103,7 @@
}
return;
}
- MailAddress recipientAddress = null;
+
//Remove < and >
recipient = recipient.substring(1, recipient.length() - 1);
if (recipient.indexOf("@") < 0) {
@@ -123,8 +124,7 @@
StringBuffer errorBuffer =
new StringBuffer(192)
.append("Error parsing recipient
address: ")
- .append(recipient)
- .append(": ")
+ .append(getContext(session))
.append(pe.getMessage());
getLogger().error(errorBuffer.toString());
}
@@ -149,7 +149,10 @@
if (!session.getConfigurationData().getMailServer
().isLocalServer(toDomain)) {
responseString = "530 "+DSNStatus.getStatus
(DSNStatus.PERMANENT,DSNStatus.SECURITY_AUTH)+" Authentication
Required";
session.writeResponse(responseString);
- getLogger().error("Rejected message -
authentication is required for mail request");
+ StringBuffer sb = new StringBuffer(128);
+ sb.append("Rejected message - authentication is
required for mail request");
+ sb.append(getContext(session));
+ getLogger().error(sb.toString());
return;
}
} else {
@@ -168,7 +171,8 @@
.append("User ")
.append(authUser)
.append(" authenticated,
however tried sending email as ")
- .append(senderAddress);
+ .append(senderAddress)
+ .append(getContext(session));
getLogger().error(errorBuffer.toString
());
}
return;
@@ -180,7 +184,7 @@
if (!session.getConfigurationData().getMailServer
().isLocalServer(toDomain)) {
responseString = "550 "+DSNStatus.getStatus
(DSNStatus.PERMANENT,DSNStatus.SECURITY_AUTH)+" Requested action not
taken: relaying denied";
session.writeResponse(responseString);
- getLogger().error("Rejected message - " +
session.getRemoteIPAddress() + " not authorized to relay to " +
toDomain);
+ getLogger().error("Rejected message - " +
session.getRemoteIPAddress() + " not authorized to relay to " + toDomain
+ " " + getContext(session));
return;
}
}
@@ -203,7 +207,8 @@
.append("RCPT command had
unrecognized/unexpected option ")
.append(rcptOptionName)
.append(" with value ")
- .append(rcptOptionValue);
+ .append(rcptOptionValue)
+ .append(getContext(session));
getLogger().debug(debugBuffer.toString());
}
}
@@ -219,5 +224,15 @@
}
}
-
+ private String getContext(SMTPSession session){
+ StringBuffer sb = new StringBuffer(128);
+ if(null!=recipientAddress){
+ sb.append(" [to:" + (recipientAddress).toInternetAddress
().getAddress() + "]");
+ }else if(null!=recipient){
+ sb.append(" [to:" + recipient + "]");
+ }
+ if(null!=session.getState().get(SENDER))
+ sb.append(" [from:" + ((MailAddress)session.getState().get
(SENDER)).toInternetAddress().getAddress() + "]");
+ return sb.toString();
+ }
}
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
http://www.sykesdevelopment.com
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Stefano Bagnara <ap...@bago.org>.
Andrew Sykes wrote:
> Stefano,
>
> This is exactly the kind of thing I was thinking about. It's one that
> can be really easily delegated to a newbie.
The problem with IMAP is that there is no lead to coordinate the
activity you are describing.
There is a need of a lead that knows his fact about IMAP and understand
James too in order to create subtask, assign them, know the current
status, being able to review the code proposed.
I don't know IMAP so I can't be of help here.
> I had a look at the JIRA stuff for IMAP. There are 5 open issues here, I
> assume that doesn't represent all the work required for a functional
> IMAP. Everyone I've spoken to about JAMES has ruled it out because
> there's no IMAP support (and a few have complained about the GUI) - Ok,
> enough already!
>
> So the Solution is...
> Break down IMAP stuff into little tasks like the logging one. This would
> have 3 effects...
> [...]
> Let me know what you think...
The current effort is to release James 2.3.0 *without* IMAP.
As far as I understood in past the main blocking IMAP issue is related
to repositories. We want to (scheduled to) change/improve repositories
but we can't do that before 2.3.0 is out.
I always heard about IMAP SEARCH command implementation that is a big
thing and we don't have it and it is not so related to James. You may
want to look in the James archives for "Imap search" and try to
understand something about.
Again, I don't know much / I don't use IMAP so take my words as a vague
memory dump.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Stefano,
This is exactly the kind of thing I was thinking about. It's one that
can be really easily delegated to a newbie.
I had a look at the JIRA stuff for IMAP. There are 5 open issues here, I
assume that doesn't represent all the work required for a functional
IMAP. Everyone I've spoken to about JAMES has ruled it out because
there's no IMAP support (and a few have complained about the GUI) - Ok,
enough already!
So the Solution is...
Break down IMAP stuff into little tasks like the logging one. This would
have 3 effects...
1/ IMAP support would be perceived as very much an active task.
2/ People could watch the tasks being checked off - increasing
confidence.
3/ Developers would have an entry point to the project which would
reflect their/their boss's, requirements.
If you advertised this effort clearly on the front page of the project
website, I bet it would have a dramatic impact on the amount of interest
and confidence generated in the project. Let's face it, JAMES is a great
mail server; it has the ASF seal of approval; it runs on any platform,
what more could you want?
Well, at the moment "IMAP" doesn't appear anywhere on that front page.
If you like this suggestion, I'll happily write some new content for the
front page declaring how alive the IMAP effort is and explain how easy
it is to contribute to the effort. I'll also write an eclipse quick-
start (assuming I get it working nicely) so that contributing is as
seamless as possible.
With a feeling of inclusivity and that the project was reaching into new
ground, as well as a clear framework to make contributions to a
"vibrant" Apache JAMES project and in particular, to the things that
matter to the current non-adopters, a lot of things that seem out of
reach at the moment could quickly become just another stable feature of
an already great mail server.
Let me know what you think...
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Stefano Bagnara <ap...@bago.org>.
Andrew Sykes wrote:
> It looks like there's a lot of people, me included, who don't want to
> see the apocalyptic subject line come true!
>
> There also seem to be a lot of people, like me, who would gladly
> contribute if there was some way of doing this without losing a week or
> two.
>
> Perhaps one of the James gurus could suggest a way that this could be
> achieved? To get the ball rolling, here's my two cents...
> [....]
Well, I think the newly added bug
http://issues.apache.org/jira/browse/JAMES-437 is a perfect target for a
"starter" on James.
Reviewing the code and improving the message logging is a good feature
to have and it doesn't require Avalon knowledge.
I'm sure that looking at open bugs in the issue tracker you will find
more similar tasks.
If anyone want to contribute to the project please start looking at the
issue tracker and if you think you can do something just tell to the
list you're going to work on that issue and I will be happy to help and
review/commit the patch.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
It looks like there's a lot of people, me included, who don't want to
see the apocalyptic subject line come true!
There also seem to be a lot of people, like me, who would gladly
contribute if there was some way of doing this without losing a week or
two.
Perhaps one of the James gurus could suggest a way that this could be
achieved? To get the ball rolling, here's my two cents...
Would it be possible to take pieces of required functionality and UML
diagram them (or something similar) so that those of us with a couple of
free hours could knock a well defined class/method together and then
simply contribute that? It seems that if there were a bunch of
empty .java files looking something like...
NewClass{
public static Map newFunctionality(){
//Message from JAMES guru...
//We need this to do XYZ
//Ask me if you don't understand
}
}
I guess this wouldn't cover all the work required as much of it will be
framework oriented, but as I don't understand the framework, someone
else would need to elaborate on this strategy...
Let us know what you think JAMES gurus, also if there are non-
contributors out there who like this idea, shout loudly, I'm sure the
JAMES guys would love to hear from you...
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Mark Derricutt <ma...@talios.com>.
On 1/19/06, Ivan Jouikov <iv...@ablogic.net> wrote:
> Sounds to me like a lot of people are using JAMES... why don't we all throw
I thought I'd chime in and say that we (work) are using James in 2-3
applications fronting our email-2-sms services. Admittidly all we're
using is a simple mailet which offloads via RMI/SOAP/EJB to the main
application - but for what that provides - james kicks arse.
I wonder what the ratio of people using james as a front-end to
applications is over people using james as a traditional mail server
(with pop3, imap, nntp?)
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: James dead?
Posted by Ivan Jouikov <iv...@ablogic.net>.
Sounds to me like a lot of people are using JAMES... why don't we all throw
some money together, even $200/person, and donate it to the developers?
That should give them a good push in the right direction... And if they can
clean up the site, make some good predictions as to what features/etc
they're planning to introduce, you guys could get your bosses to cash out...
???
-----Original Message-----
From: Jesper B. Kiær [mailto:jbk@jezzper.dk]
Sent: Wednesday, January 18, 2006 3:40 PM
To: James Users List
Subject: Re: James dead?
Hi
I glad my posting created some reactions and it seems that James is not
quite dead yet ...thankfully:-)
I still see a serious problem with the James project and that is a
problem it shares with a lot of other Open Source projects
Not enough INFORMATION!
There are lots of potential users are out there, but they need to know
what is going on!!
What are the
- visions for project?
- roadmaps
- plans
- ...
Keep Information floating ! ... share what you know!
Thanks to all developers of James ..You are doing a great job!
brgds
Jesper B. Kiær
http://www.jezzper.com
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.14.19/231 - Release Date: 1/16/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.14.19/231 - Release Date: 1/16/2006
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by "Jesper B. Kiær" <jb...@jezzper.dk>.
Hi
I glad my posting created some reactions and it seems that James is not
quite dead yet ...thankfully:-)
I still see a serious problem with the James project and that is a
problem it shares with a lot of other Open Source projects
Not enough INFORMATION!
There are lots of potential users are out there, but they need to know
what is going on!!
What are the
- visions for project?
- roadmaps
- plans
- ...
Keep Information floating ! ... share what you know!
Thanks to all developers of James ..You are doing a great job!
brgds
Jesper B. Kiær
http://www.jezzper.com
Re: James dead?
Posted by Georg Sauer-Limbach <ja...@gslweb.de>.
Er, where to start?
First of all, James is great and worked out of the box
the first time I unpacked it. This never happens with
payware.
Therefore: Thanks to the developers. Don't get concerned
about what any "company" would want.
I would, like Ahmed, be happy to be able to contribute one
fine day :-)
best regards
Georg
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: James dead?
Posted by Ivan Jouikov <iv...@ablogic.net>.
We use James and I'd gladly cash out for it because it's 100 times easier to
use than other free alternatives, and so far it's been 100% stable for over
a year now.
Ivan Jouikov
www.ablogic.net
(206) 228-6670
ivan@ablogic.net
-----Original Message-----
From: Andrew Sykes [mailto:andrew@sykesdevelopment.com]
Sent: Wednesday, January 18, 2006 9:41 AM
To: James Users List
Subject: RE: James dead?
Noel,
> I don't know any UNIX administator worth his salt who uses a GUI to admin
a
> server. Only Windows users are GUI-centric.
I don't know many SMEs with a spare Unix administrator to hand!
Surely this is the whole point, it's not what the world of
java developers and unix admins want. If JAMES is going to be taken
seriously and broadly adopted as a business solution, you need to
appeal to businesses.
I find JAMES to be an excellent mail server and like the mailet
and matcher stuff in particular which offers a simple way to respond rapidly
to new business requirements. That being said I'm not afraid to do a bit of
config file editing or development.
For those I've tried (in vain) to convince to use it, the response was one
of confusion mixed with terror. You do nothing to allay those fears by
suggesting
this is only for a "UNIX administator worth his salt". Comments like this
are
a marketing disaster!
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.14.19/231 - Release Date: 1/16/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.14.19/231 - Release Date: 1/16/2006
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: James dead?
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Noel,
> I don't know any UNIX administator worth his salt who uses a GUI to admin a
> server. Only Windows users are GUI-centric.
I don't know many SMEs with a spare Unix administrator to hand!
Surely this is the whole point, it's not what the world of
java developers and unix admins want. If JAMES is going to be taken
seriously and broadly adopted as a business solution, you need to
appeal to businesses.
I find JAMES to be an excellent mail server and like the mailet
and matcher stuff in particular which offers a simple way to respond rapidly
to new business requirements. That being said I'm not afraid to do a bit of
config file editing or development.
For those I've tried (in vain) to convince to use it, the response was one
of confusion mixed with terror. You do nothing to allay those fears by suggesting
this is only for a "UNIX administator worth his salt". Comments like this are
a marketing disaster!
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: James dead?
Posted by "Noel J. Bergman" <no...@devtech.com>.
> On the GUI, you could say the same about Samba, but you're never going
> to convince the GUI-centric hoardes of movers and shakers
Really? IBM used to have a GUI tool for configuring their web server (based
on the Apache web server). They EOL'd it because no one ever uses one to
configure the Apache web server. Doesn't seem to have hurt deployment any.
I don't know any UNIX administator worth his salt who uses a GUI to admin a
server. Only Windows users are GUI-centric.
That said, there are JAMES configuration tools out there. If anyone wanted
to make a concerted effort to maintain one as part of JAMES, we'd be happy
for it.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Vincenzo,
On the GUI, you could say the same about Samba, but you're never going
to convince the GUI-centric hoardes of movers and shakers out there if
you can't actually show them something they have a chance of
understanding!
--
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Ahmed Mohombe <am...@yahoo.com>.
> I agree with you on IMAP, but not on the GUI issue, as I consider the
> configuration flexibility of James (not attainable through a GUI) as
> very powerful.
I know that from a developer point of view, that JAMES config files are
more flexible, however:
- 1. why not have both(flexibility and ease of use)
- 2. Also non-developers need to change simple things.
- 3. not everybody can afford to have a developer near the server *all* the time.
- 4. simple things should be simple, not complicated (just because one is flexible
enough(and allowed) to do complicated things).
> Btw, you don't need to use telnet to edit the config files ;-)
Yes, sure, but out of the box, this is the only way. There's no bundle,
that allows to do the entire work with JAMES out of the box.
Also there's no step by step documentation on how to do it.
IMHO the default configuration (and one distribution), should just work out-of-the-box
for most of common users, period.
Thanks in advance,
Ahmed.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Vincenzo Gianferrari Pini <vi...@praxis.it>.
I agree with you on IMAP, but not on the GUI issue, as I consider the
configuration flexibility of James (not attainable through a GUI) as
very powerful.
Btw, you don't need to use telnet to edit the config files ;-)
Vincenzo
Ahmed Mohombe wrote:
>> James is not currently actively supported/sponsored by companies
>
> Of course there is no companies support.
> Companies need stable IMAP solutions and easy to configure server
> through GUIs not editing per telnet some strange config files.
> None of the above features are(or were) a target of JAMES.
>
> Sorry but that's the reality :(.
> In several companies I was, trying to bring JAMES, the first question
> was about IMAP and GUI.
> Most of these companies don't have years to wait till someone will
> implement it in JAMES,
> so they'll take an existing solution.
>
> Have a nice day,
>
> Ahmed.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Ahmed Mohombe <am...@yahoo.com>.
> Ahmed Mohombe wrote:
>>> James is not currently actively supported/sponsored by companies
>> Of course there is no companies support.
>> Companies need stable IMAP solutions and easy to configure server
>> through GUIs not editing per telnet some strange config files.
>> None of the above features are(or were) a target of JAMES.
>
> If James had stable support for all of the companies needs then James
> would not need their support any more ;-)
I know, you are right. But those features are not even on the roadmap.
Also no one can say when will they be.
> If every company paying for a proprietary solution would instead
> contribute something to James we probably would have IMAP/GUI and
> anything else.
Because if companies "pay" (in a form or other), they need a perspective,
or at least an idea about *when*.
Also they need to see something, a small demo or something tangible that
the entire thing is possible. Regarding IMAP most of them consider it
impossible, and only that "very big companies can do it".
I personally can't really contradict them. As from the RFCs I wouldn't
be able to do implement a *reliable* IMAP solution myself :( - it just looks
too complicated to me, or the RFCs need a "translation" :).
> My company is using James and we committed a lot of improvement to James
> .. We chose james because we needed flexibility and we need a java
> mailserver to be easily integrated in our existing java application.
Yes I saw that too. Judging from the dev-list, you did the most of the contribution
in the last year.
For managers however (of non software dev companies) it's irrelevant that it's Java,
(it's only for me as a developer :) ). Most of them just need things to work, in
a predictable time frame. As if IMAP, no one can define this time frame.
> Any contribution/effort on the IMAP/GUI side is welcome: I currently
> actively review patches and apply them as soon as possible.
The problem with IMAP is not the "willing" but the "who is able" IMHO.
Ahmed.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Stefano Bagnara <ap...@bago.org>.
Ahmed Mohombe wrote:
>> James is not currently actively supported/sponsored by companies
> Of course there is no companies support.
> Companies need stable IMAP solutions and easy to configure server
> through GUIs not editing per telnet some strange config files.
> None of the above features are(or were) a target of JAMES.
If James had stable support for all of the companies needs then James
would not need their support any more ;-)
If every company paying for a proprietary solution would instead
contribute something to James we probably would have IMAP/GUI and
anything else.
My company is using James and we committed a lot of improvement to James
. We chose james because we needed flexibility and we need a java
mailserver to be easily integrated in our existing java application.
Any contribution/effort on the IMAP/GUI side is welcome: I currently
actively review patches and apply them as soon as possible.
After 2.3.0 release we've already planned changes to the Mailet APIs and
repositories interfaces to simplify IMAP development but I only will
work on the first changes and not to the IMAP capability itself.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Ahmed Mohombe <am...@yahoo.com>.
> James is not currently actively supported/sponsored by companies
Of course there is no companies support.
Companies need stable IMAP solutions and easy to configure server
through GUIs not editing per telnet some strange config files.
None of the above features are(or were) a target of JAMES.
Sorry but that's the reality :(.
In several companies I was, trying to bring JAMES, the first question was about IMAP and GUI.
Most of these companies don't have years to wait till someone will implement it in JAMES,
so they'll take an existing solution.
Have a nice day,
Ahmed.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James dead?
Posted by Stefano Bagnara <ap...@bago.org>.
Jesper B. Kiær wrote:
> Hi
>
> I think James is a great mailserver but development seems rather dead.
>
> Does James have a future?
>
> There is no information on future releases, visions etc. ..nothing
Here is a changelog/roadmap for the upcoming 2.3.0 release:
https://issues.apache.org/jira/browse/JAMES?report=com.atlassian.jira.plugin.system.project:roadmap-panel
Here is a page about 2.3.0:
http://wiki.apache.org/james/JamesV2
James is not currently actively supported/sponsored by companies so its
future will depend on the visions of the committers but mainly from the
work of the *active* committers/volunteers.
Here is an "old" vision/roadmap page for V3:
http://wiki.apache.org/james/JamesV3
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org