qmail Digest 12 May 2001 10:00:00 -0000 Issue 1362
Topics (messages 62289 through 62347):
Re: ezmlm and announce-only lists...?
62289 by: Jeff Gordon
62290 by: Jeff Gordon
62297 by: Johan Almqvist
62299 by: peter green
62301 by: Jeff Gordon
62304 by: Jeff Gordon
62305 by: peter green
Re: qmail-inject and Perl
62291 by: Tonix
62293 by: Kevin Smith
62306 by: Charles Cazabon
62313 by: Milivoj Ivkovic
Re: reboot
62292 by: Neil Whittington
62298 by: Anton Pirnat
reason for problem found: connection reset after 1 minute
62294 by: Jens Hassler
62309 by: Charles Cazabon
62321 by: Bruce Guenter
62325 by: Charles Cazabon
62331 by: Bruce Guenter
qmail-smtpd-chkusr: (reject unknown users at smtp level) patch updated
62295 by: Tonix
Re: remote smtp problem
62296 by: Jonathan.Coker.egi.co.uk
Re: Case in email address
62300 by: Milivoj Ivkovic
62307 by: Charles Cazabon
62314 by: Milivoj Ivkovic
62315 by: Milivoj Ivkovic
62324 by: Matt Simonsen
62328 by: Charles Cazabon
62334 by: Matt Simonsen
62340 by: Charles Cazabon
users/assign handling
62302 by: PHoman.at.mbe.com
Re: tcpserver blues
62303 by: Joerg Lenneis
Re: Qmail and Request Tracker
62308 by: Charles Cazabon
Re: notification of new email whenever user logs in on the shell
62310 by: alexus
62311 by: Charles Cazabon
62335 by: alexus
62341 by: Charles Cazabon
62344 by: alexus
newbie question with concurrency remote
62312 by: Michael Geier
62322 by: Dave Sill
62323 by: Charles Cazabon
62333 by: Michael Geier
Re: qmail retry
62316 by: Dave Sill
Re: QMail autostart problem
62317 by: Dave Sill
Using vchkpw (vpopmail) with qmail-pop3d?
62318 by: Steven Katz
Re: weird
62319 by: Mate Wierdl
SMTP_AUTH
62320 by: Steve Hammond
62327 by: Dave Sill
config for stand-alone box
62326 by: john gennard
62330 by: Charles Cazabon
62332 by: Robin S. Socha
��½��...�����I
62329 by: �����o
MASS mailing
62336 by: Kuriger, Michael
62342 by: Charles Cazabon
Subject Line Manipulation
62337 by: Inthereal
62343 by: Charles Cazabon
Re: Newbie with tcpserver
62338 by: Russell Nelson
Re: Newbies vs. arrogant experts (was: Newbie with tcpserver)
62339 by: Russell Nelson
HELP - newbie
62345 by: Pavel Sorejs
62346 by: Clemens Hermann
451 qq internal bug(#4.3.1)
62347 by: dgrer
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
On Thu, May 10, 2001 at 06:26:25PM -0400, audit wrote: > > You can make it a moderated list. If you'd like, I can send you the > scripts that I use for all my lists from creating them, subing people, > deleteing people, etc > > audit (Hi, 'audit'.) That's a kind offer; thank you. :-) I gather from the FAQ at ezmlm.org that it's possible to remove '~/.qmail-list' and 'DIR/editor' and end up with a list regarding which folks could still sub and unsub themselves but no one could post; the moderator would need to pipe a message directly to ezmlm-send. That sounds like one solution; but do your scripts perhaps provide an even better one...? -- -- Jeff -- <http://www.wellnow.com> "There's nothing left in the world to prove. All that's worth doing is to love one another, using whatever means are available to serve."
On Thu, May 10, 2001 at 11:47:15PM -0400, peter green wrote: > [http://www.ezmlm.org/] is decent; it covers ezmlm-idx, NOT stock ezmlm. I > think the site gives an apt description as to what the -idx part > adds...basically, you want the -idx version. > > Anyway, the FAQ there is pretty extensive, including answers to questions > like, ``How do I make an ezmlm list "announce only"?'' :-) Thanks, Peter. If I'm understanding what I'm reading, it appears the thing to do is -remove- '~/.qmail-list' and DIR/editor, then pipe directly to "ezmlm-send DIR"...? I believe it's implying list members would still be able to sub and unsub this way, but posts to the list would fall into the bit bucket. Have I got it right...? -- -- Jeff -- <http://www.wellnow.com> "There's nothing left in the world to prove. All that's worth doing is to love one another, using whatever means are available to serve."
* Jeff Gordon <[EMAIL PROTECTED]> [010510 23:08]: > I've just barely got qmail, qmailadmin and vpop running, need to know > if there's a method for making an ezmlm list "announce only"...? There is. Can't say how off-hand, though. > (Pointers to any documentation on this would be appreciated; I haven't > found any that address this exact topic so far.) man ezmlm-make http://www.ezmlm.org/ The appropriate list is [EMAIL PROTECTED] -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/
PGP signature
[ No need to Cc: me, thanks. ] * Jeff Gordon <[EMAIL PROTECTED]> [010511 06:06]: > > [http://www.ezmlm.org/] is decent; it covers ezmlm-idx, NOT stock ezmlm. I > > think the site gives an apt description as to what the -idx part > > adds...basically, you want the -idx version. > > > > Anyway, the FAQ there is pretty extensive, including answers to questions > > like, ``How do I make an ezmlm list "announce only"?'' :-) > > Thanks, Peter. > > If I'm understanding what I'm reading, it appears the thing to do is > -remove- '~/.qmail-list' and DIR/editor, then pipe directly to > "ezmlm-send DIR"...? > > I believe it's implying list members would still be able to sub and > unsub this way, but posts to the list would fall into the bit bucket. > > Have I got it right...? Almost. Posts to the list would bounce if you just remove .qmail-list. If you want them to disappear without a bounce, do: echo '#' > .qmail-list A .qmail file with only comments will effectively blackhole a piece of mail. HTH! /pg -- Peter Green : Architekton Internet Services, LLC : [EMAIL PROTECTED] --- As we were driving, we saw a sign that said: Watch for Rocks. Marta said it should read: Watch for Pretty Rocks. I told her she should write in her suggestion to the highway department, but she started saying it was a joke - just to get out of writing a simple letter! And I thought I was lazy! (Jack Handey)
On Fri, May 11, 2001 at 01:37:28AM +0200, Johan Almqvist wrote: > * Jeff Gordon <[EMAIL PROTECTED]> [010510 23:08]: > > > I've just barely got qmail, qmailadmin and vpop running, need to know > > if there's a method for making an ezmlm list "announce only"...? > > There is. Can't say how off-hand, though. > > > (Pointers to any documentation on this would be appreciated; I haven't > > found any that address this exact topic so far.) > > man ezmlm-make (Hi, Johan.) I did that -- all it says is that switch -P creates a "private" list; doesn't explain what features are or are not part of its being private. > http://www.ezmlm.org/ Yes -- understandably one might not expect to find answers for 'ezmlm' there, since the frontpage sounds like only 'ezmlm-idx' is directly covered by the site. > The appropriate list is [EMAIL PROTECTED] (Thanks.) Fair enough -- but does it have a searchable archive? If I coulda found one, I certainly would've searched there first, just as I did through the 'qmail' list archive first -- where I found several prior conversations about ezmlm, thus thought posting here might be appropriate -- and even if not, it would eventually bring -this- conversation into a searchable archive for the benefit of others coming along after us. Then those ones coming along after us won't have to disturb the peace of this list by asking the same question yet another time. -- -- Jeff -- <http://www.wellnow.com> "There's nothing left in the world to prove. All that's worth doing is to love one another, using whatever means are available to serve."
On Fri, May 11, 2001 at 07:54:56AM -0400, peter green wrote: > [ No need to Cc: me, thanks. ] (Sorry -- found your name automagically in the 'to' field so CC'd the list; I'll get the hang of this in a minute. :-) > > If I'm understanding what I'm reading, it appears the thing > > to do [to change a normal list into an announce-only one] is > > -remove- '~/.qmail-list' and DIR/editor, then pipe directly to > > "ezmlm-send DIR"...? > > > > I believe it's implying list members would still be able to sub and > > unsub this way, but posts to the list would fall into the bit bucket. > > > > Have I got it right...? > > Almost. Posts to the list would bounce if you just remove .qmail-list. If > you want them to disappear without a bounce, do: > > echo '#' > .qmail-list > > A .qmail file with only comments will effectively blackhole a piece of mail. Okay, many thanks -- and unless I hear otherwise, I'll take it you're saying that subs/unsubs will continue to work in either case. -- -- Jeff -- <http://www.wellnow.com> "There's nothing left in the world to prove. All that's worth doing is to love one another, using whatever means are available to serve."
* Jeff Gordon <[EMAIL PROTECTED]> [010511 09:21]: > > The appropriate list is [EMAIL PROTECTED] > > (Thanks.) Fair enough -- but does it have a searchable archive? If I When in doubt, check [http://marc.theaimsgroup.com/] and [http://www.mail-archive.com/]. (IIRC, ezmlm is archived and searchable at both places.) /pg -- Peter Green : Architekton Internet Services, LLC : [EMAIL PROTECTED] --- perl -wle 'print "Prime" if (1 x shift) !~ /^1?$|^(11+?)\1+$/'
Hi Kevin, I use this simple PERL code that (for me) works nicely. $from, $to, $reply, $subject, $body are the variables you have to feed. The way of filling "Reply-to, Return-Path, From" lines, depends on your needs, this is only an example. open (MESSAGE, "| /usr/sbin/sendmail -t"); print MESSAGE "Return-Path: $from\n"; print MESSAGE "From: <$from>\n"; print MESSAGE "To: $to\n"; print MESSAGE "Reply-To: $reply\n"; print MESSAGE "Subject: $subject\n"; print MESSAGE "\n$body\n"; close (MESSAGE); Ciao, Tonino At 10/05/2001 10/05/2001 +0100, Kevin Smith wrote: >Hi All, > >I want to send mail using Perl, however, I want to use qmail to send it and >for qmail to report any failed emails, i.e. bad email addresses, failed >deliveries, etc. > >Would qmail-inject do this for me and if so, does anyone have any simple >examples using this with Perl? > >Many thanks, > >Kevin Smith
The only problem with that it doesn't report back to me any failed emails... or does it and I'm not looking in the right place??? Thanks, Kevin ----- Original Message ----- From: "Tonix" <[EMAIL PROTECTED]> To: "Kevin Smith" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, May 11, 2001 10:02 AM Subject: Re: qmail-inject and Perl > Hi Kevin, > > I use this simple PERL code that (for me) works nicely. > > $from, $to, $reply, $subject, $body are the variables you have to feed. > The way of filling "Reply-to, Return-Path, From" lines, depends on your > needs, this is only an example. > > > open (MESSAGE, "| /usr/sbin/sendmail -t"); > > print MESSAGE "Return-Path: $from\n"; > print MESSAGE "From: <$from>\n"; > print MESSAGE "To: $to\n"; > print MESSAGE "Reply-To: $reply\n"; > print MESSAGE "Subject: $subject\n"; > > print MESSAGE "\n$body\n"; > > close (MESSAGE); > > Ciao, > > Tonino > > At 10/05/2001 10/05/2001 +0100, Kevin Smith wrote: > >Hi All, > > > >I want to send mail using Perl, however, I want to use qmail to send it and > >for qmail to report any failed emails, i.e. bad email addresses, failed > >deliveries, etc. > > > >Would qmail-inject do this for me and if so, does anyone have any simple > >examples using this with Perl? > > > >Many thanks, > > > >Kevin Smith > >
Kevin Smith <[EMAIL PROTECTED]> wrote: > > I want to send mail using Perl, however, I want to use qmail to send it and > for qmail to report any failed emails, i.e. bad email addresses, failed > deliveries, etc. > > Would qmail-inject do this for me and if so, does anyone have any simple > examples using this with Perl? qmail-inject is the easiest way to inject mail. However, the only way it can "report back" failures to you is by bounce messages. Those will go to whatever address you use as the envelope sender. Were you hoping for something else? Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
I use Mail:Sendmail, which sends through SMTP. Early errors are caught by the module (syntactically wrong email address, broken communication with the server). Later errors (User unknown, ...) are reported as usual by a bounce from the server to the From: address. Not exactly what you asked for, but I find it more robust and more flexible: your script can use any mail server and run on any platform. >I want to send mail using Perl, however, I want to use qmail to send it and >for qmail to report any failed emails, i.e. bad email addresses, failed >deliveries, etc. > >Would qmail-inject do this for me and if so, does anyone have any simple >examples using this with Perl? > >Many thanks, > >Kevin Smith
That's a coincidence - I logged the same query this morning. The links created are: ln -s ../init.d/svscan S89svscan in rc3.d and rc5.d ln -s ../init.d/svscan K12svscan in rc0.d rc1.d rc2.d and rc6.d If I go into the /etc/rc.d/init.d directory and type ./svscan start ./qmail start it all runs perfectly. I run Open Linux 2.3 - what about you? Neil -----Original Message----- From: colette tostivint [mailto:[EMAIL PROTECTED]] Sent: Friday, 11 May 2001 20:10 To: Qmail@List. Cr. Yp. To Subject: reboot Hi Qmail doesn't run when i reboot my system. I make a link : ln -s ../init.d/qmail /etc/rc2.d/S88qmail I must start manually /etc/rc2.d/S88qmail . What is the problem? Thank you Colette Tostivint
It is not the default init your system started up, depening from your distribution this maybe be a different one. Have a look at http://www.lifewithqmail.org and read the "Life with Qmail" doc there. You will get the needed ln -s�s and many other helpful information on how to start your qmail experience. hope this helps Anton Pirnat btw.. next time it would be helpful you also are telling us what kind of OS (... Linux?, ...BSD?) and Version you are working with. It is often important, because (in example) file paths are different sometimes. :) On Friday 11 May 2001 10:09, colette tostivint wrote: > Hi > > Qmail doesn't run when i reboot my system. > > I make a link : ln -s ../init.d/qmail /etc/rc2.d/S88qmail > > I must start manually /etc/rc2.d/S88qmail . > > What is the problem? > > Thank you > > Colette Tostivint
Hi there, I've posted some messages concerning this strange "pop3 connection reset after 1 minute". I just discovered the reason for the problem, but I still don't have a solution. I'm using "checkpasswordnt" for my authentication issues (so that all users can be authenticated with our NT PDC). I just changed this back to the normal checkpassword program and tried again with an appropriate account. Now it works. No connection reset, nothing. So checkpasswordnt seems to make problems. But, as I understand, checkpassword is only used to authenticate the connection in the first place. After that it's not accessed again? There seems to be some kind of timeout after one minute, but where? This is the ps aux output while running a pop3 session: root 6176 0.0 0.2 1224 344 pts/0 S 11:43 0:00 /var/qmail/bin/qmail-popup wetzel-office.com /bin/checkpasswordnt /var/qmail/bin/qmail-pop3d Maildir jhassler 6177 0.0 0.3 1236 396 pts/0 S 11:43 0:00 /var/qmail/bin/qmail-pop3d Maildir One thing to mention: I certainly don't like this NT authentication stuff, but in this environment its needed at the moment (can't change it). Sorry for not mentioning checkpasswordnt in the first place, but I thought this would be the last place the problem could occur. I tried several things. tcpdump output is not very helpful. After the initial authentication packets there is a "NBT Session Keepalive" packet after 20 seconds. After this packet there is no other traffic to or from the NT server. I thought there would be something after exactly 60 seconds, but there is nothing. I'm also confused about this Keepalive packet, because the session should end after the first authentication transfers, shouldn't it? Strange, again: I use this "Mrs. Brisby" version of qmail-smtpd together with checkpasswordnt to implement "SMTP AUTH". This works without any problems. The same packets are travelling through the cable, there is also this Keepalive packet, but the connection is not reset after 60 seconds. So there seems to be something about checkpasswordnt qmail-pop3d or qmail-popup don't like. Maybe an Anti-M$-check :-) If anyone on this list is also using checkpasswordnt and doesn't have this problem then the NT server is the "evil box". That's nothing new, indeed, but this would be off-topic for this list. I'll further try finding a solution, maybe someone of you has a clue where the problem might be. Some day... I'll throw these NT things out. Certainly. Thanks again for your help, I really appreciate it. Jens
Jens Hassler <[EMAIL PROTECTED]> wrote: > I'm using "checkpasswordnt" for my authentication issues (so that all users > can be authenticated with our NT PDC). I just changed this back to the > normal checkpassword program and tried again with an appropriate account. > Now it works. No connection reset, nothing. So checkpasswordnt seems to make > problems. I concur. However, I don't know anything about checkpasswordnt. > But, as I understand, checkpassword is only used to authenticate the > connection in the first place. After that it's not accessed again? There > seems to be some kind of timeout after one minute, but where? > > This is the ps aux output while running a pop3 session: > > root 6176 0.0 0.2 1224 344 pts/0 S 11:43 0:00 > /var/qmail/bin/qmail-popup wetzel-office.com /bin/checkpasswordnt > /var/qmail/bin/qmail-pop3d Maildir > jhassler 6177 0.0 0.3 1236 396 pts/0 S 11:43 0:00 > /var/qmail/bin/qmail-pop3d Maildir I don't understand this. I thought that in a normal setup, tcpserver forked qmail-popup, which exec's checkpassword, which exec's qmail-pop3d. In the case of a successful authentication, the checkpassword process replaces itself with qmail-pop3d, so it can't be left hanging around like this. Is checkpasswordnt fundamentally broken? Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
On Fri, May 11, 2001 at 08:17:47AM -0600, Charles Cazabon wrote: > I don't understand this. I thought that in a normal setup, tcpserver forked > qmail-popup, which exec's checkpassword Not quite. qmail-popup forks and exec's checkpassword, in order that if checkpassword fails qmail-popup can report an -ERR message instead of just disconnecting silently. -- Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/ http://untroubled.org/ OpenPGP key: 699980E8 / D0B7 C8DD 365D A395 29DA 2E2A E96F B2DC 6999 80E8
Bruce Guenter <[EMAIL PROTECTED]> wrote: > On Fri, May 11, 2001 at 08:17:47AM -0600, Charles Cazabon wrote: > > I don't understand this. I thought that in a normal setup, tcpserver forked > > qmail-popup, which exec's checkpassword > > Not quite. qmail-popup forks and exec's checkpassword, in order that if > checkpassword fails qmail-popup can report an -ERR message instead of > just disconnecting silently. Thanks for the correction, Bruce -- makes much more sense. However, it still doesn't explain why the other fellows' ntcheckpassword hangs around indefinitely even after authentication success, and then causes the POP3 connection to reset after 60 seconds. Moral: NT causes headaches. Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
On Fri, May 11, 2001 at 01:02:47PM -0600, Charles Cazabon wrote: > Bruce Guenter <[EMAIL PROTECTED]> wrote: > > On Fri, May 11, 2001 at 08:17:47AM -0600, Charles Cazabon wrote: > > > I don't understand this. I thought that in a normal setup, tcpserver forked > > > qmail-popup, which exec's checkpassword > > > > Not quite. qmail-popup forks and exec's checkpassword, in order that if > > checkpassword fails qmail-popup can report an -ERR message instead of > > just disconnecting silently. > > Thanks for the correction, Bruce -- makes much more sense. However, it still > doesn't explain why the other fellows' ntcheckpassword hangs around > indefinitely even after authentication success, and then causes the POP3 > connection to reset after 60 seconds. The ps report that I recall seeing showed only qmail-popup and qmail-pop3d running. The qmail-popup command-line of course includes ntcheckpassword. Now, if ntcheckpassword itself is hanging around, it's badly broken, as the checkpassword interface requires that the subprogram be exec'd and not forked. -- Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/ http://untroubled.org/ OpenPGP key: 699980E8 / D0B7 C8DD 365D A395 29DA 2E2A E96F B2DC 6999 80E8
qmail-smtpd-chkusr is a patch for qmail-smtpd (with vpopmail 4.9.x) and permits rejecting non existing users/aliases/mailing-lists in the smtp acceptance phase. I've just updaded this patch, with the following changes: - changed the error code emission (550 instead of 553) - added check for BOUNCE_MAIL flag This patch is freely available at http://www.interazioni.it/qmail
Many Thanks Dave, you were spot on. -----Original Message----- From: Dave Sill [mailto:[EMAIL PROTECTED]] Sent: 10 May 2001 18:32 To: [EMAIL PROTECTED] Subject: Re: remote smtp problem [EMAIL PROTECTED] wrote: >When ever a remote client tries to send mail thru my qmail box, qmail >appends a question mark to the end of the domain i.e >Sorry, I couldn't find any host named rbi.co.uk?. (#5.1.2) Clients injecting messages via SMTP? Using selective relaying? I'd guess that "RELAYCLIENT" is being set to " " instead of "" in the access file (perhaps /etc/tcp.smtp). -Dave ******************************DISCLAIMER****************************** This message is intended only for the use of the person(s) (\"Intended Recipient\") to whom it is addressed. It may contain information, which is privileged and confidential. Accordingly any dissemination, distribution, copying or other use of this message or any of its content by any person other than the Intended Recipient may constitute a breach of civil or criminal law and is strictly prohibited. If you are not the Intended Recipient, please contact the sender as soon as possible. Reed Business Information Ltd. +44 (0)20 8652 3500 **********************************************************************
If I read the RFCs correctly, case does not matter in the mailbox (left side) part, but should be preserved. I don't know of any mail server that fails to deliver mail if case changes. I never paid attention to see if case is preserved.
Milivoj Ivkovic <[EMAIL PROTECTED]> wrote: > If I read the RFCs correctly, case does not matter in the mailbox (left > side) part, but should be preserved. No, that's not what 2821 says. The RFC defines the FQDN part of an email address to be case-insensitive, and says that the treatment of case of local-part is up to the receiving system, and so intermediate MTAs must preserve the case of local-part. It then recommends that MTA implementors treat local-part as case insensitive when they are the final destination MTA, but does not require this. Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
>Was it 822 that said this? Or is there a different RFC I should also look >at? I went back to check the new RFC 2821. My previous interpretation was not exact. It is not that case should be preserved, it must; even though taking case into account is discouraged. RFC 2821 / 2.4: ... "The local-part of a mailbox MUST BE treated as case sensitive." ... "However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged." Sorry for spreading not really correct information. >Section 3.4.7 seems to imply to me that FROM and from are the same thing, >but the argument here is that this just is about parts of the headers and >not the email address. > > >Thanks! >Matt > >-----Original Message----- >From: Milivoj Ivkovic [mailto:[EMAIL PROTECTED]] >Sent: Friday, May 11, 2001 5:06 AM >To: [EMAIL PROTECTED] >Subject: Re: Case in email address > > >If I read the RFCs correctly, case does not matter in the mailbox (left >side) part, but should be preserved. > >I don't know of any mail server that fails to deliver mail if case changes. > >I never paid attention to see if case is preserved.
>local-part is up to the receiving system, and so intermediate MTAs must >preserve the case of local-part. >It then recommends that MTA implementors treat local-part as case insensitive >when they are the final destination MTA, but does not require this. You are correct of course, I should have re-read the RFC before posting. Sorry.
>I always thought that qmail converted the user part of an incoming email >to lowercase and then handled it appropriately. Based on other emails, it seems clear that the RFC standard is to preserve case for the user part of the email address. Qmail does this from what I can tell, as far as how delivery locally goes it also appears to me that case is ignored as the RFC recommends. Is there a way to bypass this (not that I will, I just am curious) to have [EMAIL PROTECTED] and [EMAIL PROTECTED] be delivered separately? And is the below process correct? I hope I am not asking questions that people feel are not appropriate for this list- please let me know if so and I will stop this thread. Thanks Matt
Matt Simonsen <[EMAIL PROTECTED]> wrote: > Is there a way to bypass this (not that I will, I just am curious) to have > [EMAIL PROTECTED] and [EMAIL PROTECTED] be delivered separately? Yes, the qmail-users mechanism can be used to do this. > And is the below process correct? There was nothing relevant below this in your message; what process? Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
There was a statement made that Qmail converts an email to lower-case, but judging by the fact that Qmail can handle those seperately I am guessing this is incorrect. -----Original Message----- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 12:32 PM To: Qmail@List. Cr. Yp. To Subject: Re: Case in email address Matt Simonsen <[EMAIL PROTECTED]> wrote: > Is there a way to bypass this (not that I will, I just am curious) to have > [EMAIL PROTECTED] and [EMAIL PROTECTED] be delivered separately? Yes, the qmail-users mechanism can be used to do this. > And is the below process correct? There was nothing relevant below this in your message; what process? Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
Matt Simonsen <[EMAIL PROTECTED]> wrote: > There was a statement made that Qmail converts an email to lower-case, but > judging by the fact that Qmail can handle those seperately I am guessing > this is incorrect. By default, qmail takes the users from /etc/password which have valid home directories as the list of users which can receive mail. It collapses case on these. You can override this behaviour with the qmail-users mechanism. Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
Hello, I am currently experiencing serious troubles moving a large sendmail site to a another box with qmail. The sendmail configuration was rather chaotic; a mixture of /etc/aliases and virtusertable and lots of .forward-files. Of course I am planning to make all users virtual, but right now that would be to difficult to handle as the former admin of the sendmail site doesn't know all passwords. Therefore the users do exist on the system. My problem is that a lot of assignements in virtusertable were like "@domain user", so I translated them to users/assign in the form: "+admin_of_virtual_domain-:sysuser:id:gid:::" Is that correct? What happens now is that such an assignement seems to make all messages go also to sysuser, eventhough I have specific entries like "=admin_of_virtual_domain-Email.Address:sysuser2:id:gid:::" for Email.Address@domain for sysuser2. What is happening here? Does anyone have a recipe to translate /etc/aliases and virtusertable to qmail safely?? Thank you very much in advance Philipp Homan -- Sent via webmail.mbe.at (Version 1.19) (c) 2001 by Philipp Homan
Nick (Keith) Fish: > Chris Ochap wrote: >> start() { >> # Start daemons. >> echo -n $"Starting $prog: " >> daemon /var/qmail/rc >> /usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u >> 51 -g 50 0 smtp /var/qmail/bin/qmail-smtpd >> RETVAL=$? >> [ $RETVAL -eq 0 ] && touch /var/lock/subsys/qmail >> echo >> return $RETVAL >> } > Try adding "2>&1" to the end of the tcpserver line, so: > /usr/local/bin/tcpserver -v -p -x /etc/tcprules/tcp.smtp.cdb -u 51 -g 50 0 smtp > /var/qmail/bin/qmail-smtpd 2>&1 [...] That is not correct, that will just redirect stderr to stdout. You need to put a single & at the end of the line that starts up tcpserver to put the process into the background. regards, -- Joerg Lenneis email: [EMAIL PROTECTED]
Chris Jackman <[EMAIL PROTECTED]> wrote: [...] > We noticed that there is no delivery 2: success message, nor is there > ever for any other email to [EMAIL PROTECTED] [...] > If we kill all the alias processes first, and then kill the rt process (78014 > above) that is doing "perl -T /var/rt/bin/rtmux.pl rt-mailgate tickets > correspond", we see this in the qmail logs: > > 2001-05-06 05:03:26.769179500 delivery 2: deferral: qmail-local_crashed./ It would seem at first glance that your Perl script never finishes; it blocks on something, or goes into an endless loop. The next step to debug this is to strace/truss the "rtmux.pl" process and find out what's wrong with it. However, it then becomes a Request Tracker problem, and has nothing to do with qmail. You'll probably want to follow this up on that list instead of the qmail one. Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
i'm not a coder i can't program something like that .. but i thought someone already did code this kind of software.. and i'm asking if it's out there and what is it call if it is thanks ----- Original Message ----- From: "Charles Cazabon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 10, 2001 10:26 AM Subject: Re: notification of new email whenever user logs in on the shell > alexus <[EMAIL PROTECTED]> wrote: > > > > basically somehow i need to show to user that there is a new mail for > > > > him/her whenever user logs in > > > does it matter that i no longer have /var/mail/$userid? and i have Maildir > > instead? > > Yes, that's it. $HOME/Maildir/ makes it trivial to see if you have new > messages; when you login, if there are files in $HOME/Maildir/new/, there's > new mail. If there's files in $HOME/Maildir/cur/, you have old (seen) mail. > If you want to get fancy, you can code this type of check (with whatever > output messages you want) into a system-wide shell .rc file. > > I have a Python script I use for this purpose, which checks multiple Maildirs > and presents a summary of current and new messages in each. Send me a message > off-list if you want a copy. > > Charles > -- > ----------------------------------------------------------------------- > Charles Cazabon <[EMAIL PROTECTED]> > GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ > Any opinions expressed are just that -- my opinions. > ----------------------------------------------------------------------- >
alexus <[EMAIL PROTECTED]> wrote: > > > basically somehow i need to show to user that there is a new mail for > > > him/her whenever user logs in > > I have a Python script I use for this purpose, which checks multiple > > Maildirs and presents a summary of current and new messages in each. Send > > me a message off-list if you want a copy. > i'm not a coder i can't program something like that .. but i thought someone > already did code this kind of software.. and i'm asking if it's out there > and what is it call if it is Yes, many Maildir-checkers exist. There are half a dozen or more listed in the "User-contributed Maildir support" section of qmail.org. All you have to do is put a call to one of these in a system-wide shell rc file to make it automatic for all users on login. Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
can you suggest one that widely used and most popular or 'cause i didn't find any there (i guess i'm blind or something) ----- Original Message ----- From: "Charles Cazabon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 11, 2001 11:21 AM Subject: Re: notification of new email whenever user logs in on the shell > alexus <[EMAIL PROTECTED]> wrote: > > > > > basically somehow i need to show to user that there is a new mail for > > > > him/her whenever user logs in > > > > I have a Python script I use for this purpose, which checks multiple > > > Maildirs and presents a summary of current and new messages in each. Send > > > me a message off-list if you want a copy. > > > i'm not a coder i can't program something like that .. but i thought someone > > already did code this kind of software.. and i'm asking if it's out there > > and what is it call if it is > > Yes, many Maildir-checkers exist. There are half a dozen or more listed in > the "User-contributed Maildir support" section of qmail.org. All you have to > do is put a call to one of these in a system-wide shell rc file to make it > automatic for all users on login. > > Charles > -- > ----------------------------------------------------------------------- > Charles Cazabon <[EMAIL PROTECTED]> > GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ > Any opinions expressed are just that -- my opinions. > ----------------------------------------------------------------------- >
alexus <[EMAIL PROTECTED]> wrote: > > Yes, many Maildir-checkers exist. There are half a dozen or more listed > > in the "User-contributed Maildir support" section of qmail.org. > can you suggest one that widely used and most popular or 'cause i didn't > find any there (i guess i'm blind or something) There's several. The first one one the page is a link in the line which reads "Matthew C. Mead has a ``from'' program that prints a summary of mail in a maildir waiting to be read. ". The line below that has a link to another one. I have no idea how popular these are; I use a quickie Python script I wrote. Here's a freebie, in bash shell scripting: #!/bin/bash INBOX=$HOME/Maildir new=`ls "$INBOX"/new/ | wc -l` if [ "$new" -gt 0 ] ; then echo "You have $new new messages waiting." fi Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
ok thanks for that script it works just fine:) two more questions though first if i'll put it in /etc/profile will it work for all users? i'm using FreeBSD 4.3-RELEASE and another question how do i notify user when e-mail arriving while he's on shell? ----- Original Message ----- From: "Charles Cazabon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, May 12, 2001 1:04 AM Subject: Re: notification of new email whenever user logs in on the shell > alexus <[EMAIL PROTECTED]> wrote: > > > Yes, many Maildir-checkers exist. There are half a dozen or more listed > > > in the "User-contributed Maildir support" section of qmail.org. > > > can you suggest one that widely used and most popular or 'cause i didn't > > find any there (i guess i'm blind or something) > > There's several. The first one one the page is a link in the line which reads > "Matthew C. Mead has a ``from'' program that prints a summary of mail in a > maildir waiting to be read. ". The line below that has a link to another one. > I have no idea how popular these are; I use a quickie Python script I wrote. > Here's a freebie, in bash shell scripting: > > #!/bin/bash > > INBOX=$HOME/Maildir > new=`ls "$INBOX"/new/ | wc -l` > if [ "$new" -gt 0 ] ; then > echo "You have $new new messages waiting." > fi > > Charles > -- > ----------------------------------------------------------------------- > Charles Cazabon <[EMAIL PROTECTED]> > GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ > Any opinions expressed are just that -- my opinions. > ----------------------------------------------------------------------- >
I am running qmail on: RedHat 6.2 256 Mb Ram I set concurrency remote = 150... however, most of the time, it seems like only a handful of remote processes are running, even though the queue backs up (right now, over 14000 msgs in queue and only 20 remote processes running)... Anybody have an idea about how to force it to run faster or at least not kill off my qmail-remote processes? New to this list so hope I provided enough info. Michael Geier CDM Sports Systems Administrator email: [EMAIL PROTECTED] phone: 314.991.1511 x 6505
"Michael Geier" <[EMAIL PROTECTED]> wrote: >I am running qmail on: > RedHat 6.2 > 256 Mb Ram > >I set concurrency remote = 150... > >however, most of the time, it seems like only a handful of remote processes >are running, even though the queue backs up (right now, over 14000 msgs in >queue and only 20 remote processes running)... Are you sure concurrencyremote is set to 150? You restarted qmail-send after changing it? The logs reflect the 150 setting? >Anybody have an idea about how to force it to run faster Faster disk More memory Faster network Replace syslog with multilog Install djbdns, run dnscache Kill non-qmail processes Faster CPU >or at least not kill off my qmail-remote processes? What makes you think qmail-remote processes are being killed off? -Dave
Michael Geier <[EMAIL PROTECTED]> wrote: > > I set concurrency remote = 150... > > however, most of the time, it seems like only a handful of remote processes > are running, even though the queue backs up (right now, over 14000 msgs in > queue and only 20 remote processes running)... Most likely you did not restart qmail after changing concurrencyremote, as 20 is the default maximum for this. `man qmail-send` for details. Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
thanks for the tips Dave... to those that had replied: I had rebooted qmail (frequently)... I installed djbdns, killed splogger, and rebooted server things seem to be much better. -----Original Message----- From: Dave Sill [mailto:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 12:30 PM To: Qmail Mailing List Subject: Re: newbie question with concurrency remote "Michael Geier" <[EMAIL PROTECTED]> wrote: >I am running qmail on: > RedHat 6.2 > 256 Mb Ram > >I set concurrency remote = 150... > >however, most of the time, it seems like only a handful of remote processes >are running, even though the queue backs up (right now, over 14000 msgs in >queue and only 20 remote processes running)... Are you sure concurrencyremote is set to 150? You restarted qmail-send after changing it? The logs reflect the 150 setting? >Anybody have an idea about how to force it to run faster Faster disk More memory Faster network Replace syslog with multilog Install djbdns, run dnscache Kill non-qmail processes Faster CPU >or at least not kill off my qmail-remote processes? What makes you think qmail-remote processes are being killed off? -Dave
Jamyn <[EMAIL PROTECTED]> wrote: >$qmail_home/control/concurrencyremote > The number you insert into this file determines how > many remote sockets/connections at a time your mail > server will open. Yes. >$qmail_home/control/concurrencylocal > The number you insert into this file determines how > many local/incoming mail connections you want Qmail > to allow at a time. No. It's the maximum number of simultaneous local deliveries. The limit on incoming SMTP sessions is determined by tcpserver, if you use it. The default is 20. "Life with qmail" adds a pseudo-control file called concurrencyincoming that is passed to tcpserver. -Dave
"Neil Whittington" <[EMAIL PROTECTED]> wrote: >The default run level is 3. > >The links created are: > ln -s ../init.d/svscan S89svscan > in rc3.d and rc5.d > > ln -s ../init.d/svscan K12svscan > in rc0.d rc1.d rc2.d and rc6.d So you're starting svscan at runlevel 3. Is it running after the system boots? What links did you create for qmail? -Dave
Excellent list people, I'm trying to get the smtp after pop authentication part of vpopmail to work. I followed the LWQ instructions to install qmail and I'm using qmail-pop3d. Where should the below startup line for vchkpw be placed? Thanks! Steven 12. How to use vchkpw with qmail-pop3d server Here is a sample startup line for qmail-pop3d and vchkpw env - PATH="/var/qmail/bin:/usr/local/bin" \ tcpserver -H -R 0 pop-3 \ /var/qmail/bin/qmail-popup your.domain.com \ /home-dir-of-vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir &
On Fri, May 11, 2001 at 09:56:10AM +0200, Peter van Dijk wrote: > [note: section 2.4.1 doesn't exist in RFC2821, nor in RFC821] The author means section 2.4. Mate
Hi - I have qmail setup 1.03 - Solaris 8 recent patch cluster - Netra X1. I have roaming users ( sales guys ) that need to auth thru smtp ( qmail ) to send messages. I can't seem to get it to go. This is just Outlook 2000 DELL win 2000 )on a laptop and the server for testing purposes. I have installed auth patch and djb's checkpasswd program - I upgrade to the SMTP_AUTH patch .30 and was trying cmd5checkpw - same result. I need a little bit more info on how to implement. I have followed the instructions but things are still a little unclear. Do I need qmail remote or a pop server. ( They only want to send mail thru this server - they will dial there isp and then auth thru the qmail server. I am also using tcpserver to run qmail. I had some instructions on how to test the server with the AUTH cmd through checkpasswd ( I only tested plain at the time) which I can no longer find - it work as outlines and put me in my home dir. Since I have upgraded I need to retest the server. Right now under AUTH plain it gives me out of memory - I don't know that I'm still testing this procedure right. I would like to test LOGIN but don't know how or what to return when it returns it's string. qmail_smtp_auth 0.30 cmd5checkpd 0.22 or checkpasswd qmail 1.03 tcpserver smtp startup #!/bin/sh QMAILDUID=`/usr/xpg4/bin/id -u qmaild` NOFILESGID=`/usr/xpg4/bin/id -g qmaild` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` exec /usr/local/bin/softlimit -m 2000000 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp /var/qmail/bin/qmail-smtpd me.me.com \ /bin/cmd5checkpw /bin/true smtpd 3 2>&1 I have followed the outgoing instruction for Outlook for the client but it won't let me auth. question - what should be in inet.conf if I'm using tcpserver? Thanks [EMAIL PROTECTED] Please send all flames to PG&E and EL PASO Natural GAS( the weasels! )
<[EMAIL PROTECTED]> wrote: >I had some instructions on how to test the server with the AUTH cmd through >checkpasswd ( I only tested plain at the time) which I can no longer find - >it work as outlines and put me in my home dir. Since I have upgraded I need >to retest the server. Right now under AUTH plain it gives me out of memory - >I don't know that I'm still testing this procedure right. I would like to >test LOGIN but don't know how or what to return when it returns it's string. > >qmail_smtp_auth 0.30 >cmd5checkpd 0.22 or checkpasswd >qmail 1.03 > >tcpserver smtp startup >#!/bin/sh >QMAILDUID=`/usr/xpg4/bin/id -u qmaild` >NOFILESGID=`/usr/xpg4/bin/id -g qmaild` >MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` >exec /usr/local/bin/softlimit -m 2000000 \ > /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c "$MAXSMTPD" \ > -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp /var/qmail/bin/qmail-smtpd >me.me.com \ > /bin/cmd5checkpw /bin/true smtpd 3 2>&1 > >I have followed the outgoing instruction for Outlook for the client but it >won't let me auth. Try raising the memory limit (the 2000000) to 4000000, 8000000 until the "out of memory" error goes away. >question - what should be in inet.conf if I'm using tcpserver? Nothing related to the services handled by tcpserver. -Dave
I've installed v.1.03 from a src.deb package onto Debian Potato. There is a large volume of literature which I've spent some days reading and can't find explanations for a number of points (entirely due to my semi- computer literate state). I connect to an ISP by dialling with a modem and have just two user accounts. I've never really understood the concept of a FQDN and so can't with confidence create a /var/qmail/control file. Hypothetically, my ISP is heaven.com, I call my box eden and have users adam and eve, what is my FQDN? (I log in as say garden - so outsiders email me as [EMAIL PROTECTED]). I fail to understand exactly what part alias plays in the setup. At a minimum, I should create three - root, postmaster and mailer-daemon, but do I need any for my user accounts and why? With the simple setup I have should I bother with the dot-forward, daemontools and fastforward packages? I know these are very simple questions, but could someone give a simple explanation to help me along. What I would ideally like is a write up for a minimal setup for the type of installation I have - it seems none exists or else I can't find it. Help will be much appreciated. John.
john gennard <[EMAIL PROTECTED]> wrote: > I've installed v.1.03 from a src.deb package onto Debian Potato. > There is a large volume of literature which I've spent some days > reading and can't find explanations for a number of points (entirely > due to my semi- computer literate state). Please do not take this as a flame, insult, or pointless reply, but if (by your own admission) you are only semi-literate in computers, what are you doing installing a Unix MTA? Perhaps you should instead use something like mutt to read mail off your ISP's POP3 or IMAP server, and transfer any outgoing mail to them with a relay-only MTA like nullmailer. > I connect to an ISP by dialling with a modem and have just two user > accounts. I've never really understood the concept of a FQDN and so > can't with confidence create a /var/qmail/control file. Hypothetically, > my ISP is heaven.com, I call my box eden and have users adam and > eve, what is my FQDN? (I log in as say garden - so outsiders email > me as [EMAIL PROTECTED]). You don't have an FQDN. Well, you do, but it changes everytime you connect, and it's something like "dialin-254-43-129-32-us-west.spurious.isp.net". > I fail to understand exactly what part alias plays in the setup. At > a minimum, I should create three - root, postmaster and > mailer-daemon, but do I need any for my user accounts and why? No, and it's a big discussion. > With the simple setup I have should I bother with the dot-forward, > daemontools and fastforward packages? No. > I know these are very simple questions, but could someone give > a simple explanation to help me along. What I would ideally like is > a write up for a minimal setup for the type of installation I have - > it seems none exists or else I can't find it. qmail is designed for well-connected hosts (read: your internet connection is fast and always-on). While it can be made to do what you want it to do, it isn't completely trivial, and probably requires more Unix system administration skills to install, configure, and maintain than you currently posess. Lurk in this list for a few months, and you may pick up enough to get there. Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
* john gennard <[EMAIL PROTECTED]> [010511 15:25]: > I connect to an ISP by dialling with a modem and have just two user > accounts. So you need serialmail. Get and install it. There are many hints on how to do this in this list's archive. > I've never really understood the concept of a FQDN and so > can't with confidence create a /var/qmail/control file. Your box has a name, consisting of your domain (which you don't have) and its local hostname. You can register a domain for a dial-up system at dyndns.org or something. > Hypothetically, my ISP is heaven.com, I call my box eden and have > users adam and eve, what is my FQDN? (I log in as say garden - so > outsiders email me as [EMAIL PROTECTED]). That is irrelevant. You just want your From address to be correct. > I fail to understand exactly what part alias plays in the setup. At a > minimum, I should create three - root, postmaster and mailer-daemon, > but do I need any for my user accounts and why? Aliases are email addresses without local users. Mail to root is internally forwarded to a user you put in ~alias/.qmail-root, for example. > With the simple setup I have should I bother with the dot-forward, > daemontools and fastforward packages? Depends on where you come from and where you want to go. dot-forward and fastforward should be unnecessary, but daemontools and ucspi-tcp are very clever. > I know these are very simple questions, but could someone give > a simple explanation to help me along. What I would ideally like is > a write up for a minimal setup for the type of installation I have - > it seems none exists or else I can't find it. Ummmm... Just install qmail, ucspi-tcp, daemontools and serialmail and follow the instructions step by set. Really. :-)
Title: �U��m�ˤ��ѭ�,�ڴNŪ�x�_�Y��ߤj�ǤT�~�žǥ�.��}�l�ڤ]
���۫H�����i�H�ȿ�.���O��Ĺ�F����2,000��!!!
�]����eWorld Casino
�䲼�F! �ڷQ��j�a���ɧ�
���߮�........�I�i�h����A�̴N���D������F....
�ոլ�.....�N�O�U���o�@�a!!!!!!!!!
eWorld Casino
Title: MASS mailingHi,
My name is Mike and I am the UNIX admin at WB online. Anyway, I was tasked with rolling out a new mailing list server because our ListServe box is too slow and easy to hack. I set up qmail on a small 450mhz SUN netra and it seems to also be too slow. I need to be able to deliver about 1,000,000 emails a day and from the speed I get out of my netra I will need a dozen of them!Does anyone have any idea of what hardware will work best for huge "newsletter" server? I was thinking of setting up a cluster of 5 to 10 netras to speed up delivery. However, it may be better to just get bigger servers. I have also run out of inodes in the var filesystem due to too many queued mails :-)
Thanks for any suggestions,
Mike Kuriger
WBOnline
818-977-8198
Kuriger, Michael <[EMAIL PROTECTED]> wrote: > My name is Mike and I am the UNIX admin at WB online. Anyway, I was tasked > with rolling out a new mailing list server because our ListServe box is too > slow and easy to hack. I set up qmail on a small 450mhz SUN netra and it > seems to also be too slow. I need to be able to deliver about 1,000,000 > emails a day and from the speed I get out of my netra I will need a dozen of > them! High-volume qmail servers is a topic which comes up regularly on this list; if you search the qmail mailing list archives, you will find many good technical suggestions on getting the best performance out of your system. You can find a link to the archives at qmail.org. A few things you'll probably want: -big-concurrency patch, and a concurrencyremote setting of 500 or as high as you have resources for -queue on it's own disk or disks (RAID), possibly on its own SCSI controller -15kRPM SCSI disk(s) -logging through multilog, to separate disk -use something other than Solaris; it's horribly slow in file operations and its networking code is bloated, buggy, and slow -if your mailings are unique-per-user (i.e. body changes for every recipient), you'll need the big-todo patch, and there are various ways of scheduling the message injection to maximize delivery speed -if your mailings are all identical message bodies, use ezmlm/ezmlm-idx as your mailing list manager, or write something custom which uses qmail's VERP functionality to automate bounce handling -have bounces handled by a separate machine There's other tricks as well, but with the above list you should easily be able to handle 1M deliveries a day on decent hardware. I'm afraid I'm not familiar with the Netra you mention. Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
Hello, I would like to control (or add) to a subject line text. This is for a server that virt hosts approx 20 domains. I would like to be able to add information to all incoming mail for one particular domain. Is there a qmail trick for this, or do I need to go through a pl script? Thanks in advance. So far I have been unable to find anything like this. Derrik
Inthereal <[EMAIL PROTECTED]> wrote: > > This is for a server that virt hosts approx 20 domains. I would like to > be able to add information to all incoming mail for one particular domain. > Is there a qmail trick for this, or do I need to go through a pl script? One way would be to use Bruce Guenter's QMAILQUEUE patch, and then use his qmail-qfilter mechanism (or roll your own) to modify the messages as they are injected into the queue. You can find the neccessary links at qmail.org. Charles -- ----------------------------------------------------------------------- Charles Cazabon <[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. -----------------------------------------------------------------------
Robin S. Socha writes: > * Paulo Jan <[EMAIL PROTECTED]> [010510 11:00]: > > Considering the guy's name, perhaps English isn't his primary language > > and he isn't fluent at all with it, which would also explain why he > > wasn't able to express himself politely enough when rejecting the > > "offer" from that consultant, and had to resort to a > > basic-and-apparently-rude-sounding phrase like "I was asking for free > > help". Did that thought cross your mind? > > Not for second. I'm German. I don't think. Please forgive Robin. English isn't his primary language, and he sometimes uses rude words and phrases that I'm sure he would never, ever say in his native German. -- -russ nelson will be speaking at http://www.osdn.com/conferences/handhelds/ Crynwr sells support for free software | PGPok | Mailing lists should not set 521 Pleasant Valley Rd. | +1 315 268 1925 voice | Reply-To: back to the list! Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | http://russnelson.com/rt.html
Dave Sill writes: > Second, the offer of commercial support made to Pablo was sent > privately, not to list. Pablo's reposting it publicly is at least as > rude as trolling the list for clients. The best way to troll the list for clients is to answer people's questions. > Answering FAQ's is "nice", but it's tiresome and contributes to > lowering the signal/noise ratio on the list and it encourages other > newbies to ask their FAQ's. Flaming them about it, though, produces triple the traffic: 1) The newbie's mail 2) The flamer's mail, and 3) The backlash against Robin. > Ignoring FAQ's is the easiest and safest approach. It encourages the > newbie to search the web, list archives, etc. and doesn't reward > newbies by answering their question. It keeps the signal/noise ratio > high, and it keeps the civility and morale high. Probably. But it demands a certain amount of Teutonic self-control. -- -russ nelson will be speaking at http://www.osdn.com/conferences/handhelds/ Crynwr sells support for free software | PGPok | Mailing lists should not set 521 Pleasant Valley Rd. | +1 315 268 1925 voice | Reply-To: back to the list! Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | http://russnelson.com/rt.html
I have problem with Users. I Using qmail with MySQL and trying to send mail. If i send mail then i don't receive that user doesn't exist but the mail isnt't delivered to his mailbox. What can be wrong ?? I did everything in LifeWithQMAIL configuration guide and it doesn't work. If you need some confs pleas tell mi which one you need. Can someone help me ??
Am 12.05.2001 um 08:14:41 schrieb Pavel Sorejs: Hi Pavel, > I Using qmail with MySQL > I did everything in LifeWithQMAIL afaik LWQ does not talk about MySQL, does it? As it seems that you do not have long-time experience with qmail it might make sense to follow LWQ *EXACTLY* to get a plain installation that works. If this works and if you got at least a basic knowledge of what is going on you could customize the setup, e.g. patch qmail to use a MySQL Database to look up users. bye /ch
hello, I install the qmail on Solaris 5.7, I can receive letter,but when I diliver letters, the server say "451 qq internal bug(#4.3.1)" ,How to deal with this problem? thx!
