Java Mailing List Archive

Mailing List
Forum Home
JBoss - Java Application Server
Tomcat - JSP/Servlet container
Struts - A MVC web framework
iText - An open source PDF Java Library
JSP - A mailing list about Java Server Pages specification and reference
J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition
J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog
Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology
Struts & Hibernate
JSP editor plugin for eclipse ?
org apache jasper JasperException: Unable to compile class for JSP
Tomcat: Connection reset by peer: socket write error
Cannot retrieve definition for form bean null
Struts Tiles Tutorial (free Struts training)
Where do I download Tomcat 4 0 6?
Data Access Object (DAO) pattern, example DAO 's
Where to download Tomcat v 4 1 24 from?
Tomcat 5 0 16 Requested resource not available
Subject: Servlet : Session invalidate
Oracle Connection Pooling in 3 2 2
Servlet action is currently unavailable
Tomcat/Struts Unicode Encoding/Decoding problems
Subject: Running a Simple JMS Example
Tomcat and webapplication specific java library path
Mapping in workers2 properties
org apache jasper JasperException
problem with html:text bean throwing exception
Cannot find message resources under key org apache struts action
Cannot find message resources under key org apache struts action MESSAGE
invalid direct reference problem with solution
Tool for jsp debug Try Sysdeo Eclipse Plugin
Tomcat 5 Cannot load JDBC driver class 'null ' SQL state: null
weblogic ejbc
java properties file
Jboss 3 2 3 Coyote Can 't re
Tomcat 5, Apache2 and mod jk2 integration problem
JBoss example problem new to J2EE
Value attribute of <html:checkbox
url string for connecting jboss to oracle
javax servlet ServletException: BeanUtils populate
5 0 18: Windows XP Pro vs Windows 2000
HTTP Status 404 The requested resource is not available
Subscription probe for J2EEPATTERNS-INTEREST - please ignore

Subscription probe for J2EEPATTERNS-INTEREST - please ignore

2007-01-10       - By L-Soft list server at Sun Microsystems Inc. (1.8e)

Wed, 10 Jan 2007 06:00:05

This   message   is   a   "probe"    for   your   subscription   to   the
J2EEPATTERNS-INTEREST list. You do not need  to take any action to remain
subscribed to  the list, and in  particular you should not  reply to this
message. Simply discard it now, or read on if you would like to know more
about how this probing mechanism works.

A  "probe"  is a  message  like  the one  you  are  reading, sent  to  an
individual subscriber  and tagged  with a  special signature  to uniquely
identify  this  particular  subscriber  (you can  probably  not  see  the
signature because it is in the  mail headers). If the subscriber's e-mail
address is no longer valid, the  message will be returned to LISTSERV and
the faulty  address will be  removed from  the list. If  the subscriber's
address is still valid, the message will not bounce and the user will not
be deleted.

The main advantage  of this technique is that it  can be fully automated;
the list owner does not need to read a single delivery error. For a large
or active  list, the manpower  savings can  be tremendous. In  fact, some
lists are  so large that it  is virtually impossible to  process delivery
errors manually. Another advantage is that the special, unique signatures
make it possible to accurately process delivery errors that are otherwise
unintelligible, even to an experienced technical person.

The  drawback,  however,  is  that  this  method  lacks  flexibility  and
forgiveness. Since the Internet does not provide a reliable mechanism for
probing an  e-mail address without  actually delivering a message  to the
human  recipient, the  subscribers  need to  be  inconvenienced with  yet
another "junk message." And, unlike  a human list owner, LISTSERV follows
a number of  simple rules in determining when and  whether to terminate a
subscription. In  particular, a common  problem with automatic  probes is
mail gateways  that return a delivery  error, but do deliver  the message
anyway.  LISTSERV  has no  way  to  know that  the  message  was in  fact
delivered, and in most cases the subscriber is not aware of the existence
of these  "false" error reports.  If this  happens to you,  LISTSERV will
send you  another message with a  copy of the delivery  error returned by
your mail system, so that you can show it to your technical people.

©2008 - Jax Systems, LLC, U.S.A.