[
https://issues.apache.org/jira/browse/JSPF-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293937#comment-13293937
]
Hontvari Jozsef commented on JSPF-55:
-
I have implemented SRS in Mireka a while
[
https://issues.apache.org/jira/browse/JAMES-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707277#action_12707277
]
Hontvari Jozsef commented on JAMES-901:
---
I met the same problem 1-2 years ago an
The current 2.3.1 cannot be compiled using ant compile-main, because
mordred PoolConnEntry assumes a very old version of java.sql.Connection.
Is this correct?
compile-main:
[javac] ...\src\java\org\apache\james\util\mordred\PoolConnEntry.java:37
: org.apache.james.util.mordred.PoolConnEntry
Robert Burrell Donkin írta:
1. i know that quite a lot of the IMAP/mailbox stuff is junk (both
mine code and the old stuff). IMAP/mailbox is most of trunk. so yes, a
substantial quantity of code in trunk is junk. a more important issue
is that it's difficult to gain consensus on the production
Considering the low frequency of releases and the small number of new
features, the version management structure of James seems to be an
overkill.
(Or maybe I just don't understand the system.)
Although I don't think this is new for anybody here is the simplest
procedure:
The trunk receives al
[
http://issues.apache.org/jira/browse/JAMES-52?page=comments#action_12313376 ]
Hontvari Jozsef commented on JAMES-52:
--
I think this is simply a bug in IIS. If IIS supports 8bitmime then it must be
able to forward (and convert) it to non-8bitmime mail
I forgot to mention: It doesn't check for abuse@, only postmaster@ and
the email address used in the error message is hard coded.
Hontvari Jozsef wrote:
Maybe it helps, I have attached the source which we use for about a
year. I cannot create a standard patch because my last workspa
Maybe it helps, I have attached the source which we use for about a
year. I cannot create a standard patch because my last workspace is
based on the now non-existent cvs repository.
The code must be inserted before these lines into the SMTPHandler.java file:
if (authRequired) {
I don't know what is in subversion now. In order to continue we only need
one thing as the absolute minimum: the current 2.1 (or 2.2? I assume these
two are same) head in the subversion trunk directory. Everything else
(current production release, current head) should be left at its current
place.
the merging process, which took almost 2 years (until now) will kill James,
if it hasn't killed it already. Nobody knows which is the real head branch,
etc.
It would be better if you rename 2.1(?), which is the production version
(almost), and officially abandon the current head. If somebody wa
> Thoughts? Has anyone other than Danny had time to look at the reverse
path
> handling changes? Vincenzo, you need for me to commit these bounce castle
I also read it carefully and it seems to be correct (but I didn't noticed
that subtle bug you mentioned). However the hardest part is to justif
There are is reference to an email in the first (and also in the last)
sentence of the description, that email includes both the fix and the
analysis, which may answer your question.
"Related email thread:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=11183"
- Original Message --
If someone would try to use the email list mailets with non-local users then
he will very soon change his mind because of the catastrophic "JAMES-264
UNRESOLVED mail list loop caused by using Return-Path" bug.
In the description of the issue I included a quick fix, which consists of
about 5 lines
"null sender" is explicitly mentioned in the smtp rfcs, so it is intuitive
if the null sender corresponds to (java) null. A counter argument could be
if null has another meaning, i.e. if it indicates unknown/not assigned, but
then the null pointer cannot be eliminated for that reason. The null send
(I am not sure what is the status of the merge, so I don't send a patch now,
and anyway, you may not agree on my evaluation)
org.apache.james.James class has a bounce method, which is intended to be
used for bouncing invalid emails to the reverse path (i.e. the email address
supplied in the SMTP M
It seems to me that this line is not correct:
if (timeToSleep < 0) {
I think it should be "<=". Otherwise if timeToSleep is (accidentally) 0, the
following wait() will wait undefinitely, according to its specification.
-
To uns
I was thinking about this too, I guess most of the work comes from the
requirement, that if you accept 8bitmime, then you have to be able to
convert it to 7bit, because a recipient server may not support 8bitmime.
- Original Message -
From: "Craig Raw" <[EMAIL PROTECTED]>
To: <[EMAIL PROT
Now again in zip.
- Original Message -
From: "Hontvari Jozsef" <[EMAIL PROTECTED]>
To: "James Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, October 29, 2003 10:38 PM
Subject: [PATCH] GenericListServ, reversePath can be specified
> This is a
This is a small patch which makes possible to specify a reversePath in
descendant classes. Until now postmaster was used always and the bounces got
on my nerves :)
It is against the 2.1 branch.
-
To unsubscribe, e-mail: [EMAIL PR
(on bounces I also mean failed attempts, before the configured retry attemps
ended, this event could be used for such a notification)
- Original Message -
From: "Hontvari Jozsef" <[EMAIL PROTECTED]>
To: "James Developers List" <[EMAIL PROTECTED]>
Sent:
I am not against this patch, actually this was one of the most important
missing features for me. The current configuration is better in one (and
only one) issue, it does provide feedback after about a day to the sender.
I have no idea about the implementation of DSN, but sending bounces to a
proc
I think it causes more trouble then benefit if it delays a mail for not less
then 5 days _without_ notifying the sender after 24 hours, saying that "I am
James, your email is delayed, but I am still trying to deliver".
- Original Message -
From: "Noel J. Bergman" <[EMAIL PROTECTED]>
To: "
www.mailet.org doesn't seem to be working, a domain registrator's page is
displayed instead of actual content.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
By the way, when I updated from cvs, javamail and activation was missing,
but the ant build created the sar file without any error message.
- Original Message -
From: "Steve Brewin" <[EMAIL PROTECTED]>
To: "James Developers List (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, September 24
From: "Noel J. Bergman"
> Is this something that we want in CVS?
sure
> One thing that bothers me is that passing a list as a configuration string
> is a hardcoded mechansim, whereas someone might have the same data in a
> file, DNS zone, etc., but that is not unique to this Matcher.
yes, but i
IsImpersonallySent matcher could also be really useful for a different
purpose, filtering out false virus bounces coming to an innocent email
address.
>(vi) the sender is not the postmaster and
and not a [EMAIL PROTECTED]
>(viii) the recipient is listed in the To header and
if the user forwards
>There is nothing to "propose." If you want it, just do it.
yes, I did it for myself, and I find it useful. My proposal was to make this
the default configuration. I have attached my original mail.
Regarding the "turn on DEBUG" part, the default log level, INFO, should
contain more info. I think
> Steven Short suggested that some people might prefer to have all of the
> messages sequential in a single log. On the other hand, that doesn't
> highlight the sequence that happens to a single message if that processing
> is interleaved with other things over a wide amount of time.
I also propo
James has about 10 log files now, and I usually have no idea in which one
should I look for a specific entry - even after using james for a few moths
and having some practice with the source code. The mail software I used
before only had one log file, and I found that better. Finally I changed
Jame
; Stick it in a .ZIP and send again.
>
> --- Noel
>
> -----Original Message-
> From: Hontvari Jozsef [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 02, 2003 17:49
> To: James Developers List
> Subject: Re: [PATCH] null pointer exception if mail without subject header
>
something is wrong with the new list, look at the raw body of my previous
letters, somehing strips the body of the attachment.
- Original Message -
From: "Hontvari Jozsef" <[EMAIL PROTECTED]>
To: "James Developers List (E-mail)" <[EMAIL PROTECTED]>
Sent: W
again, although I did attach the patch...
- Original Message -
From: "Hontvari Jozsef" <[EMAIL PROTECTED]>
To: "James Developers List (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, July 02, 2003 11:39 PM
Subject: [PATCH] null pointer exception if mail
1 code + 2 javadoc lines changed, the charset aware subject replacing
function didn't handle correctly mails which had no subject. The result was
a NPE if the prefix configuration parameter was set on an AbstractRedirect
or GenericListserv descendant and a mail was received without a subject
header
33 matches
Mail list logo
