headers
Jack De Winter | 1 Jan 1997 20:04
Picon

Re: e mail

Um, this is a discussion group on SMTP, but I will respond to you
in private email.

regards,
Jack

At 12:52 PM 1/1/97 +0000, ben wrote:
>hi,
>
>I am looking for a way to include email parameters in html eg..
>
>mailto:WHATEVER YOUR E-MAIL ADDRESS IS! ?subject=You can also put an
automatic 
>subject here!
>
>I want to know if there is a parameter for contents as well.
>
>Thanks in advance..
>-- 
>ben
>
>http://personal.pitnet.net/bluesky/snow.dcr
>
>
>
-------------------------------------------------
Jack De Winter - Wildbear Consulting, Inc.
(519) 576-3873		http://www.wildbear.on.ca/

Author of SLMail(95/NT) (http://www.seattlelab.com/) and other great products.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ones-And-Zeros | 6 Jan 1997 08:45
Picon

! MASS POST Was Here! (RdTSpJ)

MASS POST--the program by Ones and Zeros--has been used to send this message 
to thousands of newsgroups.

(RdTSpJ)
From Edward.M.Greshko <at> cdc.com Mon Jan  6 04:40:46 1997
Received: from dimacs.rutgers.edu (dimacs.rutgers.edu [128.6.75.16]) by list.cren.net
(8.7.6/8.6.12) with SMTP id EAA07660 for <ietf-smtp <at> list.cren.net>; Mon, 6 Jan 1997 04:40:45 -0500 (EST)
Received: from calvin.twntpe.cdc.com (ip129179-17-10.dblrev-129-179.cdc.com [129.179.17.10]) by
dimacs.rutgers.edu (8.6.12+bestmx+oldruq+newsunq/8.6.12) with ESMTP id EAA04247 for
<ietf-smtp <at> dimacs.rutgers.edu>; Mon, 6 Jan 1997 04:40:44 -0500
Received: from hobbes.twntpe.cdc.com by calvin.twntpe.cdc.com; Mon, 6 Jan 1997 17:39:20 +0800
Date: Mon, 6 Jan 1997 17:34:09 +0800 (GMT)
From: Ed Greshko <Edward.M.Greshko <at> cdc.com>
To: info-mime <at> CS.UTK.EDU
cc: ietf-smtp <at> dimacs.rutgers.edu
Subject: ESMTP 8BITMIME downgrading
Message-ID: <Pine.SOL.3.95.970106172235.23824P-100000 <at> hobbes.twntpe.cdc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi,

	Some supposedly MIME compliant UA, NetScape mail in particular,
can be made to generate 8bit data in the body as well as in headers.  This
seems especially true out here in Asia.  In the case of the headers they
are not generated to be RFC1522 compliant. 

	In the case of a gateway negociating ESMTP 8BITMIME it is clear
from RFC1652 what should occur in the case of the body of the message.
What is not addressed, or maybe I missed it, is what should be the action
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jim Conklin | 9 Jan 1997 23:07

This list is becoming ietf-smtp <at> imc.org

  Because I am resigning from CREN, Paul Hoffman, Director of the Internet
Mail Consortium, has graciously agreed to take over this list.  It will
become ietf-smtp <at> imc.org effective immediately, if all goes as planned.
Paul will notify the list when the change has been completed.  If you try
sending to the defunct CREN list address after the move, your message will
be returned with notification of the change, as a reminder to update your
alias for the list.

  I've closed the list to subscriptions for the duration of the transfer to
IMC, but subscriptions will again be accepted when the move is completed.
Subscription requests should then be sent to
     ietf-smtp-request <at> imc.org
with the line
     subscribe
as the body of the message.

  Archives for the list will be at <http://www.imc.org/ietf-smtp/>.

Jim
Permalink | Reply | 0 comments |
headers
dozer | 10 Jan 1997 02:57

would you be my friend?

Hello,

I'm 14 years old and I think I may be a gay.  I'm looking for some support and friendship 
with a older male age 18-40.  Please email if you can help.
Permalink | Reply | 0 comments |
headers
Paul E. Hoffman | 13 Jan 1997 02:23
Picon

The new "ietf-smtp" mailing list

Greetings. This is the first message on the ietf-smtp mailing list, which
has moved from CREN to IMC. The participants of the list are the same.
There is a Web site for the list at <http://www.imc.org/ietf-smtp> which
has an archive of both the old list and the new one.

--Paul E. Hoffman, Director
--Internet Mail Consortium
Permalink | Reply | 0 comments |
headers
Jack De Winter | 14 Jan 1997 01:19
Picon

general question about failed DNS request when looking up MXs

Okay, here's a general question for the group at large:

You are doing an MX request to resolve an address that
you need to send to.  You get back a Server Error (RCODE=2)
or an illegal return code (RCODE=6..15).  What is the best
thing to do to try and resolve this?

regards,
Jack
-------------------------------------------------
Jack De Winter - Wildbear Consulting, Inc.
(519) 576-3873		http://www.wildbear.on.ca/

Author of SLMail for 95 & NT (http://www.seattlelab.com/)
Permalink | Reply | 1 comment |
headers
Ned Freed | 14 Jan 1997 01:47

Re: general question about failed DNS request when looking up MXs

> Okay, here's a general question for the group at large:

> You are doing an MX request to resolve an address that
> you need to send to.  You get back a Server Error (RCODE=2)
> or an illegal return code (RCODE=6..15).  What is the best
> thing to do to try and resolve this?

You have to abort the delivery attempt and try again later (temporary error).
No other course of action is acceptable, really -- there is nothing that says
that trying the host directly (even assuming you can get its A record when you
can't get its MX record list) will produce correct results. Even if you're
willing to enter a special mode where you treat any errors you get under these
circumstances as temporary, it won't work in general. There are cases where the
host in user <at> host being an MX pointing to several other systems ends up
resolving to an entirely different mailbox than user <at> host where host is treated
as simply an A record. There are also cases where direct delivery ignoring MX
leads to loops. (Yes, such setups are problematic given the fact that not
everything on the Internet is consistent in its support of MX, but such setups
exist nevertheless and have to be dealt with.)

The bottom line is that RFC974 says that when an the DNS returns a non-empty MX
list the client is supposed to try all the hosts on that list and then stop,
and setups have been built and are actively being used that take advantage of
every nuance of this described behavior. So if you cannot get the MX
list you don't know what you should or should not do, so your only
course of action is to not do anything.

				Ned
(Continue reading)

Permalink | Reply | 0 comments |

Gmane