qmail Digest 7 Feb 2001 11:00:00 -0000 Issue 1268

Topics (messages 56733 through 56771):

chrooting qmail...
        56733 by: Thomas Ackermann
        56736 by: Uwe Ohse

Re: unable to pick up email
        56734 by: Charles Cazabon

Re: Best option for sending a newsletter
        56735 by: Charles Cazabon

error
        56737 by: Dale Herring
        56739 by: Charles Cazabon

qmail+antivirus question
        56738 by: Tore Micaelsen
        56740 by: Olivier M.

Re: qmtp and spammers.
        56741 by: Sam Trenholme
        56750 by: Pavel Kankovsky

QMail problem
        56742 by: NDSoftware

.... msg 299012 to local [EMAIL PROTECTED]
        56743 by: g0thic
        56744 by: Charles Cazabon

How can I patch qmail-smtpd-auth?
        56745 by: bc201.21cn.com
        56746 by: Charles Cazabon

Perl checkpassword
        56747 by: Larry M. Smith is the BPFH
        56748 by: Mark Delany

Re: ms-tnef attachments
        56749 by: Jason Haar

Re: Netsaint and qmail-stat
        56751 by: Steve Tylock

to supervise or not to supervise
        56752 by: Peter Brezny
        56754 by: Kris Kelley
        56755 by: Greg White
        56766 by: Paul Jarc

Re: virtualdomain/smtproute
        56753 by: Jamin A. Brown

QMail not relaying
        56756 by: bmcalpine.macconnect.com

OT Can't login to Qmailadmin webpage as postmaster
        56757 by: David Litke

Re: CNAME lookup failed temporarily. (#4.4.3) - BUG In qmail-remote ?!
        56758 by: Curtis Generous
        56760 by: Pavel Kankovsky

lwq & freebsd
        56759 by: t_oo

Slow response time
        56761 by: Michael Owens
        56764 by: Campos Mario

no incoming mail from outside
        56762 by: Ross Davis - Data Anywhere
        56763 by: Chris Johnson
        56765 by: Mark Delany

thanks for you answer my question!but it is none used.
        56767 by: dick

Sluggish SMTP
        56768 by: Timothy J. Z. Olow

logging to console and log files
        56769 by: Tim Hassan

qmail + Solaris 7.0 fatal: data 451 qq write error or disk full (#4.3.0)
        56770 by: Michael Maier

Re: qmail + Solaris 7.0 fatal: data 451 qq write error or disk f
        56771 by: Stefaan A Eeckels

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]


----------------------------------------------------------------------


hy!
i recently started to chroot my qmail, now i got sort of stuck.

when trying to deliver a message i get the following output from qmail:

delivery 1: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/

my chrooted tree looks as follows:
.:
total 20
drwxr-xr-x    5 root     root         4096 Feb  6 14:36 .
drwxr-xr-x    6 root     root         4096 Feb  6 13:29 ..
drwxr-xr-x    2 root     root         4096 Feb  6 14:36 bin
drwxr-xr-x    2 root     root         4096 Feb  6 14:38 lib
drwxr-xr-x   10 qmailb   qmail        4096 Feb  6 14:32 qmail

./bin:
total 788
drwxr-xr-x    2 root     root         4096 Feb  6 14:36 .
drwxr-xr-x    5 root     root         4096 Feb  6 14:36 ..
-rwxr-xr-x    1 root     root       316848 Feb  6 13:36 bash
-rwxr-xr-x    1 root     root         6108 Feb  6 13:41 env
-rwxr-xr-x    1 root     root        12820 Feb  6 13:49 expr
-rwxr-xr-x    1 root     root        54544 Feb  6 13:49 find
-rwxr-xr-x    1 root     root        43024 Feb  6 13:35 ls
-rwxr-xr-x    1 root     root       316848 Feb  6 13:34 sh
-rwxr-xr-x    1 root     root        18032 Feb  6 13:49 wc

./lib:
total 4544
drwxr-xr-x    2 root     root         4096 Feb  6 14:38 .
drwxr-xr-x    5 root     root         4096 Feb  6 14:36 ..
-rwxr-xr-x    1 root     root       340663 Feb  6 13:30 ld-linux.so.2
-rwxr-xr-x    1 root     root      4101324 Feb  6 13:29 libc.so.6
-rwxr-xr-x    1 root     root       169720 Feb  6 13:31 libresolv.so.2
-rwxr-xr-x    1 root     root        12224 Feb  6 14:38 libtermcap.so.2

./qmail:
as usual

am i missing something ???
thx
thomas





On Tue, Feb 06, 2001 at 02:40:59PM +0000, Thomas Ackermann wrote:

> delivery 1: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/
[...]
 
> am i missing something ???

/etc/resolv.conf

Regards, Uwe




george bernath <[EMAIL PROTECTED]> wrote:
> 
> I have come across a weird problem with qmail. 

No, you haven't, actually.

> When mail is received from one particular source and
> we try and pick it up with Outlook 2000 it hangs -
> displaying for example, "receiving message 1 of 10".

It's a bug in Outlook.  In fact, it's one of many -- there are a lot of
different problems that can cause Outlook to hang.  One is if a retrieved
message has no Subject: header, which is perfectly legal.  There are many
others, so I cannot tell you which particular bug you are encountering at
this time.

Fix Outlook, and everything will work fine.

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.
-----------------------------------------------------------------------




Paco Gracia <[EMAIL PROTECTED]> wrote:
> 
> I have to send a daily newsletter to 60.000 e-mail addresses that are stored
> in a MySQL database. The newsletter is the same for everybody and the process
> of composing and sending it will be started from a PHP web app.

Sounds good so far.

> 1- Should I use mail() function from PHP, invoke qmail directly or create a
> mailing list with ezmlm?

ezmlm is a particularly nice way to go, because of its completely automatic
bounce handling.

If you don't want to do that, write a little script to pull the recipients
out of the database and inject using /var/qmail/bin/qmail-queue.  You'll 
need to read the man page for qmail-queue to figure out how it wants to
be called.

> 2- If I don't log the sending of the newsletter will it increase the speed or
> just free CPU?

This won't buy you a lot, providing your qmail installation is logging with
multilog.  And not logging the sending of 60,000 messages is not a bright
thing to do for a mail administrator.

> 3- What side effects have to set concurrencyremote to high values like 300?

Your fd limits will need to be set high.

> 4- Is it necessary to use a higher value in tcpserver's -c option if I use
> mail() function?

tcpserver doesn't affect outgoing mail at all.

> 5- Could I set up a second qmail instalation for just sending the newsletter
> so it doesn't slow the "normal users" mail?

Yes, you could.  It will still have some effect, though, because they will
be sharing I/O bandwidth on the queue and log disks, and on the network.

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 anyone give me a idea why I am getting this message.  I can send mail
to my personal account fine
anytime I try to send to another user on the system I get this error.
 delivery 9: deferral: Unable_to_chdir_to_maildir._(#4.2.1)/
I ran the maildirmake on the user.. the maildir is there and has the proper
ownership.
But no matter what I try I get the same error....
Suggestions????? Please




Dale Herring <[EMAIL PROTECTED]> wrote:
> Can anyone give me a idea why I am getting this message.  I can send mail to
> my personal account fine anytime I try to send to another user on the system
> I get this error.
>      delivery 9: deferral: Unable_to_chdir_to_maildir._(#4.2.1)/
> I ran the maildirmake on the user.. the maildir is there and has the proper
> ownership.

Well, something isn't right.  Post the output of `qmail-showctl`, along with
the output of the following for the user that doesn't work:

    `ls -ld ~USER ~USER/Maildir ~USER/Maildir/*`

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.
-----------------------------------------------------------------------




Have installed amavis with the fsav anti virus engine...works great. But
would like to install this on a server with alot of virtual domains, and
what im looking for is the possibility to specify which of the domains i
want to scan for. ( Due to the heavy load of scanning all of them, and
because we are going to give this as a service for those who want it, and
some dont)

But i find this very difficult since amavis replaces the qmail-local and
qmail-remote.. no option with other words. Have heard that some people have
made this work in some way.

Can anyone point me in the right direction?

Regards
Tore





On Tue, Feb 06, 2001 at 03:59:29PM +0100, Tore Micaelsen wrote:
> Can anyone point me in the right direction?

This should be easy to add to qmail-scanner... (perl)
It's even planed AFAIK.

Olivier
-- 
_________________________________________________________________
 Olivier Mueller - [EMAIL PROTECTED] - PGPkeyID: 0E84D2EA - Switzerland
qmail projects: http://omail.omnis.ch  -  http://webmail.omnis.ch

PGP signature





On Thu, 1 Feb 2001, Faried Nawaz wrote:

> With QMTP, you get
>
> C: <message and sender and recipients sent before the server says anything,
>     tying up the connection for 30 seconds and wasting bandwidth>
> S: 7:Dgo away,

This also wastes the Spammer's time and bandwidth.

- Sam





On Tue, 6 Feb 2001, Sam Trenholme wrote:

> On Thu, 1 Feb 2001, Faried Nawaz wrote:
> 
> > With QMTP, you get
> >
> > C: <message and sender and recipients sent before the server says anything,
> >     tying up the connection for 30 seconds and wasting bandwidth>
> > S: 7:Dgo away,
> 
> This also wastes the Spammer's time and bandwidth.

If you really want to make spammers waste their time and bandwidth (and
you have got bandwidth to waste yourself), you should pretend to accept
their junk and discard it. And of course, you should also fool their scans
testing whether the mail server acts as an open relay or not by sending a
real short message (making the difference between early and late refusal
irrelevant from their pov).

--Pavel Kankovsky aka Peak  [ Boycott Microsoft--http://www.vcnet.com/bms ]
"Resistance is futile. Open your source code and prepare for assimilation."





Hi,
My qmail host is:
mail.ndsoftware.net

When i send a message to [EMAIL PROTECTED] from
[EMAIL PROTECTED], i received this message by 2 !!!
Why ?

Header:
Message1:
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 862 invoked by uid 503); 6 Feb 2001 16:04:01 -0000
Received: from unknown (HELO billy) (193.253.221.190)
  by ns207.ovh.net with SMTP; 6 Feb 2001 16:04:01 -0000
From: "NDSoftware" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject:
Date: Tue, 6 Feb 2001 17:00:08 +0100
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal

Message2:
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 862 invoked by uid 503); 6 Feb 2001 16:04:01 -0000
Received: from unknown (HELO billy) (193.253.221.190)
  by ns207.ovh.net with SMTP; 6 Feb 2001 16:04:01 -0000
From: "NDSoftware" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject:
Date: Tue, 6 Feb 2001 17:00:08 +0100
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal

Logs:
@400000003a80207c0dbbdc8c new msg 196348
@400000003a80207c0dbbf7e4 info msg 196348: bytes 931 from
<[EMAIL PROTECTED]> qp 862 uid 503
@400000003a80207c0ddcbe84 starting delivery 2929: msg 196348 to local
[EMAIL PROTECTED]
@400000003a80207c0ddcd9dc status: local 1/10 remote 0/20
@400000003a80207c14e3407c delivery 2929: success: did_0+0+1/
@400000003a80207c14e357ec status: local 0/10 remote 0/20
@400000003a80207c14e35fbc end msg 196348

THANKS YOU VERY MUCH

Nicolas DEFFAYET, NDSoftware
http://www.ndsoftware.net - [EMAIL PROTECTED]
France: Tel +33 671887502 - Fax N/A
UK: Tel +44 8453348750 - Fax +44 8453348751
USA: Tel N/A - Fax N/A
---
Note: All HTML email sent to me can be deleted for security reasons.





Hey there guys!

    I have a quick question about this one line in my logs, that shows up
for every message:

    to local [EMAIL PROTECTED]

    I think I know what msglog does, but where do I turn it off?  I have
looked in my /etc/qmail/alias/.qmail-msglog file, however this is the
out-put:


# This alias control file is processed on EVERY SINGLE message.
# ***THINK*** before you do this as it can put extra load on your system.
#
# Several things can be done here:
# 1. Record EVERY single message in a mailbox file.
#    *** ARE YOU SURE YOU ***REALLY*** WANT TO RECORD EVERY SINGLE
MESSAGE!!!???
#    EXAMPLE:
#./msglog
#
# 2. Record Message-IDs for later tracking.
#    EXAMPLE:
#| awk '/^$/ { exit } /^[mM][eE][sS][sS][aA][gG][eE]-/ { print }'

     If you notice, it is all commented out.  I thought that the msglog item
would not even show in the logs, unless this file was in use?  I guess I was
wrong.

@400000003a7d220f060782ac info msg 299012: bytes 85402 from
<[EMAIL PROTECTED]> qp 3181 uid 891
@400000003a7d220f11944c2c starting delivery 31: msg 299012 to local
[EMAIL PROTECTED]
@400000003a7d220f119c721c status: local 1/10 remote 0/20
@400000003a7d220f11b0adcc starting delivery 32: msg 299012 to remote
[EMAIL PROTECTED]
@400000003a7d220f11b8c41c status: local 1/10 remote 1/20
@400000003a7d220f18db78d4 delivery 31: success: did_0+0+0/
@400000003a7d220f1a729f4c status: local 0/10 remote 1/20
@400000003a7d224c2e23d22c delivery 32: success:
209.226.175.26_accepted_message./Remote_host_said:_250_Message_re
ceived:[EMAIL PROTECTED]/





g0thic <[EMAIL PROTECTED]> wrote:
> 
>     I have a quick question about this one line in my logs, that shows up
> for every message:
> 
>     to local [EMAIL PROTECTED]

This was asked on the mailing list within the last three days.  Look in the
archives (you can find a link to searchable archives from www.qmail.org).

In short, this is a feature of Bruce Guenter's SRPM.  If you don't like
the extra (null) delivery by default, you'll need to modify the SPEC file
and rebuild the binary RPM, then reinstall from that.

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 have get qmail-smtpd-auth-0.26.tar.gz.
 "tar xvfz qmail-smtpd-auth-0.26.tar.gz"
Then I get qmail-smtpd.patch 
Now I do not know how to use is.
Please tell me how to do it. Thanks.
----------------------------------------------
��ӭʹ�� 21CN �����ʼ�ϵͳ http://www.21cn.com
Thank you for using 21cn.com Email system





[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I have get qmail-smtpd-auth-0.26.tar.gz.
>  "tar xvfz qmail-smtpd-auth-0.26.tar.gz"
> Then I get qmail-smtpd.patch 
> Now I do not know how to use is.
> Please tell me how to do it. Thanks.

Read `man patch` (and probably `man diff`).  If you're not familiar with how
to apply patches to software source code, you may not want to use modifications
which change qmail's behaviour.  It may make it more difficult to diagnose
problems from the existing documentation.

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.
-----------------------------------------------------------------------




Someone had asked for this some time ago... But I forget who or when.

DJB, if you would, please archive locally to www.qmail.org.

--Larry

checkpassword.pl





On Tue, Feb 06, 2001 at 12:17:44PM -0600, Larry M. Smith is the BPFH wrote:
> Someone had asked for this some time ago... But I forget who or when.
> 
> DJB, if you would, please archive locally to www.qmail.org.

That would be [EMAIL PROTECTED], aka Russ Nelson, but I'm sure he'll
see the message.


Regards.




On Tue, Feb 06, 2001 at 01:26:31PM +0800, Ng Hak Beng wrote:
> Has any encountered this problem?  I've noticed some Microsoft MUA users 
> send attachments with the mime-type ms-tnef.  When I receive the file via 
> my qmail setup, it is unable to convert the attachment accordingly, and I 
> end up with a file in the form like message.dat
> 
> I have some tools to convert it, but I'm looking for more of an 'automated' 
> solution, meaning for it to be converted as qmail receives it.  It seems to 
> be a MS problem, and I don't seem to find a patch or whatever to fix
> 

This has nothing to do with Qmail or any other SMTP server. This is yet
another cr*p M$ "feature".

I have had people here sending Emails with Outlook Professional to Outlook
Express users - and the latter complaining about "corrupt" messages and
those weird message.dat attachments. 

Even M$ products don't talk to each other...


-- 
Cheers

Jason Haar

Unix/Special Projects, Trimble NZ
Phone: +64 3 9635 377 Fax: +64 3 9635 417




Ok,

I'm happy to report I found a solution to the note I sent out last week.

The problem was not that the file in mess was not going away quick enough,
but that the file was not being created quick enough;-)  That is, the
file in mess grows as the data comes off the net and the message is built.

But - if the email is large enough, and the rate of data transfer is slow
enough, the file appears to be sitting there for a while.  In our case,
the message was of large size, and was being delivered to our server from
a client over a slow/dialup link...  In all cases, when the transfer was
complete, the message was delivered quickly enough and without error.

I had failed to note the size changes in earlier checks, and had never
timed the log entry of delivery to the file growth/ereaseure.

steve
--
Steven Tylock <[EMAIL PROTECTED]>
Questra Corporation, (716) 381-0260 x521

-----

Steve Tylock wrote:
> 
> I'm looking for info and have an offer to make - We have Netsaint running
> here to monitor servers / services (plug - http://www.netsaint.org/) and
> we wrote a very small plugin to check the queue of mail messages sitting
> on the servers.
> 
> I would be happy to provide this to anyone looking to do a similar thing.
> 
> The problem - 'phantom' qmail-qstat responses.
> 
> The qmail archives have a few messages about determining how many messages
> are in the queue from back a ways, but I didn't find any touching on this:
> 
> qmail-qstat looks at 'messages in queue' by looking for files in the
> directories queue/mess/*.
> 
> But - we seem to have a condition (relatively infrequently, but often
> enough to cause a stir) - where a file is left in this directory <after>
> the message has been delivered. (log confirms delivery, no error)
> 
> That is, every other file with the same name from that message is gone,
> but the mess file remains for some period of time.  0-60 minutes later,
> the file is removed.
> 
> The best I have been able to guess is that some program is holding onto
> an inode, the file is really left there and cleaned up later when it is
> used again, or we have some local bug.
> 
> Other info - qmail 1.0.3, Linux 2.2.18, MDA is procmail.
> (I'd offer more direct info, but it isn't happening right now...-)
> [I started this message in January and waited - I'm attaching an 'ls -lr'
> on the queue directory showing 2 left over files in 'mess']
> 
> I could work around this by changing the way we look for messages in the
> queue, or fix this.  (and am somewhat thinking I'll see a response -
> "your site gets to an empty queue!-)"  ((Note - we use the inside the
> firewall queue & outside the firewall queue - the inside server should
> always get back to a nothing in the queue state.  It delivers locally
> or gives the messages to the other server to deliver))
> 
> any help or advice appreciated,
> steve
> --
> Steven Tylock <[EMAIL PROTECTED]>
> Questra Corporation, (716) 381-0260 x521




our new qmail install is started simply by

exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start ./Maildir splogger qmail&

however I've noticed a lot of people using daemontools and supervise.

What are the primary advantages of using supervise?

Our mail server probably handles less than 2000 messges a day is it
something I really need to do?

Is there a good document that points to how to correctly configure supervise
to start/run/manage qmail?

Thanks for your help.

Peter Brezny
SysAdmin Services Inc.





> What are the primary advantages of using supervise?

If qmail (or any supervised process) abnormally dies, supervise will
automatically start it back up.

> Our mail server probably handles less than 2000 messges a day is it
> something I really need to do?

Can't hurt.

> Is there a good document that points to how to correctly configure
supervise
> to start/run/manage qmail?

http://www.lifewithqmail.org

---Kris Kelley





On Tue, Feb 06, 2001 at 05:16:36PM -0500, Peter Brezny wrote:
> our new qmail install is started simply by
> 
> exec env - PATH="/var/qmail/bin:$PATH" \
> qmail-start ./Maildir splogger qmail&
> 
> however I've noticed a lot of people using daemontools and supervise.
> 
> What are the primary advantages of using supervise?

My personal thoughts:

1. multilog. multilog uses a lot less overhead than syslog, and does
not listen on the network, and so is not vulnerable to remote DoS or
exploit. It's self-rotating (configurable), and uses a super-accurate
timestamp (although the timestamp is not _that_ relevant to me
personally). 

2. Unification with other djb-ware, especially djbdns. Personally, I'd
just love it if sshd could log to STDOUT, and that way most of my hosts
would use supervise for _all_ the important processes. ;)

3. Simple process control. Downing all supervised processes is as simple
as 'svc -d /service/*/log ; svc -d /service/*'. Gotta like that.

> 
> Our mail server probably handles less than 2000 messges a day is it
> something I really need to do?


Need? No. But well worth it IMHO.

> 
> Is there a good document that points to how to correctly configure supervise
> to start/run/manage qmail?

http://www.lifewithqmail.org/

Just snag and modify the /var/qmail/supervise directory structure and
'run' scripts.
> 
> Thanks for your help.

You're welcome. ;)

> 
> Peter Brezny
> SysAdmin Services Inc.
> 

-- 
Greg White
Those who make peaceful revolution impossible will make violent
revolution inevitable.
                -- John F. Kennedy




"Peter Brezny" <[EMAIL PROTECTED]> writes:
> What are the primary advantages of using supervise?

Among those already mentioned: reliability.  You *can't* reliably
manage a service without cooperation from the parent process or the
process itself.  Putting the management functionality into the process
itself results in unnecessary duplication; putting it in the parent
results in supervise.

An example of the kind of unreliability you get without supervise:
suppose you want to send a service a signal.  How do you find the pid?
ps?  Command names are not a perfect indicator; multiple instances
complicate the problem.  A pid file?  It might be out of date: the
process might have died since the pid file was written, and the pid
might have been reused.  But a parent can always keep track of its
children; supervise never sends signals to the wrong process.


paul




Michael,

Haven't yet seen a response, so I'll write one. :)

You can do this fairly easily by setting up the following:

virtualdomains:
corp.rocketcash.com:alias-corp_rocketcash_com/

Then, you'll need to 'mkdir ~alias/.qmail-corp_rocketcash_com'

Inside that directory, you'll want to create a file called '-default'
(this can be tricky, as most programs see - as a switch delimiter. You
will probably need to specify the file as ./-default while in that
directory.) Inside this file, place the line:

|forward ${DEFAULT}@corp.netzero.net

The above file acts as a .qmail-default for that domain, forwarding
anything not already specified to the same [EMAIL PROTECTED]

You can now create specific user files in the same directory to override
this behaviour.

Say you wanted [EMAIL PROTECTED] to forward to
[EMAIL PROTECTED] You would create a file called -jamin in the
~alias/.qmail-corp_rocketcash_com directory, and inside it place:

&jbrown@@corp.netzero.net

Hope this makes sense to you.

Jamin

On Mon, 5 Feb 2001, Michael Boyiazis wrote:

> I have a situation which leaves me (I think) caught between
> virtualdomain and smtproute files...
>
> We have qmail running on a firewall box and forwarding
> to the corporate exchange server...
>
> We have users from one domain:
> aimtv.com which we use smtproutes to forward directly
> to a virus scan box...  all the email addresses in the aimtv
> domain match those found on the forwarding domain, so
> smtproutes is appropriate.
>
> I'd like all our domains to be that way, but each domain that
> the virus scan box checks needs extra licensing ($$)...
>
> so, we have another domain,   corp.rocketcash.com...
> some email addresses are [EMAIL PROTECTED]
>
> the mail comes in and I use a .qmail file to forward these to
> [EMAIL PROTECTED]
>
> future new addresses will be along the line of
> [EMAIL PROTECTED] which will forward
> to the equivalent on corp.netzero.net....
>
> is there a way to catch all those future addresses and forward them to
> @corp.netzero.net w/o using smtproutes and without creating a separate
> .qmail for each new employee?  would a catchall .qmail
> file be able to do that?  i don't see how.  it makes sense to use smtproutes
> but i cannot from what i can see.
>
> any suggestions?
>
> Thanks,
> --
> Michael Boyiazis
> [EMAIL PROTECTED]
> Mail Architect, NetZero, Inc.
>
>


-----------------------------------------------------------------
Jamin A. Brown                      Systems Operations Department
[EMAIL PROTECTED]   * Great Works Internet *   207.286.8686 x142
RSA PGP Key:              http://www.gwi.net/~jamin/pgp/jamin.asc





Hey all

I have a queuing question for everyone.  We have our server set to relay if
the message comes from a user with an IP address in our list of acceptable
IP addresses.  We have the tcp.smtp database set up correctly as far as we
can see, but yet, when we start up qmail, it just queues up mail.  It
doesn't reject any mail, it just stores it up in the queue, and doesn't
deliver it.  Any ideas as to what we may have set up incorrectly?

Thanks

Brendan





Hi all,
        I am running qmail-1.03+patches-12 on a RH6.2 system and have suddenly 
began to have a problem with the qmailadmin page.  I can't seem to login as 
postmaster to either of the domains I administer.  I am using the same 
password that I use with postmaster to check the mail which works 
fine.  The error I keep getting is "Invalid Login." I was also wondering if 
there was a log file that I could look at that would tell me what the 
reason is that I keep getting this error.
        Thanks in advance,
                David Litke





According to Dave Sill:
> 
> "Alex V. Toropov" <[EMAIL PROTECTED]> wrote:
> 
> >May be this should be reported as "BUG" in qmail ?
> >Or it's a bug somewhere else (I mean the author of <arpa/nameser.h>) ?
> 
> See:
> 
>   http://Web.InfoAve.Net/~dsill/lwq.html#dns-problem
> 
> for a discussion of this issue and the workarounds.
> 
> -Dave

Thought I would pass this along since I didn't see this issue
addressed in any of the existing archives/docs/lwq/etc...

For everyones benefit, having spent the better part of a day
trying to find out why my QMAIL installation was not working, only
reporting the dreaded "CNAME_lookup_failed_temporarily._(#4.4.3)"
error, turns out the 'real' problem was permissions on /etc/resolv.conf
was too restrictive:

    # ls -l /etc/resolv.conf 
    -r--r-----   1 root     other          93 Feb  6 15:40 /etc/resolv.conf

Changing that to a world readable file caused the errors to go away.
Note: all other SOLARIS tools (ping, nslookup, sendmail, telnet, ftp, etc...)
worked fine..

Environment: Solaris 8 on a SPARC

--curtis




On Tue, 6 Feb 2001, Curtis Generous wrote:

>     # ls -l /etc/resolv.conf 
>     -r--r-----   1 root     other          93 Feb  6 15:40 /etc/resolv.conf

IMHO, this is a pretty bizzare kind of misconfiguration.

> Changing that to a world readable file caused the errors to go away.
> Note: all other SOLARIS tools (ping, nslookup, sendmail, telnet, ftp, etc...)
> worked fine..

They did not resolve names themselves. They asked nscd to do it. Running
under root, nscd did not have any problem with world unreadable
resolv.conf.

--Pavel Kankovsky aka Peak  [ Boycott Microsoft--http://www.vcnet.com/bms ]
"Resistance is futile. Open your source code and prepare for assimilation."





hi,

i've tryed to installed qmail 1.03
according "Life with qmail"
http://www.lifewithqmail.org/lwq.html
instructions on FreeBSD4.0, but
script

/var/qmail/supervise/qmail-smtpd/run
reporting errors:

bash-2.03# /var/qmail/supervise/qmail-smtpd/run
softlimit: usage: softlimit [-a allbytes] [-c corebytes] [-d databytes] [-f filebytes] 
[-l lockbytes] 
[-m membytes] [-o openfiles] [-p processes] [-r residentbytes] [-s stackbytes] [-t 
cpusecs] 
child
bash-2.03# 

script /var/qmail/supervise/qmail-send/run
reoprts:

bash-2.03# /var/qmail/supervise/qmail-send/run
env: illegal option -- P
usage: env [-] [-i] [name=value ...] [command]

scripts:

------------------------------
/var/qmail/supervise/qmail-smtpd/run script
------------------------------

#!/bin/sh

QMAILDUID=`id -u qmaild`

NOFILESGID=`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 2>&1

------------------------------------
/var/qmail/supervise/qmail-send/run script
-----------------------------------
#!/bin/sh

exec /var/qmail/rc
---------------------

Could it be incompatibility with FreeBSD?
Or my system misconfiguration?
thank you in advance,

t_oo

Stating the Obvious.  All meta, all the time.  <http://www.theobvious.com/>
____________________________________________________________
Get your own FREE Web and POP E-mail Service in 14 languages at http://www.zzn.com.




Perhaps I have my DNS settings botched, but lately I have noticed a delay in 
qmail's response when sending mail from my LAN. If I telnet to it, it can 
take up to 30 seconds or longer before I get the greeting. Once I do get the 
greeting, or make the connection, subsequent responses are perfectly fine. It 
seems that only after a period of inactivity will this happen. I don't think 
this problem is present for others sending mail in from the Internet. My LAN 
IP's are not stored in any DNS server that qmail knows of, but they are on 
/etc/hosts.

Any ideas?




Hi Michael. I posted this message a couple of days ago.
There is also a very good article that talks about using "split DNS" for
your internal network, which would help your linux box resolve the incoming
clients.
You can find it at http://www.linuxgazette.com/issue45/tag/11.html
I really recommend it.
Good luck.

Mario Campos

<<<<<<<<<<<<
Hi. I was having the same problem on my linux system and the -R option
didn't seem to help. What fixed it was adding the -l localhostname argument
which helps qmail resolve the local host name which I think is what's taking
the longest. Actually, when it was happening on my system, it would take
about 2 minutes to send an email, but then it would work fine for 10 minutes
because the hostname resolution was cached. After 10 minutes, it would go
back to the same issue.

-----Original Message-----
From: Uwe Ohse [mailto:[EMAIL PROTECTED]]
Sent: Sunday, February 04, 2001 11:47 PM
To: Jagadish.N
Cc: cr.yp.to log list; [EMAIL PROTECTED]
Subject: Re: Delay in POP and SMTP response


On Mon, Feb 05, 2001 at 12:13:45PM +0530, Jagadish.N wrote:

>I even telneted to 110 and 25 specifing
>the mail server's ip address but it takes quite a long time to respond.

try starting tcpserver with the -R option.

Regards, Uwe

-----Original Message-----
From: Michael Owens [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 4:35 PM
To: [EMAIL PROTECTED]
Subject: Slow response time


Perhaps I have my DNS settings botched, but lately I have noticed a delay in

qmail's response when sending mail from my LAN. If I telnet to it, it can 
take up to 30 seconds or longer before I get the greeting. Once I do get the

greeting, or make the connection, subsequent responses are perfectly fine.
It 
seems that only after a period of inactivity will this happen. I don't think

this problem is present for others sending mail in from the Internet. My LAN

IP's are not stored in any DNS server that qmail knows of, but they are on 
/etc/hosts.

Any ideas?





Joinhands Hosting Agreement for the 2001 yearI am having a problem with mail
from other servers not being delivered to my server.  I can use qmail-inject
to send mail to my users and I can send mail from an account on the same
server, I just can't get mail from a another host.

any ideas? Clean Redhat 7.0 install with all the latest qmail and vpopmail.
I have followed the instructions to the letter 4 times and I can't seem to
figure out what is wrong.

The physical hostname is ws1.joinhands.com ( I am taking over hosting of
this site and testing with one of my own domains innsandcottages.com)

Here are my script files that are starting the server and list of the
processes.

Thanks in advance

cat rc
#!/bin/sh

# Using stdout for logging
# Using control/defaultdelivery from qmail-local to deliver messages by
default

# These following are the defaults from LWQ mail - doesn't work with
vpopmail

[ross@ws1 qmail]$ cat rc
exec env - PATH="/var/qmail/bin:$PATH" \
qmail-start .Mailbox

**** I am running the rc.pop3d manually right now
[ross@ws1 qmail]$ cat rc.pop3d
#!/bin/sh
exec env - PATH="/var/qmail/bin:/usr/local/bin" \
tcpserver -H -R 0 pop-3 \
/var/qmail/bin/qmail-popup mail.innsandcottages.com \
/home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir &

[ross@ws1 control]$ cat locals
mail.innsandcottages.com

[ross@ws1 control]$ cat plusdomain
joinhands.com
innsandcottages.com

[ross@ws1 control]$ cat virtualdomains
innsandcottages.com:innsandcottages.com

[ross@ws1 control]$ cat defaultdomain
innsandcottages.com

[ross@ws1 control]$ cat me
mail.innsandcottages.com

[ross@ws1 supervise]$ cat qmail-send/run
#!/bin/sh
exec /var/qmail/rc

[ross@ws1 supervise]$ cat qmail-smtpd/run
#!/bin/sh
QMAILDUID='id -u qmaild'
NOFILESGID='id -g qmaild'
MAXSMTPD='cat /var/qmail/control/concurrencyincoming'
#this is the out of the box way from lwq
#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
2>&1

# this is the way that works with vpopmail
# smtp services
env - PATH="/var/qmail/bin:/usr/local/bin" \
tcpserver -v -p -u vpopmail -g vchkpw 0 smtp /var/qmail/bin/qmail-smtpd 2>&1

[ross@ws1 supervise]$ cat /home/vpopmail/etc/tcp.smtp
127.:allow,RELAYCLIENT=""
207.194.2.103:allow,RELAYCLIENT=""
:allow
[ross@ws1 supervise]$

UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 09:49 ?        00:01:36 init [3]
root         2     1  0 09:49 ?        00:00:00 [kflushd]
root         3     1  0 09:49 ?        00:00:00 [kupdate]
root         4     1  0 09:49 ?        00:00:00 [kpiod]
root         5     1  0 09:49 ?        00:00:00 [kswapd]
root         6     1  0 09:50 ?        00:00:00 [mdrecoveryd]
root       329     1  0 09:51 ?        00:00:00 syslogd -m 0
root       339     1  0 09:51 ?        00:00:00 klogd
rpc        354     1  0 09:51 ?        00:00:00 portmap
root       369     1  0 09:51 ?        00:00:00 /usr/sbin/apmd -p 10 -w
5 -W -P
nobody     423     1  0 09:51 ?        00:00:00 identd -e -o
nobody     427   423  0 09:51 ?        00:00:00 identd -e -o
nobody     428   427  0 09:51 ?        00:00:00 identd -e -o
nobody     429   427  0 09:51 ?        00:00:00 identd -e -o
nobody     430   427  0 09:51 ?        00:00:00 identd -e -o
daemon     442     1  0 09:51 ?        00:00:00 /usr/sbin/atd
root       473     1  0 09:51 ?        00:00:00 xinetd -reuse -pidfile
/var/run/
root       488     1  0 09:51 ?        00:00:00 /usr/sbin/sshd
root       545     1  0 09:51 ?        00:00:00 gpm -t ps/2
root       684     1  0 09:51 ?        00:00:00 /usr/sbin/httpd -D
HAVE_PERL -D
apache     694   684  0 09:51 ?        00:00:00 /usr/sbin/httpd -D
HAVE_PERL -D
apache     695   684  0 09:51 ?        00:00:00 /usr/sbin/httpd -D
HAVE_PERL -D
apache     696   684  0 09:51 ?        00:00:00 /usr/sbin/httpd -D
HAVE_PERL -D
apache     697   684  0 09:51 ?        00:00:00 /usr/sbin/httpd -D
HAVE_PERL -D
apache     698   684  0 09:51 ?        00:00:00 /usr/sbin/httpd -D
HAVE_PERL -D
apache     699   684  0 09:51 ?        00:00:00 /usr/sbin/httpd -D
HAVE_PERL -D
apache     700   684  0 09:51 ?        00:00:00 /usr/sbin/httpd -D
HAVE_PERL -D
apache     701   684  0 09:51 ?        00:00:00 /usr/sbin/httpd -D
HAVE_PERL -D
nobody     710     1  0 09:51 ?        00:00:00 proftpd (accepting
connections)
root       725     1  0 09:51 ?        00:00:00 crond
root       755     1  0 09:51 ?        00:00:00 rhnsd --interval 120
root       778     1  0 09:51 ?        00:00:00 sh
/usr/local/mysql/bin/safe_mys
root       781     1  0 09:51 tty1     00:00:00 /sbin/mingetty tty1
root       782     1  0 09:51 tty2     00:00:00 /sbin/mingetty tty2
root       783     1  0 09:51 tty3     00:00:00 /sbin/mingetty tty3
root       784     1  0 09:51 tty4     00:00:00 /sbin/mingetty tty4
root       785     1  0 09:51 tty5     00:00:00 /sbin/mingetty tty5
root       786     1  0 09:51 tty6     00:00:00 /sbin/mingetty tty6
root       806   778  0 09:51 ?        00:00:00
/usr/local/mysql/libexec/mysqld
root       808   806  0 09:51 ?        00:00:00
/usr/local/mysql/libexec/mysqld
root       809   808  0 09:51 ?        00:00:00
/usr/local/mysql/libexec/mysqld
root     16532     1  0 15:03 ?        00:00:00 svscan
root     16533 16532  0 15:03 ?        00:00:00 supervise qmail-send
root     16534 16532  0 15:03 ?        00:00:00 supervise log
root     16535 16532  0 15:03 ?        00:00:00 supervise qmail-smtpd
root     16536 16532  0 15:03 ?        00:00:00 supervise log
qmails   16537 16533  0 15:03 ?        00:00:00 qmail-send
qmaill   16538 16534  0 15:03 ?        00:00:00 /usr/local/bin/multilog t
/var/l
qmaill   16539 16536  0 15:03 ?        00:00:00 /usr/local/bin/multilog t
/var/l
root     16541 16537  0 15:03 ?        00:00:00 qmail-lspawn .Mailbox
qmailr   16542 16537  0 15:03 ?        00:00:00 qmail-rspawn
qmailq   16543 16537  0 15:03 ?        00:00:00 qmail-clean
root     16753 16535  0 15:58 ?        00:00:00 sh ./run
root     16754 16753  0 15:58 ?        00:00:00 tcpserver -v -p -u
vpopmail -g v
ross     16811 16810  0 16:30 pts/1    00:00:00 -bash
ross     16845 16811  0 16:37 pts/1    00:00:00 ps -ef






On Tue, Feb 06, 2001 at 04:32:04PM -0800, Ross Davis - Data Anywhere wrote:
> Joinhands Hosting Agreement for the 2001 yearI am having a problem with mail
> from other servers not being delivered to my server.  I can use qmail-inject
> to send mail to my users and I can send mail from an account on the same
> server, I just can't get mail from a another host.
> 
> any ideas? Clean Redhat 7.0 install with all the latest qmail and vpopmail.
> I have followed the instructions to the letter 4 times and I can't seem to
> figure out what is wrong.
> 
> The physical hostname is ws1.joinhands.com ( I am taking over hosting of
> this site and testing with one of my own domains innsandcottages.com)

You've got a couple of problems. One is that innsandcottages.com has a CNAME
record pointing at dns1.innsandcottages.com. If you do that, unexpected things
will happen. Give it an A record or, preferably, an MX record.

Second is that dns1.innsandcottages.com resolves to 207.194.2.101, which isn't
the same address that ws1.joinhands.com resolves to (207.194.2.103). There's
nothing listening on the SMTP port of 207.194.2.101, though there is on
207.194.2.103.

Fix your DNS, wait for the old records to time out, and then you should be in
good shape.

Thanks for providing real domain names. It makes it a lot easier (and in this
case possible) to answer questions.

Chris




Well, usually the log files will tell you what's going on... what do
they say?


> any ideas? Clean Redhat 7.0 install with all the latest qmail and vpopmail.
> I have followed the instructions to the letter 4 times and I can't seem to

> cat rc
> #!/bin/sh
> 
> # Using stdout for logging
> # Using control/defaultdelivery from qmail-local to deliver messages by
> default
> 
> # These following are the defaults from LWQ mail - doesn't work with
> vpopmail
> 
> [ross@ws1 qmail]$ cat rc
> exec env - PATH="/var/qmail/bin:$PATH" \
> qmail-start .Mailbox

Default delivery is to .Mailbox? Is that what the instructions really
say? Are you over-riding this with per-user .qmail files? If not, you
have a mismatch between your delivery type and the pop server as:


> exec env - PATH="/var/qmail/bin:/usr/local/bin" \
> tcpserver -H -R 0 pop-3 \
> /var/qmail/bin/qmail-popup mail.innsandcottages.com \
> /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir &

The qmail pop server only reads Maildirs - it knows nothing about
.Mailbox

You may find that your logs are showing delivery, but you're maybe
expecting the mail to be delivered into a Maildir and it's not?


Regards.





----- Original Message ----- 
From: Uwe Ohse <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 06, 2001 4:53 PM
Subject: Re: anybody can't help me insert some text in the end of every message my 
mailserver relay for?


> On Tue, Feb 06, 2001 at 01:35:52PM +0800, dick wrote:
> 
> > Subject: anybody can't help me insert some text in the end of every message my 
>mailserver relay for?
> 
> This is possibly an evil idea, but anyway:
> Either patch qmail-queue.c or qmail-smtpd.c (depending on what you want
> to achieve). In the later case try adding something like this to the
> end of blast():
> { 
> char corrupted[]="This message has been changed on";
> qmail_put(&qqt,corrupted,sizeof(corrupted)-1);
> qmail_put(&qqt,greeting.s,greeting.len);
> qmail_put(&qqt,"\n",1);
> }
> 
> Regards, Uwe
>
i add these codes in the end of qmail-smtpd.c.but it won't work.
can't you tell me how can i do it!
(by the way, i don't know how to patch the qmail-queue.c or qmail-smtpd.c.only add 
these code into blast?)
 




Ok,  about 2 months ago i switched IP address on a computer running 
qmail.  Since that time the server has had problems with SMTP being 
sluggish.  To this point i have changed the /etc/resolve.conf and the 
DNS to the correct settings.  When trying to connect to the remote 
box via the telnet command to port 25 it connects within seconds but, 
the banner does not appear for a good 40 seconds.  This has lead to 
problems with outlook timing out when sending messages.  When trying 
to rebuild qmail, ./config reports errors about not being able to 
find the canonical name in DNS.   But it does resolve from all boxes 
including localy.  I have also tryed to use the -F option, but this 
does not seem to be making the problem go away.  Is this a problem 
with BIND or with Qmail or a combination of both?  I have been trying 
to figure this problem out for some time on my own with no luck.  If 
you wish, i can provide more information on the box if needed.  


Tim






Hi, 

I setup once a qmail box and forgot to set the sticky bit (chmod +t) on the 
qmail-send and qmail-smtpd directories (in /var/qmail/supervise) so 
supervise was outputing everything to console.
I actually liked that very much (if server is physically restricted) but 
there is one draw back; nothing will be logged to log/current.
Therefore, I wandered if there is a way to have supervise log to both 
console and to qmail-send/log and/or qmail-smtpd/log. 

Any ideas?
Tim Hassan 




Someone knows why I get fatal: data 451 qq write error or disk full
(#4.3.0) ?
It comes after different Message Counts when sending via SMTP.
I think there is an Error in that qmail-smtpd. Any Solutions ?
Never seen that on Linux btw.
--
Michael..






On 07-Feb-2001 Michael Maier wrote:
>  Someone knows why I get fatal: data 451 qq write error or disk full
>  (#4.3.0) ?
>  It comes after different Message Counts when sending via SMTP.
>  I think there is an Error in that qmail-smtpd. Any Solutions ?
>  Never seen that on Linux btw.

Are you using quotas on Solaris?

Stefaan
-- 
How's it supposed to get the respect of management if you've got just
one guy working on the project?  It's much more impressive to have a
battery of programmers slaving away. -- Jeffrey Hobbs (comp.lang.tcl)


Reply via email to