tyc@cbnewse.att.com (felix.a.lugo) (03/23/91)
How do I tell MailApp to use newlines instead of carriage-returns at the end of Non-NeXT messages. Here's the scenario, I write-up a mail message using MailApp in Non-NeXT mode and send it to a non- NeXT system (actually running System V). When I receive the message, every line has a carriage return at the end, making it very unfriendly. Maybe it's not the MailApp? It could be sendmail, since I've noticed that if I use "mail" or "Mail", I end up with the same result. Anyone has any idea how to correct this???? /* ** ============================================================================ ** ** Felix A. Lugo AT&T Bell Laboratories ** ** E-Mail: ** (708) 713-4374 coco@ihcoco.ihlpb.att.com att!ihlpb!ihcoco!coco ** ** ============================================================================ */
irv@happym.WA.COM (Irving Wolfe) (03/26/91)
In <1991Mar22.221810.20589@cbnewse.att.com> tyc@cbnewse.att.com (felix.a.lugo) writes: > How do I tell MailApp to use newlines instead of carriage-returns > at the end of Non-NeXT messages It's one of the many bugs in the sendmail.*.cf files that NeXT distributes. Near as I could figure out, talking to them, they have no sendmail expert and don't really care because they use SMTP, ethernet, Internet, etc., almost exclusively so it looks to them like their broken .cf files are okay. The fix for the particular problem that's bothering you is to change from: Muucp, P=/usr/bin/uux, F=msDFMhuU, S=13, R=23, A=uux - -r $h!rmail ($u) to: Muucp, P=/usr/bin/uux, F=sCDRMhumU, S=13, R=23, M=100000, A=uux - -gC -a$f $h!rmail ($u), E=\n In this case, it's the E=\n that does the trick. I don't remember what the other changes do, and they may depend upon changes elsewhere, so if you only have the one problem, you might want to ignore the rest and just add ", E=\n" to solve this one. Really, since almost all uucp systems use FQDN (@) addressing preferentially to bang (!) addressing at this point, the lack of any support for a "uusmail" or "uusendmail" mailer that doesn't attempt to convert to bang format in NeXT's .cf files is pretty hard to understand. The distributed .cf files also have the obnoxious habit of illegally re-writing the From: and To: lines of uucp messages, instead of just monkeying with the envelope (From_ in uucp) header and inserting the usual Received-by: stuff to allow tracing a return path at the delivery end. We know _extremely_ little about this stuff, but the people that do know (outside NeXT) are busy and just say RTFM (which we don't have and don't know how to get), so we had to come up with a few fixes ourselves. And if anyone wonders why our quite good accounting software hasn't yet appeared on the NeXT, it's because the two people doing the port have had to spend most of their time getting basic system stuff like networking and uucp working right so they couldn't do their real jobs. We _wanted_ to be application programmers, not system hackers, but the people at NeXT couldn't or wouldn't solve these system-level problems for us and we got stuck working on them. One good starting point for anyone interested in solving these problems is Evi Nemeth's UNIX System Administration Handbook. Unfortunately, it isn't quite enough in the sendmail area, but it helped a lot, and includes .cf sample code that doesn't munge the From: and To: (and Reply-To:) headers. While you're changing things, this will be helpful instead of what's there: # my official hostname Dj$?m$w.$m$|$w$. -- Irving_Wolfe@happym.wa.com Happy Man Corp. 206/463-9399 x101 4410 SW Pt. Robinson Rd., Vashon Island, WA 98070-7399 fax x104 We publish SOLID VALUE for the intelligent investor. (NextMail Info. free (sample $20): E-mail patty@happym.wa.com. okay too)