Hey there,
I thought I would ask before spending tonight researching.
Is there an "easy" way to trigger a bounce from the the Mail storage step?
For instance, mail has arrived for user Z, but now I notice that I can't write
it. I want to bounce it back to the sender as undeliverable.
If I thr
Eric,
Yes, thanks for the correction, I mean empty MAIL FROM (in other words "MAIL
FROM <>".
You are already handling the situation where a mail client/relay is not
passing a MAIL FROM at all properly (by responding with "503 5.5.0 Need MAIL
before RCPT").
I'll open the ticket and be more prec
We pulled down 3.0 beta 5 and rolled it in and tested ... timestamp now
working great!
Thanks a ton!
Aaron
> -Original Message-
> From: Eric Charles [mailto:e...@apache.org]
> Sent: Tuesday, June 26, 2012 4:03 AM
> To: James Users List
> Subject: Re: James 3.0 - beta 4 Date/Time Proble
Hi Aaron,
Yes, please open the ticket on JAMES.
I suppose you mean 'empty' MAIL FROM, and not 'null'.
In other words, in case of MAIL FROM command not issued, do we have to
throw and exception, and if yes, which one?
(sorry, no time atm to dig into the RFC)
Thx, Eric
On 06/26/2012 05:57 PM,
I'm not sure the usage of "ToSenderFolder" in "mailetcontainer.conf" is
correct.
Here is the code:
Sent
false
I think that matcher should match known senders, not any local recipient.
I'm not sure what is the exact matcher for that, maybe "SMTPAuthSuccessful"
?
I'll be happy to open a ticket (though I haven't done one before so don't
hate me if I screw it up a bit) -- which component do you think is more
appropriate, JAMES or PROTOCOL? I'll essentially just include this thread,
including Stefano's responses -- I can't add much beyond his statement that
R
2012/6/26 Eric Charles :
> I was supposing that, but didn't take time to point the exact line in the
> RFC.
This is all best summed up by section 5.2.9 of RFC1123, which says:
The syntax shown in RFC-821 for the MAIL FROM: command omits the case
of an empty path: "MAIL FROM:<>" (see RFC-821 P
2012/6/26 Eric Charles :
> On 06/26/2012 11:07 AM, Stefano Bagnara wrote:
>> "MAIL FORM:<>" is REQUIRED to work. This is the way DSN bounce are
>> delivered.
>> Mailservers not supporting this "sender" are listed by
>> http://www.rfc-ignorant.org/
>
> I was supposing that, but didn't take time to p
On 06/26/2012 11:07 AM, Stefano Bagnara wrote:
2012/6/26 Eric Charles:
Hi Aaron,
Sorry to return you the question, but what does SMTP RFC
(http://www.ietf.org/rfc/rfc2821.txt) tells about empty mails? (is it
allowed?)
I was supposing that, but didn't take time to point the exact line in
th
2012/6/26 Eric Charles :
> Hi Aaron,
>
> Sorry to return you the question, but what does SMTP RFC
> (http://www.ietf.org/rfc/rfc2821.txt) tells about empty mails? (is it
> allowed?)
"MAIL FORM: <>" is REQUIRED to work. This is the way DSN bounce are delivered.
Mailservers not supporting this "send
Hi Aaron,
Sorry to return you the question, but what does SMTP RFC
(http://www.ietf.org/rfc/rfc2821.txt) tells about empty mails? (is it
allowed?)
In any case, it would be better to a more specific and throw an
exception with a correct readable message.
Based on your finding, it will be go
This is a bug which is fixed in trunk (see PROTOCOLS-96).
You should be able to test the fix with the latest snapshot to download
from
https://repository.apache.org/content/repositories/snapshots/org/apache/james/apache-james/3.0-beta5-SNAPSHOT/
(I hope this one will have my latest commit:
h
Hello Gufiya,
It should be fixed in 3.0-beta5 (unreleased). To fix bet4 change
wrapper.conf and add conf/lib to the classpath (or use run.sh to start
james which builds the classpath ok).
https://issues.apache.org/jira/browse/JAMESAPP-8
Cheers,
2012/6/26 gufiya :
>
> I have the same problem her
I have the same problem here.
Here is a flow to reproduce it:
1. Download James3-beta4
2. Update "james-database.properties" to use MySQL
3. Put "mysql-connector-java-5.1.18-bin.jar" in conf/lib dir
4. Install service with "james install" script
5. Run James with "james start" script
5. Same probl
14 matches
Mail list logo