Processing mail headers ...
Return address: "<ArabiaNewsEnglish@arabia.com> (Arabia.On.Line's Daily Dispatch in English)"
Processing message contents...
Command: Dear future VServers client,
>>>>>>>> Command DEAR unknown
Command: Thank you for your interest in VServers! This is an automated response from the VServers Sales Department to inform you that we received a message from you at 9:16:56 AM Pacific Time on 11/6/99. For tracking purposes, we have assigned this issue the following tracking number:
>>>>>>>> Command THANK unknown
Command: VSD1999110600000460
>>>>>>>> Command VSD1999110600000460 unknown
Command: Your message has been queued and a member of our team will be responding personally to the following E-Mail address which you've provided:
>>>>>>>> Command YOUR unknown
Command: ArabiaNewsEnglish@arabia.com
>>>>>>>> Command ARABIANEWSENGLISH@ARABIA.COM unknown
Command: In the event that you need to contact us regarding your original message, please refer to the tracking number that has been assigned to this message. This will help our staff locate and review your correspondence with us, and ensure that your request is handled in an efficient manner.
>>>>>>>> Command IN unknown
Command: For a list of current VServer Products, including a spec sheet and pricing, please visit:
>>>>>>>> Command FOR unknown
Command: For information about our server technology and hardware specifications, please see
>>>>>>>> Command FOR unknown
Command: Thanks once again for contacting us. We look forward to assisting you,
>>>>>>>> Command THANKS unknown
Command: Sincerely,
>>>>>>>> Command SINCERELY unknown
Command: VServers Sales Department
>>>>>>>> Command VSERVERS unknown
Command: VServers
>>>>>>>> Command VSERVERS unknown
Command: sales@vservers.com
>>>>>>>> Command SALES@VSERVERS.COM unknown
Command: This is a multi-part message in MIME format.
>>>>>>>> Command THIS unknown
Command: ------=_NextPart_000_006E_01BF28F4.44F4FA20
=> Assume a USENET .signature follows; I'll ignore the rest of the message
Your message has been processed.
Validating service contract:
>>>>>>>> Validation failed -- could not find customer id for <ArabiaNewsEnglish@arabia.com> (Arabia.On.Line's Daily Dispatch in English)
Number of errors detected = 15.
NO FILES WILL BE SENT.
NOTICE:
This server provides access to the official patches for BSD/OS.
All patches are Copyright 1995 Berkeley Software Design, Inc.,
all rights reserved. Other copyrights may apply to some patches.
Access to this server is available to BSDI customers with valid
support contracts only.
AUTHENTICATION:
This server uses your return email address (or customer ID or
specified path -- see the CUST and PATH commands below) to validate
your request against the BSDI customer database. If it determines
you have a valid service contract, it will return a group name
and password that may be used to access the patches via the
ftp.BSDI.COM ftp server, or you may use `SEND' commands (see
below) to retrieve them via email.
If the server reports that it could not resolve your address
into a customer ID, please use either the CUST or PATH commands
to specify your customer number or the correct official email
point-of-contact, or contact BSDI at ftpmail-admin@bsdi.com or
719-593-2082 to correct your database entry.
Expired contracts or warranties may be renewed through the
distributor from which the software was purchased if international,
or by calling BSDI at 719-593-2082.
All responses are sent to the officially registered email address
for your customer ID. For example, say your customer ID was
X1234 and your officially registered email address was joe@foo.com.
If you send mail to the server from joe@host.foo.com, the server
will NOT be able to validate the request. If you specify either
`cust X1234' or `path joe@foo.com' in the message you send to
the server, the server will correctly validate your service
contract and the return mail will be sent to the official address,
in this case, joe@foo.com. YOU CANNOT SPECIFY AN ALTERNATE
DESTINATION -- mail from the server will ALWAYS go to the
officially registered address ONLY. If you wish to change the
officially registered address for your customer ID (or if you
never registered one), contact BSDI at the email address or
phone number listed above.
FTP ACCESS:
The URL ftp://ftp.bsdi.com/bsdi/patches directory (a.k.a.
ftp.bsdi.com:/bsdi/patches in the old notation) provides
access to all the same files as this patch server. Many
of the patches (security related fixes, other critical fixes)
are available via anonymous ftp. While anonymous users can
see the names of all the patches in that directory, some
of the patches require additional authentication before they
may be retrieved.
If your email address or customer ID is associated with a valid
service contract, the message returned by the patches server
will contain lines similar to:
FTP-group: xxxxxxx
Password: yyyyyyy
This group/password combination may be used to access the
restricted patches in the archive on the ftp.BSDI.COM server.
All group/password combinations expire at 2am US/Mountain time
each day, so you must obtain a new group/password each day you
wish to access the ftp version of the archive.
If you send multiple requests to the patches server, each request
will issue a different password for ftp. The most recent request
will always be the valid password and the older passwords will
no longer enable access.
Once you have a valid group/password combination, you can access the
server using the following procedure:
o Connect to ftp.bsdi.com and log in as `anonymous' (or `ftp')
and present your email address as a password.
o Enable access to the patches directory by giving the `site group'
and `site gpass' commands (you type the parts after the ftp>
prompt -- the server should respond as shown):
ftp> site group xxxxxxx
200 Request for access to group xxxxxxx accepted.
ftp> site gpass yyyyyyy
200 Group access enabled.
o You should now be able to `cd' to the patches directory
and use `ls', `get', and/or `mget' commands to list and
retrieve files.
If the server refuses access because it cannot reverse resolve
your host name, you can always use e-mail access. We will not
make exceptions for people who cannot configure DNS correctly
(even if it's your service provider's fault -- complain to them,
not to BSDI). Patches are available via email to patches@bsdi.com
(this server). Access to the regular anonymous archive on
ftp.bsdi.com is available via email to ftpmail@bsdi.com.
Some FTP clients do not support the `site' command. If you get
an error similar to `invalid command' when attempting to use
the site command, the problem is with your client, not the
server. Some ftp clients (including virtually all 4.2BSD derived
clients) support the `quote' command which can be used to send
arbitrary commands (including site commands). E.g.:
ftp> quote site group xxxxxxx
If that fails, try a more up-to-date client (like the one included
with BSD/OS) or use the patches@bsdi.com mail-back server.
EMAIL ACCESS:
Access to patches is also available via this mail-back server. See
the command reference below for a complete list of the commands
accepted by this server.
Lines of the form:
send filename (if the file is at the top level)
send directory/filename (if the file is in a subdirectory)
will cause the server to send you the requested file. The file
will be split into pieces if it exceeds 64K bytes or the size
specified by a `limit' command.
The patches themselves are typically sorted into subdirectories
(see the index file for the ls -R listing of files available
from the server -- retrieve the index with `send index').
For example, to retrieve the U210-001 patch for the 2.1 release,
you would use the command:
send patches-2.1/U210-001
The most common problems with email access are caused by specifying
the filename incorrectly (case IS significant) or by appending a
signature file to the commands without specifying the `end' command
(some signature files will confuse the server enough that it won't
even respond at all).
Hints for retrieving files via email:
CASE IS SIGNIFICANT IN FILE NAMES. The file named `foo'
is a different file than the file named `FOO' is a different
file than one named `FoO', etc. You must request the
correct name of the file.
IF YOU SEND THE SERVER A REQUEST AND IT RESPONDS WITH A
MESSAGE SAYING THE PARTICULAR FILE WAS `Unknown', YOU REQUESTED
A NON-EXISTENT FILE AND NOTHING WILL BE SENT TO YOU. You don't
need to wait for hours or days and then send mail to ftpmail-admin.
You SHOULD request the file `index' and determine the correct
name of the file you want.
The server typically responds within seconds of receiving
a request. Large files (or files split into many pieces)
often take longer, but if you receive the `your request has
been processed' message and don't start receiving the files
right away, check the message you did receive to make sure
the server could find the files and that none of them
were `Unknown'.
The file `index' contains the list of file names available
in the archive. Use the command:
send index
to retrieve it..
Many (most) mail paths can handle larger chunks than 64K
(which will save you having to reassemble files). You can
change the limit with the `limit' command:
limit 1024k
will increase the limit on a single message to 1 megabyte
(the maximum limit).
There are two scripts meant to help you reassemble the
pieces of a file (unpack.pl and unpack.sh) retrieve them
from the server with the commands:
send unpack.sh
send unpack.pl
If you save all the message pieces into a single file (no
need to strip off the headers) and run either of these
scripts on the file it will recreate the original file from
the server:
perl unpack.pl < file
or
sh unpack.sh < file
COMMENTS OR QUESTIONS/PROBLEMS:
Please address any questions or comments about this server to
ftpmail-admin@bsdi.com.
--------------------------------------------------------------------------
Valid server commands are:
CUST <custid>
Specify which customer ID to send the patch to. The patch
will be sent to the email address registered for the specified
customer ID.
If you purchased the system from BSDI's main office, your
customer number will be something like G1234 or N2345.
European customers need to prepend an `E' to their system ID
to make a `Customer number', i.e., if your system ID is
26ffffe24
then your customer id is
E26ffffe24
PATH <path>
Specify return path. Use this if you are not sure that
your mail system generates correct return addresses.
LIMIT <number>
Maximum number of bytes to be sent per mail transfer.
Default is 64K bytes.
The limit applies to subsequent "send" commands.
UUENCODE
BTOA
Specify encoding to be used. Default is UUENCODE.
The encoding applies to subsequent "send" commands.
SEND <item> [<item>...]
Specify files to be sent.
Use "send index" to request a listing of available files.
RESEND <item> <part> [<part>...]
Re-sends the indicated <parts> from the specified <item>.
The encoding and limit must be identical to those used in the
original request.
HELP
This message.
END
EXIT
Terminate command processing. The remainder of
the input will be ignored.
Case is insignificant in the command verbs, but it IS
significant in the <path> and <item> specifications.
This server will provide files only to registered users with valid
service contracts. Requests are validated in either of two ways:
1) The return path (from the message headers or from a PATH
command) must match the registered E-mail address of a customer
with a valid support contract.
2) Specifying a customer ID (via the CUST command) will
validate the request against the specified customer's
service contract, and the reply will be sent to the
officially registered E-mail address for that customer ID.
If neither of these restrictions are met, the request will be ignored
and the reason for the error will be returned.
Please report problems with this server to ftpmail-admin@BSDI.COM.
Mail Server finished.
___________________________________________
This message is sent to you because you are subscribed to
the mailing list <ArabiaNewsEnglish@arabia.com>.
To unsubscribe, E-mail to: <ArabiaNewsEnglish-off@arabia.com>
Send administrative queries to <ArabiaNewsEnglish-request@arabia.com>