Email class - Revision history

JAL: minor cleanup

2014-11-11T22:41:43Z

minor cleanup

← Older revision		Revision as of 22:41, 11 November 2014
Line 809:		Line 809:
	%rc = $procopn(%procname, %procfile)		%rc = $procopn(%procname, %procfile)
	if %rc ne 0 then		if %rc ne 0 then
	print 'Can''t open procedure ' with %procname -		print 'Can''t open procedure ' with %procname -
	with ' in file ' with %procfile with ', rc = ' -		with ' in file ' with %procfile with ', rc = ' -
	with %rc		with %rc
Line 837:		Line 837:

	==List of Email methods==		==List of Email methods==
	The [[List of Email methods~~\|"List of Email methods"~~]] shows all the class methods.		The [[List of Email methods]] shows all the class methods.

	==See also==		==See also==
	<ul>		<ul>
	<li>[[Janus Sockets User Language coding considerations]]		<li>[[Janus Sockets User Language coding considerations]]</li>
	<li>[[Sample Janus Sockets programs]]		<li>[[Sample Janus Sockets programs]]</li>
	<li>Socket-level interfaces:		<li>Socket-level interfaces:
	<ul>		<ul>
	<li>[[Janus Sockets $functions\|$functions]]		<li>[[Janus Sockets $functions\|$functions]]</li>
	<li>[[Socket class]]		<li>[[Socket class]]</li>
	</ul>		</ul></li>

	<li>Higher-level interfaces:		<li>Higher-level interfaces:
	<ul>		<ul>
	<li>[[Email class]]		<li>[[Email class]]</li>
	<li>[[HTTP Helper\|HTTP Helper classes]]		<li>[[HTTP Helper\|HTTP Helper classes]]</li>
	<li>[[LDAP class]]		<li>[[LDAP class]]</li>
	<li>[[Janus FTP Server]]		<li>[[Janus FTP Server]]</li>
	<li>[[Janus Telnet Server]]		<li>[[Janus Telnet Server]]</li>
			</ul></li>
	</ul>		</ul>

	[[Category: Janus Sockets]]		[[Category: Janus Sockets]]
	[[Category:System classes]]		[[Category:System classes]]

JAL at 21:03, 2 September 2014

2014-09-02T21:03:48Z

← Older revision		Revision as of 21:03, 2 September 2014
Line 748:		Line 748:
	%name = 'D_Eisenhower@presidents.usa'		%name = 'D_Eisenhower@presidents.usa'
	%nick = 'Ike'		%nick = 'Ike'
	%letter:~~AddCc~~(%name, %nick)		%letter:AddCC(%name, %nick)

	%name = L_Johnson@presidents.usa'		%name = L_Johnson@presidents.usa'
	%nick = 'LBJ'		%nick = 'LBJ'
	%letter:~~AddBcc~~(%name, %nick)		%letter:AddBCC(%name, %nick)

	%letter:Sender('a_huckster@bankandtrustme.com')		%letter:Sender('a_huckster@bankandtrustme.com')

JAL: /* Dummy SMTP Server */

2014-09-02T21:02:39Z

Dummy SMTP Server

← Older revision		Revision as of 21:02, 2 September 2014
Line 77:		Line 77:

	<b>emclass.ul</b>:		<b>emclass.ul</b>:
	<~~pre~~>		<p class="code"><nowiki>***********************************************************************
	***********************************************************************
	* *		* *
	* encoding enumerations. *		* encoding enumerations. *
Line 674:		Line 673:

	end class		end class
	</~~pre~~>		</nowiki></p>
	<b>driver.ul</b>:		<b>driver.ul</b>:
	<~~pre~~>		<p class="code">UTABLE LNTBL 128
	UTABLE LNTBL 128
	b		b

Line 698:		Line 696:
	%x = $bldproc(%tp, %ename, 'OPEN')		%x = $bldproc(%tp, %ename, 'OPEN')
	assert %x eq 0		assert %x eq 0
	*		*
	* Get attachments and copy content to output procedure		* Get attachments and copy content to output procedure
	*		*
	%op = 'APPEND'		%op = 'APPEND'
	for %i from 1 to %this:parts		for %i from 1 to %this:parts
Line 723:		Line 721:
	USE Fred		USE Fred
	DISPLAY PROCEDURE 0		DISPLAY PROCEDURE 0
	</~~pre~~>		</p>

	==SMTP examples==		==SMTP examples==

JAL: /* Dummy SMTP Server example */

2014-03-20T18:24:31Z

Dummy SMTP Server example

← Older revision		Revision as of 18:24, 20 March 2014
Line 68:		Line 68:

	==Dummy SMTP Server example==		==Dummy SMTP Server example==
	This is an example of a very basic SMTP Server ~~which simple excepts~~ <var>Email</var> objects from a SMTP client in turn sends a response.		This is an example of a very basic SMTP Server: it simply accepts <var>Email</var> objects from an SMTP client, and in turn, sends a response.
	It does not store or retrieve messages.		It does not store or retrieve messages.

	No <var class="product">Janus</var> port definitions are shown.		No <var class="product">Janus</var> port definitions are shown.
	For comments about defining <var class="product">Janus</var> ports for the <var>Email</var> class, see		For comments about defining <var class="product">Janus</var> ports for the <var>Email</var> class, see the [[#jport\|earlier]] remarks.
	the [[#jport\|earlier]] remarks.

	===Dummy SMTP Server===		===Dummy SMTP Server===
Line 724:		Line 724:
	DISPLAY PROCEDURE 0		DISPLAY PROCEDURE 0
	</pre>		</pre>

	==SMTP examples==		==SMTP examples==
	Examples follow in which <var>Email</var> objects are used to create and send a request to an SMTP server.		Examples follow in which <var>Email</var> objects are used to create and send a request to an SMTP server.

SNelson at 18:18, 20 March 2014

2014-03-20T18:18:40Z

← Older revision		Revision as of 18:18, 20 March 2014
Line 68:		Line 68:

	==Dummy SMTP Server example==		==Dummy SMTP Server example==
	This is an example of very basic SMTP ~~Service~~ which simple excepts <var>Email</var> objects from a SMTP client ~~and~~ response ~~back to the client~~.		This is an example of a very basic SMTP Server which simple excepts <var>Email</var> objects from a SMTP client in turn sends a response.
			It does not store or retrieve messages.
	No <var class="product">Janus</var> port definitions are shown.		No <var class="product">Janus</var> port definitions are shown.
	For comments about defining <var class="product">Janus</var> ports for the <var>Email</var> class, see		For comments about defining <var class="product">Janus</var> ports for the <var>Email</var> class, see
	the [[#jport\|earlier]] remarks.		the [[#jport\|earlier]] remarks.

	===Dummy SMTP Server ~~example~~===		===Dummy SMTP Server===

	<b>emclass.ul</b>:		<b>emclass.ul</b>:

SNelson at 18:03, 20 March 2014

2014-03-20T18:03:58Z

← Older revision		Revision as of 18:03, 20 March 2014
Line 75:		Line 75:
	===Dummy SMTP Server example===		===Dummy SMTP Server example===

	<b>emclass</b>:		<b>emclass.ul</b>:
	<pre>		<pre>
	***********************************************************************		***********************************************************************
Line 674:		Line 674:
	end class		end class
	</pre>		</pre>
	<u>driver.ul</b>:		<b>driver.ul</b>:
	<pre>		<pre>
	UTABLE LNTBL 128		UTABLE LNTBL 128

SNelson at 18:03, 20 March 2014

2014-03-20T18:03:00Z

← Older revision		Revision as of 18:03, 20 March 2014
Line 76:		Line 76:

	<b>emclass</b>:		<b>emclass</b>:
			<pre>
	***********************************************************************		***********************************************************************
	* *		* *
Line 673:		Line 673:

	end class		end class
			</pre>
	<u>driver.ul</b>:		<u>driver.ul</b>:
			<pre>
	UTABLE LNTBL 128		UTABLE LNTBL 128
	b		b
Line 722:		Line 722:
	USE Fred		USE Fred
	DISPLAY PROCEDURE 0		DISPLAY PROCEDURE 0
			</pre>

	==SMTP examples==		==SMTP examples==

SNelson at 18:01, 20 March 2014

2014-03-20T18:01:37Z

Show changes

JAL at 17:10, 2 January 2014

2014-01-02T17:10:39Z

← Older revision		Revision as of 17:10, 2 January 2014
Line 46:		Line 46:

	For information about using SOUL objects, see [[Object oriented programming in SOUL]] and		For information about using SOUL objects, see [[Object oriented programming in SOUL]] and
	[[Getting started with ~~object-oriented programming~~ for User Language programmers]].		[[Getting started with OOP for User Language programmers]].

	==Email class summary==		==Email class summary==

JAL at 23:07, 21 October 2013

2013-10-21T23:07:58Z

← Older revision		Revision as of 23:07, 21 October 2013
Line 1:		Line 1:
	The <var>Email</var> class is a high level,		The <var>Email</var> class is a high level,
	object oriented interface to client sockets that lets you write a <var class="product">~~User Language~~</var> SMTP		object oriented interface to client sockets that lets you write a <var class="product">SOUL</var> SMTP
	(Simple Mail Transfer Protocol)		(Simple Mail Transfer Protocol) request without knowledge of socket level programming
	request without knowledge of socket level programming
	or the format of SMTP requests and responses.		or the format of SMTP requests and responses.

	The <var>Email</var> class methods let a <var class="product">~~User Language~~</var> program act as an SMTP client.		The <var>Email</var> class methods let a <var class="product">SOUL</var> program act as an SMTP client.
	SMTP clients send mail requests		SMTP clients send mail requests
	to an SMTP server, not directly to other SMTP clients.		to an SMTP server, not directly to other SMTP clients.
	The <var>Email</var> class methods only support communication with SMTP servers.		The <var>Email</var> class methods only support communication with SMTP servers.

	An SMTP server will ~~“~~store and forward~~”~~ mail it receives.		An SMTP server will "store and forward" mail it receives.
	This means that all		This means that all
	messages are first received in entirety on the SMTP server,		messages are first received in entirety on the SMTP server,
Line 16:		Line 15:
	Mail delivery can be delayed by a server that is down or too busy to		Mail delivery can be delayed by a server that is down or too busy to
	accept connections.		accept connections.
	~~“~~Store and forward~~”~~ gives the SMTP server the ability		"Store and forward" gives the SMTP server the ability
	to retry delivery without making the SMTP client wait for completion.		to retry delivery without making the SMTP client wait for completion.

Line 22:		Line 21:
	This, of course, makes it impractical for a client to wait for delivery		This, of course, makes it impractical for a client to wait for delivery
	confirmation, so the SMTP protocol does not provide such information.		confirmation, so the SMTP protocol does not provide such information.
	A ~~“~~success~~”~~ response from an SMTP server indicates		A "success" response from an SMTP server indicates
	only that the server has accepted the request and will		only that the server has accepted the request and will
	attempt to deliver the mail to the recipients.		attempt to deliver the mail to the recipients.
Line 44:		Line 43:
	<p class="note">'''Note:'''		<p class="note">'''Note:'''
	To use <var>Email</var> objects under versions of Model 204 earlier than 7.5, you must have licensed <var class="product">[[Janus TCP/IP Base]]</var>, <var class="product">[[Janus Sockets]]</var>, '''and''' <var class="product">[[Janus SOAP]]</var>. Under version 7.5 and later,		To use <var>Email</var> objects under versions of Model 204 earlier than 7.5, you must have licensed <var class="product">[[Janus TCP/IP Base]]</var>, <var class="product">[[Janus Sockets]]</var>, '''and''' <var class="product">[[Janus SOAP]]</var>. Under version 7.5 and later,
	you do not require <var class="product">[[Janus SOAP]]</var>. </p>		you do not require <var class="product">Janus SOAP</var>. </p>

	For information about using SOUL objects, see [[~~Janus SOAP User Language Interface~~]] and		For information about using SOUL objects, see [[Object oriented programming in SOUL]] and
	[[Getting started with object-oriented programming for User Language programmers]].		[[Getting started with object-oriented programming for User Language programmers]].