nv-l
[Top] [All Lists]

[nv-l] Garbage attached to list post (was RE: [nv-l] Managing devices vi

To: James Shanks <jshanks@us.ibm.com>
Subject: [nv-l] Garbage attached to list post (was RE: [nv-l] Managing devices via their web interface)
From: "Zlatko Krastev" <acit@attglobal.net>
Date: Fri, 15 Aug 2003 01:29:45 +0300
Cc: nv-l@lists.tivoli.com
Delivered-to: mailing list nv-l@lists.tivoli.com
Delivery-date: Fri, 15 Aug 2003 11:39:53 +0100
Envelope-to: nv-l-archive@lists.skills-1st.co.uk
List-help: <mailto:nv-l-help@lists.tivoli.com>
List-post: <mailto:nv-l@lists.tivoli.com>
List-subscribe: <mailto:nv-l-subscribe@lists.tivoli.com>
List-unsubscribe: <mailto:nv-l-unsubscribe@lists.tivoli.com>
Mailing-list: contact nv-l-help@lists.tivoli.com; run by ezmlm
As the mail server serving the list is striping down all "Received:" 
headers I cannot investigate the actual source of the offending message. 
The only source is (unreliable) "From:" header.
But mailer-identification header also came through and had the value of 
"Internet Mail Service (5.5.2654.52)". This ought to explain why even the 
first (short) message instead of actual zip-file attachment was delivered 
in my Lotus Notes with nearly useless file named "attkjuba.dat". The 
question why I receive such garbage only from Exchange users is 
rhetorical.

16 months ago I've complained on tme10 list about couple of posts/replies 
with large files attached. As result the list-owner set a limit on the 
message size. Since then tme10 is just fine.

On ADSM-L list the things are even better:
-       list server does not stripe the headers and the investigation who 
is retransmitting particular message can be performed.
-       list distribution application is a lot smarter and compares new 
messages with recently distributed ones, effectively eliminating 
duplicates!!!

Probably you cannot move the list to VM, but message size limit ought to 
be easy to implement.

Zlatko Krastev
IT Consultant






James Shanks <jshanks@us.ibm.com>
14.08.2003 23:52

 
        To:     nv-l@lists.tivoli.com
        cc: 
        Subject:        RE: [nv-l] Managing devices via their web interface



Folks, 
I don't believe that it was Bernard's mail server that was at fault here. 
True, he inadvertently caused the problem by adding attachments to his 
note to the list, but it was not his mail server that kept returning them. 
Rather some other person subscribed to the list had a server which 
returned the original note, complete with its attachments, back to the 
list, after having added other attachments of its own indicating that it 
did not like getting the original ones.     Since this was posted to the 
list, the list then sent that out to all subscribers, including the server 
which returned the fist note.  It promptly returned the second and the 
cycle continued.  I don't know what ultimately stopped it.  Perhaps that 
server is now blocking mail for that user; I don't know.  But  I do know 
that I looked at the extended addressing in some of the notes I got and I 
think I know whose mail server it was , and it was not Bernard's.  I won't 
point fingers on the list but I will say that we should all avoid 
attaching anything for just this reason.  If you want to share files, you 
should do it directly and not thru the list.!  It's just not set up for 
this, and apparently neither are some of the other subscribers. 


James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group 

...


---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)


<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web