Fetching Mail with Movemail - Revision history

Gray: /* Mailutils Ticket File */

2011-10-30T11:16:41Z

Mailutils Ticket File

Gray at 14:23, 26 October 2011

2011-10-26T14:23:25Z

Gray: /* Error Handling */

2010-12-24T22:45:02Z

Error Handling

Gray: Describe error handling and the onerror configuration statement.

2010-12-24T22:44:27Z

Describe error handling and the onerror configuration statement.

Gray at 21:40, 22 December 2010

2010-12-22T21:40:07Z

Show changes

Gray: /* POP3S */

2010-12-14T10:10:42Z

POP3S

Gray: /* POP3 Mailboxes */

2010-12-14T10:09:49Z

POP3 Mailboxes

Gray: /* Mailutils Ticket File */

2010-12-14T10:02:47Z

Mailutils Ticket File

Gray: /* SMTP Mailboxes */

2010-12-14T09:57:51Z

SMTP Mailboxes

Gray at 09:56, 14 December 2010

2010-12-14T09:56:09Z

@@ Line 249: / Line 249: @@
 In the example above, the best match is <tt>smtp://bar:baz@gnu.org</tt>.
-{{note|Use ''mu wicket'' command to check which ticket will be matched by
+{{note|Use the [[mu#wicket|''mu wicket'']] command to check which ticket will be matched by
 a particular URL.}}

@@ Line 97: / Line 97: @@
    'smtp://localhost;domain=example.com'
-recipient addresses without domain part will get ''@example.com'' apended to them.  Thus <tt>smith</tt> becomes <tt>smith@example.com</tt> and so on.
+recipient addresses without domain part will get ''@example.com'' appended to them.  Thus <tt>smith</tt> becomes <tt>smith@example.com</tt> and so on.
 You can also request removing any original domain part from recipient addresses by specifying the <tt>strip-domain</tt> parameter.  When used together with <tt>domain</tt> it causes replacing of the original domain name with the new one:
@@ Line 154: / Line 154: @@
    'smtp://smith:guessme@localhost;auth=cram-md5,digest-md5'
-Putting authentication credentials in the URL itself can be unsecure,
+Putting authentication credentials in the URL itself hurts security,
 because they become visible for other users in the <tt>ps</tt> output.  To
 avoid compromising your authentication credentials, store them in
@@ Line 206: / Line 206: @@
 is formatted as a usual UNIX line-oriented configuration
 file, i.e. comments are introduced by a <tt>#</tt> sign and extend to the end
-of the line on which this sign appears, emtpy lines and comments are
+of the line on which this sign appears, empty lines and comments are
 ignored.  Each remaining line must be formatted as a URL, which
 contains at least one of ''username'' and ''password'' parts.  We call
@@ Line 220: / Line 220: @@
 compared as follows:
-* ''scheme'' and ''host'' use case-insensitve comparison.
+* ''scheme'' and ''host'' use case-insensitive comparison.
 * ''user'' uses case-sensitive comparison.
 * ''port'' is compared for numeric equality.

@@ Line 320: / Line 320: @@
    onerror ''keyword''[,''keyword...''];
-Each ''keyword'' is one of the following:
+A ''keyword'' is one of the following:
 ;abort

← Older revision		Revision as of 22:44, 24 December 2010
Line 313:		Line 313:
	Replace ''rname'' and ''pass'' with your user name and password on '''gmail'''		Replace ''rname'' and ''pass'' with your user name and password on '''gmail'''
	and ''lname'' with your local name.		and ''lname'' with your local name.
		+
		+	== Error Handling ==
		+
		+	Various errors can occur during retrieval of each particular messages as well as during injecting it into the MTA queue. When an error occurs, '''movemail''' normally stops any further processing and terminates, without deleting already moved messages. Although such a behavior is a safest way, there may be cases when it is not desired. Therefore, a special configuration option is provided, which controls the '''movemail''' actions when an error occurs while trying to append the message to the destination mailbox:
		+
		+	onerror ''keyword''[,''keyword...''];
		+
		+	Each ''keyword'' is one of the following:
		+
		+	;abort
		+	:Abort any further processing, reset source mailbox to its original state, and terminate with code 1. This is the default behavior. No other keyword can be given together with <tt>abort</tt>.
		+	;skip
		+	:Skip this message and try to move the next one. None of the messages is deleted before closing the mailbox. '''Movemail''' terminates with code 1.
		+	;count
		+	:Count this message as successfully processed, but do not mark it for deletion. '''Movemail''' expunges the successfully processed messages from the source mailbox and terminates with code 0.
		+	;delete
		+	:Mark the message for deletion, and continue processing. Before exiting, '''movemail''' will expunge both successfully copied messages and failed ones. It will, however, terminate with code 1, unless <tt>count</tt> is also given.
		+
		+	These keywords can also be given from the command line, using the <tt>--onerror</tt> command line option.

@@ Line 339: / Line 339: @@
 Unless ''port'' is given, the default value 995 is used.  The <tt>notls</tt>
-parameter is not supported, since POPS goes over an already encrypted
+parameter is not supported, since POP3S goes over an already encrypted
 channel.

@@ Line 304: / Line 304: @@
 The syntax for POP3 URLs is similar to SMTP:
-<code>
+<tt>
 pop://[''user''[:''pass''][;auth=+APOP]@]''hostname''[:''port''][;notls]
-</code>
+</tt>
 The ''hostname'' gives the name or IP address of the host running a POP3
@@ Line 325: / Line 325: @@
 If the server offers the STLS capability, '''movemail''' attempts to
-establish encrypted TLS connection.  To disable this behavior use
+establish encrypted TLS connection.  To disable this behavior, use
 the <tt>notls</tt> parameter.
-The deprecated <tt>pops</tt> protocol is also supported.  It is enabled by
+=== POP3S ===
 an URL beginning with <tt>pops://</tt> instead of <tt>pop://</tt>.
 The URL syntax is similar to the above:
-<code>
+<tt>
 pops://[''user''[:''pass''][;auth=+APOP]@]''hostname''[:''port'']
-</code>
+</tt>
 Unless ''port'' is given, the default value 995 is used.  The <tt>notls</tt>

@@ Line 45: / Line 45: @@
 </tt>
-The only mandatory part, beside the <tt>smtp://</tt> scheme designator, is ''hostname'' -- a hostname or IP address of the server to connect to. Rest of elements (shown enclosed in square brackets) is optional:
+The only mandatory part, beside the <tt>smtp://</tt> scheme designator, is ''hostname'' -- a hostname or IP address of the server to connect to. The rest of elements (shown enclosed in square brackets) is optional:
 * The ''user'' part supplies the user name for authentication.
 * Password for this user is supplied by the ''path'' component.
 * The <tt>auth=</tt> parameter is used to specify a list of ''mechanisms'' acceptable for authentication.  Each ''mech'' is a name of a mechanism.
-* ''hostname'' is the name or IP address of the host to connect to
+* ''hostname'' is the name or IP address of the host to connect to.
 * ''port'' is the port number or symbolic name (from <tt>/etc/services</tt>.
-* Additional parameters (''param'') are a semicolon-separated list of key-value
+* Additional parameters (''param'') are a semicolon-separated list of key-value pairs.
 The ''port'' element, if supplied, specifies the port number to use instead of the default 25.  For example, to inject mail using the mail submission port (587), we can write:

@@ Line 10: / Line 10: @@
 The '''movemail''' invocation scheme is:
-<code>
+<tt>
 movemail [''options''] ''source-mailbox'' ''dest-mailbox''
-</code>
+</tt>
 where ''options'' are movemail-specific command line options, ''source-mailbox'' is the mailbox to retrieve messages from, and ''dest-mailbox'' is the mailbox to move those messages to.  Both mailboxes can be specified as ''URLs'', for example:
@@ Line 41: / Line 41: @@
 The SMTP URL syntax is:
-<code>
+<tt>
 smtp://[''user''[:''pass''][;auth=''mech'',...]@]''hostname''[:''port''][;''param''[;''param''...]]
-</code>
+</tt>
 The only mandatory part, beside the <tt>smtp://</tt> scheme designator, is ''hostname'' -- a hostname or IP address of the server to connect to. Rest of elements (shown enclosed in square brackets) is optional:
-;user
+* The ''user'' part supplies the user name for authentication.
-: The user name
+* Password for this user is supplied by the ''path'' component.
-;pass
+* The <tt>auth=</tt> parameter is used to specify a list of ''mechanisms'' acceptable for authentication.  Each ''mech'' is a name of a mechanism.
-: This user's password
+* ''hostname'' is the name or IP address of the host to connect to
-;mech
+* ''port'' is the port number or symbolic name (from <tt>/etc/services</tt>.
-: The authentication mechanism to be used
+* Additional parameters (''param'') are a semicolon-separated list of key-value
-;hostname
+pairs.
 The ''port'' element, if supplied, specifies the port number to use instead of the default 25.  For example, to inject mail using the mail submission port (587), we can write: