In data 08 aprile 2009 alle ore 10:44:53, Corrado Alesso
<[email protected]> ha scritto:
Thank you, actually this point of view made me understand better the
problem.
I'm trying to prevent the scenario number 2. That is, prevent the
processing of mails sent by users hosted by me to users hosted somewhere
else. Instead, every mail coming from outside should be processed. So,
maybe, RecipientIsLocal is the matcher I need.
I'll try this and let you know.
Thank you,
Corrado
Unfortunately, this is not going to work.
I just realized that actually I do not have repicient to match the mail
against.
Let's me explain a little bit in detail...
I'm developing a web application, and the data it is going to consume
comes from emails.
For example, people can send emails with data to random addresses like:
a...@mydomain, eve...@mydomain, ran...@mydomain, but there are no users in
the system called 'abc', 'event1' or 'random', and this is OK. I just want
to process the emails, get the recipient they have (abc, event1, etc),
save the data to db, and then send back to the original sender a
confirmation email. What happens here is that, when I send the
confirmation email back, that email get processed, and this is what I want
to avoid (the mathcer for my custom Mailet is, at the moment, All).
The RecipientIsLocal matcher is not good, because I have no users in the
system.
Any idea is appreciated, thank you in advance.
Corrado
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
