Re: POP3Server. How to separate the commands and the data of TIdServerInterceptL

Giganews Newsgroups
Subject: Re: POP3Server. How to separate the commands and the data of TIdServerInterceptL
Posted by:  Remy Lebeau (TeamB) (no.spam@no.spam.com)
Date: Thu, 20 Oct 2005

"Pedro" <pizquierdo20…@hotmail.com> wrote in message
news:08F69958ACDEE240pizquierdo20…@hotmail.com...

> How to detect in TIdServerInterceptLogEvent when
> the line is a command of protocol or is data transfer?

Indy's logging system is not designed for what you are asking for.  It is
designed to log all data as-is without any filtering.  You have to handle
any filtering yourself.  To do what you are asking, y have to manually parse
all of the POP3 traffic that the log component receives, looking for the
DATA command.  You can then set a flag somewhere that tells your code to
ignore the rest of the traffic data until a terminting CRLF+'.'+CRLF is
detected, at which point you reset the flag and continue processing the
traffic data as needed.

Gambit

Replies

In response to

POP3Server. How to separate the commands and the data of TIdServerInterceptLogEv posted by Pedro on Thu, 20 Oct 2005