hi,
please excuse my posting, just seconds after hitting the send button I
realized, that I had forgot to call super.init(config)...
oh my!
thx
philipp
> -Original Message-
> From: Philipp Salzgeber
> Sent: Montag, 16. Februar 2004 08:50
> To: James Developers List
> Subject: initial
hi,
I am developing a mailet and want to initialize it with parameters from
config.xml...
in config.xml I have the following parameters:
queue/SomeQueue
org.jnp.interfaces.NamingContextFactory
jnp://localhost:1099
when I try to call:
Serge Knystautas wrote:
>
> Steve Brewin wrote:
> > There is a boundary case where the hostname in the received
> header cannot be
> > resolved. This used to always treat the mail as
> undeliverable. Now there's
> > an option to inject it. The fix just applied ensures that
> in this case, or
> > an
> > I don't know of any reason not to use a tool, but we should make sure of
> > Avalon's plans.
> Fine, I will wait for his response.
Nah, go ahead and do it. If we have to change from @phoenix to some other
tag format, we'll just make that change.
--- Noel
--
Steve Brewin wrote:
There is a boundary case where the hostname in the received header cannot be
resolved. This used to always treat the mail as undeliverable. Now there's
an option to inject it. The fix just applied ensures that in this case, or
any future case, where the remote address or host ca
> I don't know of any reason not to use a tool, but we should make sure of
> Avalon's plans. Hopefully they are maintaining compatibility as they add
> JMX into Merlin. I looked at http://avalon.apache.org/merlin, the Avalon
> Wiki, and the mailing lists, but couldn't find anything other than som
> Noel J. Bergman wrote:
> > > I am just getting ready to commit Steve Shorts JMX extensions.
> > To where? MAIN?
> Well both MAIN and branch_2_1_fcs
Ah, that's cool. :-)
> > > The patch removes the need to handcode the .mxinfo files by using the
> > > Phoenix supplied doclet
> > Is this a bui
Noel J. Bergman wrote:
>
> Does this open any concerns that such messages could leak out
> of the system
> because they would appear to be locally generated?
Fair question. The short answer is no, these changes do not alter what mail
is fetched and injected into James.
In fact, by default, fetchm
On Sunday 15 February 2004 00:14, Noel J. Bergman wrote:
> > I am just getting ready to commit Steve Shorts JMX extensions.
>
> To where? MAIN?
Well both MAIN and branch_2_1_fcs, is that not what you prefer?
or would you rather have that I wait until the merger has finished?
>
> > The patch remo
Steve,
> +if (getRemoteAddress() == null || getRemoteHostName() == null)
> +{
> +mail.setRemoteAddr("127.0.0.1");
> +mail.setRemoteHost("localhost");
> +}
Does this open any concerns that such messages could leak out of the system
because they
Message:
The following issue has been resolved as FIXED.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-152
Here is an overview of the issue:
The following issue has been updated:
Updater: Steve Brewin (mailto:[EMAIL PROTECTED])
Date: Sun, 15 Feb 2004 6:38 AM
Changes:
Version changed from 2.2.0a15
Version changed to 2.2.0a16
sbrewin 2004/02/15 06:37:09
Modified:src/xdocs fetchmail_configuration_2_2.xml
src/java/org/apache/james/fetchmail MessageProcessor.java
Log:
Ensure mail is always created with a remote address and remote hostname.
See http://nagoya.apache.org/jira/secure/ViewIs
sbrewin 2004/02/15 06:36:08
Modified:src/xdocs Tag: branch_2_1_fcs
fetchmail_configuration_2_2.xml
src/java/org/apache/james/fetchmail Tag: branch_2_1_fcs
MessageProcessor.java
Log:
Ensure mail is always created with a re
14 matches
Mail list logo
