Re: Protocol Event sink

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Razzie (razzie_at_quicknet.nl)
Date: 09/21/04

  • Next message: Siu: "WEB APPLICATION AND WORKFLOW ON EXCHANGE SERVER 2003" 
    Date: Tue, 21 Sep 2004 10:04:11 +0200

    Peter, thank you very much for the reply.

    It's too bad you can't get the server to ignore a command. A client is
    waiting for a response, but a response could easily be an error code.

    I guess I'll have to look at something else. What is _EOD? I have no clue :)
    Do you know what event sink would best fit my needs? I can't use the
    OnArrival sink I think, because the recipient should be discarded BEFORE the
    mail is sent. I was thinking of PostCategorize, I hope you can shine a light
    on this!

    Again, thanks for your reply, I asked this question a million times and
    didn't get a good resonse so far :)

    Razzie

    "Peter Karsai" <peter.karsai@enternet.hu> wrote in message
    news:e4fCYm0nEHA.1160@tk2msftngp13.phx.gbl...
    > Hi Razzie,
    >
    > I don't think you can get IIS SMTP to "ignore" the command. In a protocol
    > event sink, the client is waiting for response and that response may be
    > set
    > by an event sink or the SMTP Service itself, but there _must_ be a
    > response
    > (or you must close the connection by setting the command status to
    > EXPE_DROP_SESSION).
    >
    > An alternative approach could be to hook _EOD for example and rewrite the
    > recipient list so the unwanted recipients can be removed. I guess you
    > can't
    > do that from an RCPT hook as the recipient is added to the envelope after
    > all sinks are evaluated (<-- mere speculation, but sounds logical :).
    >
    > Peter Karsai
    > http://www.vamsoft.com/orf
    >
    > "Razzie" <razzie@quicknet.nl> wrote in message
    > news:eEnfjSjnEHA.3352@TK2MSFTNGP15.phx.gbl...
    >> Hey all,
    >>
    >> Simple question me thinks, but can't seem to find the solution.
    >>
    >> I have a protocol event sink and listen for the RCPT command. If the
    >> recipient has a certain email address I simply want to discard that
    > command.
    >> It seems I can only terminate the complete session by throwing an
    > exception.
    >> I just want the smtp server / session to ignore a command. I have tried
    >> setting the Command / Server status to 550, S_Ok, EXPE_CONSUMED,
    >> whatever,
    >> but that still consumes the command!
    >>
    >> Please help! Thanks in advance.
    >>
    >> Razzie
    >>
    >>
    >
    >

  • Next message: Siu: "WEB APPLICATION AND WORKFLOW ON EXCHANGE SERVER 2003"

    Relevant Pages

    • Re: Protocol Event sink
      ... It's too bad you can't get the server to ignore a command. ... waiting for a response, but a response could easily be an error code. ... Do you know what event sink would best fit my needs? ... because the recipient should be discarded BEFORE the ...
      (microsoft.public.exchange2000.development)
    • Re: Protocol Event sink
      ... I don't think you can get IIS SMTP to "ignore" the command. ... event sink, the client is waiting for response and that response may be set ... recipient list so the unwanted recipients can be removed. ...
      (microsoft.public.exchange2000.development)
    • Re: Protocol Event sink
      ... I don't think you can get IIS SMTP to "ignore" the command. ... event sink, the client is waiting for response and that response may be set ... recipient list so the unwanted recipients can be removed. ...
      (microsoft.public.exchange.development)
    • Re: Protocol Event sink
      ... If I use my own SMTP server and I type a non-existing recipient, ... recipient' or something like that. ... > waiting for a response, but a response could easily be an error code. ... >> event sink, the client is waiting for response and that response may be ...
      (microsoft.public.exchange2000.development)
    • Re: Protocol Event sink
      ... If I use my own SMTP server and I type a non-existing recipient, ... recipient' or something like that. ... > waiting for a response, but a response could easily be an error code. ... >> event sink, the client is waiting for response and that response may be ...
      (microsoft.public.exchange.development)