LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

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

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

Print Reply
Eric Thomas <[log in to unmask]>
Wed, 29 Jun 1994 15:57:21 +0200
text/plain (36 lines)
On Wed, 29 Jun 1994 08:36:09 CET Hans-Ulrich Giese <[log in to unmask]>
said:
 
>questions are now :
>   - is the receiving MTA in trouble ?
>   - is FAL/SMTP in error ?
>   - is this a listserv problem ?
>   - is there a way to circumvent the problem ?
>
>HELP !!!
 
It is a religious question, with only religious answers.
 
Answer 1 is that it is LISTSERV's fault for not using MIME.
 
Answer 2 is that MIME does not  attempt to claim that everyone should use
MIME, and it is technically possible for  anyone to send a message to FAL
with binary  characters (note that  such "binary" characters  can include
national characters in  some countries), so FAL should be  able to handle
them. So it is the fault of FAL for not deleting these characters.
 
Answer  3 is  that, since  FAL is  not ESMTP-capable,  the receiving  MTA
cannot possibly have  negotiated any of the extended SMTP  options. So it
should just swallow what FAL sends as is, and should not complain. If the
high-order bit is on, it should either take it in or turn it off.
 
Answer 4 is that it is the fault of X.400 users for not using SMTP.
 
Answer 5 is that it is the fault of the Internet for not using X.400.
 
You can choose any  of the answers you like, they  are all equally valid.
And there is  no solution to your problem besides  using F=MIME or fixing
the MTA (if you selected answer 3).
 
  Eric

ATOM RSS1 RSS2