qmail Digest 20 Jan 1999 11:00:16 -0000 Issue 526
qmail Digest 20 Jan 1999 11:00:16 - Issue 526 Topics (messages 20654 through 20701): Three solutions for spam 20654 by: [EMAIL PROTECTED] 20674 by: "Racer X" <[EMAIL PROTECTED]> 20676 by: "Racer X" <[EMAIL PROTECTED]> 20692 by: Russ Allbery <[EMAIL PROTECTED]> 20693 by: Russ Allbery <[EMAIL PROTECTED]> 20695 by: "Racer X" <[EMAIL PROTECTED]> 20696 by: "Racer X" <[EMAIL PROTECTED]> 20700 by: Pavel Kankovsky <[EMAIL PROTECTED]> 20701 by: [EMAIL PROTECTED] Possible Anti-spam solution (was Re: Example of the anti-fax effect) 20655 by: Pavel Kankovsky <[EMAIL PROTECTED]> 20679 by: Mark Delany <[EMAIL PROTECTED]> Mailbox altered by pine? 20656 by: Stanley Horwitz <[EMAIL PROTECTED]> 20657 by: Sam <[EMAIL PROTECTED]> 20658 by: Vince Vielhaber <[EMAIL PROTECTED]> 5,000 dial-up users. 20659 by: "Andy Cowles" <[EMAIL PROTECTED]> How do I filter outgoing mail based on Sender ? 20660 by: [EMAIL PROTECTED] 20675 by: "Luca Olivetti" <[EMAIL PROTECTED]> remember this? 20661 by: Steve Vertigan <[EMAIL PROTECTED]> [[EMAIL PROTECTED]: failure notice] 20662 by: Peter van Dijk <[EMAIL PROTECTED]> 20671 by: Mario Lorenz <[EMAIL PROTECTED]> 20678 by: "D. J. Bernstein" <[EMAIL PROTECTED]> Newsgroups w/qmail 20663 by: "Brock Eastman" <[EMAIL PROTECTED]> 20664 by: Lars Balker Rasmussen <[EMAIL PROTECTED]> Emacs MUA's and sendmail errors 20665 by: Dave Sill <[EMAIL PROTECTED]> pipelining 20666 by: Dave Sill <[EMAIL PROTECTED]> Some Progress... 20667 by: Craig Burley <[EMAIL PROTECTED]> 20669 by: Sam <[EMAIL PROTECTED]> unresolvable relay 20668 by: [EMAIL PROTECTED] 20670 by: Sam <[EMAIL PROTECTED]> 20672 by: Michael Bracker <[EMAIL PROTECTED]> relays and VERP 20673 by: Pavel Kankovsky <[EMAIL PROTECTED]> 20680 by: Mark Delany <[EMAIL PROTECTED]> 20685 by: Pavel Kankovsky <[EMAIL PROTECTED]> VERB 20677 by: Russell Nelson <[EMAIL PROTECTED]> 20682 by: Matthias Pigulla <[EMAIL PROTECTED]> 20683 by: Keith Burdis <[EMAIL PROTECTED]> 20684 by: Sam <[EMAIL PROTECTED]> 20686 by: [EMAIL PROTECTED] 20687 by: Russell Nelson <[EMAIL PROTECTED]> 20688 by: Matthias Pigulla <[EMAIL PROTECTED]> 20689 by: Pavel Kankovsky <[EMAIL PROTECTED]> 20690 by: Matthias Pigulla <[EMAIL PROTECTED]> RFC qmail optimizations [Was: relays and VERP] 20681 by: Matthias Pigulla <[EMAIL PROTECTED]> Fwd: Fwd: Re: Unsubscribe info 20691 by: Keith Burdis <[EMAIL PROTECTED]> qmail error loggin 20694 by: Matthias Pigulla <[EMAIL PROTECTED]> HELP ! qmail-pop3d not timing out. 20697 by: R Aldridge <[EMAIL PROTECTED]> Solaris 7 intel and Qmail install 20698 by: Bert Beaudin <[EMAIL PROTECTED]> 20699 by: "Adam D. McKenna" <[EMAIL PROTECTED]> Administrivia: To subscribe to the digest, e-mail: [EMAIL PROTECTED] To unsubscribe from the digest, e-mail: [EMAIL PROTECTED] To post to the list, e-mail: [EMAIL PROTECTED] -- On Mon, 18 Jan 1999, Edward S. Marshall wrote: > On Mon, 18 Jan 1999 [EMAIL PROTECTED] wrote: > > > Invalid assumption; you do not have the "right" to send me mail. You -may- > > > be able to send me mail if you pass my "arbitrary criteria". > > > > Do you warn your customers, that they may never receive legitimate mail? > > Of course. Anything else would be a disservice to them, and a legal > liability to me. Really? Well the good news are, u show some wisdowm, the bad news i would never use your services. :-) I prefer to get some spam (which in fact i do, i don't count it, but's something like 3-4 messages a day) than to lose legitimate mail. -- Tiago Pascoal ([EMAIL PROTECTED]) FAX : +351-1-7273394 Politicamente incorrecto, e membro (nao muito) proeminente da geracao rasca. >Of course there is. Blocking port 25 for all their dialup lines is a >simple router configuration. Re-enabling it on a customer-by-customer >basis on dynamic dialups requires software to interact with the terminal >authentication server that they'd probably have to write themselves. Wrong. It simply requires you to use Radius and network equipment that allows you to send back filters in your Radius authentication. Neither of these are esoteric or hard to do, and are the rule, not the exception, at any ISP with more than a handful of users. >Lots of people scream loudly at an overworked ISP about spam from their >dialups. ISP could (a) improve their tracking and reporting measures and >their abuse staff and cancel spammer accounts faster, What exactly did you have in mind to "improve tracking and reporting measures?" Tracking and reporting is not the probl
Re: Solaris 7 intel and Qmail install
Try putting /usr/ccs/bin in your path, I don't know if this will fix your problem but it fixed a lot of compile problems I was having on Solaris. --Adam - Original Message - From: Bert Beaudin <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 19, 1999 10:21 PM Subject: Solaris 7 intel and Qmail install :Hello all : Trying to install qmail on a solaris 7 intel box. I have compiled other :programs fine. When I try to install qmail I get the following. I have :taken a look at the archives but not found any answers. Thanks for any help. : :Bert Beaudin : : :chmod 755 makelib :./compile case_diffb.c :./compile case_diffs.c :./compile case_lowerb.c :./compile case_lowers.c :./compile case_starts.c :./makelib case.a case_diffb.o case_diffs.o case_lowerb.o \ :case_lowers.o case_starts.o :ar: cannot open case_diffb.o :No such file or directory :ar: cannot open case_diffs.o :No such file or directory :ar: cannot open case_lowerb.o :No such file or directory :ar: cannot open case_lowers.o :No such file or directory :ar: cannot open case_starts.o :No such file or directory :ar: case_diffb.o not found :ar: case_diffs.o not found :ar: case_lowerb.o not found :ar: case_lowers.o not found :ar: case_starts.o not found :make: *** [case.a] Error 5 : : : : :
Re: Three solutions for spam
On 19 Jan 1999, Russ Allbery wrote: > But in a world where ISPs routinely give out free trial accounts and > certain large ISPs refuse as a matter of policy to even check credit > card numbers to see if they belong to people who were previously > kicked off for spamming, trying to do anything *real* about spam is > almost a lost cause. Complain loudly about EVERY SINGLE piece of spam you receive. They will change their mind. Sooner or later. :) --Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ] "NSA GCHQ KGB CIA nuclear conspiration war weapon spy agent... Hi Echelon!"
Qmail's user database
Hi, Regarding Qmail and it's record of users (as opposed to user authentication in POP), so that mail can be delivered to a user's mailbox: I understand that this is generated into a cdb file, which is periodically rebuilt with qmail-newu. Regarding this cdb mechanism, - How long would it take to rebuild a file for, say, 10 users on a powerful machine (say good Sun or dual-Pentium)? - Is Qmail tied to using cdb as its mailbox-lookup mechanism, or could a back-end database be used, to accept new users on the fly without having to rebuild a 'static' database periodically? cheers, Andrew Richards.
Is IMAP cpu-, io- and ram-CONSUMING?
Hello, not directly qmail-related, but as a posting to the german mailserver group did not end in an answer, I will try it here: - am I right that while a imap-connection exists, one or two instances of the imapd are staying in memory, - one instance of imapd on my RH5.2 takes about 1,5MB of memory, of which ca. 750kB are shared, - so if I wanted to run a system with a maximum of 50 clients connected, memory consumption will be approx. 2x0.75x50 = 75MB and therefore - it would be reasonable to install at least 96MB of RAM to warrant reaction time is OK for the clients. - I'd guess I/O is important too especially if the users have a whole bunch of big mailboxes - Now what about CPU power? Is this important? Maybe someone would be so kind to assure, comment or deny my assumptions. Thank you Mirko -- mailto:[EMAIL PROTECTED] surfto:http://sites.inka.de/picard -- mailto:[EMAIL PROTECTED] surfto:http://sites.inka.de/picard
forwarding is BCC?
Hello, I now let deliver all mail from this list to a maildir and post it afterwards with a simple batch. Now I want to send a mail to the list out of the newsclient. I tried to simply reply and changing the to-field to [EMAIL PROTECTED] and deleting the in-replyto this will start a new thread. I tried to define an "global alias" like this: [root@picard queue]# cat /etc/qmail/alias/.qmail-qmail-liste | forward [EMAIL PROTECTED] But when I mailed to qmail-liste, the message was bounced at muncher.math.uic.edu. <[EMAIL PROTECTED]>: I do not accept blind carbon copies. Please use To or Cc. Does qmail do a BCC when forwarding messages like above?. Thanks for your answers Mirko -- mailto:[EMAIL PROTECTED] surfto:http://sites.inka.de/picard
Anyone can help me?
Hi, I'm a user of qmail but I'm not very experienced on it. By the way, this is my question: I've defined a virtual domain in a Linux machine where the qmail is running and from an Exchange Server in another place I try to connect to the qmail server to download the mail but I can't. Someone has told me about maildir2smtp, but I don't know how it works. Thanks. Carles Latorre.
Re: Three solutions for spam
On Tue, 19 Jan 1999, Racer X wrote: > >Don't fool yourself. The benefit to the customer in blocking port 25 > >outbound is basically nonexistent; it's entirely about administrative > >resources devoted to keeping one's site from abusing the Internet. It > may > >be necessary, but you can't sell it as a feature. > > Methinks you've never actually worked in this business. Perhaps you > can't "sell" the feature, no. But it makes the business more efficient > and competitive by taking better advantage of scarce resources (and yes, > resources are quite scarce in this industry). This is a Good Thing for > everyone involved. Who are u to decide what's best for others? U may certainly know what's best for you, but please don't decide what is best for others. It seems u have the "i know best" attitude. As your client, i would simply go away, and turn to people who let other people decide what's best for them. -- Tiago Pascoal ([EMAIL PROTECTED]) FAX : +351-1-7273394 Politicamente incorrecto, e membro (nao muito) proeminente da geracao rasca.
Re: forwarding is BCC?
- Mirko Zeibig <[EMAIL PROTECTED]>: | I tried to define an "global alias" like this: | [root@picard queue]# cat /etc/qmail/alias/.qmail-qmail-liste | | forward [EMAIL PROTECTED] | | But when I mailed to qmail-liste, the message was bounced at | muncher.math.uic.edu. | <[EMAIL PROTECTED]>: | I do not accept blind carbon copies. Please use To or Cc. | | Does qmail do a BCC when forwarding messages like above?. It does not edit the To: or Cc: header fields, just passes the mail on with the new envelope recipient. I would not call that "do a BCC", but the effect is essentially the same. You will have to rewrite headers if you wish to post to the qmail list in this way. It may be that you can find a program in Dan's mess822 package that will help you with the header rewriting. - Harald
Re: qmail error loggin
- Matthias Pigulla <[EMAIL PROTECTED]>: | where can I look up descriptions for error messages qmail logs, | e.g. "I could'nt find any host by that name (#4.1.2)"? RFC 1893. - Harald
Help?
Hello, whoever's there; What I'm trying to do is this; set up [EMAIL PROTECTED], [EMAIL PROTECTED], etc, virtually. That is; I have a box; gwydion.domain.net. I can recive mail on it; [EMAIL PROTECTED] I want to be able to recieve mail at [EMAIL PROTECTED] and have that mail automatically forwarded to [EMAIL PROTECTED], for example, and have [EMAIL PROTECTED] forward it's mail automatically to [EMAIL PROTECTED] Regardless of the eventually recieving mailbox, I want to be able to configure qmail to recieve mail at [EMAIL PROTECTED] and for each user have qmail know where to send on that message so that the user gets it. IS THERE any way to do this? (I can't find it in the documentation) IF so; what is it? Thanks for you time and attention, cHris Naden (sysadmin, HighwayOne corporation
UCE Patches
Dear Qmail Users, where can I find the "sender domain must exist" patch? where can I find the badrcptto patch? where can I find the "match address against a regex" patch? I looked at www.qmail.org, but all patches I found are for old versions or not available. Thanks. Bernhard
Qmail RPMs.
RPMs for qmail. Sorry if this is a repost. ftp://moni.msci.memphis.edu/pub/qmail Hope this helps some people. Reid Sutherland Network Administrator ISYS Technology Inc. http://www.isys.ca Fingerprint: 1683 001F A573 B6DF A074 0C96 DBE0 A070 28BE EEA5
Re: Help?
- [EMAIL PROTECTED] (Chris Naden): | What I'm trying to do is this; set up [EMAIL PROTECTED], | [EMAIL PROTECTED], etc, virtually. That is; I have a box; | gwydion.domain.net. | I can recive mail on it; [EMAIL PROTECTED] I want to be able to | recieve mail at [EMAIL PROTECTED] and have that mail automatically | forwarded to [EMAIL PROTECTED], for example, and have [EMAIL PROTECTED] | forward it's mail automatically to [EMAIL PROTECTED] Do: echo domain.org:alias-domain >> ~qmails/control/virtualdomains echo domain.org >> ~qmails/control/rcpthosts echo [EMAIL PROTECTED] > ~alias/.qmail-domain-mailadd1 echo [EMAIL PROTECTED] > ~alias/.qmail-domain-mailadd2 and don't forget: echo [EMAIL PROTECTED] > ~alias/.qmail-domain-postmaster Make sure domain.org is not in control/locals. Restart qmail (or just give qmail-send a SIGHUP), and voila. To understand how this works and how to extend it to other situations, RTFM qmail-send and dot-qmail. The above suggestions come with no guarantee; you must understand it yourself, or else. - Harald
Re: relays and VERP
On Tue, 19 Jan 1999 20:28:38 +0100 (MET), Pavel Kankovsky wrote: >Conclusion: qmail does not need to send multiple copies of VERPed message >if the destination SMTP server runs qmail (or any other VERP-enabled MTA >if such MTA existed). > >Of course, it needs to figure out whether a particular MTA supports VERP. This sounds like a job for QMTP. -Sincerely, Fred (Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)
Re: VERH [was VERB]
On 19 Jan 1999 20:11:56 -, Russell Nelson wrote:
>Okay, VERP has solved the bounce problem. Now we need VERB (Variable
>Envelope Recipient in Body) to solve the unsubscribe problem.
>Basically, we need qmail-remote to merge the envelope recipient into
>the message somewhere. The problem, of course, is *where* to insert
I think the substitution idea is good, but putting it into the message
is Not Good (TM). qmail should not under any circumstances corrupt the
message, which might contain any character sequence.
Putting it into the header circumvents that problem. Also, the amount
of text that has to be parsed is limited this way. Yes, there are
disadvantages (stupid subscribers), but that's less important than
message integrity.
There is rfc2069 which describes how to put unsubscribe info into
headers. I think putting it there, maybe doing VERH expansion like VERP
-@[] or separate tokens for LOCAL and HOST? The flag controlling this
could be if VERP is used for the message.
Currently, VERP expansion is done at the level of qmail-send. VERH
expansion needs to be in qmail-remote (and really also qmail-local).
qmail-send has the info that VERP is used, so it would have to pass the
flag to qmail-{r|l}spawn to qmail-remote/local. There is no reason the
character sequence -@[] should occur in a header. Whatever the magic
token is, it should be legal in a header, since someone might use it
where VERH is not supported.
For subscribers, you could to a message trailer add "see
List-Unsubscribe: header for info on how to unsubscribe". As Sen Nagata
pointed out on the ezmlm list, rfc2069 may not be such a bad idea, and
good MUAs will rapidly support it once it's used more. ezmlm would
support this "out of the box".
-Sincerely, Fred
(Frederik Lindberg, Infectious Diseases, WashU, St. Louis, MO, USA)
MAILHOST and envelope sender
I would really like to know what the heck MAILHOST and friends are doing. It was stated that MAILHOST does not set the envelope sender. Well, I did the following experiment $ export MAILHOST=oki.doki $ export QMAILINJECT=f $ echo '|echo $SENDER > hosttest.out' .qmail-hosttest $ echo|mail mw-hosttest $ cat hosttest.out [EMAIL PROTECTED] So it is supposed to effect the envelope sender. But then I start Emacs from the same shell, send a message as To: mw-hosttest Subject: test --text follows this line-- test and I get $ cat hosttest.out [EMAIL PROTECTED] Setting QMAILSHOST has the same effect---nothing. The only way I can change the domain part of the envelope sender's address for Emacs, if I put oki.doki in defaulthost. What is going on? Mate
RE: MAILHOST and envelope sender
Mate Wierdl wrote/schrieb/scribsit: > $ export MAILHOST=oki.doki > $ export QMAILINJECT=f Have you tried setting it to "s"? Emacs might be supplying a return-path. Stefan
Re: MAILHOST and envelope sender
On Wed, Jan 20, 1999 at 09:58:09AM -0600, Mate Wierdl wrote: > I would really like to know what the heck MAILHOST and friends are doing. > > It was stated that MAILHOST does not set the envelope sender. Well, I did > the following experiment > > $ export MAILHOST=oki.doki > $ export QMAILINJECT=f > $ echo '|echo $SENDER > hosttest.out' .qmail-hosttest > $ echo|mail mw-hosttest > $ cat hosttest.out > [EMAIL PROTECTED] > > So it is supposed to effect the envelope sender. It looks that way. When I posted that message saying it didn't, I was basing it on this, from man qmail-inject: "The default envelope sender address is the same as the default From address, but it can be overridden with QMAILSUSER and QMAILSHOST." I erroneously thought that "default" From address was one with defaulthost in the host part of the address, not the with the host that someone may have overridden with MAILHOST. So it appears that MAILHOST will set the host name in the From header, and that that host will be used in the envelope sender unless it's overridden by QMAILSHOST. > But then I start Emacs from the same shell, send a message as > > To: mw-hosttest > Subject: test > --text follows this line-- > test > > and I get > > $ cat hosttest.out > [EMAIL PROTECTED] > > Setting QMAILSHOST has the same effect---nothing. > > The only way I can change the domain part of the envelope sender's > address for Emacs, if I put oki.doki in defaulthost. How does Emacs inject mail? Chris
Re: MAILHOST and envelope sender
Mate Wierdl wrote/schrieb/scribsit: > $ export MAILHOST=3Doki.doki =20 > $ export QMAILINJECT=3Df Have you tried setting it to "s"? Emacs might be supplying a return-path. Stefan Makes no difference. Mate
Re: MAILHOST and envelope sender
- Chris Johnson <[EMAIL PROTECTED]>:
| How does Emacs inject mail?
Usually, it uses sendmail-send-it, defined in sendmail.el. The
important part says
(apply 'call-process-region
(append (list (point-min) (point-max)
(if (boundp 'sendmail-program)
sendmail-program
"/usr/lib/sendmail")
nil errbuf nil "-oi")
;; Always specify who from,
;; since some systems have broken sendmails.
(list "-f" (user-login-name))
(and mail-alias-file
(list (concat "-oA" mail-alias-file)))
;; These mean "report errors by mail"
;; and "deliver in background".
(if (null mail-interactive) '("-oem" "-odb"))
;; Get the addresses from the message
;; unless this is a resend.
;; We must not do that for a resend
;; because we would find the original addresses.
;; For a resend, include the specific addresses.
(or resend-to-addresses
'("-t"
In other words, it basically runs
/usr/lib/sendmail -oi -f USER -oem -edb -t
where USER is your login name.
That is presumably what causes the problem.
This was from emacs 19; things may be different in the emacs 20 world.
- Harald
Re: MAILHOST and envelope sender
On Wed, 20 Jan 1999, Stefan Paletta wrote: > > Mate Wierdl wrote/schrieb/scribsit: > > > $ export MAILHOST=oki.doki > > $ export QMAILINJECT=f > > Have you tried setting it to "s"? > Emacs might be supplying a return-path. Is it possible that emacs isn't using /usr/lib/sendmail, but instead injecting the message directly via SMTP? The MAILHOST, QMAILUSER, ... environment variables aren't, as far as I know, used except by qmail, so emacs wouldn't do something with them unless it was using qmail's sendmail or using qmail-inject directly. It did occur to me but: 1) If I remove /usr/lib/sendmail, Emacs cannot send a message. (In fact, Emacs is the *only* program in Rh that uses /usr/lib/sendmail) 2) If I put a domain in defaulthost, the envelope sender's address does get changed to that domain. Mate
Re: MAILHOST and envelope sender
[[EMAIL PROTECTED] writes:] >I would really like to know what the heck MAILHOST and friends are doing. Me too, and I'd like to thank Mate for asking these questions here, after having privately offered me help in response to my queries (and suggesting I try the experiment he's since tried himself, before I got to it, the results of which confuse him, so I'm not the only one ;-). >The only way I can change the domain part of the envelope sender's >address for Emacs, if I put oki.doki in defaulthost. Strangely, this didn't help me. That is, back when I was using MAILHOST=jcb-sc.com, I also had jcb-sc.com as the entry in defaulthost, but email sent from Emacs had "Return-Path: [EMAIL PROTECTED]", though the "From:" address was fine. >What is going on? The man page for qmail-inject strongly implies QMAILHOST and MAILHOST are treated exactly the same way, which is why I tried MAILHOST and gave up (and queried here) when it didn't affect Return-Path as I'd hoped it would. If there's indeed no difference in how these environment variables are treated by qmail-inject, I'd suspect something in the way Emacs sets up the environment for sending mail, or the sendmail (stub?) it invokes. Okay, I've just tried various combination of things using just qmail-inject. It seems like MAILHOST and QMAILHOST indeed do override defaulthosts and affect both From: and Return-Path: in exactly the same way, and QMAILSHOST also works (changes the Return-Path header, but not the From header composed by qmail-inject). So, my guess is that the sendmail program Emacs uses when sending mail isn't obeying defaulthost as expected. When I use it without MAILHOST, QMAILHOST, and QMAILINJECT defined, even though defaulthost=jcb-sc.com, I get email with both From and Return-Path set to deer.jcb-sc.com. If I restore QMAILINJECT=f, that fixes the From but not the Return-Path. Now, setting MAILHOST=xxx.yyy sets the From field accordingly (in email sent from within Emacs), but leaves the Return-Path field unchanged. Same thing for QMAILHOST! Hey, to heck with this guessing, I'm going to try a new approach. First, I've now appended "defaulthost" to the name in defaulthost, "defaultdomain" to the name in defaultdomain, and "me" to the name in "me", just so I can see from where these names come. Now, with nothing seemingly pertinent in my environment: [root@deer /root]# echo hey | qmail-inject -n Return-Path: <[EMAIL PROTECTED]> Date: 20 Jan 1999 16:32:29 - Message-ID: <[EMAIL PROTECTED]> From: [EMAIL PROTECTED] Cc: recipient list not shown: ; hey So, we can see where these names come from. Now I'll try sending an email from within Emacs in the same environment: Return-Path: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Received: (qmail 6125 invoked by uid 0); 20 Jan 1999 16:34:17 - Date: 20 Jan 1999 16:34:17 - Message-ID: <[EMAIL PROTECTED]> From: root <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: test (I had to pull this out of ~alias/pppdir, natch.) Isn't that interesting? When sending email from within Emacs, its the defaultdomain, not defaulthost, that gets used, and the host name gets prepended. (I'd already unset HOSTNAME to get it out of my environment for the moment.) But that applies only to From and Return-Path, not To. Adding QMAILINJECT=f to my environment changes only the Emacs-sent >From field, but not Return-Path. Further adding MAILHOST=xxx.yyy affects both the From and Return-Path headers using qmail-inject directly, but only the From using Emacs-send. Replacing MAILHOST with the same QMAILHOST definition has the exact same effect, so these indeed do behave similarly. Defining QMAILSHOST seems to have no effect whatsoever on the Emacs-send case! Well, at this point, I'm indeed stumped, especially since I *thought* I'd gotten it working yesterday. Probably just a matter of restoring my control files and /etc/profile, though I've just tried that, and it doesn't seem to have worked. Anyway, it seems as though the qmail-inject stuff is, on its own, working fine. Perhaps only the /var/qmail/bin/sendmail program needs some fixing, or some documentation, or something. Meanwhile, I've got to get some lunch. tq vm, (burley)
Re: MAILHOST and envelope sender
On Wed, Jan 20, 1999 at 05:41:06PM +0100, Harald Hanche-Olsen wrote: > In other words, it basically runs > > /usr/lib/sendmail -oi -f USER -oem -edb -t > > where USER is your login name. Right, from the manpage of qmail-inject: -fsender Pass sender to qmail-queue as the envelope sender address. This overrides Return-Path and all environ- ment variables. Jost -- | [EMAIL PROTECTED] Please help stamp out spam! | | Postmaster, JAPH, resident answer machine am RZ der RUB | | non sunt multiplicanda entia praeter necessitatem| | William of Ockham (1285-1347/49) |
Re: Some Progress...
>On Tue, 19 Jan 1999, Craig Burley wrote: > >> That's helped some. I've made the specified changes (defining MAILHOST and >> QMAILINJECT, but not MAILUSER, since I want to leave that be) to the >> /etc/profile on my system. It causes the newly sent "From:" addresses >> to be "[EMAIL PROTECTED]". >> >> However, maildirsmtp still reports "451 Domain must resolve" errors >> on new messages, so my ISP is still rejecting them. > >Now, set QMAILSHOST to fix that. Errr... I think it's QMAILSHOST. Looks like it does work for qmail-inject, but there's some problem with /var/qmail/bin/sendmail that prevents it working from there (though Mate has had slightly different results from me pertaining the defaulthost file -- for him, it gets into the Return-Path, but it doesn't seem to for me using Emacs). >Why don't you read the manual page for qmail-inject, and look at all the >environment variables that are used for rewriting addresses. I'd already read that man page several times, and probably all of the others at least once. That doesn't mean I am anywhere near fully understanding them, of course. :) But, when I thought that Return-Path was the culprit, I simply *searched* qmail-inject's man page for "Return-Path". I found several instances, none of which seemed to apply to my situation. It hadn't occurred to me to look for the phrase "envelope sender address" or recognize that (when re-skimming the page) as meaning "Return-Path", as I haven't memorized all the email terminology yet. (When I write documentation, I try to make sure I use consistent terminology, and, wherever possible, stick to terms and phrases consistent with what a user will see on his screen, so searches and indexes are more useful.) Anyway, if I had tried defining QMAILSHOST, it wouldn't have worked for the case I care about, though it does (nicely) for the simple qmail-inject case. tq vm, (burley)
loggers and syslog
Hello there: we're seeing a very noticeable overload on syslogd due mainly to logging email. I'm running qmail-1.03 as: /bin/csh -cf '/var/qmail/rc &' /usr/local/bin/tcpserver -R -x /etc/tcp.smtp.cdb -c120 -u7181 -g101 0 smtp /var/qmail/bin/qmail-smtpd & with my /var/qmail/rc file: exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start '|dot-forward .forward ./Mailbox' splogger qmail relevant lines of my /etc/syslog.conf *.=notice /usr/adm/messages *.=debug/usr/adm/debug *.warn /usr/adm/syslog mail.* /var/adm/maillog mail.crit /var/adm/mailerr questions: Is this a splogger matter? Does it requires fine tunnig? i've read at qmail.org that splogger doesn't log everything, that another loggers more reliables but i'll don't need more overload. Thanks for any hint regards Abel Lucano [EMAIL PROTECTED]
Re: loggers and syslog
On Wed, Jan 20, 1999 at 02:05:46PM +, Abel Lucano wrote: > Hello there: > we're seeing a very noticeable overload on syslogd due mainly to logging > email. That is correct. syslogd is very inefficient. You should use cyclog from djb's daemontools. They're somewhere at the qmail page I think. Greetz, Peter. -- AND I AM GONNA KILL MIKE| Peter van Dijk hardbeat, als je nog nuchter bent: | [EMAIL PROTECTED] @date = localtime(time); | realtime security d00d $date[5] += 2000 if ($date[5] < 37); | $date[5] += 1900 if ($date[5] < 99); |* blah *
Re: loggers and syslog
- Abel Lucano <[EMAIL PROTECTED]>: | we're seeing a very noticeable overload on syslogd due mainly to | logging email. Then use cyclog instead of syslog. You can find it in Dan's daemontools package. - Harald
RE: MAILHOST and envelope sender
On Wed, 20 Jan 1999, Stefan Paletta wrote: > > Mate Wierdl wrote/schrieb/scribsit: > > > $ export MAILHOST=oki.doki > > $ export QMAILINJECT=f > > Have you tried setting it to "s"? > Emacs might be supplying a return-path. Is it possible that emacs isn't using /usr/lib/sendmail, but instead injecting the message directly via SMTP? The MAILHOST, QMAILUSER, ... environment variables aren't, as far as I know, used except by qmail, so emacs wouldn't do something with them unless it was using qmail's sendmail or using qmail-inject directly. [I don't use emacs.] > Stefan -- "Life is much too important to be taken seriously." Thomas Erskine<[EMAIL PROTECTED]>(613) 998-2836
.qmail file oddities
Greetings. I'm experiencing an oddity with .qmail files in qmail-1.03. In /var/qmail/control/virtualdomains: domain.com:user In the past, messages sent to "[EMAIL PROTECTED]" were sent to ~user/.qmail-joe, and if that file didn't exist, they were bounced back to the sender. This still happens, except on one domain. This domain is set up like all the others, with no detectable differences in configuration or permissions, but messages sent to "[EMAIL PROTECTED]" are delivered to ~user/Mailbox If I put *no* .qmail files in ~user, all messages to any user are delivered to ~user/MailboxIf I put a .qmail file in ~user, all messages are piped throgh that file, even if I add a ~user/.qmail-joe file, it still goes through ~user/.qmail. It's as if there's an invisible .qmail-default file at work, but I can't find what's causing this. Any ideas? Thanks, Chris - Chris Hardie[EMAIL PROTECTED] http://www.summersault.com/chris great is the power of truth -
Same user, multiple virtual domains.
Hi all, Have a question about the following: We host domains, and have many of our customers requesting things like [EMAIL PROTECTED] and the next customer asks for [EMAIL PROTECTED] I do understand the .qmail alias mechanism for when the situation is "local". Can someone smack me in the direction of how to accomplish this for when a qmail server is hosting virtual domains? Thanks, Morgan
Re: .qmail file oddities
- Chris Hardie <[EMAIL PROTECTED]>: | It's as if there's an invisible .qmail-default file at work, but I can't | find what's causing this. Any ideas? Do you employ the users/assign mechanism at all? If so, maybe there is a clue there. Also, take a look at the topmost Delivered-To: header field in the incoming messages for possible clues. - Harald
Re: loggers and syslog
On 20-Jan-99 Sam wrote: > syslog sync-s after every message. > > Prefix each filename with a dash to turn off the syncs. On which system. There are no signs of such feature on my FreeBSD-3.0. On the other hand I have also no problems with syslogd performance and qmail. > RTFM man syslog Nothing there on my system. Martin --- [PGP KeyID F3F409C4]]
Re: loggers and syslog
On Wed, Jan 20, 1999 at 05:51:14PM +, Sam wrote: > > other hand I have also no problems with syslogd performance and qmail. > > > > > RTFM man syslog > > > > Nothing there on my system. > > Try man syslog.conf, it could be there. I'm sure the documentation is, but the "-" feature is one that seems to be unique to linux's syslog.conf - at least it's not on solaris or freebsd. -Peter
System w/o /etc/passwd
Hello all, I'm working on moving our system from Sendmail to Qmail. So far everything is going smooth.. I have qmail-pop3d authing from a checkpasswd program that uses a different password file than the system, only problem I've noticed is that when you do this you have to have an entry in users/assign for every user on the system. Anyone know of a way to get around this? Say, to tell qmail to drop all mail to something like /mail/u/s/username? -Jason --- Robert J. Adams [EMAIL PROTECTED] http://www.siscom.net Looking to outsource news? http://www.newshosting.com SISCOM Network Administration - President, SISCOM Inc. Phone: 888-4-SISCOM 937-222-8150 FAX: 937-222-8153
Re: MAILHOST and envelope sender
How does Emacs inject mail? I do not know---I am trying to look at sendmail-send-it () in sendmail.el, and I think the crucial part is (if (boundp 'sendmail-program) sendmail-program "/usr/lib/sendmail") nil errbuf nil "-oi") But I know nothing about the sendmail flags (no documentation of them in the qmail distr). Mate
Re: MAILHOST and envelope sender
In other words, it basically runs /usr/lib/sendmail -oi -f USER -oem -edb -t where USER is your login name. And I have to correct myself: even an entry in defaulthost does not help. The correct line I think is /usr/lib/sendmail -oi -f USER -oem -odb -t Mate
Re: loggers and syslog
Abel Lucano writes: > > relevant lines of my /etc/syslog.conf > *.=notice /usr/adm/messages > *.=debug/usr/adm/debug > *.warn /usr/adm/syslog > mail.* /var/adm/maillog > mail.crit /var/adm/mailerr syslog sync-s after every message. Prefix each filename with a dash to turn off the syncs. RTFM man syslog
Re: .qmail file oddities
On Wed, 20 Jan 1999, Harald Hanche-Olsen wrote: > - Chris Hardie <[EMAIL PROTECTED]>: > > | It's as if there's an invisible .qmail-default file at work, but I can't > | find what's causing this. Any ideas? > > Do you employ the users/assign mechanism at all? If so, maybe there > is a clue there. Also, take a look at the topmost Delivered-To: > header field in the incoming messages for possible clues. There's nothing in the users/ directory, so I don't think that would come into play. The topmost delivered-to is always either the contents of .qmail (if that file exists) or [EMAIL PROTECTED] or something else that seems very reasonable. But if it was really delivering to user-joe, it should be paying attention to .qmail-joe, which it is not. Chris - Chris Hardie[EMAIL PROTECTED] http://www.summersault.com/chris great is the power of truth -
Re: .qmail file oddities
Are you SURE the domain is NOT listed in locals? If it is, it could cause this... On Wed, 20 Jan 1999, Chris Hardie wrote: > > Greetings. I'm experiencing an oddity with .qmail files in qmail-1.03. > > In /var/qmail/control/virtualdomains: > >domain.com:user > > > In the past, messages sent to "[EMAIL PROTECTED]" were sent to > ~user/.qmail-joe, and if that file didn't exist, they were bounced back to > the sender. > > This still happens, except on one domain. This domain is set up like all > the others, with no detectable differences in configuration or > permissions, but messages sent to "[EMAIL PROTECTED]" are delivered to > ~user/Mailbox > > If I put *no* .qmail files in ~user, all messages to any user are > delivered to ~user/MailboxIf I put a .qmail file in ~user, all > messages are piped throgh that file, even if I add a ~user/.qmail-joe > file, it still goes through ~user/.qmail. > > It's as if there's an invisible .qmail-default file at work, but I can't > find what's causing this. Any ideas? > > Thanks, > Chris > > - > Chris Hardie[EMAIL PROTECTED] > http://www.summersault.com/chris > great is the power of truth > - > > James SmallacombeInternet Access for The Delaware [EMAIL PROTECTED]Valley in PA, NJ and DE PlantageNet Internet Ltd.http://www.pil.net = ISPF 2.0b, The Forum for ISPs by ISPs. San Diego, CA, March 8-10 '99 Three days of clues, news, and views from the industry's best and brightest. http://www.ispf.com for information and registration. =
Re: loggers and syslog
Martin Machacek writes: > > On 20-Jan-99 Sam wrote: > > syslog sync-s after every message. > > > > Prefix each filename with a dash to turn off the syncs. > > On which system. There are no signs of such feature on my FreeBSD-3.0. On the Linux. > other hand I have also no problems with syslogd performance and qmail. > > > RTFM man syslog > > Nothing there on my system. Try man syslog.conf, it could be there.
Re: .qmail file oddities
On Wed, 20 Jan 1999, James Smallacombe wrote: > > Are you SURE the domain is NOT listed in locals? If it is, it could cause > this... Positive. - Chris Hardie[EMAIL PROTECTED] http://www.summersault.com/chris great is the power of truth -
Re: loggers and syslog
On Wed, Jan 20, 1999 at 12:59:48PM -0500, Peter C. Norton wrote: > On Wed, Jan 20, 1999 at 05:51:14PM +, Sam wrote: > > > other hand I have also no problems with syslogd performance and qmail. > > > > > > > RTFM man syslog > > > > > > Nothing there on my system. > > > > Try man syslog.conf, it could be there. > > I'm sure the documentation is, but the "-" feature is one that seems > to be unique to linux's syslog.conf - at least it's not on solaris or > freebsd. > I think it is a linux-ism, since I can't find that "feature" on SunOS or any of Net/Open/FreeBSD. No problems with syslog performance and qmail on NetBSD though. -- // //Scott Ellis // [EMAIL PROTECTED] // [EMAIL PROTECTED] // // // WARNING: This signature warps time and space in its vicinity//
Re: forwarding is BCC?
On Wed, Jan 20, 1999 at 01:14:27PM +0100, Mirko Zeibig wrote: > Does qmail do a BCC when forwarding messages like > above?. No. qmail does not rewrite the message in that stage (it does so only in the injection phase). It merely rewrites the envelope. But the mailing list software looks into the message header for it's own address (spam prevention). So you need to either: - use some tool from the mess822 package (new-inject should be able to handle that case), - write a few-lines awk/sed/perl script to replace the string in the header (that's almost a no-brainer in this case), - or try rewriteheader from ftp://tirka.ohse.de/uwe/releases/smtptools-0.2.3.* You would need to do something like: |rewriteheader to qmail-liste@MEINE_KISTE [EMAIL PROTECTED] (it does have nothing to do with smtp, but fits perfectly into the package infrastructure) Regard, Uwe
Re: MAILHOST and envelope sender
Harald Hanche-Olsen <[EMAIL PROTECTED]> wrote: > In other words, [emacs] it basically runs > > /usr/lib/sendmail -oi -f USER -oem -edb -t > > where USER is your login name. > That is presumably what causes the problem. Emacs 20 still does this. I handled this problem by editing and recompiling the sendmail-send-it function. Upgrades to emacs usually involve re-discovering this problem. Len. -- The king's heart is in the hand of the LORD, as the rivers of water: he turneth it whithersoever he will. --Proverbs 21:1
Re: Some Progress...
Looks like it does work for qmail-inject, but there's some problem with /var/qmail/bin/sendmail that prevents it working from there (though Mate has had slightly different results from me pertaining the defaulthost file -- for him, it gets into the Return-Path, but it doesn't seem to for me using Emacs). Now the difference is that defaulthost is working on my home machine which has 20.1 installed---and qmail 1.01. But defaulthost is not working on my office machine (20.3 and qmail-1.03). But now I want to double check my home machine---later today. Mate
Re: .qmail file oddities
- Chris Hardie <[EMAIL PROTECTED]>: | On Wed, 20 Jan 1999, Harald Hanche-Olsen wrote: | | > - Chris Hardie <[EMAIL PROTECTED]>: | > | > | It's as if there's an invisible .qmail-default file at work, but I can't | > | find what's causing this. Any ideas? | > | > Do you employ the users/assign mechanism at all? If so, maybe there | > is a clue there. Also, take a look at the topmost Delivered-To: | > header field in the incoming messages for possible clues. | | There's nothing in the users/ directory, so I don't think that would | come into play. And you don't use a non-standard substitute for qmail-getpw either, I presume? Normally, if you run /var/qmaill/bin/qmail-getpw user-joe | tr '\000' : it should print a line like user:123:456:/home/user:-:joe: | The topmost delivered-to is always either the contents of .qmail (if | that file exists) Really? I have never heard of such a thing. It is supposed to always hold the recipient address. | or [EMAIL PROTECTED] or something else that seems very reasonable. | But if it was really delivering to user-joe, it should be paying | attention to .qmail-joe, which it is not. Yes. Another tack: The code in qmail-local might suppose that a .qmail file does not exist if an open() on the file fails with a weird and unexpected error code. (Expected errors are various temporary errors, plus permission and access errors.) Maybe it is conceivable (highly unlikely, but your problem seems weird) that you are hitting one of these cases? - Harald
Re: MAILHOST and envelope sender
>=20 > /usr/lib/sendmail -oi -f USER -oem -edb -t >=20 > where USER is your login name. =17 Right, from the manpage of qmail-inject: -fsender Pass sender to qmail-queue as the envelope sender address. This overrides Return-Path and all environ- ment variables. I think it is an error in sendmail.el to specify the envelope sender this way. It overrides, for example, if the sysadm sets MASQUERADE_AS---which I think is necessary on a mail server. Can we convince rms about this? Arguing with qmail will not make a difference, but perhaps giving an example using the latest sendmail could result in change. Mate
Re: .qmail file oddities
On Wed, 20 Jan 1999, Harald Hanche-Olsen wrote:
> | su-2.01# /var/qmail/bin/qmail-getpw lindgren-pat | tr '\000' :
> | lindgren:1021:1021:/home/lindgren:::
> |
> | Does this look right?
>
> No!
>
> | What are the last two fields in the printed results
> | ("-" and "joe" in your example above)?
>
> They are the dash and extension. Together, they are what qmail-local
> adds after ".qmail" to find out what .qmail file to use, thus ending
> with .qmail-joe. It's divided up into dash and extension so the
> latter can be put into $EXT for use by any commands run from the
> .qmail file.
>
> In your example, the expected output would be
>
> lindgren:1021:1021:/home/lindgren:-:pat:
>
> whereas /var/qmail/bin/qmail-getpw lindgren | tr '\000' :
> ought to print what you did get.
>
> So this is your problem, right there. Now, do you run qmail's
> standard qmail-getpw or not?
Yes, we haven't changed anything with the default qmail configuration, and
we experienced a clean install. As I said, this behavior is only present
with this one domain, and no others, for no apparent reason.
> If you do, I must conclude that
> getpwnam() behaves rather strangely on your system. (Or that there is
> another user actually named lindgren-pat in the passwd database.)
Is there any state information stored by qmail in terms of usernames and
domains? That is, at one time there was a .qmail-default in that
directory, but I've since removed it, but the functionality hasn't gone
away.
Thanks for your help.
-
Chris Hardie[EMAIL PROTECTED]
http://www.summersault.com/chris
great is the power of truth
-
Re: .qmail file oddities
- Chris Hardie <[EMAIL PROTECTED]>:
| Is there any state information stored by qmail in terms of usernames
| and domains?
No surprises of that kind in qmail. qmail-local looks for and reads
.qmail over again on each delivery. In fact, a separate copy of
qmail-local is run each time.
But wait! I have an idea! It just occured to me that "lindgren" is
exactly 8 characters long, which is exactly the maximum length of a
username on many systems. So here is my conjecture: When your
system's getpwnam() is fed anything longer than 8 characters, it chops
it down to 8 characters and looks up the remainder in the database.
In fact, looking at the code in qmail-getpw.c, this is the only
reasonable explanation I can come up with (for some unreasonable
definition of "reasonable").
To help verify my hypothesis, try compiling and running the appended
program. Running it as ./getpwnam lindgren-pat will then return
lindgren-pat: name="lindgren", uid=1021, gid=1021, homedir=/home/lindgren
Here is a sample run on my system:
; gcc -o getpwnam getpwnam.c
; ./getpwnam hanche operator operator-foo
hanche: name="hanche", uid=1357, gid=1999, homedir=/home/fiinbeck/hanche
operator: name="operator", uid=5, gid=5, homedir=/home-pw/operator
operator-foo: nope.
So what system is this happening on? I am sure Dan will be
interested, so he can try to harden qmail against this kind of
silliness.
- Harald
#include
#include
#include
int main(int argc, char *argv[]) {
struct passwd *pw;
while (*(++argv)) {
printf ("%s: ", *argv);
pw = getpwnam(*argv);
if (pw)
printf("name=\"%s\", uid=%d, gid=%d, homedir=%s\n",
pw->pw_name, pw->pw_uid, pw->pw_gid, pw->pw_dir);
else
printf("nope.\n");
}
}
Re: .qmail file oddities
- Chris Hardie <[EMAIL PROTECTED]>: | > So what system is this happening on? I am sure Dan will be | > interested, so he can try to harden qmail against this kind of | > silliness. | | This is on FreeBSD 2.2.8. So, um, what do I/we do now? First, replace the line #define GETPW_USERLEN 32 in qmail-getpw.c by #define GETPW_USERLEN 9 and recompile (use 9, not 8, to have room for the terminating NUL). This should take care of your immediate problem. Second, I guess a bug report to the FreeBSD maintainers might be appropriate. There is a form for submitting bug reports available from the FreeBSD home page at http://www.freebsd.org/> somewhere. - Harald
alias overriding ~user/.qmail
HELO :) Suppose I have an user named 'mailer'. When a message comes to 'mailer-daemon', qmail-local tries to deliver it through '~mailer/.qmail-daemon'. The mere existence of this user implies that qmail won't try to use /var/qmail/alias/.qmail-mailer-daemon Apart from the use of qmail-users, is there any way, using alias, to override the control of mailer-daemon in this situation? -- Saludos, Jose Luis Painceira.
Re: .qmail file oddities
On 20-Jan-99 Harald Hanche-Olsen wrote: > - Chris Hardie <[EMAIL PROTECTED]>: > > Second, I guess a bug report to the FreeBSD maintainers might be > appropriate. There is a form for submitting bug reports available > from the FreeBSD home page at http://www.freebsd.org/> somewhere. You can also use the send-pr program (part of baseic FreeBSD distribution). Interesting, on FreeBSD RELENG-2.2 dated October 28 1998 it seems to be OK. Here is output for user netadmin: martin@servis:/tmp# ./test netadmin netadmin: name="netadmin", uid=1000, gid=21, homedir=/usr/home/netadmin martin@servis:/tmp# ./test netadmin-foo netadmin-foo: nope. martin@servis:/tmp# Martin --- [PGP KeyID F3F409C4]]
Re: .qmail file oddities
On Wed, 20 Jan 1999, Harald Hanche-Olsen wrote: > > But wait! I have an idea! It just occured to me that "lindgren" is > exactly 8 characters long, which is exactly the maximum length of a > username on many systems. So here is my conjecture: When your > system's getpwnam() is fed anything longer than 8 characters, it chops > it down to 8 characters and looks up the remainder in the database. > In fact, looking at the code in qmail-getpw.c, this is the only > reasonable explanation I can come up with (for some unreasonable > definition of "reasonable"). > > To help verify my hypothesis, try compiling and running the appended > program. Running it as ./getpwnam lindgren-pat will then return > > lindgren-pat: name="lindgren", uid=1021, gid=1021, homedir=/home/lindgren It returned: lindgren-pat: name="lindgren", uid=1021, gid=1021, homedir=/home/lindgren I think you're on to something here; I tested this on another virtual domain with an 8-char username, and got the same results (sorry that I claimed this was the only domain on which this happened, I only tested on non-8-char username domains and made an assumption). > So what system is this happening on? I am sure Dan will be > interested, so he can try to harden qmail against this kind of > silliness. This is on FreeBSD 2.2.8. So, um, what do I/we do now? Thanks very much! Chris - Chris Hardie[EMAIL PROTECTED] http://www.summersault.com/chris great is the power of truth -
Re: .qmail file oddities
On Wed, Jan 20, 1999 at 10:13:15PM +0100, Martin Machacek wrote: > > On 20-Jan-99 Harald Hanche-Olsen wrote: > > - Chris Hardie <[EMAIL PROTECTED]>: > > > > Second, I guess a bug report to the FreeBSD maintainers might be > > appropriate. There is a form for submitting bug reports available > > from the FreeBSD home page at http://www.freebsd.org/> somewhere. > > You can also use the send-pr program (part of baseic FreeBSD distribution). > > Interesting, on FreeBSD RELENG-2.2 dated October 28 1998 it seems to be OK. > Here is output for user netadmin: > > martin@servis:/tmp# ./test netadmin > netadmin: name="netadmin", uid=1000, gid=21, homedir=/usr/home/netadmin > martin@servis:/tmp# ./test netadmin-foo > netadmin-foo: nope. > martin@servis:/tmp# I've tried it on a 2.2.7-RELEASE system, two 2.2-STABLE systems from around September, a 2.2-STABLE system from late December, and a 3.0-CURRENT system, current as of yesterday, and they all behave correctly. ./getpwnam cjohnson gives me the goods, and ./getpwnam cjohnson-test gives me a "nope." News flash! I just checked http://www.freebsd.org/releases/2.2.8R/errata.html and here's what it says: ogetpwnam(3) semantics are incorrect in some cases. Fix: If passed a string longer than the maximum allowed for a user name, getpwnam will incorrectly return an entry for a user that matches the initial characters in the string up to the maximum length allowed for a user name. To correct this behaviour, libc needs to be patched and recompiled. The appropriate patch can be obtained from: http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/gen/getpwent.c.diff?r1=1.35.2.2&r2=1.35.2.3 Chris
message size
How do I limit the size of messages going outbound and/or inbound? Joe
Re: message size
Text written by Joe Garcia at 04:58 PM 1/20/99 -0500: >How do I limit the size of messages going outbound and/or inbound? Use the control/databytes file. "man qmail-smtpd" for details. --Kai MacTane.
Re: message size
At 02:13 PM 1/20/99 -0800, Kai MacTane wrote: >Text written by Joe Garcia at 04:58 PM 1/20/99 -0500: >>How do I limit the size of messages going outbound and/or inbound? > >Use the control/databytes file. "man qmail-smtpd" for details. Which helps incoming, but outbound requires a different solution. Either a qmail-queue wrapper and/or apply quotas on /var/qmail/queue. (I'm assuming your outbound is injected from a shell comand). Also note that you can set DATABYTES via tcpserver so that the allowable size is different for different addresses, ie internal and external. Regards.
Re: alias overriding ~user/.qmail
- Jose Luis Painceira <[EMAIL PROTECTED]>: | Suppose I have an user named 'mailer'. When a message comes to | 'mailer-daemon', qmail-local tries to deliver it through | '~mailer/.qmail-daemon'. | | The mere existence of this user implies that qmail won't try to | use /var/qmail/alias/.qmail-mailer-daemon | | Apart from the use of qmail-users, is there any way, using alias, to | override the control of mailer-daemon in this situation? Yes: Let root own the home directory of mailer. If that is not an option, you can use virtualdomains (painful if you have many local domains, as you need a virtual user per local domain). - Harald
memphis problems (solution)
OK the solution turned out to be frustration After much hacking at various files I decided to reinstall RedHat and Memphis all went off without a hitch The problem? Probably me Thanks to all for suggestions, I did learn some from the experience. Kind regards Kevin -- Kevin Waterson Oceania Computer Services
Switching machines and delivery of queued messages?
Here's the situation: We (compusense.com) have qmail running on our firewall, and it passes mail to machine A which has the highest MX priority. Now machine A is running Exchange and has given me so much grief that machine A presently has a screwdriver embedded in the motherboard, so we're not going to use machine A anymore. We have a new Linux box, machine B, running qmail that I would like to give the highest MX priority to. Presently the mail that couldn't be delivered to machine A is being queued on the firewall machine. If I set up the new machine, change the DNS to reflect the fact I hate Microsoft and give machine B the highest MX priority, when the machine B comes on-line and I restart named, will qmail push all the mail in the queue to machine B, or will it still try to get mail to machine A. Is it easier just to give machine B the same IP that machine A had? Or will things just work with the new DNS setup. Much appreciated, jason van Zyl
Re: Switching machines and delivery of queued messages?
root writes: > Here's the situation: > > We (compusense.com) have qmail running on our firewall, and it passes mail > to machine A which has the highest MX priority. Now machine A is > running Exchange and has given me so much > grief that machine A presently has a screwdriver embedded in the > motherboard, so we're not going to use machine A anymore. NT 5.0 Beta, right? > If I set up the new machine, change the DNS to reflect the fact I hate > Microsoft and give machine B the highest MX priority, when the machine > B comes on-line and I restart named, will qmail push all the mail in the > queue to machine B, or will it still try to get mail to machine A. > > Is it easier just to give machine B the same IP that machine A had? Or > will things just work with the new DNS setup. Qmail keeps things queued up based on the recipient's domain. Each time it tries to deliver, it looks up MX and A records. In order to redirect mail, you can do either of the following: 1) Put out a different MX record for the recipient's domain. 2) Put out a different IP address for the same A record to which the MX is pointing to. 3) Use control/smtproutes to flush all mail addressed to domain X to the IP address Y, irrespective of what DNS says.
Re: MAILHOST and envelope sender
> In other words, it basically runs > > /usr/lib/sendmail -oi -f USER -oem -edb -t > > where USER is your login name. > >And I have to correct myself: even an entry in defaulthost does not >help. The correct line I think is > > /usr/lib/sendmail -oi -f USER -oem -odb -t I don't seem to have `sendmail' available as a man page...could you give me a quick idea of whether that is, indeed, the right fix, and what it means? No, I did not mean that it fixes things. I meant this is the command Emacs runs to send mail. And the problem is the `-f' flag: it just sets the envelope sender. I do not have any idea about the other flags, since, as you pointed out, there is no man page for sendmail in the qmail distribution---hopefully will be fixed for the next release. But right now I am home, and I can confirm: here putting a domain name in defaulthost does have the desired effect! My setup is RH GNU/Linux 4.2, qmail-1.01 and Emacs 20.2. So I made some investigation, and the point is that sendmail.el is different in 20.2. Applying either of the following patches makes control/defaulthost work: --- sendmail.el.old Wed Jan 20 21:12:49 1999 +++ sendmail.el Wed Jan 20 21:02:42 1999 @@ -888,7 +888,7 @@ ;; since some systems have broken sendmails. ;; unless user has said no. (if (memq mail-from-style '(angles parens nil)) - (list "-f" user-mail-address)) + (list "-f" (user-login-name))) ;;; ;; Don't say "from root" if running under su. ;;; (and (equal (user-real-login-name) "root") ;;;(list "-f" (user-login-name))) --- sendmail.el.old Wed Jan 20 21:12:49 1999 +++ sendmail.el Wed Jan 20 21:26:30 1999 @@ -887,8 +887,8 @@ ;; Always specify who from, ;; since some systems have broken sendmails. ;; unless user has said no. - (if (memq mail-from-style '(angles parens nil)) - (list "-f" user-mail-address)) +; (if (memq mail-from-style '(angles parens nil)) +; (list "-f" user-mail-address)) ;;; ;; Don't say "from root" if running under su. ;;; (and (equal (user-real-login-name) "root") ;;;(list "-f" (user-login-name))) With the second patch, I also verified that QMAILHOST works. I have a feeling that the second patch is the cleaner one: it will not break anything when using qmail, while I have no idea about the implications of the first one. Mate
Re: VERH [was VERB]
Fred Lindberg writes: > On 19 Jan 1999 20:11:56 -, Russell Nelson wrote: > > >Okay, VERP has solved the bounce problem. Now we need VERB (Variable > >Envelope Recipient in Body) to solve the unsubscribe problem. > >Basically, we need qmail-remote to merge the envelope recipient into > >the message somewhere. The problem, of course, is *where* to insert > > I think the substitution idea is good, but putting it into the message > is Not Good (TM). qmail should not under any circumstances corrupt the > message, which might contain any character sequence. Right, that's the conundrum. It has to be in the body to be useful, yet it cannot be in the body. Maybe a magical header which means "When you see X, substitute the envelope recipient"? Like this: VERB-Substitute: 4jiu%8@#l No header, no body munging. > Putting it into the header circumvents that problem. Also, the amount > of text that has to be parsed is limited this way. Yes, there are > disadvantages (stupid subscribers), but that's less important than > message integrity. It's more a matter of ignorant than stupid (ignorant returns a 4XX error; stupid is a 5XX error :). No matter; the cost of correcting the ignorance means that the list gets extraneous messages. It is this problem I expect VERB to fix. > For subscribers, you could to a message trailer add "see > List-Unsubscribe: header for info on how to unsubscribe". As Sen Nagata > pointed out on the ezmlm list, rfc2069 may not be such a bad idea, and > good MUAs will rapidly support it once it's used more. ezmlm would > support this "out of the box". Is rfc2069 in effect now? Is it an Internet Standards track RFC? Or just an Informational RFC like my RFCs? -- -russ nelson <[EMAIL PROTECTED]> http://crynwr.com/~nelson Crynwr supports Open Source(tm) Software| PGPok | There is good evidence 521 Pleasant Valley Rd. | +1 315 268 1925 voice | that freedom is the Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | cause of world peace.
