Index: openacs-4/packages/acs-mail-lite/acs-mail-lite.info =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/acs-mail-lite.info,v diff -u -r1.52.2.8 -r1.52.2.9 --- openacs-4/packages/acs-mail-lite/acs-mail-lite.info 27 Feb 2017 07:42:02 -0000 1.52.2.8 +++ openacs-4/packages/acs-mail-lite/acs-mail-lite.info 21 Apr 2017 16:11:28 -0000 1.52.2.9 @@ -38,7 +38,7 @@ Set this parameter to the root of your filesystem will disable this restriction. Default for the empty value of this parameter will be to allow only files into the temporary folder of the system, as in '[ns_tmpdir]'" section_name="email"/> - + Index: openacs-4/packages/acs-mail-lite/tcl/acs-mail-lite-callback-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/tcl/acs-mail-lite-callback-procs.tcl,v diff -u -r1.23.2.2 -r1.23.2.3 --- openacs-4/packages/acs-mail-lite/tcl/acs-mail-lite-callback-procs.tcl 8 Jan 2016 21:17:10 -0000 1.23.2.2 +++ openacs-4/packages/acs-mail-lite/tcl/acs-mail-lite-callback-procs.tcl 21 Apr 2017 16:11:28 -0000 1.23.2.3 @@ -92,7 +92,7 @@ upvar $array email set to [acs_mail_lite::parse_email_address -email $email(to)] - ns_log Debug "acs_mail_lite::incoming_email -impl acs-mail-lite called. Recepient $to" + ns_log Debug "acs_mail_lite::incoming_email -impl acs-mail-lite called. Recipient $to" lassign [acs_mail_lite::parse_bounce_address -bounce_address $to] user_id package_id signature Index: openacs-4/packages/acs-mail-lite/tcl/acs-mail-lite-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/tcl/acs-mail-lite-procs.tcl,v diff -u -r1.92.2.8 -r1.92.2.9 --- openacs-4/packages/acs-mail-lite/tcl/acs-mail-lite-procs.tcl 27 Mar 2017 10:51:27 -0000 1.92.2.8 +++ openacs-4/packages/acs-mail-lite/tcl/acs-mail-lite-procs.tcl 21 Apr 2017 16:11:28 -0000 1.92.2.9 @@ -688,7 +688,7 @@ {bcc {}} } { - Replacement for ns_sendmail for backward compability. + Replacement for ns_sendmail for backward compatibility. } { Index: openacs-4/packages/acs-mail-lite/tcl/incoming-mail-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/tcl/Attic/incoming-mail-procs.tcl,v diff -u -r1.7.2.3 -r1.7.2.4 --- openacs-4/packages/acs-mail-lite/tcl/incoming-mail-procs.tcl 27 Mar 2017 10:51:27 -0000 1.7.2.3 +++ openacs-4/packages/acs-mail-lite/tcl/incoming-mail-procs.tcl 21 Apr 2017 16:11:28 -0000 1.7.2.4 @@ -134,7 +134,7 @@ } { An email is splitted into several parts: headers, bodies and files lists and all headers directly. - The headers consists of a list with header names as keys and their correponding values. All keys are lower case. + The headers consists of a list with header names as keys and their corresponding values. All keys are lower case. The bodies consists of a list with two elements: content-type and content. The files consists of a list with three elements: content-type, filename and content. Index: openacs-4/packages/acs-mail-lite/www/doc/index.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/www/doc/index.adp,v diff -u -r1.1.2.4 -r1.1.2.5 --- openacs-4/packages/acs-mail-lite/www/doc/index.adp 5 Jul 2016 12:18:25 -0000 1.1.2.4 +++ openacs-4/packages/acs-mail-lite/www/doc/index.adp 21 Apr 2017 16:11:28 -0000 1.1.2.5 @@ -14,12 +14,12 @@ the sending fails, the mail will be placed in the outgoing queue again and be given another try a few minutes later when processing the queue again.

-

Each email contains an X-Envelope-From adress constructed as +

Each email contains an X-Envelope-From address constructed as follows:
-The adress starts with "bounce" (can be changed by a +The address starts with "bounce" (can be changed by a parameter) followed by the user_id, a hashkey and the package_id of the package instance that sent the email, separated by -"-". The domain name of this adress can be changed with a +"-". The domain name of this address can be changed with a parameter.

The system checks every 2 minutes (configurable) in a certain maildirectory (configurable) for newly bounced emails, so the @@ -29,7 +29,7 @@ bounced emails, strips out the message_id and verifies the hashkey in the bounce-address. After that the package-key of the package sending the original mail is found out by using the package_id -provided in the bounce adress. With that, the system then tries to +provided in the bounce address. With that, the system then tries to invoke a callback procedure via a service contract if one is registered for that particular package-key. This enables each package to deal with bouncing mails on their own - probably logging Index: openacs-4/packages/acs-mail-lite/www/doc/index.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/www/doc/Attic/index.html,v diff -u -r1.2.18.1 -r1.2.18.2 --- openacs-4/packages/acs-mail-lite/www/doc/index.html 21 Aug 2015 10:28:45 -0000 1.2.18.1 +++ openacs-4/packages/acs-mail-lite/www/doc/index.html 21 Apr 2017 16:11:28 -0000 1.2.18.2 @@ -17,12 +17,12 @@ again and be given another try a few minutes later when processing the queue again.

-Each email contains an X-Envelope-From adress constructed as +Each email contains an X-Envelope-From address constructed as follows:
-The adress starts with "bounce" (can be changed by a parameter) +The address starts with "bounce" (can be changed by a parameter) followed by the user_id, a hashkey and the package_id of the package instance that sent the email, separated by "-". The -domain name of this adress can be changed with a parameter. +domain name of this address can be changed with a parameter.

The system checks every 2 minutes (configurable) in a certain maildirectory (configurable) for newly bounced emails, so the @@ -32,7 +32,7 @@ strips out the message_id and verifies the hashkey in the bounce-address. After that the package-key of the package sending the original mail is found out by using the package_id provided in the bounce -adress. With that, the system then tries to invoke a callback +address. With that, the system then tries to invoke a callback procedure via a service contract if one is registered for that particular package-key. This enables each package to deal with bouncing mails on their own - probably logging this in special tables. Index: openacs-4/packages/acs-messaging/acs-messaging.info =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-messaging/acs-messaging.info,v diff -u -r1.39.2.10 -r1.39.2.11 --- openacs-4/packages/acs-messaging/acs-messaging.info 27 Feb 2017 07:42:03 -0000 1.39.2.10 +++ openacs-4/packages/acs-messaging/acs-messaging.info 21 Apr 2017 16:14:09 -0000 1.39.2.11 @@ -17,7 +17,7 @@ 2017-02-27 OpenACS Provides generic message services, with email sending. acs-mail-lite and notifications are the - prefered packages for delivering this functionality and it is anticipated that this package will ultimately be deprecated. + preferred packages for delivering this functionality and it is anticipated that this package will ultimately be deprecated. GPL 3 Index: openacs-4/packages/acs-messaging/www/doc/requirements.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-messaging/www/doc/requirements.adp,v diff -u -r1.2.2.5 -r1.2.2.6 --- openacs-4/packages/acs-messaging/www/doc/requirements.adp 5 Jul 2016 12:15:32 -0000 1.2.2.5 +++ openacs-4/packages/acs-messaging/www/doc/requirements.adp 21 Apr 2017 16:14:09 -0000 1.2.2.6 @@ -84,7 +84,7 @@

20.0 Message Content

A message should have a primary content body consisting of a specified MIME type and a block of storage holding the content. In -addition, applications may store one or more seperate revisions of +addition, applications may store one or more separate revisions of a message.

30.0 Attachments

Messages may be composed of additional attachments. Each @@ -131,7 +131,7 @@

The system should provide the following interfaces for integrating with existing E-mail systems. Note that these requirements only deal with sending mail. Our feeling that -a seperate package should be implemented to deal with +a separate package should be implemented to deal with receiving mail that would use ACS Messages for storage of incoming messages.

Index: openacs-4/packages/acs-messaging/www/doc/requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-messaging/www/doc/requirements.html,v diff -u -r1.1.1.1 -r1.1.1.1.30.1 --- openacs-4/packages/acs-messaging/www/doc/requirements.html 13 Mar 2001 22:59:26 -0000 1.1.1.1 +++ openacs-4/packages/acs-messaging/www/doc/requirements.html 21 Apr 2017 16:14:09 -0000 1.1.1.1.30.1 @@ -160,7 +160,7 @@ A message should have a primary content body consisting of a specified MIME type and a block of storage holding the content. In addition, applications may store one or - more seperate revisions of a message. + more separate revisions of a message.

30.0 Attachments

Messages may be composed @@ -250,7 +250,7 @@

The system should provide the following interfaces for integrating with existing E-mail systems. Note that these requirements only - deal with sending mail. Our feeling that a seperate package + deal with sending mail. Our feeling that a separate package should be implemented to deal with receiving mail that would use ACS Messages for storage of incoming messages.

Index: openacs-4/packages/acs-outdated/tcl/acs-lang-localization-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-outdated/tcl/acs-lang-localization-procs.tcl,v diff -u -r1.1 -r1.1.4.1 --- openacs-4/packages/acs-outdated/tcl/acs-lang-localization-procs.tcl 2 Oct 2013 07:42:04 -0000 1.1 +++ openacs-4/packages/acs-outdated/tcl/acs-lang-localization-procs.tcl 21 Apr 2017 16:15:28 -0000 1.1.4.1 @@ -111,7 +111,7 @@ set sign [lc_get -locale $locale "positive_sign"] } - # decimal seperator + # decimal separator set dec [lc_get -locale $locale "mon_decimal_point"] regsub {\.} $out $dec out Index: openacs-4/packages/acs-reference/acs-reference.info =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-reference/acs-reference.info,v diff -u -r1.37.2.6 -r1.37.2.7 --- openacs-4/packages/acs-reference/acs-reference.info 27 Feb 2017 07:42:03 -0000 1.37.2.6 +++ openacs-4/packages/acs-reference/acs-reference.info 21 Apr 2017 16:17:39 -0000 1.37.2.7 @@ -9,7 +9,7 @@ Jon Griffin - Tools and API for managing refrence data. + Tools and API for managing reference data. 2017-02-27 3 Mayuli Enterprises, LLC Index: openacs-4/packages/acs-reference/www/doc/requirements.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-reference/www/doc/requirements.adp,v diff -u -r1.2.2.9 -r1.2.2.10 --- openacs-4/packages/acs-reference/www/doc/requirements.adp 5 Jul 2016 12:16:50 -0000 1.2.2.9 +++ openacs-4/packages/acs-reference/www/doc/requirements.adp 21 Apr 2017 16:17:39 -0000 1.2.2.10 @@ -106,5 +106,5 @@

Note also that it is possible to have overlapping effective dates. This will not be implemented in the first version, but -should be recognized and accomodated throughout the development +should be recognized and accommodated throughout the development process for the service package.

Index: openacs-4/packages/acs-reference/www/doc/requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-reference/www/doc/requirements.html,v diff -u -r1.3.14.1 -r1.3.14.2 --- openacs-4/packages/acs-reference/www/doc/requirements.html 21 Aug 2015 10:49:21 -0000 1.3.14.1 +++ openacs-4/packages/acs-reference/www/doc/requirements.html 21 Apr 2017 16:17:39 -0000 1.3.14.2 @@ -109,7 +109,7 @@
  • Historical data will be available using this diff for those applications that need to use the old data

    • Note also that it is possible to have overlapping effective dates. -This will not be implemented in the first version, but should be recognized and accomodated throughout the development +This will not be implemented in the first version, but should be recognized and accommodated throughout the development process for the service package.