| View previous topic :: View next topic |
| Author |
Message |
Rubes_sw
Valued Contributor
Joined: 11 Jun 2001
Posts: 625
Location: Northern Ireland
|
 Posted: Mon Dec 09, 2002 4:47 pm Post subject: Email Question |
 |
|
Is there any way to make an EMail server:
A. To handle internal Email via a Network
Handle multiple users and mailboxes
B. To send and receive external email.
Handle multiple users and mailboxes.
Any ideas, scripts, etc.???
Nathan |
|
| Back to top |
|
 |
Garrett
Moderator Team
Joined: 04 Oct 2001
Posts: 2149
Location: A House
|
| Posted: Mon Dec 09, 2002 11:23 pm Post subject: Re: Email Question |
|
|
| Rubes_sw wrote: | | Is there any way to make an EMail server: |
Well at least I can answer yes, you can at least make an email server.
| Rubes_sw wrote: | A. To handle internal Email via a Network
Handle multiple users and mailboxes |
Yes.
| Rubes_sw wrote: | B. To send and receive external email.
Handle multiple users and mailboxes. |
Yes.
| Rubes_sw wrote: | | Any ideas, scripts, etc.??? |
I know these things can be done. I have attempted a smtp server
before, but at the time, didn't have time to follow through with it.
Below is everything I have at least on smtp:
| Code: | SMTP SERVER COMMANDS/RESPONSES TO CLIENTS:
211 System status, or system help reply
214 Help message
[Information on how to use the receiver or the meaning of a particular non-standard command;
his reply is useful only to the human user]
220 <domain> Service ready
221 <domain> Service closing transmission channel
250 Requested mail action okay, completed
251 User not local; will forward to <forward-path>
354 Start mail input; end with <CRLF>.<CRLF>
421 <domain> Service not available, closing transmission channel
[This may be a reply to any command if the service knows it must shut down]
450 Requested mail action not taken: mailbox unavailable
[E.g., mailbox busy]
451 Requested action aborted: local error in processing
452 Requested action not taken: insufficient system storage
500 Syntax error, command unrecognized
[This may include errors such as command line too long]
501 Syntax error in parameters or arguments
502 Command not implemented
503 Bad sequence of commands
504 Command parameter not implemented
550 Requested action not taken: mailbox unavailable
[E.g., mailbox not found, no access]
551 User not local; please try <forward-path>
552 Requested mail action aborted: exceeded storage allocation
553 Requested action not taken: mailbox name not allowed
[E.g., mailbox syntax incorrect]
554 Transaction failed |
| Code: | The SMTP commands define the mail transfer or the mail system
function requested by the user. SMTP commands are character
strings terminated by <CRLF>. The command codes themselves
are alphabetic characters terminated by <SP> if parameters
follow and <CRLF> otherwise. The syntax of mailboxes must
conform to receiver site conventions. The SMTP commands are
discussed below. The SMTP replies are discussed in the next
part. A mail transaction involves several data objects,
which are communicated as arguments to different commands. The
reverse-path is the argument of the MAIL command, the forward-path
is the argument of the RCPT command, and the mail data is the
argument of the DATA command. These arguments or data objects
must be transmitted and held pending the confirmation
communicated by the end of mail data indication, which
finalizes the transaction. The model for this is that distinct
buffers are provided to hold the types of data objects, that
is, there is a reverse-path buffer, a forward-path buffer, and
a mail data buffer. Specific commands cause information to be
appended to a specific buffer, or cause one or more buffers to
be cleared.
The commands (these specifications are taken from RFC 821, which
is the place to look in for further details):
HELLO (HELO)
-----------------------------------------------------------------
This command is used to identify the sender-SMTP to the
receiver-SMTP. The argument field contains the host name of
the sender-SMTP. The receiver-SMTP identifies itself to the
sender-SMTP in the connection greeting reply, and in the
response to this command.
This command and an OK reply to it confirm that both the
sender-SMTP and the receiver-SMTP are in the initial state,
that is, there is no transaction in progress and all state
tables and buffers are cleared.
MAIL (MAIL)
-----------------------------------------------------------------
This command is used to initiate a mail transaction in which the
Sending a Message Using SMTP
Let’s look at an interactive session describing a simple
one-line message being sent using SMTP. The MTA used is
Sendmail in this case. When the -v flag is specified this
MTA displays what is sent and received across the SMTP
connection. Lines beginning with >>> are commands sent
by the SMTP client, and lines beginning with a 3-digit
reply code are from the SMTP server:
following is an example of a communication between client and server.
Connecting to mailhost via ether...
Trying 140.252.1.54... connected
220 noao.edu Sendmail 4.1/SAG-Noao.G89 ready at Mon, 19 Jul 93 12:47:34 MST
>>> HELO sun.tuc.noao.edu
250 noao.edu Hello sun.tuc.noao.edu., pleased to meet you
>>> MAIL From:<rstevens@sun.tuc.noao.edu>
250 <rstevens@sun.tuc.noao.edu>... Sender ok
>>> RCPT To:<rstevens@noao.edu>
250 <rstevens@noao.edu>... Recipient ok
>>> DATA
354 Enter mail, end with “.” on a line by itself
>>> .
250 Mail accepted
>>> QUIT
221 noao.edu delivering mail
rstevens@noao.edu... Sent
sent.
this is output by user agent
The amount of data typed to the user agent was a one-line message
(“1, 2, 3.”), but 393 bytes of data were sent - these 12 lines
sent to the client:
Received: by sun.tuc.noao.edu. (4.1/SMI-4.1)
id AA00502; Mon, 19 Jul 93 12:47:32 MST
Message-Id: <9307191947.AA00502@sun.tuc.noao.edu.>
From: rstevens@sun.tuc.noao.edu (Richard Stevens)
Reply-To: rstevens@noao.edu
X-Phone: +1 602 676 1676
X-Mailer: Mail User’s Shell (7.2.5 10/14/92)
To: rstevens@noao.edu
Subject: testing
1, 2, 3.
The first three lines ( Received: and Message-Id: ) are added by the MTA, and the next nine are generated by the user agent.
mail data is delivered to one or more mailboxes. The argument
field contains a reverse-path.
The reverse-path consists of an optional list of hosts and the
sender mailbox. When the list of hosts is present, it is a
"reverse" source route and indicates that the mail was relayed
through each host on the list (the first host in the list was
the most recent relay). This list is used as a source route to
return non-delivery notices to the sender. As each relay host
adds itself to the beginning of the list, it must use its name
as known in the IPCE to which it is relaying the mail rather
than the IPCE from which the mail came (if they are different).
In some types of error reporting messages (for example,
undeliverable mail notifications) the reverse-path may be
null (see Example 1).
This command clears the reverse-path buffer, the forward-path
buffer, and the mail data buffer; and inserts the reverse-path
information from this command into the path buffer.
RECIPIENT (RCPT)
-----------------------------------------------------------------
This command is used to identify an individual recipient of the mail data; multiple recipients are specified by multiple use of this command.
The forward-path consists of an optional list of hosts and a required destination mailbox. When the list of hosts is present, it is a source route and indicates that the mail must be relayed to the next host on the list. If the receiver-SMTP does not implement the relay function it may user the same reply it would for an unknown local user (550).
When mail is relayed, the relay host must remove itself from the beginning forward-path and put itself at the beginning of the reverse-path. When mail reaches its ultimate destination (the forward-path contains only a destination mailbox), the receiver-SMTP inserts it into the destination mailbox in accordance with its host mail conventions.
For example, mail received at relay host A with arguments
FROM:<USERX@HOSTY.ARPA>
TO:<@HOSTA.ARPA,@HOSTB.ARPA:USERC@HOSTD.ARPA>
will be relayed on to host B with arguments
FROM:<@HOSTA.ARPA:USERX@HOSTY.ARPA>
TO:<@HOSTB.ARPA:USERC@HOSTD.ARPA>.
This command causes its forward-path argument to be appended to the forward-path buffer.
DATA (DATA)
-----------------------------------------------------------------
The receiver treats the lines following the command as mail data from the sender. This command causes the mail data from this command to be appended to the mail data buffer. The mail data may contain any of the 128 ASCII character codes.
The mail data is terminated by a line containing only a period, that is the character sequence "<CRLF>.<CRLF>"). This is the end of mail data indication. The end of mail data indication requires that the receiver must now process the stored mail transaction information. This processing consumes the information in the reverse-path buffer, the forward-path buffer, and the mail data buffer, and on the completion of this command these buffers are cleared. If the processing is successful the receiver must send an OK reply. If the processing fails completely the receiver must send a failure reply.
When the receiver-SMTP accepts a message either for relaying or for final delivery it inserts at the beginning of the mail data a time stamp line. The time stamp line indicates the identity of the host that sent the message, and the identity of the host that received the message (and is inserting this time stamp), and the date and time the message was received. Relayed messages will have multiple time stamp lines.
When the receiver-SMTP makes the "final delivery" of a message it inserts at the beginning of the mail data a return path line. The return path line preserves the information in the <reverse-path> from the MAIL command. Here, final delivery means the message leaves the SMTP world. Normally, this would mean it has been delivered to the destination user, but in some cases it may be further processed and transmitted by another mail system.
It is possible for the mailbox in the return path be different from the actual sender's mailbox, for example, if error responses are to be delivered a special error handling mailbox rather than the message senders.
The preceding two paragraphs imply that the final mail data will begin with a return path line, followed by one or more time stamp lines. These lines will be followed by the mail data header and body. See Example 2.
Special mention is needed of the response and further action required when the processing following the end of mail data indication is partially successful. This could arise if after accepting several recipients and the mail data, the receiver-SMTP finds that the mail data can be successfully delivered to some of the recipients, but it cannot be to others (for example, due to mailbox space allocation problems). In such a situation, the response to the DATA command must be an OK reply. But, the receiver-SMTP must compose and send an "undeliverable mail" notification message to the originator of the message. Either a single notification which lists all of the recipients that failed to get the message, or separate notification messages must be sent for each failed recipient (see Example 1). All undeliverable mail notification messages are sent using the MAIL command (even if they result from processing a SEND, SOML, or SAML command).
SEND (SEND)
-----------------------------------------------------------------
This command is used to initiate a mail transaction in which the mail data is delivered to one or more terminals. The argument field contains a reverse-path. This command is successful if the message is delivered to a terminal. The reverse-path consists of an optional list of hosts and the sender mailbox. When the list of hosts is present, it is a "reverse" source route and indicates that the mail was relayed through each host on the list (the first host in the list was the most recent relay). This list is used as a
source route to return non-delivery notices to the sender. As each relay host adds itself to the beginning of the list, it must use its name as known in the IPCE to which it is relaying the mail rather than the IPCE from which the mail came (if they are different).
This command clears the reverse-path buffer, the forward-path buffer, and the mail data buffer; and inserts the reverse-path information from this command into the reverse-path buffer.
SEND OR MAIL (SOML)
-----------------------------------------------------------------
This command is used to initiate a mail transaction in which the mail data is delivered to one or more terminals or mailboxes. For each recipient the mail data is delivered to the recipient's terminal if the recipient is active on the host (and accepting terminal messages), otherwise to the recipient's mailbox. The argument field contains a reverse-path. This command is successful if the message is delivered to a terminal or the mailbox.
The reverse-path consists of an optional list of hosts and the sender mailbox. When the list of hosts is present, it is a "reverse" source route and indicates that the mail was relayed through each host on the list (the first host in the list was the most recent relay). This list is used as a source route to return non-delivery notices to the sender. As each relay host adds itself to the beginning of the list, it must use its name as known in the IPCE to which it is relaying the mail rather than the IPCE from which the mail came (if they are different).
This command clears the reverse-path buffer, the forward-path buffer, and the mail data buffer; and inserts the reverse-path information from this command into the reverse-path buffer.
SEND AND MAIL (SAML)
-----------------------------------------------------------------
This command is used to initiate a mail transaction in which the mail data is delivered to one or more terminals and mailboxes. For each recipient the mail data is delivered to the recipient's terminal if the recipient is active on the host (and accepting terminal messages), and for all recipients to the recipient's mailbox. The argument field contains a reverse-path. This command is successful if the message is delivered to the mailbox.
The reverse-path consists of an optional list of hosts and the sender mailbox. When the list of hosts is present, it is a "reverse" source route and indicates that the mail was relayed through each host on the list (the first host in the list was the most recent relay). This list is used as a source route to return non-delivery notices to the sender. As each relay host adds itself to the beginning of the list, it must use its name as known in the IPCE to which it is relaying the mail rather than the IPCE from which the mail came (if they are different).
This command clears the reverse-path buffer, the forward-path buffer, and the mail data buffer; and inserts the reverse-path information from this command into the reverse-path buffer.
RESET (RSET)
-----------------------------------------------------------------
This command specifies that the current mail transaction is to be aborted. Any stored sender, recipients, and mail data must be discarded, and all buffers and state tables cleared. The receiver must send an OK reply.
VERIFY (VRFY)
-----------------------------------------------------------------
This command asks the receiver to confirm that the argument identifies a user. If it is a user name, the full name of the user (if known) and the fully specified mailbox are returned.
This command has no effect on any of the reverse-path buffer, the forward-path buffer, or the mail data buffer.
EXPAND (EXPN)
-----------------------------------------------------------------
This command asks the receiver to confirm that the argument identifies a mailing list, and if so, to return the membership of that list. The full name of the users (if known) and the fully specified mailboxes are returned in a multiline reply.
This command has no effect on any of the reverse-path buffer, the forward-path buffer, or the mail data buffer.
HELP (HELP)
-----------------------------------------------------------------
This command causes the receiver to send helpful information to the sender of the HELP command. The command may take an argument (e.g., any command name) and return more specific information as a response.
This command has no effect on any of the reverse-path buffer, the forward-path buffer, or the mail data buffer.
NOOP (NOOP)
-----------------------------------------------------------------
This command does not affect any parameters or previously entered commands. It specifies no action other than that the receiver sends an OK reply.
This command has no effect on any of the reverse-path buffer, the forward-path buffer, or the mail data buffer.
QUIT (QUIT)
-----------------------------------------------------------------
This command specifies that the receiver must send an OK reply, and then close the transmission channel.
The receiver should not close the transmission channel until it receives and replies to a QUIT command (even if there was an error). The sender should not close the transmission channel until it sends a QUIT command and receives the reply (even if there was an error response to a previous command).
If the connection is closed prematurely the receiver should act as if a RSET command had been received (canceling any pending transaction, but not undoing any previously completed transaction), the sender should act as if the command or transaction in progress had received a temporary error (4xx).
TURN (TURN)
-----------------------------------------------------------------
This command specifies that the receiver must either (1) send an OK reply and then take on the role of the sender-SMTP, or (2) send a refusal reply and retain the role of the receiver-SMTP.
If program-A is currently the sender-SMTP and it sends the TURN command and receives an OK reply (250) then program-A becomes the receiver-SMTP. Program-A is then in the initial state as if the transmission channel just opened, and it then sends the 220 service ready greeting.
If program-B is currently the receiver-SMTP and it receives the TURN command and sends an OK reply (250) then program-B becomes the sender-SMTP. Program-B is then in the initial state as if the transmission channel just opened, and it then expects to receive the 220 service ready greeting.
To refuse to change roles the receiver sends the 502 reply.
There are restrictions on the order in which these commands may be used.
The first command in a session must be the HELO command.
The HELO command may be used later in a session as well. If the HELO command argument is not acceptable a 501 failure reply must be returned and the receiver-SMTP must stay in the same state.
The NOOP, HELP, EXPN, and VRFY commands can be used at any time during a session.
The MAIL, SEND, SOML, or SAML commands begin a mail transaction. Once started a mail transaction consists of one of the transaction beginning commands, one or more RCPT commands, and a DATA command, in that order. A mail transaction may be aborted by the RSET command. There may be zero or more transactions in a session.
If the transaction beginning command argument is not acceptable a 501 failure reply must be returned and the receiver-SMTP must stay in the same state. If the commands in a transaction are out of order a 503 failure reply must be returned and the receiver-SMTP must stay in the same state.
The last command in a session must be the QUIT command. The QUIT command can not be used at any other time in a session.
Some enlightening examples:
An undeliverable mail notification message is shown in example 1.
This notification is in response to a message originated by JOE at HOSTW and sent via HOSTX to HOSTY with instructions to relay it on to HOSTZ. What we see in the example is the transaction between
HOSTY and HOSTX, which is the first step in the return of the notification message.
Example 1
Example of Undeliverable Mail Notification Message
S: MAIL FROM:<>
R: 250 ok
S: RCPT TO:<@HOSTX.ARPA:JOE@HOSTW.ARPA>
R: 250 ok
S: DATA
R: 354 send the mail data, end with .
S: Date: 23 Oct 81 11:22:33
S: From: SMTP@HOSTY.ARPA
S: To: JOE@HOSTW.ARPA
S: Subject: Mail System Problem
S:
S: Sorry JOE, your message to SAM@HOSTZ.ARPA lost.
S: HOSTZ.ARPA said this:
S: "550 No Such User"
S: .
R: 250 ok
Example 1
Example 2
Example of Return Path and Received Time Stamps
Return-Path: <@GHI.ARPA,@DEF.ARPA,@ABC.ARPA:JOE@ABC.ARPA>
Received: from GHI.ARPA by JKL.ARPA ; 27 Oct 81 15:27:39 PST
Received: from DEF.ARPA by GHI.ARPA ; 27 Oct 81 15:15:13 PST
Received: from ABC.ARPA by DEF.ARPA ; 27 Oct 81 15:01:59 PST
Date: 27 Oct 81 15:01:01 PST
From: JOE@ABC.ARPA
Subject: Improved Mailing System Installed
To: SAM@JKL.ARPA
This is to inform you that ...
Example 2
|
The following code is old, and uses dlls. If you use this, you may want
to update it to newer dlls. Also, this is not a complete smtp server,
just the begining of one.
| Code: | OPTION ERRORTRAP,ERROR
Option Scale,96
external @path(%0)vdsdns.dll
EXTERNAL @path(%0)vdsinet.dll,
DIALOG CREATE,SMTP Server [Test Alpha],49,65,600,400
DIALOG ADD,STYLE,STYLE2,Courier New,8,,BLACK,LTGREEN
DIALOG ADD,STYLE,STYLE1,Courier New,10,,BLACK,CYAN
DIALOG ADD,LIST,LIST1,8,4,590,342,STYLE1,DBLCLICK
DIALOG ADD,EDIT,EDIT1,356,2,334,20
DIALOG ADD,BUTTON,SENDUSER,356,338,64,20,Send,default
DIALOG ADD,BUTTON,BUTTON2,356,404,64,20,Save Data
DIALOG ADD,BUTTON,bSERVER,356,470,30,20,On
DIALOG ADD,BUTTON,bDISCONNECT,356,502,30,20,Off
DIALOG ADD,BUTTON,EXIT,356,534,64,20,Exit
DIALOG ADD,STATUS,sSTATUS
DIALOG SHOW
Option Sleeptime,100
List Create,1
net socket,auto,
NET SOCKET,VDSEVENTS,
:evloop
Wait Event,0
%E = @event()
if %E
goto %E
end
goto evloop
:Timer
%%data1 = @NET(SOCKET,EVENT)
%%senderaddr = @net(socket,senderaddr)
dialog set,sSTATUS,%%data - %%data1
rem If @not(@null(%%data))
rem List Add,LIST1,%%data
rem List Seek,LIST1,@fsub(@count(LIST1),1)
rem gosub CHECKCOMMANDS
rem List Seek,LIST1,@fsub(@count(LIST1),1)
rem %%data =
rem End
If @not(@null(%%data1))
If @equal(%%data1,ACCEPT)
%%data = @net(socket,data)
List Add,LIST1,%%data
net socket,sendaddr,%%senderaddr,220 c248317-b.tcma1.wa.home.com
List Add,LIST1,220 c248317-b.tcma1.wa.home.com
gosub CHECKCOMMANDS
List Seek,LIST1,@fsub(@count(LIST1),1)
End
If @equal(%%data1,NETWORK)
%%data = @net(socket,data)
List Add,LIST1,%%data
List Seek,LIST1,@fsub(@count(LIST1),1)
gosub CHECKCOMMANDS
List Seek,LIST1,@fsub(@count(LIST1),1)
End
If @equal(%%data1,CLOSEC)
%%data = @net(socket,data)
List Add,LIST1,%%data
List Seek,LIST1,@fsub(@count(LIST1),1)
gosub CHECKCOMMANDS
List Seek,LIST1,@fsub(@count(LIST1),1)
End
%%data1 =
%%data =
End
rem dialog set,sSTATUS,@net(socket,status)
goto evloop
:CHECKCOMMANDS
If @equal(@substr(%%data,1,4),HELO)
net socket,sendaddr,%%senderaddr,250 Welcome [127.0.0.1], pleased to meet you
List Add,LIST1,250 Welcome [127.0.0.1], pleased to meet you
Exit
End
If @equal(@substr(%%data,1,4),MAIL)
net socket,sendaddr,%%senderaddr,250 Sender "logicalbox@home.com" OK...
List Add,LIST1,250 Sender "logicalbox@home.com" OK...
Exit
End
If @equal(@substr(%%data,1,4),RCPT)
net socket,sendaddr,%%senderaddr,250 Recipient OK
List Add,LIST1,250 Recipient OK
Exit
End
If @equal(@substr(%%data,1,4),DATA)
net socket,sendaddr,%%senderaddr,354 "Enter mail, end with "@chr(34).@chr(34)" on a line by itself"
List Add,LIST1,"Enter mail, end with "@chr(34).@chr(34)" on a line by itself"
Wait 1
Exit
End
If @equal(@substr(%%data,@fsub(@len(%%data),3),@len(%%data),@cr().@cr()))
net socket,sendaddr,%%senderaddr,250 Message accepted for delivery.
List Add,LIST1,250 Message accepted for delivery.
Wait 1
Exit
End
If @equal(@substr(%%data,1,4),QUIT)
net socket,sendaddr,%%senderaddr,221 Will send - Goodbye.
List Add,LIST1,221 Will send - Goodbye
Exit
End
Exit
:NETWORK
goto evloop
:SENDUSERBUTTON
net socket,sendaddr,127.0.0.1,@dlgtext(EDIT1)
List Add,LIST1,@dlgtext(EDIT1)
Dialog Set,EDIT1,
goto evloop
:bSERVERBUTTON
net socket,port,26
NET SOCKET,ADDR,127.0.0.1
net socket,server
DIALOG Enable,bDISCONNECT
DIALOG DISABLE,bSERVER
dialog set,sSTATUS,@net(socket,status)
goto evloop
:bDISCONNECTBUTTON
net socket,close
DIALOG DISABLE,bDISCONNECT
DIALOG Enable,bSERVER
dialog set,sSTATUS,@net(socket,status)
goto evloop
:LIST1DBLCLICK
Info @item(LIST1)
goto evloop
:BUTTON2BUTTON
List Savefile,LIST1,@path(%0)smtp-output.txt
Info Saved
goto evloop
:ERROR
net socket,close
Warn Error Line: @error(n)@cr()Error Number: @error(e)@CR()Error Network: @net(socket,error)@cr()Event Called: %E
:EXITBUTTON
:Close
Exit |
-Garrett |
|
| Back to top |
|
|
Skit3000
Admin Team
Joined: 11 May 2002
Posts: 2166
Location: The Netherlands
|
| Posted: Tue Dec 10, 2002 1:06 pm Post subject: |
|
|
Hi Rubes,
I made a example for this a little time ago, you can find it here. I didn't had all that info Garrett posted, so maybe I'll update it some time.... |
|
| Back to top |
|
|
Garrett
Moderator Team
Joined: 04 Oct 2001
Posts: 2149
Location: A House
|
| Posted: Tue Dec 10, 2002 8:42 pm Post subject: |
|
|
Skit, if you had posted about smtp before, I may have missed your
post, otherwise, I probably would have dumped all this on you also. 
-Garrett |
|
| Back to top |
|
|
Hortalonus
Valued Contributor
Joined: 15 Mar 2002
Posts: 344
Location: Western USA
|
| Posted: Tue Dec 10, 2002 11:14 pm Post subject: |
|
|
Garrett,
I'm curious about the vdsdns.dll file you used in you SMTP server. I have never seen any other reference to it. I could very much use a DNS extension in several of my programs. Can you point me in the right direction? |
|
| Back to top |
|
|
Garrett
Moderator Team
Joined: 04 Oct 2001
Posts: 2149
Location: A House
|
| Posted: Tue Dec 10, 2002 11:51 pm Post subject: |
|
|
Hmmm, let me see if that was a release dll or not... BRB.
-Garrett |
|
| Back to top |
|
|
Garrett
Moderator Team
Joined: 04 Oct 2001
Posts: 2149
Location: A House
|
| Posted: Tue Dec 10, 2002 11:56 pm Post subject: |
|
|
Well don't I feel like an idiot again! There's that ADD of mine doing it's
job!. That dll was not released, and it's been sitting here for almost a
year now! 
I'll try to get that zipped up and posted today, or during the week
sometime.
-Garrett |
|
| Back to top |
|
|
Hortalonus
Valued Contributor
Joined: 15 Mar 2002
Posts: 344
Location: Western USA
|
| Posted: Wed Dec 11, 2002 2:12 pm Post subject: |
|
|
 Sweet! I'm excited already... early Christmas for me! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
@vdsworld