www.sendmail.org/faq/section4.html#4.7
Date: July 9, 1996 Updated: November 5, 1997 If at all possible, no. See RFCs 1535, 1536, and 1912 (updates RFC 1537) for more detail and other related (or common) problems. Wildcard MX records are just a bad idea, plain and simple. They don't work the way you'd expect, and virtually no one gets them right. Date: March 23, 1996 Updated: February 16, 1999 Updated: July 30, 2002 This is a local mailer issue, not a sendmail issue. Date: July 9, 1996 Updated: January 7, 1999 Again, this is a local mailer issue, not a sendmail issue. Either modify your local mailer (source code will be required) or change the program called in the "local" mailer configuration description to be a new program that does this local delivery. Date: March 23, 1996 Updated: August 14, 2000 Or, I'm trying to use the "don't deliver to expensive mailer" flag, and it delivers the mail interactively anyway. I can see it does it: here's the output of "sendmail -v foo@somehost" (or Mail -v or equivalent). The -v flag to sendmail (which is implied by the -v flag to Mail and other programs in that family) tells sendmail to watch the transaction. Since you have explicitly asked to see what's going on, it assumes that you do not want to to auto-queue, and turns that feature off. Remove the -v flag and use a "tail -f" of the log instead to see what's going on. If you are trying to use the "don't deliver to expensive mailer" flag (mailer flag "e"), be sure you also turn on global option "HoldExpensive" (whose old one-character name was "c") -- otherwise it ignores the mailer flag. The proper fix is to point the MX at the actual name, a "work-around" to add the MX target to class w. Date: March 23, 1996 I'm connected to the network via a SLIP/PPP link. Sometimes my sendmail process hangs (although it looks like part of the message has been transfered). Most likely, the problem isn't sendmail at all, but the low level network connection. It's important that the MTU (Maximum Transfer Unit) for the SLIP connection be set properly at both ends. If they disagree, large packets will be trashed and the connection will hang. To see what else is available today, check the 28 Comprehensive Perl Archive Network. If you're interested in using these kinds of tools to help you do some near real-time monitoring of your system, you might be interested in MEWS (Mail Early Warning System). From the README: If you've ever written a perl script to parse sendmail log files looking for errors, MEWS might be of interest to you. If you've ever thought about writing a perl script to munge sendmail log files, cringed a little and hurriedly came up with an excuse not to do it, read on. The Mail Early Warning System (MEWS) gives postmasters immediate notification of trouble spots on your mail backbone. To explain it in a nutshell, whenever sendmail returns a 4xx or 5xx SMTP code, with the MEWS modifications, it also sends the code over UDP to a daemon which then replays the error message to interested parties. Here's an update from Stephane Lentz on June 29, 2000: * 31 anteater - written in C++ (+ STL lib), fast, really promising (you can add modules) * 32 mreport - written in C, works fine on small logs but not with big hubs' log (all data are stored into memory) See also John Oliver's 33 sendmail tools page for pointers to several related scripts. Date: June 3, 2002 Sendmail's test mode is best for this. It has been ported to run on virtually every Unix-like OS you're likely to run into, and has a whole host of features. It is typically about 30% faster performing the job of the local mailer than programs such as /bin/mail or /usr/bin/mail, it has been hammered on widely to make it extremely secure (much more so than most local mailers) and very robust. In short, whatever you've got, you're almost guaranteed that procmail is better (if nothing else, the author has been able to focus lots of time and energy into making it the best and fastest tool available, while most system vendors just throw something together as fast as they can and move on to the whole rest of the OS). However, this only begins to scratch the surface of what procmail is capable of. It's most important feature is the fact that it gives you a standard way to create rules (procmail calls them "recipes") to process your mail before the messages get put into your mailbox, and for that feature alone, it is one of the most important tools any administrator can have in their repertoire. By filtering out or automatically dealing with 80% of your daily cruft, it lets you spend more time on the hard 20%. Procmail is also the core to a mailing list management package called "SmartList", so if you've already got procmail, adding SmartList may be a good option. Some listowners prefer Majordomo, Listserv, or one of those other programs, but SmartList has more than a few adherents as well. Your personal tastes will dictate whether you swear by SmartList or at it. Date: April 24, 1997 Updated: July 7, 1999 Please refer to the Sendmail 41 Year 2000 Readiness Disclosure page. Date: October 14, 1997 Updated: February 9, 1999 First, you need to get sendmail not to use DNS on your local machine so your host doesn't trying to connect to your ISP for a DNS query. You also need to designate a 43 "smart host" or external relay to handle all mail that you can't deliver locally (this would be your ISP's mailhost). You need to configure it so that the smtp mailer is considered "expensive" by adding the F=e mailer flag and tell sendmail not to connect to expensive mailers by default by setting the 44 HoldExpensive option to True. Finally, you need to run a program periodically to check in with your ISP and get them to deliver any mail they may have queued for you. Date: September 24, 1998 In general, sendmail does not perform final delivery of messages, but relies on a local delivery agent instead. These generally run in the range 64 - 78, so 1 would be out of range, and lead to sendmail generating the above error. The last two records are there "just in case" (someone forgot masquerading). Creating e-mail messages, including adding attachments or signatures, is the function of a mail user agent (MUA). Some popular MUAs include mutt, elm, exmh, Netscape, Eudora and Pine. Date: August 2, 1999 Updated: July 19, 2000 Updated: December 28, 2001 To find out which version is actually running, from without, telnet to the SMTP port (port 25). Date: November 18, 1999 Updated: August 8, 2001 You really shouldn't, because upper case characters in user names are contrary to the Unix tradition. As this is contrary to the expectations of many, it is not recommended. Another hack is the creation of aliases for Uppercase local users in the form: # lowercase version to real one uppercase: Uppercase It will make sendmail deliver messages to uppercase local recipients in a case insensitive manner. If it happens very often, it's either someone playing around or it's a network problem. In particular, NOQUEUE isn't an error indication, but just a "place-holder" when no queue ID has been assigned, typically because message collection hasn't started (yet). It can occur in other messages too, and there too the significant part is what comes after the NOQUEUE. Sendmail is a mail transfer agent whose primary purpose is to send and receive e-mail (primarily via SMTP). Sendmail does not implement any remote access protocols such as POP or IMAP. But if you want to learn more about these and other (non-sendmail) e-mail related things, please refer to our 56 Other (Non-Sendmail) E-Mail Related Links page. Date: June 30, 2000 Updated: February 27, 2001 Updated: June 5, 2001 Updated: February 13, 2003 It would require custom programming. Date: December 12, 2000 There is no magic short-cut for this. But it is not hard to set up: create an aliases entry alluser: :include:/etc/mail/allusers Don't forget to run 'newaliases'. Then list your users, one per line, in the file '/etc/mail/allusers'. Date: December 4, 2002 Several vendors have changed the way that sendmail is run. They decided that most people need a client-only version of sendmail.
|