> list
> request
> requesting user - the user who sent the mail/made the request
> victim - the address that the request acted on
> command line - includes the modes and such
> interface - shell, email, web, etc.
> status - succeed, fail, stall for confirmation
> passworded - was a password used
> time - when it happened
Hi Jason,
Just another idea. I'm not sure if this is covered within your interface
line or not.
Referrer???
I'd like to know what web page the client used to process the commands. A
slot for an IP # would be the key I'm looking for I think.
With the majorcool and the mailserv things working -- and then there are
other sites who could be doing the same type of things. ... Subscribers
could come to the list from an other sources. I want to track where
people are learning about and signing onto my lists. Perhaps there is a
list-of-lists service that gives users the opportunity to subscribe and
unsubscribe as well as listing the contact info. I'd like to know how
those folks found the list.
--------------
Mark Rauterkus, Publisher, S.S.S. http://www.sportsurf.net
mrauterkus@sportsurf.net http://www.SportSurf.Net/FootNotes
FootNotes: Mac E-book authoring and distribution environment with
built-in multi-media, lan, web, internet and e-mail capabilities.
--------------
Follow-Ups:
|
|
