Serge, Danny etc,
> Yeah, I think we have enough votes. What do we do to get you added?
Well I am in. What I suggest is the following.
1) Tonight, I make changes in my local CVS mostly to build.xml. There
will be some trimming from libs/ and creation of a Phoenix-bin
directory. I should d
Hi Serge.
You again?
It was some indexing and retrieval reason that made me create the Tamino
mail repository. With the XML database in the back, a search on mails/news
can be done easily and fast.
I believe such functionality should not be implemented in James but the
different repositories by
Hi, Serge.
Actually I thought to have done so. It is clear for me that a transfer agent
needs to know about the domains it serves, and as you mentioned in another
mail this information cannot be obtained using DNS. But every computer
connected on the internet has a resolver library for name to ip
[I changed the topic, since it really has nothing to do with the LIBRARY
issue I had raised]
> the mail gets written to the spool only if the state is changed, which
means
> it needs to be transferred to the next processor. If the state is
unchanged,
> it won't be written back to the spool.
That
If u look at LinerProcessor service method
//See if the state was changed by the mailet
if (!mail.getState().equals(originalState)) {
//If this message was ghosted, we just want to let it die
if (mail.getState().equals(mail.GHOST)) {
Looking over his code, his reply object is not a MimeMessageWrapper instance
MimeMessage reply = new
MimeMessage(Session.getDefaultInstance(System.getProperties(), null));
so saveStream should be true, unless I'm overlooking something.
-Original Message-
From: Noel J. Bergman [mailto:[EM
Hi again,
> However, looking over his code, it did appear that isModified would be
true
> (it would have been set by any number of operations on the reply object).
you are right, but then take a look at next magic thing (line 146):
MimeMessageWrapper.writeTo(OutputStream os)
in this method it o
> 2. Check if your mailet is setting the state correctly to be
>written back to the spool & transferred to the next mailet.
How does one do that? The examples I've seen appear to show new messages
being re-posted, and the old message being ghosted. He isn't doing that; he
appears to be tryi
Oh good point ... and if it IS a MimeMessageWrapper instance, then the code
would be active.
However, looking over his code, it did appear that isModified would be true
(it would have been set by any number of operations on the reply object).
--- Noel
-Original Message-
From: An
This is probably most obvious & most likely u must have tried it, but just
in case. Have u made sure u're chaining the mailets correctly & your config
file has correct entries for ur mailet? Make sure the foll. is happening
1. Your mailet is being invoked.
2. Check if your mailet is setting the st
I think it is always instance of MimeMessageWrapper if you obtain it as
mail.getMessage()... in mailet...
Andrei
>
> Seems to me that if the MimeMessage is NOT a MimeMessage wrapper, then
> saveStream is TRUE by default and writeMessageTo will be called.
>
> Mind you, I have NOT traced all of the
I think it is always instance of MimeMessageWrapper if you obtain it as
mail.getMessage()... in mailet...
Andrei
>
> Seems to me that if the MimeMessage is NOT a MimeMessage wrapper, then
> saveStream is TRUE by default and writeMessageTo will be called.
>
> Mind you, I have NOT traced all of the
Are you saying that his code:
//Pass the revised MimeMessage for further processing...
mail.setMessage(reply);
is too naive, and needs to be something like:
//Send it off...
getMailetContext().sendMail(sender,recipients,reply);
if (! getPassThrough()) mail.setState(Mail.GHO
Just hasy guess, you asked:
> Why hasn't the method updated the message
MimeMessages from MailImp are stored to stream repository by means of
MimeMessageWrapper, while other content of MailImpl is stored to object
repository. Check the AvalonMailRepository where "magic" happens.
So when you mod
I would appreciate it if anyone can provide some useful input into this
issue.
Thanks,
Sam.
>From: "Samuel Sadek" <[EMAIL PROTECTED]>
>Reply-To: "James Users List" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: Matcher/Mailet Library
>Date: Tue, 14 May 2002 18:56:45 +0100
>
>Noel,
>
> I have resolved this issue throught the creation of special processing
> mailet which reformats all binary content type mimebodypart attachments to
a
> fixed length of 76 characters. This was needed for IMAP protocol
processing
> because it cannot handle 60 character widths sent from Hotmail.com
I think you'll find it helpful if you go read about how DNS works.
--
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com/
Chaudhuri, Hiran wrote:
> Hi, David.
>
> Isn't it the operating system's task to determine IP-address and
> DNS-servers? Either the admin conf
Hi, Shilpa.
How about stripping the caching functionality of your filememrepository to a
cacherepository instead? This cacherepository could then cache the messages
and send them to another real persistent repository, thus making the cache
functionality pluggable to all available repositories.
H
Hi, Serge.
Thank you for that answer. I was on vacation myself now and am just catching
up.
My current repository implementation is not sophisticated, but it did not
require changes in existing classes. Attached you find the classes I created
and the Tamino database schema I used to store the da
Hi, David.
Isn't it the operating system's task to determine IP-address and
DNS-servers? Either the admin configured everything for a machine, or she
chose to use DHCP on that. I never understood why a mail transfer agent like
James or Sendmail needs special settings for DNS.
Hiran
20 matches
Mail list logo
