LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (22 lines)
Print Reply
Mime-Version:
1.0
Sender:
LISTSERV list owners' forum <[log in to unmask]>
Subject:
From:
Pete Weiss <[log in to unmask]>
Date:
Sun, 27 Apr 2003 10:47:48 -0400
In-Reply-To:
Content-Type:
text/plain; charset="us-ascii"; format=flowed
Reply-To:
LISTSERV list owners' forum <[log in to unmask]>
At 10:40 04/27/2003 Sunday, rex wrote:
 >Pete Weiss <[log in to unmask]> [2003-04-27 07:21]:
 >>
 >> I just tried an in-line image (attachments= no) on my test list and it
 >> was rejected:
 >>
 >> Your posting to the L-PETE list has been rejected because it contains an
 >> attachment of type 'IMAGE/GIF'. The L-PETE list has been configured to
 >> reject such attachments ...
 >
 >Looks as if it wasn't in-line to me. If there's no MIME info LISTSERV
 >wouldn't be able to distinguish the (encoded) image from the rest of the
 >text.
 >
 >Perhaps I don't understand what you mean by in-line...

I don't have the technical jargon for describing this, but I can have out
of line images (attachments) that appear as clickable icons; or I can
embed images within the text which are visable as-is.

I think LISTSERV "attachments="  processing treat these identically.

ATOM RSS1 RSS2