harrison@csl.dl.nec.com (Mark Harrison) (06/22/91)
I am looking for different mail servers, where someone can send mail
in the form "send file", and that file is then mailed back to the
user.
I currently have netlib, but am wondering if there is anything else
availible. I would like to use this to manage file updating between
two different sites, with messages like
"edit foo/Makefile" #source is checked out from sccs and mailed, and
"delta foo/Makefile" #updates file with the text of the mail message
#sans headers, or else puts it in a queue for
#an administrator to approve and update.
Any pointers appreciated. If you post, would you mind mailing
me a copy for good luck? I'm drowning in news and would hate
to miss a suggestion.
Thanks in advance,
Mark.
--
Mark Harrison | Note: harrison@ssd.dl.nec.com and
harrison@csl.dl.nec.com | necssd!harrison are not operating at
(214)518-5050 | present. Please forward mail through the
| above address. Sorry for the inconvenience.renkel@motcid.UUCP (Will Renkel) (06/24/91)
Using mailx one can pipe the mail message to another program and then the whole world opens up. ------------------------------------------------------------------------------ Will Renkel - Motorola - Cellular 1501 W. Shure Drive - Room N258, Arlington Heights, IL 60004 (708) 632-4416 - ...uunet!mcdchg!motcid!renkel - renkel@void.rtsg.mot.com ------------------------------------------------------------------------------
shaver@convex.com (Dave Shaver) (06/24/91)
harrison@csl.dl.nec.com (Mark Harrison) writes: >I am looking for different mail servers, where someone can send mail >in the form "send file", and that file is then mailed back to the >user. >I currently have netlib, but am wondering if there is anything else >availible. [...] I wrote such a server in Perl---many people are either using it or the original upon which I based my server. Thanks once again to jv@mh.nl (Johan Vromans) for sharing his Multihouse server. I'm willing to mail either uuencoded or btoa'ed compressed tar files of the server code if you can't FTP. If you can FTP, the server code is on elroy.cs.iastate.edu (129.186.3.15) in /pub/servers/csdserv.TZ. Let me know if you try it or if you need help. Here's my original summary posting when I asked this question a little over a year ago. All of these servers are available via ftp in the /pub/servers directory on elroy. /\ Dave Shaver \\ CONVEX Computer Corporation, Richardson, TX \/ Internet: shaver@convex.com UUCP: uunet!convex!shaver | From shaver Mon Apr 23 15:40:38 1990 | From: shaver | Newsgroups: comp.mail.misc | Distribution: na | Subject: Summary: Mail servers: Seeking comments and source code | Keywords: Summary | | A while back I asked: | | > I'm looking for source code, documentation, and user/administrator | > comments about any mail/archive servers running under UNIX. I'm going | > to combine the best documentation and more useful features of the | > various packages into a mail server for our department. | > [...] | > I will summarize and post a follow-up to comp.mail.misc (only). | | Thanks to everyone who responded to my request. Based on your comments | and some digging of my own I've chosen an existing server as a starting | point for our server. However, I'd still like comments from USERS of | mail servers as to what features they find most useful, confusing, | poorly documented, etc. | | In all I found five servers: DECWRL server, B-Server, KISS, Multihouse | Research server, and the NETLIB server. From this line-up I've chosen | the Multihouse Research server. The main win for it was that it's | written in Perl. (I'm a newly-hatched perl fanatic.) | | Here are my comments on each server. I apologize in advance if I | offend anyone, but my opinions of the servers were based on a one hour | or so look though the source code of each server. | | DECWRL server | | - Written with many shell scripts and a few AWK scripts | - Very careful about not overloading server machine | (Remember, this used to run on an over-worked VAX.) | - Very easy to install; best of the group? | - Code is all quite generic | - Good at letting person making request know what happened | (No black holes for mail.) | - Good user-level docs (especially the "help" file) | - Very fair queuing system; people can't make "pigs" of themselves | - 4 user commands: help, index, send, path | | NETLIB server | | - User-level docs a bit rough. Assumes user is quite mail savvy. | (Not a fair assumption in my case.) | - Catches "pigs" effectively, but no queuing system for requests. | - Notices attempted security violations using magic shell characters | - Install docs adequate, but not outstanding | - Hard to install since site-specific stuff not centralized | in a config file. | - Has almost no interal documentation (i.e. comments) | - Eclectic mix of shell scripts and C programs | - Some sections of code very specific to serving libs. Does | not generalize well to ASCII files. | | Multihouse Research server | | - Written in Perl!!! | - Distribution under the GNU PL | - Good at letting person making request know what happened | - 10 user-level commands: path, limit, uuencode, btoa, send, resend, index, | help, test, end/exit. | - Good "help" reply | - Very extentable and easily modified | - Code is readable; useful, plentiful comments | - Easy to install. | - Very good about splitting archives | - Can resend PARTS of archives which were mangled in transport | | KISS | - Simple. 8-) | - One shell script, plus a user-supplied program | - No batching, quotas, or scheduling. | - 5 user commands: help, index, send, path, quit | - Good install docs | | B-Server | - Don't need to create system-wide alias (uses sendmail .forward file) | - One shell script | - Can refuse to provide service to certain people | - Has file and request limits | - 4 user commands: help, index, send, get |[...]