You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Norman Maurer <nm...@byteaction.de> on 2006/08/28 19:58:26 UTC
RE: [jira] Commented: (JAMES-597) Add rcpthandler to map
virtualusers before call ValidRcptHandler
Am Montag, den 28.08.2006, 13:40 -0400 schrieb Noel J. Bergman:
> > I don't think that its a good idea to do the mapping in fastfail. I
> > think the best way at the moment whould be to check for valid mappings
> > only.
>
> Why?
>
Cause we still whould need the mailet stuff anyway if we want to use
fetchpop.
> Regardless, we still need to make sure that we don't assume that something
> like:
>
> error:550 Requested action not taken: no such user here
>
> is not mistaken for a virtual user mapping.
Sure that is what i just workin on. I will commit later so you can see.
I think if we really want to do the mapping here we can change the code
easy later.
>
> --- Noel
bye
Norman
Re: Processor Flexibility Enhancements
Posted by Bernd Fondermann <be...@googlemail.com>.
+1
(will there be unit tests?)
On 8/28/06, Noel J. Bergman <no...@devtech.com> wrote:
> One of the things I'd like for us to do is change the SMTP handler to allow
> specifying the entry point for injecting messages into the pipeline, rather
> than the hardcoded "root", and likewise for FetchMail. So messages coming
> from FetchMail might enter the pipeline in a different processor, and go
> through a different route before merging at a delivery point.
>
> Related to that, I'd like to enhance ToProcessor to allow:
>
> <mailet class="ToProcessor">
> <from-attribute>some.attr.name</from-attribute>
> <processor>some-default-processor</processor>
> </mailet>
>
> which would send the mail to the processor specified in the attribute, and
> to the named processor if the attribute isn't present. I might have that
> default processor set to send a warning to the administrator, and record the
> message into a holding repository for later respooling after the
> configuration error has been corrected.
>
> --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Processor Flexibility Enhancements
Posted by Norman Maurer <nm...@byteaction.de>.
Maybe you should look at Stefanos idea how we can do this. It sounds
easier and cleaner for me...
And yes you are right we need mre junit tests.
bye
Norman
Bernd Fondermann schrieb:
> +1
>
> (will there be unit tests?)
>
> On 8/28/06, Noel J. Bergman <no...@devtech.com> wrote:
>> One of the things I'd like for us to do is change the SMTP handler to
>> allow
>> specifying the entry point for injecting messages into the pipeline,
>> rather
>> than the hardcoded "root", and likewise for FetchMail. So messages
>> coming
>> from FetchMail might enter the pipeline in a different processor, and go
>> through a different route before merging at a delivery point.
>>
>> Related to that, I'd like to enhance ToProcessor to allow:
>>
>> <mailet class="ToProcessor">
>> <from-attribute>some.attr.name</from-attribute>
>> <processor>some-default-processor</processor>
>> </mailet>
>>
>> which would send the mail to the processor specified in the
>> attribute, and
>> to the named processor if the attribute isn't present. I might have
>> that
>> default processor set to send a warning to the administrator, and
>> record the
>> message into a holding repository for later respooling after the
>> configuration error has been corrected.
>>
>> --- Noel
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
> !EXCUBATOR:1,450b06ff53071982917462!
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: [jira] Commented: (JAMES-597) Add rcpthandler to mapvirtualusers before call ValidRcptHandler
Posted by "Noel J. Bergman" <no...@devtech.com>.
Norman Maurer wrote:
> Cause we still would need the mailet stuff anyway if we
> want to use fetchpop.
Not necessarily. See my message about "Processor Flexibility Enhancements".
> > Regardless, we still need to make sure that we don't assume that
> > something like:
> > error:550 Requested action not taken: no such user here
> > is not mistaken for a virtual user mapping.
> Sure that is what i just working on. I will commit later so you can see.
> I think if we really want to do the mapping here we can change the code
> easy later.
+1 :-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Processor Flexibility Enhancements
Posted by Stefano Bagnara <ap...@bago.org>.
Using the fastfail MessageHandler filter it should be possible to call
the setState for the message being received and the message would be
posted to that repository: wouldn't this be enough?
Stefano
Noel J. Bergman wrote:
> One of the things I'd like for us to do is change the SMTP handler to allow
> specifying the entry point for injecting messages into the pipeline, rather
> than the hardcoded "root", and likewise for FetchMail. So messages coming
> from FetchMail might enter the pipeline in a different processor, and go
> through a different route before merging at a delivery point.
>
> Related to that, I'd like to enhance ToProcessor to allow:
>
> <mailet class="ToProcessor">
> <from-attribute>some.attr.name</from-attribute>
> <processor>some-default-processor</processor>
> </mailet>
>
> which would send the mail to the processor specified in the attribute, and
> to the named processor if the attribute isn't present. I might have that
> default processor set to send a warning to the administrator, and record the
> message into a holding repository for later respooling after the
> configuration error has been corrected.
>
> --- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Processor Flexibility Enhancements
Posted by Norman Maurer <nm...@byteaction.de>.
Yes this should work.. Good idea..
bye
Norman
Stefano Bagnara schrieb:
> Using the fastfail MessageHandler filter it should be possible to call
> the setState for the message being received and the message would be
> posted to that repository: wouldn't this be enough?
>
> Stefano
>
> Noel J. Bergman wrote:
>> One of the things I'd like for us to do is change the SMTP handler to
>> allow
>> specifying the entry point for injecting messages into the pipeline,
>> rather
>> than the hardcoded "root", and likewise for FetchMail. So messages
>> coming
>> from FetchMail might enter the pipeline in a different processor, and go
>> through a different route before merging at a delivery point.
>>
>> Related to that, I'd like to enhance ToProcessor to allow:
>>
>> <mailet class="ToProcessor">
>> <from-attribute>some.attr.name</from-attribute>
>> <processor>some-default-processor</processor>
>> </mailet>
>>
>> which would send the mail to the processor specified in the
>> attribute, and
>> to the named processor if the attribute isn't present. I might have
>> that
>> default processor set to send a warning to the administrator, and
>> record the
>> message into a holding repository for later respooling after the
>> configuration error has been corrected.
>>
>> --- Noel
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
> !EXCUBATOR:1,45093a3545111352054979!
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Processor Flexibility Enhancements
Posted by "Noel J. Bergman" <no...@devtech.com>.
One of the things I'd like for us to do is change the SMTP handler to allow
specifying the entry point for injecting messages into the pipeline, rather
than the hardcoded "root", and likewise for FetchMail. So messages coming
from FetchMail might enter the pipeline in a different processor, and go
through a different route before merging at a delivery point.
Related to that, I'd like to enhance ToProcessor to allow:
<mailet class="ToProcessor">
<from-attribute>some.attr.name</from-attribute>
<processor>some-default-processor</processor>
</mailet>
which would send the mail to the processor specified in the attribute, and
to the named processor if the attribute isn't present. I might have that
default processor set to send a warning to the administrator, and record the
message into a holding repository for later respooling after the
configuration error has been corrected.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org