qmail Digest 4 Feb 2000 11:00:00 -0000 Issue 901
Topics (messages 36662 through 36750):
SPAMCONTROL101 Patch
36662 by: Erwin Hoffmann
Error on startup
36663 by: Andreas Altenburg
36682 by: Dave Sill
36683 by: Chris Johnson
SPAMCONTROL patch not working?
36664 by: Erwin van Kroonenburg
36665 by: Dave Sill
36668 by: Russ Allbery
36706 by: Erwin Hoffmann
Re: multilog datestamping
36666 by: Dave Sill
36670 by: Mark Delany
36671 by: Charles Cazabon
36676 by: Bruce Guenter
Re: Error in piping message contents
36667 by: Dave Sill
Re: Linux kernel turning for mail performance?
36669 by: Len Budney
36672 by: cmikk.uswest.net
36674 by: Len Budney
36680 by: nascheme.enme.ucalgary.ca
36687 by: cmikk.uswest.net
36690 by: nascheme.enme.ucalgary.ca
36693 by: Andre Oppermann
36694 by: Len Budney
36697 by: nascheme.enme.ucalgary.ca
36705 by: cmikk.uswest.net
36707 by: Russell Nelson
Re: Bandwidth
36673 by: Marek Narkiewicz
36735 by: John White
Re: Linux Patch for fsync of metdata
36675 by: Bruce Guenter
LEAVE
36677 by: Carles Latorre
Bounce and virtualdomains
36678 by: Alessandro Ambrosini
36681 by: Dave Sill
Re: qmail logging tools
36679 by: Charles Cazabon
36696 by: Bruce Guenter
Re: complex user routing
36684 by: Dave Sill
Re: Error in sending mails
36685 by: Dave Sill
Re: delete mails in queue
36686 by: Dave Sill
Re: load balancing
36688 by: Dave Sill
Re: Broken tcp_wrappers (resulting in selective relaying not work ing)
36689 by: Dave Sill
36726 by: Stephen Mills
36727 by: Stephen Mills
36728 by: Chris Johnson
36733 by: Stephen Mills
Re: "shell-init: could not get current directory"
36691 by: Dave Sill
36695 by: Mullen, Patrick
36699 by: Dave Sill
36708 by: Mullen, Patrick
36713 by: Mullen, Patrick
36724 by: Mullen, Patrick
36725 by: John Gonzalez/netMDC admin
36729 by: Mullen, Patrick
36732 by: Matthew Brown
Re: HOw:very virtual domains - copy mail between domains
36692 by: Dave Sill
Semd multipart messages with flash embeded
36698 by: Carlo Gibertini
36700 by: Dave Sill
36701 by: Mullen, Patrick
Re: popbull
36702 by: Russell Nelson
Re: Filtering out email addresses with pipe symbol
36703 by: Russell Nelson
Re: MIME
36704 by: Russell Nelson
qmail and rblsmtpd
36709 by: kevin
36749 by: kevin
qmail-clean does not work
36710 by: DeChavez , Andrew
36711 by: Chris Johnson
36712 by: DeChavez , Andrew
36714 by: Chris Johnson
36717 by: DeChavez , Andrew
36718 by: Chris Johnson
36719 by: DeChavez , Andrew
36720 by: Racer X
36721 by: Chris Johnson
36722 by: asantos
36723 by: DeChavez , Andrew
36736 by: Russell Nelson
Re: fsync semantics (was Re: Linux kernel ....)
36715 by: cmikk.uswest.net
36737 by: Russell Nelson
36738 by: cmikk.uswest.net
36741 by: Russell Nelson
Usage "accounting" with Qmail in Real Time?
36716 by: Qmail
How do I create a Maildir directory when I am adding a user?
36730 by: Max
36731 by: Chris Johnson
36734 by: Mullen, Patrick
'goodmailfrom' ?
36739 by: Michael Boman
36740 by: Chris Johnson
/var/spool/mail delivery using a dot-qmail file
36742 by: Kristina
Databytes and users?
36743 by: TAG
36746 by: nascheme.enme.ucalgary.ca
Problem with .qmail in vpopmail
36744 by: Dian Pamilih
how do i
36745 by: Chris Burton
Re: Qmail anti-virus package?
36747 by: Erwin van Kroonenburg
Routin only some virtual-adresses
36748 by: Puck
36750 by: Petr Novotny
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]
----------------------------------------------------------------------
Hi,
for those folks, which did not consider applying this patch because of the
spelling error RECEIPIENT (I apologize for that) -- here the corrected
version.
However, NO change to the logic has been applied. Thus, those ones using it
already can happily stay with the old version.
regards
eh.
spamcontrol101.tgz
+-----------------------------------------------------------------------+
| fff hh Dr. Erwin Hoffmann |
| ff hh |
| ff eee hhhh ccc ooo mm mm mm Wiener Weg 8 |
| fff ee ee hh hh cc oo oo mmm mm mm 50858 Koeln |
| ff ee eee hh hh cc oo oo mm mm mm |
| ff eee hh hh cc oo oo mm mm mm Tel 0221 484 4923 |
| ff eeee hh hh ccc ooo mm mm mm Fax 0221 484 4924 |
+-----------------------------------------------------------------------+
my
script:
env -
PATH="/var/qmail/bin:/usr/local/bin" \
tcpserver 0 pop-3
/var/qmail/bin/qmail-popup orbital.inter7.com \
/home/vpopmail/bin/vchkpw
/var/qmail/bin/qmail-pop3d Maildir
The paths are o.k.,
but I get the error "Maildir command not found" during start-up.
Why??
"Andreas Altenburg" <[EMAIL PROTECTED]> wrote:
>my script:
>
>env - PATH="/var/qmail/bin:/usr/local/bin" \
> tcpserver 0 pop-3 /var/qmail/bin/qmail-popup orbital.inter7.com \
> /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir
>
>The paths are o.k., but I get the error "Maildir command not found" during
>start-up. Why??
Is that really your entire script, verbatim? I don't see anything
wrong with it.
-Dave
On Thu, Feb 03, 2000 at 01:20:39PM +0100, Andreas Altenburg wrote:
> my script:
>
> env - PATH="/var/qmail/bin:/usr/local/bin" \
> tcpserver 0 pop-3 /var/qmail/bin/qmail-popup orbital.inter7.com \
> /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir
>
> The paths are o.k., but I get the error "Maildir command not found" during
> start-up. Why??
During startup of what? The above won't produce an error like that--you could
put any kind of nonsense after "tcpserver 0 pop-3" and you won't see any error
until someone actually tries to connect to your pop3 port. So if this error is
coming about when you run some script or another, it's not this script.
Chris
Hi,
I've just setup a new Qmail-1.03 server running tcpserver and the
SPAMCONTROL patch I received from Erwin Hoffmann. When I test my mailserver
at http://www.abuse.net/relay.html it still failes at Relay test 6... so it
seems the patch is not working. What could be wrong?
Erwin
Telematica International
[EMAIL PROTECTED]
tel: 0495-547700
fax: 0495-548411
Erwin van Kroonenburg <[EMAIL PROTECTED]> wrote:
>I've just setup a new Qmail-1.03 server running tcpserver and the
>SPAMCONTROL patch I received from Erwin Hoffmann. When I test my mailserver
>at http://www.abuse.net/relay.html it still failes at Relay test 6... so it
>seems the patch is not working. What could be wrong?
Aaarrrggghhh!
-Dave
Dave Sill <[EMAIL PROTECTED]> writes:
> Erwin van Kroonenburg <[EMAIL PROTECTED]> wrote:
>> I've just setup a new Qmail-1.03 server running tcpserver and the
>> SPAMCONTROL patch I received from Erwin Hoffmann. When I test my
>> mailserver at http://www.abuse.net/relay.html it still failes at Relay
>> test 6... so it seems the patch is not working. What could be wrong?
> Aaarrrggghhh!
I think we should propose to the maintainer of that tester that to the end
of the text already there:
Anonymous mode sends commands to the server to be tested but doesn't
actually send any mail. This can report false positives, hosts that
appear to be open relays but actually aren't because they reject or
discard a message after appearing to accept it.
that he add, in bright red:
Do not use the anonymous mode of this tester to test qmail hosts! The
normal qmail configuration will appear to accept the mail, which means
that the tester will report false positives. It will specifically
tell you that the positive may be a false positive, but you won't read
it, and will therefore waste time thinking that the host is a relay
when it isn't. Please use the registered user mode instead.
--
Russ Allbery ([EMAIL PROTECTED]) <URL:http://www.eyrie.org/~eagle/>
At 16:12 3.2.2000 +0100, you wrote:
>
>When I test something like "mail from: [EMAIL PROTECTED]" the spampatch
does work! :)
>But are you sure I can pass all tests on abuse.net/relay.html with the
spampatch? Because that's why I got the patch...
>
>Regards,
>
>Erwin
>
>
Hi,
the RELAY test (according to some of your postings):
Relay test 6
>>> RSET
<<< 250 flushed
>>> MAIL FROM:<spamtest@[193.58.204.195]>
<<< 250 ok
>>> RCPT TO:<relaytest%abuse.net@[193.58.204.195]>
<<< 250 ok
Your configuration according to qmail-showctl:
badmailfrom:
@193.58.204.200 not accepted in MAIL FROM.
%193.58.204.200 not accepted in MAIL FROM.
badmailpatterns:
*193.58.204.200* not accepted in MAIL FROM (Not if line starts with !).
*200.204.58.195.in-addr.arpa.* not accepted in MAIL FROM (Not if line
starts with !).
badreceipients:
@193.58.204.200 not accepted in RCPT TO.
%193.58.204.200 not accepted in RCPT TO.
badrcptpatterns:
*193.58.204.200* not accepted in RCPT TO (Not if line starts with !).
*200.204.58.195.in-addr.arpa.* not accepted in RCPT TO (Not if line starts
with !).
Obviously, your QMAIL MTA has the IP address 193.58.204.195.
As long als you DO NOT put this address into the bad* configuration files,
the patch CAN NOT work. Pls. have a look at the README.spamcontrol. Thats
what it is for.
Regards,
eh.
+-----------------------------------------------------------------------+
| fff hh Dr. Erwin Hoffmann |
| ff hh |
| ff eee hhhh ccc ooo mm mm mm Wiener Weg 8 |
| fff ee ee hh hh cc oo oo mmm mm mm 50858 Koeln |
| ff ee eee hh hh cc oo oo mm mm mm |
| ff eee hh hh cc oo oo mm mm mm Tel 0221 484 4923 |
| ff eeee hh hh ccc ooo mm mm mm Fax 0221 484 4924 |
+-----------------------------------------------------------------------+
"Tim Hunter" <[EMAIL PROTECTED]> wrote:
>Am I right in assuming that you can use a command such as
>#!/bin/sh
>exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t !tai64nlocal
>/var/log/qmail/smtpd
>
>for logging qmail-smtpd and this will process the log through tai64nlocal
>*after* completing the log?
Yes.
-Dave
On Thu, Feb 03, 2000 at 01:15:35AM -0800, Russ Allbery wrote:
> Mark Delany <[EMAIL PROTECTED]> writes:
>
> > I just did a count of a couple of (smallish) log files and I found that
> > on average, qmail-send is logging 469 bytes per delivery and sendmail is
> > logging 430 bytes per delivery. FWIW, the qmail logging is piping into
> > logger.
>
> > My strawman conclusion? qmail and sendmail log similar amounts of data
> > per delivery.
>
> It's not the bytes so much as the lines. I may be extremely confused, but
> I believe that logger and splogger both log each separate line to syslog
> as a separate syslog() call. Each one of these messages therefore
> requires separate handling by the syslogd daemon, a separate disk write,
> and (the part that particular hurts) a separate fsync() call on systems
> that don't support unsync'd syslog logs. The fact that sendmail embeds
> all of the information in two lines per message instead of seven therefore
> makes a big difference.
>
> But see my followup message. Even taking that into account doesn't
> explain how incredibly slow syslogd is.
Oh, absolutely. I certainly wasn't doubting your observations on that front as
I've seen the same sort of load myself. If anything posting those byte counts
only confirmed the syslog has as lot of explaining to do.
Regards.
Russ Allbery <[EMAIL PROTECTED]> wrote:
>
> Unfortunately, multilog still lacks, so far as I can see, the ability to
> limit by both space *and* time so that you can create clear reporting
> boundaries for log summaries. I'd love to have it roll to a new log after
> either one day or the size limit, whichever it hits first.
If I remember correctly, Bruce Guenter wrote a patch to allow one of the
loggers to do exactly this, by having it close and reopen its log upon
receipt of a HUP or some such signal. However, I don't remember if it was
multilog or cyclog he patched, and I can't seem to find the info quickly
on his website at the moment.
It's at http://www.em.ca/~bruceg/ if anyone else cares to look.
Charles
--
----------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
Any opinions expressed are just that -- my opinions.
----------------------------------------------------
On Thu, Feb 03, 2000 at 08:26:33AM -0600, Charles Cazabon wrote:
> If I remember correctly, Bruce Guenter wrote a patch to allow one of the
> loggers to do exactly this, by having it close and reopen its log upon
> receipt of a HUP or some such signal. However, I don't remember if it was
> multilog or cyclog he patched, and I can't seem to find the info quickly
> on his website at the moment.
>
> It's at http://www.em.ca/~bruceg/ if anyone else cares to look.
Close, but not quite. I just wrote a whole new logger that writes to a
single file instead of a directory. On HUP it reopens its log file, so
you could do a nightly logrotate on it. It's the "qfilelog" part of the
qlogtools in:
http://em.ca/~bruceg/qlogtools/
I should probably put this up seperately.
--
Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/
Ryan Hughes <[EMAIL PROTECTED]> wrote:
>I am using qmail as my MTA on a RedHat Linux 5.2 server. I have setup
>majordomo on the machine, but can't get it to work right. Here is what
>my .qmail-majordomo file looks like:
>
> |/usr/local/majordomo/wrapper majordomo
See:
http://Web.InfoAve.Net/~dsill/lwq.html#mlm-majordomo
Properly configured, majordomo doesn't use "wrapper", which is a
security nightmare.
-Dave
[EMAIL PROTECTED] wrote:
>
> I strongly _dis_recommend mounting ext2fs filesystems sync. The system
> I described earlier had _terrible_ performance at first, it turned
> out this was because I followed the FAQ and mounted it sync.
Agreed; that's a serious issue. I would recommend switching to a better
synchronous filesystem, though, rather than using ext2 async.
Unfortunately, Linux offers few choices there. The BSD fs would be great
if it wasn't so immature under Linux; raiserfs might be just as good
(I don't know). It's rumored that ext3 will be journalled, synchronous
and real real fast--we'll see.
> Yes, mounting it async is bad for reliability, so decide for yourself.
The question underlying my recommendation to mount sync was: Would a
speed test be completely valid if reliability corners were cut?
Since a Linux box seldom goes down, you could 1) buy a 2-hour UPS, and 2)
mount a ramdisk on /var/qmail/queue (untested). Still ``pretty'' reliable,
but I bet that queue performance goes sky-high.
Len.
PS Then again, ``Profile--don't speculate.'' Mounting ext2 async might
approximate the performance of a ramdisk, since that's roughly what
``async'' means.
--
There's an engineering term for systems like that: ``garbage.''
-- Dan Bernstein
On Thu, 03 Feb 2000 09:05:35 -0500 , "Len Budney" writes:
> Agreed; that's a serious issue. I would recommend switching to a better
> synchronous filesystem, though, rather than using ext2 async.
>
> Unfortunately, Linux offers few choices there. The BSD fs would be great
> if it wasn't so immature under Linux;
However, it's quite mature under *BSD ;-)
Using softupdates under *BSD gives you the reliability
of sync (somewhat more, actually), with nearly the speed
of async.
--
Chris Mikkelson | "I have yet to see any problem, however complicated,
[EMAIL PROTECTED] | which, when you looked at it the right way, did not
| become still more complicated." -- Poul Anderson
[EMAIL PROTECTED] wrote:
>
> On Thu, 03 Feb 2000 09:05:35 -0500 , "Len Budney" writes:
> >
> > Unfortunately, Linux offers few choices there. The BSD fs would be
> > great if it wasn't so immature under Linux;
>
> Using softupdates under *BSD gives you the reliability of sync (somewhat
> more, actually), with nearly the speed of async.
In October of 1999, that wasn't quite true. Softupdates is less likely
than async to produce an inconsistent filesystem, but is still vulnerable
to data loss.
``In particular, if you put a mail queue on a softupdates filesystem,
you can lose mail when the power goes out, just as if you were using
Linux.'' -- Dan Bernstein, <http://x38.deja.com/getdoc.xp?AN=539496358>
>From Dan's other comments in that thread, it appears that the rename()
call returns success before the rename was committed to disk. Dan said
``mail programs'' rely on rename() to tell the truth. A look at the
source code suggests that qmail is not one of them--qmail-queue doesn't
use the rename() call.
If link() is subject to the same complaint as rename(), then qmail probably
_does_ have the same reliability problem on a softupdates filesystem as on
an async filesystem.
Len.
--
Translate the patents into English and you will see that there is
nothing new in the Sperry patent. The only way that Unisys can make
money off this patent is by convincing gullible people to pay them.
-- Dan Bernstein
On Thu, Feb 03, 2000 at 09:32:36AM -0600, [EMAIL PROTECTED] wrote:
> Using softupdates under *BSD gives you the reliability
> of sync (somewhat more, actually), with nearly the speed
> of async.
softupdates are supposed to help keep your filesystem in a
consistent state while providing asyncronous operation. When
qmail spools an email it assumes that it has been safely written
to disk. If you are using softupdates or an async filesystem the
file may still be in memory when the write call returns to qmail.
You will lose this message if you machine goes down at this time
but your whole filesystem won't be trashed.
AFAIK, the benefits of softupdates over fully asyncronous
operation has not been well proven. softupdates assure that the
metadata on the disk is always in a consistant state. It says
nothing about the data. In my past 7 years of using Linux I have
never seen an ext2 filesystem that fsck could not fix. Please
don't start this flamewar again though. Go to dejanews and
relive it in all its glory. :)
Getting back on topic, I use an ext2 async filesystem for qmail.
The tradeoff of performance for reliability is not worth it in my
opinion. The chances of my machines going down at the exact
moment that email could be lost seems pretty small. For high
volume sites with reliability requirements a journalling
filesystem like ext3 should probably be used.
Neil
On Thu, 3 Feb 2000 11:47:43 -0700 , [EMAIL PROTECTED] writes:
> AFAIK, the benefits of softupdates over fully asyncronous
> operation has not been well proven. softupdates assure that the
> metadata on the disk is always in a consistant state. It says
> nothing about the data.
Neither does vanilla FFS (which is apparently Dan's
benchmark for reliability). That's why the fsync()
call was invented. FFS/softupdates honors fsync
calls, FFS/async does not. That's the difference.
The one issue I had forgotten about was the
rename()/link() issue. I'll be looking more into
that when I have the time (the softupdates code
is really quite complex).
> Getting back on topic, I use an ext2 async filesystem for qmail.
> The tradeoff of performance for reliability is not worth it in my
> opinion. The chances of my machines going down at the exact
> moment that email could be lost seems pretty small. For high
> volume sites with reliability requirements a journalling
> filesystem like ext3 should probably be used.
FFS gives fairly decent performance, even without
async.
--
Chris Mikkelson | Einstein himself said that God doesn't roll dice. But
[EMAIL PROTECTED] | he was wrong. And in fact, anyone who has played role-
| playing games knows that God probably had to roll quite
| a few dice to come up with a character like Einstein.
| -- Larry Wall
On Thu, Feb 03, 2000 at 01:07:47PM -0600, [EMAIL PROTECTED] wrote:
> Neither does vanilla FFS (which is apparently Dan's
> benchmark for reliability). That's why the fsync()
> call was invented. FFS/softupdates honors fsync
> calls, FFS/async does not. That's the difference.
I believe that ext2 honors fsync() as well (but not in 2.3 yet).
Could someone who knows more confirm? The metadata is still
asyncronous though so FFS with softupdates is probably better.
Also note the journalling version ResierFS only writes metadata
to the journal. ext3 journals both data and metadata. You
want both for qmail.
Neil
[EMAIL PROTECTED] wrote:
>
> On Thu, Feb 03, 2000 at 01:07:47PM -0600, [EMAIL PROTECTED] wrote:
> > Neither does vanilla FFS (which is apparently Dan's
> > benchmark for reliability). That's why the fsync()
> > call was invented. FFS/softupdates honors fsync
> > calls, FFS/async does not. That's the difference.
>
> I believe that ext2 honors fsync() as well (but not in 2.3 yet).
> Could someone who knows more confirm? The metadata is still
> asyncronous though so FFS with softupdates is probably better.
OK, to get things how they are:
1. Linux honors fsync() for data but NOT for metadata (unless you
fsync() the directory the file is in).
-> The fsync() call returns when the data is written to disk but
not the metadata (happens every 30s). This leads qmail-queue
to believe everything is written completly onto safe storage
and returns message queued. If you loose power the next secs
you loose the file also. This does not mean your FS is corrupted.
== not reliable for DJB
2. *BSD FFS (with and without softupdates) honors fsync() for data
AND metadata in any case.
-> The fsync() call returns when the data and metadata is written
to the disk.
== reliable for DJB
This discussion is not only about lost filesystems but lost files.
> Also note the journalling version ResierFS only writes metadata
> to the journal. ext3 journals both data and metadata. You
> want both for qmail.
Well, that doesn't matter at all as long the fsync() system call
semantics are honored by the operating system and filesystem.
--
Andre
[EMAIL PROTECTED] wrote:
>
> In my past 7 years of using Linux I have never seen an ext2 filesystem
> that fsck could not fix.
In my 7+- years, I haven't either. My worst experience was the time I
had to use the -b option (fsck told me to, so I did, and it worked). I've
lost about 3 files in that time to ext2 inconsistency--not too bad.
> Getting back on topic, I use an ext2 async filesystem for qmail.
I use ext2 sync for /var/qmail/queue. But I handle so little mail, that
the fs doesn't visibly impact latency.
> The chances of my machines going down at the exact moment that
> email could be lost seems pretty small. For high volume sites with
> reliability requirements a journalling filesystem like ext3 should
> probably be used.
Sounds exactly right to me. (For 'reliability requirements' I'm reading,
'handles other peoples email'.)
Len.
--
Early to bed and early to rise makes a man tired and grumpy.
-- Dan Bernstein
On Thu, Feb 03, 2000 at 08:51:17PM +0100, Andre Oppermann wrote:
> 2. *BSD FFS (with and without softupdates) honors fsync() for data
> AND metadata in any case.
>
> -> The fsync() call returns when the data and metadata is written
> to the disk.
>
> == reliable for DJB
Why does he say not to use softupdates then?
I guess the main point is that any filesystem that honors fsync()
for data and metadata is okay.
Neil
On Thu, 3 Feb 2000 13:29:03 -0700 , [EMAIL PROTECTED] writes:
> On Thu, Feb 03, 2000 at 08:51:17PM +0100, Andre Oppermann wrote:
> > 2. *BSD FFS (with and without softupdates) honors fsync() for data
> > AND metadata in any case.
> >
> > -> The fsync() call returns when the data and metadata is written
> > to the disk.
> >
> > == reliable for DJB
>
> Why does he say not to use softupdates then?
>
> I guess the main point is that any filesystem that honors fsync()
> for data and metadata is okay.
There's the rename() issue also: if rename() [ or
link() ] return before the modified directories have
been committed, then qmail-local will drop the mail,
when delivering to a maildir. qmail-queue will
similarly drop mail, if it is told falsely that it
has renamed intd/whatever to todo/msgnum.
I don't know if McKusick's softupdates code will
let rename() return earlier than documented.
--
Chris Mikkelson | ... a pet peeve of mine is people who directly edit
[EMAIL PROTECTED] | the .cf file instead of using the m4 configuration
| files ... I treat the .cf file as a binary file
| - you should too. --- Eric Allman
[EMAIL PROTECTED] writes:
> I believe that ext2 honors fsync() as well (but not in 2.3 yet).
> Could someone who knows more confirm? The metadata is still
> asyncronous though so FFS with softupdates is probably better.
ext2 has always honored fsync. You fsync a file, and its data goes
off to disk. You fsync a directory and its data goes off to disk.
The only reason this surprises anyone is because the BSD hackers
decided that fsyncing a file should also fsync the directory the file
resides in.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not what your country
521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
Nice work indeed. Perks of being in a niche market with government funding all over
the place.
Anyway, my original idea was a 2mbit line to cover all services including web. As you
say web will be the most
bandwidth consumptive (real word?) so as i can work that out roughly i am looking for
email stats. The
services will be broken down in these ways. Email will be primarily for home users
with a small percentage
business (daytime users). we willhandle dialin smtp and pop3 but dialup itself is
outsourced so we don't need
to provide bandwidth for dialup connections. In effect all i need really is email
stats. Quality wise i want to
provide a good alround service which if it slows slightly at peak usage times is not
too much of a problem. The
bandwidth i am talking about is internet connectivity. All dialups are 56 or possibly
a small percentage of 64 k
isdn and a tiny percentage of 128k isdn. Let me stress again. This is part of a
dedicated server farm with no
dialup servers which are located elsewhere. Thanks all.
On Tue, 1 Feb 2000 22:07:24 -0800, [EMAIL PROTECTED] wrote:
>On Tue, Feb 01, 2000 at 04:03:51AM +0000, Marek Narkiewicz wrote:
>> I hate to ask such a general question, but hat sort of bandwidth is needed to
>accomodate up to 10000
home
>> dialup users for smtp and pop3 services? I just need some sort o rough estimate as
>I have a budget to
>> overcompensate somewhat.
>
>You have a budget and you don't know what you need to buy yet? Nice work if you
>can get it :>
>
>But what quality of service are you wanting to provide?
>
>And what is the anticipated traffic profile?
>
>Are they corporate users or general public?
>
>Are you talking about internet bandwidth, internal bandwidth or bandwidth to your
>customer
>connections?
>
>What speed dialups are these? 56K? Less? ISDN?
>
>How many concurrent connections?
>
>Oh, and, er, can these users do web browsing? If so, you'd best hang out in a
>web-traffic
>list as that will dominate your bandwidth requirements.
>
>
>Regards.
--
Marek Narkiewicz, Systems Director WelshDragon ltd
[EMAIL PROTECTED]
02/02/2000 at 15:38:11
If I understand correctly, you don't need to plan bandwidth for
web browsing, as that goes through the dial-in provider, but
you do need to plan for smtp bandwidth, as that's in-house?
I'm reading page 33 of the Jan 31, 2000 Netword World magazine,
which has an article quoting stats from Ferris Research:
User messaging will jump 81% to 34 messages -received- per user per day.
Message size will jump 192% to 286KB per message.
If you take that at face value, you need to be able to handle
(286KB * 8) * 34 * 10,000 (or whatever you said), divided by
36000 seconds in 10 hours, gets you ... 21Kb/sec? Assuming
every user also sends you that traffic as a smarthost in that
same time period means you need... 63Kb/sec line?
And you have a 2meg line spec'd currently? :)
This all changes if you need bandwidth for web traffic, of course.
John
On Wed, Feb 02, 2000 at 09:51:11AM -0800, Qmail wrote:
> I'm curious if I need this patch on RH 6.1 or higher?
Yes. Linux does not (and most likely will not ever) explicitly sync
directory data (sometimes mistakenly called file metadata) when syncing
the file data. The patch I think you're referring to explicitly fsync's
the directories after syncing the files.
--
Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/
Question: how control a double-bounce in a virtualdomains environment.
I'm using qmail 1.03 with two virtualdomains in a RedHat 6.1 Linux box.
This is the content of various control files:
ME:
mydomain.org
LOCALS:
mydomains.org
VIRTUALDOMAINS:
domain1.org:dm1
domain2.org:dm2
In /var/qmail/alias there are usual files:
.qmail-postmaster
.qmail-root
.qmail-mailer-daemon
.qmail-dm1-postmaster
.qmail-dm1-root
.qmail-dm1-mailer-daemon
.qmail-dm2-postmaster
.qmail-dm2-root
.qmail-dm2-mailer-daemon
Different users inside virtualdomains are controlled by
users/assign and related "cdb" database.
These are the first rows
------------------------------------------------------------------
=alias:alias:104:501:/var/qmail/alias:::
+alias-:alias:104:501:/var/qmail/alias:-::
=dm1-alfa:dm1-alfa:108:500:/var/mail/d/dm1-alfa:::
+dm1-alfa-:dm1-alfa:108:500:/var/mail/d/dm1-alfa:-::
=dm1-beta:dm1-beta:108:500:/var/mail/d/dm1-beta:::
+dm1-beta-:dm1-beta:108:500:/var/mail/d/dm1-beta:-::
=dm2-delta:dm2-delta:108:500:/var/mail/d/dm2-delta:::
+dm2-delta-:dm2-delta:108:500:/var/mail/d/dm2-delta:-::
--------------------------------------------------------------------
Now I create a double-bounce using an email client (outlook express) on
onother PC connected to LAN.
This email client is setup with a non existing account inside a
virtualdomain (From field):
[EMAIL PROTECTED]
Now I send a message to another non existing account in the same
virtualdomain:
[EMAIL PROTECTED]
Right, qmail send the bounce to alias/.qmail-postmaster because
[EMAIL PROTECTED] doesn't exist.
This are the first rows of the failure notice message:
----------------------------------
Hi. This is the qmail-send program at mydomain.org.
I've tried to deliver a bounce message to this address, but the bounce
bounced!
etc. etc.
----------------------------------
**And NOW the question:**
I have many different real "postmaster" (inside
alias/.qmail-???-postmaster), one for every
virtualdomains.
So:
1) How can I setup qmail to send a generic double bounce to
.qmail-dm1-postmaster
and so on for every virtualdomains ? I want that a bounce about a particular
virtualdomain will be sent to his postmaster
Perhaps setting up a "~dm1/" and a "~dm2/" directory ?
2) How can I setup the content of "failure notice" above to show the
virtualdomain
"Hi. This is the qmail-send program at domain1.org."
instead of
"Hi. This is the qmail-send program at mydomain.org."
---
Alessandro Ambrosini
Cernusco s/N (MI)
Italy
+39-0347-2443074
[EMAIL PROTECTED]
"Alessandro Ambrosini" <[EMAIL PROTECTED]> wrote:
>Question: how control a double-bounce in a virtualdomains
>environment.
Short answer: I don't think you can. Sounds like a nice feature for
qmail 2, though.
>VIRTUALDOMAINS:
>domain1.org:dm1
>domain2.org:dm2
>
>In /var/qmail/alias there are usual files:
>.qmail-postmaster
>.qmail-root
>.qmail-mailer-daemon
>
>.qmail-dm1-postmaster
>.qmail-dm1-root
>.qmail-dm1-mailer-daemon
>
>.qmail-dm2-postmaster
>.qmail-dm2-root
>.qmail-dm2-mailer-daemon
>--------------------------------------------------------------------
>
>...
>
>1) How can I setup qmail to send a generic double bounce to
>.qmail-dm1-postmaster
>and so on for every virtualdomains ?
You could use a .qmail-dm1-default file to catch messages before the
first bounce. Then you could generate your own bounce message, in
whatever format you desire. You could even check the return address
and determine in advance if it going to result in a double bounce to a
local virtual domain. But you wouldn't be able to catch all double
bounces.
-Dave
Bruce Guenter <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 03, 2000 at 08:26:33AM -0600, Charles Cazabon wrote:
> > If I remember correctly, Bruce Guenter wrote a patch to allow one of the
> > loggers to do exactly this
[...]
> Close, but not quite. I just wrote a whole new logger that writes to a
> single file instead of a directory. On HUP it reopens its log file, so
> you could do a nightly logrotate on it.
Out of curiosity, have you done any comparisons (performance or feature)
of qfilelog vs. multilog vs. cyclog?
Charles
--
----------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
Any opinions expressed are just that -- my opinions.
----------------------------------------------------
On Thu, Feb 03, 2000 at 12:31:53PM -0600, Charles Cazabon wrote:
> Out of curiosity, have you done any comparisons (performance or feature)
> of qfilelog vs. multilog vs. cyclog?
Well, let's try.
Performance:
- qfilelog, multilog, and cyclog all read messages from stdin and write
to a single file at a time, using fairly low-level IO commands and no
fsync's, so their performance is going to be close to each other (and
very fast). To compare, syslog reads messages through a relatively
complex input mechanism, and writes to a set of files at once,
fsync'ing them all by default. In its default mode, it's quite slow.
Features:
- qfilelog and syslog do no file size limiting. multilog and cyclog
limit the total size of the log files in a directory.
- qfilelog and syslog do no file rotation, but can be integrated with
tools like logrotate to accomplish this. It is difficult (but not
impossible) to integrate multilog or cyclog with logrotate, but they
already do log rotation of another kind internally.
- Only multilog has built-in hooks to filter the logs through an
external program. If you need to do this with qfilelog or syslog,
just rotate the file over and filter the (now unchanging) rotated
file.
- Only syslog can (currently) log from programs that use the syslog
interface. I suppose one could build a compatible front end that
reads from /dev/log, but it doesn't exist yet...
I think that's it.
--
Bruce Guenter <[EMAIL PROTECTED]> http://em.ca/~bruceg/
"sachin" <[EMAIL PROTECTED]> wrote:
>i want complex user routing i.e the mail fom particulor email add.
Is that "from" or "for"? I'll assume "from".
>[EMAIL PROTECTED] will forwardes to another smtp server
>how can i use smtproutes for that will it possible in smtproutes
>
>[EMAIL PROTECTED]:bom3.vsnl.net.in
No, you can't use smtproutes for that. You could use a virtualdomains
entry, if aceindia.com is a virtual domain. E.g.:
[EMAIL PROTECTED]:sachin
Then, in ~alias/.qmail-sachin-default:
[EMAIL PROTECTED]
-Dave
[EMAIL PROTECTED] wrote:
> I sometimes encounter errors like "error writing to
>network, error reading from network, connection reset
>by remote side 10054, etc" even without attachments.Do
>I need to adjust something? How is that.
We need lots more details.
-Dave
mail_manoj <[EMAIL PROTECTED]> wrote:
>I want to delete mails that's in queue for the last four days. Does it
>effect on qmail-send because few days ago I deleted mails in queue that's
>caused qmail stop, and I had to restart the qmail. So, I want to know the
>safest way to delete it.
1) stop qmail
2) delete messages from queue
3) start qmail
Step 2 can be accomplished by deleting all files under
/var/qmail/queue belonging to each message. There will be at least two
files for each message. There are utilities on www.qmail.org that make
this easier.
But I have to ask: why not leave them alone and let qmail bounce them
(or deliver them) naturally? Except in extreme cases, you shouldn't
have to micromanage the queue like this.
-Dave
"Muhammad Ali" <[EMAIL PROTECTED]> wrote:
>I have three qmail servers for my LAN. Two are directly connected to
>Internet for receiving and sending of mails for my LAN. Third one is
>POP3 server. All users first send their mails to POP3 server which
>then forwards outgoing mails to one of the two servers which are
>directly connected to Internet. For load balancing feature, I want
>that if my POP3 server is queued with lot of mails. He then forward
>rest of the mails to second server automatically. So the mails may be
>cleared form both of the servers. I have done this configuration but
>haven't tested yet:
>
>/var/qmail/control/
>smtproutes
>
>:firstqmail.server
>:secondqmail.server
>
>
>will this alteration work for load balancing???/
No, that'll either send everything to both systems, or only one of
them--I'd have to check the code to see which.
What you could do is install DJB's dnscache and use pickdns to balance
the load.
-Dave
Stephen Mills <[EMAIL PROTECTED]> wrote:
>Well ive installed about 8 servers with selective relaying with
>tcpserver and they all work fine, but this one isnt, Ive went through
>everything I know and still can't resolve it...
Post details and maybe we'll spot something you missed.
>I might just upgrade and trust (argh) redhats upgrade tool....
I'd be *very* surprised if an OS upgrade fixed your relaying problem.
-Dave
Stephen Mills <[EMAIL PROTECTED]> wrote:
>Well ive installed about 8 servers with selective relaying with
>tcpserver and they all work fine, but this one isnt, Ive went through
>everything I know and still can't resolve it...
Post details and maybe we'll spot something you missed.
>I might just upgrade and trust (argh) redhats upgrade tool....
I'd be *very* surprised if an OS upgrade fixed your relaying problem.
Sure thing Dave. Here is my details :
[root@proxy /]# cat /etc/tcp.smtp
203.17.254.:allow, RELAYCLIENT=""
192.168.1.:allow, RELAYCLIENT=""
127.:allow, RELAYCLIENT=""
:allow
[root@proxy /]# cat /etc/passwd | grep qmaild
qmaild:!!:558:557::/var/qmail:/bin/bash
[root@proxy /]# cat /etc/rc.d/rc.local | grep tcpserver
tcpserver -x/etc/tcp.smtp.cdb -u558 -g557 0 smtp /var/qmail/bin/qmail-smtpd
&
[root@proxy control]# ps ax | grep tcpserver
546 ? S 0:13 tcpserver -x/etc/tcp.smtp.cdb -u558 -g557 0 smtp
/var/qmail/
[root@proxy /]# cat /var/qmail/control/rcpthosts1 | grep lan1.com.au
lan1.com.au
exchange.lan1.com.au
proxy.lan1.com.au
Ive telneted to my mail server from a 203.17.254.* address :
220 How may I help you ? ESMTP
MAIL
250 ok
rcpt from: [EMAIL PROTECTED]
250 ok
rcpt to: [EMAIL PROTECTED]
553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)
As you can see, its totally just not letting specified hosts to relay...
Ive totally out-resourced myself on this one :-)
We hacked qmail-smtpd to enable only a given number of rcpt's to relay, but
I recompiled qmail-smtpd from source and it didnt make a difference.....
--Stephen
sorry I forgot to change :
[root@proxy /]# cat /var/qmail/control/rcpthosts1 | grep lan1.com.au
to
[root@proxy /]# cat /var/qmail/control/rcpthosts | grep lan1.com.au
I renamed it to rcpthosts1 just so the file isnt read when I restart
qmail.....so ignore the 1 at the end......qmail reads in rcpthosts
properly.
-----Original Message-----
From: Stephen Mills [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 04, 2000 12:16 PM
To: 'Dave Sill'
Cc: '[EMAIL PROTECTED]'
Subject: RE: Broken tcp_wrappers (resulting in selective relaying not
working)
Stephen Mills <[EMAIL PROTECTED]> wrote:
>Well ive installed about 8 servers with selective relaying with
>tcpserver and they all work fine, but this one isnt, Ive went through
>everything I know and still can't resolve it...
Post details and maybe we'll spot something you missed.
>I might just upgrade and trust (argh) redhats upgrade tool....
I'd be *very* surprised if an OS upgrade fixed your relaying problem.
Sure thing Dave. Here is my details :
[root@proxy /]# cat /etc/tcp.smtp
203.17.254.:allow, RELAYCLIENT=""
192.168.1.:allow, RELAYCLIENT=""
127.:allow, RELAYCLIENT=""
:allow
[root@proxy /]# cat /etc/passwd | grep qmaild
qmaild:!!:558:557::/var/qmail:/bin/bash
[root@proxy /]# cat /etc/rc.d/rc.local | grep tcpserver
tcpserver -x/etc/tcp.smtp.cdb -u558 -g557 0 smtp /var/qmail/bin/qmail-smtpd
&
[root@proxy control]# ps ax | grep tcpserver
546 ? S 0:13 tcpserver -x/etc/tcp.smtp.cdb -u558 -g557 0 smtp
/var/qmail/
[root@proxy /]# cat /var/qmail/control/rcpthosts1 | grep lan1.com.au
lan1.com.au
exchange.lan1.com.au
proxy.lan1.com.au
Ive telneted to my mail server from a 203.17.254.* address :
220 How may I help you ? ESMTP
MAIL
250 ok
rcpt from: [EMAIL PROTECTED]
250 ok
rcpt to: [EMAIL PROTECTED]
553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)
As you can see, its totally just not letting specified hosts to relay...
Ive totally out-resourced myself on this one :-)
We hacked qmail-smtpd to enable only a given number of rcpt's to relay, but
I recompiled qmail-smtpd from source and it didnt make a difference.....
--Stephen
On Fri, Feb 04, 2000 at 12:16:28PM +1100, Stephen Mills wrote:
> [root@proxy /]# cat /etc/tcp.smtp
> 203.17.254.:allow, RELAYCLIENT=""
^
Remove the space before RELAYCLIENT.
Chris
Chris,
It works ! Thanks.
I owe you a slab of beer and a barby :)
--Stephen
-----Original Message-----
From: Chris Johnson [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 04, 2000 12:38 PM
To: Stephen Mills
Cc: '[EMAIL PROTECTED]'
Subject: Re: Broken tcp_wrappers (resulting in selective relaying not
work ing)
On Fri, Feb 04, 2000 at 12:16:28PM +1100, Stephen Mills wrote:
> [root@proxy /]# cat /etc/tcp.smtp
> 203.17.254.:allow, RELAYCLIENT=""
^
Remove the space before RELAYCLIENT.
Chris
"Mullen, Patrick" <[EMAIL PROTECTED]> wrote:
>This is the line I'm using to start the pop3 demon is:
>
>tcpserver -v 0 pop-3 /var/qmail/bin/qmail-popup myhost.net \
>/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir 2>&1 | \
>/var/qmail/bin/splogger qmail-pop3d 3 &
>
>This line works perfectly on my other server, but on this one I get
>the message from the subject line (shell-init: couldn't get current
>directory) after authenticating.
>
>I telnetted to port 110, and I can enter the lines "USER username"
>"PASS password" and get a valid login (with that error) but if I
>do "LIST" it lists the messages. Unfortunately, at least two
>POP clients (spruce and Netscape) treat that message as fatal.
I don't recognize "shell-init", but it's not part of qmail.
Off hand, I'd guess it's a permission problem. Check the modes on all
the parent directories of the Maildir. Compare them with the system
that works right.
-Dave
> Off hand, I'd guess it's a permission problem. Check the modes on all
> the parent directories of the Maildir. Compare them with the system
> that works right.
Here is what happens when I do this manually --
[me@myhost me]$ telnet localhost 110
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
+OK <[EMAIL PROTECTED]>
user me
+OK
pass mypassword
shell-init: could not get current directory
+OK
list
+OK
1 601
quit
+OK
Connection closed by foreign host.
If I am reading the `list` correctly, that is
the one message that I have in my Maildirs,
which is 601 bytes long (verified using ls -l)
and is actually stored in the "curr" directory
of a folder (Maildir/.folder/curr has a file
which is 601 bytes long), so it doesn't appear
to be a permissions problem at that end.
When running the test line from checkpassword
as a normal user, I get "authorization failed".
If I run it as root, I can log in correctly.
The test command is:
/var/qmail/bin/qmail-popup host /bin/checkpassword pwd
I get the impression there is a permissions
problem which prohibits login even on a properly
configured server because the two different
servers I have also fail running the above
command, but the one (RH6.0) complains about
not being able to write to a pipe, and the
other (RH5.1) complains about not being able
to write to the filter files for temporary
relaying ala open-smtpd mods and then complains
about tcpmakectl not being able to write to
temporary output. Both of these systems work
during normal operation, however.
Notice on my non-working system it seems to
not even get far enough to complain about
not being able to write to the output pipe.
Any ideas where I should look for these
permissions problems? What other applications
are needed to login?
Thanks,
~Patrick
"Mullen, Patrick" <[EMAIL PROTECTED]> wrote:
>Any ideas where I should look for these
>permissions problems?
Say the full path to Maildir is /home/user/Maildir. Do:
ls -ld /
ls -ld /home
ls -ld /home/user
ls -ld /home/user/Maildir
ls -ld /home/user/Maildir/*
Compare the results with a working Maildir on a working system. If you
don't see the problem, post the output of those commands here.
-Dave
> Say the full path to Maildir is /home/user/Maildir. Do:
[ snip getting of full path permissions ]
> Compare the results with a working Maildir on a working
> system. If you
> don't see the problem, post the output of those commands here.
They are exactly the same (except that originally I
had the o+x bit set on the broken system because I also
have web pages in there), but here are the results:
[user@host user]$ ls -ld /
drwxr-xr-x 17 root root 1024 Jan 24 19:32 /
[user@host user]$ ls -ld /home
drwxr-xr-x 10 root root 4096 Feb 1 10:55 /home
[user@host user]$ ls -ld /home/user/
drwx------ 12 user user 4096 Feb 2 19:41 /home/user/
[user@host user]$ ls -ld /home/user/Maildir/
drwx------ 7 user user 4096 Feb 3 15:48 /home/user/Maildir/
[user@host user]$ ls -ld /home/user/Maildir/*
-rw-rw-r-- 1 user user 42 Feb 2 19:38
/home/user/Maildir/courierimapuiddb
drwx------ 2 user user 4096 Feb 2 19:40 /home/user/Maildir/cur
drwx------ 2 user user 4096 Feb 2 19:00 /home/user/Maildir/new
drwx------ 2 user user 4096 Feb 3 12:57 /home/user/Maildir/tmp
In ~/Maildir, I also have .folder with permissions 700.
Oh. Sudden brain spark. On this system I use shadow
passwords, and on the others I don't. Is there something
special that I have to do for one of the support programs?
My last email seems to indicate I do have a proper login
in the long run because it successfully reads my Maildir,
but maybe something in the middle has problems (I'm using
the open-smtpd patch to checkpassword.c).
Thanks,
~Patrick
> Just for a test, try making both of those mode 755 or 750.
I made both ~ and ~/Maildir mode 755, and the results
were exactly the same. :(
Anywhere else you want me to try? Here is a
complete listing of the situation through
telnet and the test from checkpassword's INSTALL --
[user@host user]$ telnet localhost 110
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
+OK <[EMAIL PROTECTED]>
user user
+OK
pass password
shell-init: could not get current directory
+OK
list
+OK
1 601
.
quit
+OK
Connection closed by foreign host.
[user@host user]$ /var/qmail/bin/qmail-popup host /bin/checkpassword pwd
+OK <2120.949612644@host>
user user
+OK
pass password
-ERR authorization failed
[user@host user]$ su
Password:
[root@host user]# /var/qmail/bin/qmail-popup host /bin/checkpassword pwd
+OK <2124.949612664@host>
user user
+OK
pass password
/home/user
...So it definately seems to be a permissions problem,
but I can't figure out what doesn't have the proper
permissions to do what.
Thanks,
~Patrick
> I don't recognize "shell-init", but it's not part of qmail.
Well, after grinding the heck out of my hard drive, I
finally found both "shell-init" and "could not get current
directory" in the same program. As should have been
expected, they were from /bin/bash (and /bin/sh which is
only a symbolic link to /bin/bash on RH6.1).
Where and why would bash be called while connecting to
qmail-pop3d, and what would cause it to not be able to
get the current directory?
Thanks,
~Patrick
Sounds like it's time to modify your /etc/inetd.conf or tcpserver and add
strace and make sure you dont have any typos.
On Thu, 3 Feb 2000, Mullen, Patrick wrote:
>> I don't recognize "shell-init", but it's not part of qmail.
>
>Well, after grinding the heck out of my hard drive, I
>finally found both "shell-init" and "could not get current
>directory" in the same program. As should have been
>expected, they were from /bin/bash (and /bin/sh which is
>only a symbolic link to /bin/bash on RH6.1).
>
>Where and why would bash be called while connecting to
>qmail-pop3d, and what would cause it to not be able to
>get the current directory?
_ __ _____ __ _________
______________ /_______ ___ ____ /______ John Gonzalez/Net.Tech
__ __ \ __ \ __/_ __ `__ \/ __ /_ ___/ MDC Computers/netMDC!
_ / / / `__/ /_ / / / / / / /_/ / / /__ (505)437-7600/fax-437-3052
/_/ /_/\___/\__/ /_/ /_/ /_/\__,_/ \___/ http://www.netmdc.com
[---------------------------------------------[system info]-----------]
6:10pm up 10 days, 2:07, 3 users, load average: 0.00, 0.09, 0.14
> Sounds like it's time to modify your /etc/inetd.conf or
> tcpserver and add
> strace and make sure you dont have any typos.
ARGH! I was saying just today that I hate computers, and
I now have a fresh reminder of why. Suddenly, it works.
Unfortunately, I don't know why it suddenly works, but
it does. Thanks for the help everyone. Maybe there was
some typo that I just kept repeating or something, even
though going back through the console log shows the same
exact settings from `ps` as I get now. Hrm...
Thanks!
~Patrick
P.S. Obviously, I mean one of those love-hate things
toward computers. I'm sure everyone knows what I mean. ;)
> Where and why would bash be called while connecting to
> qmail-pop3d,
I'd look into your checkpasswd implementation, since that's the point at
which the message gets printed. How does qmail-pop3d run checkpasswd? I
wouldn't have thought system() knowing Dan's way of doing things, but
perhaps it's a shell script?
> and what would cause it to not be able to
> get the current directory?
There, I have no idea.
-Matt
--
Matt Brown ---- UNIX Administrator ---- tickets.com
Phone: (714) 327-5571 --- Email: [EMAIL PROTECTED]
"Bolmehag, Peter" <[EMAIL PROTECTED]> wrote:
>I just moved from sendmail to qmail. Now I have domainaliases in the
>sendmail configuratio that looks like this:
>
>[EMAIL PROTECTED] [EMAIL PROTECTED]
>
>Mail is received for [EMAIL PROTECTED] and is copied and sent out to
>[EMAIL PROTECTED] .
First, note that qmail smashes case on the local part, so "Mark"
becomes "mark" before local delivery takes place. For remote
deliveries, it preserves the case.
Second, which of netcentral.com and audiostore.no are virtual, and
which, if any, is local?
>I have lots of these pairs where mail comes in to one domain and leaves for
>another directly.
Is it a simple forward, or do you retain a copy locally?
-Dave
Hello,
I want to send messages with flash animations embeded (multipart mime
messages).
Is this possible? How?
Thanks,
Carlo Gibertini
[EMAIL PROTECTED] wrote:
>I want to send messages with flash animations embeded (multipart mime
>messages).
I'm sorry to hear that. :-)
>Is this possible? How?
Don't know, but (a) it's not a qmail question, and (b) very few MUA's
will be able to display such messages properly.
-Dave
> I want to send messages with flash animations
> embeded (multipart mime messages).
Oh, dear God. Please don't abuse the mail
infrastructure this way. It's really not
designed for it. If you take a 1k binary
file (say a VERY small picture or something,
which is much smaller than flash) and
attach it to an email, by the time it
gets converted to 7-bit ASCII to go
through mail servers it is likely to expand
to 3k. Now extrapolate that to a flash
animation file, which is several to many
kilobytes long.
But, to answer your question so this isn't
[just?] a flame mail --
Simply attach the file like any other. *IF*
the remote mail client will automatically
extract the animation and run it, then it
will do so. Otherwise, the recipient would
have to save the attachment to disk and
run it from there. This is the same as
how some mailers will display attached
pictures inline, and others will make
you have to save the image to disk first.
IOW, your question is more about mail
client software than mail servers.
~Patrick
> -----Original Message-----
> From: Carlo Gibertini [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 03, 2000 3:38 PM
> To: qmail
> Subject: Semd multipart messages with flash embeded
>
>
>
> Hello,
>
> I want to send messages with flash animations embeded (multipart mime
> messages).
>
> Is this possible? How?
>
> Thanks,
>
>
> Carlo Gibertini
>
TAG writes:
> Is there some documentatoin about using popbull around - if so - please
> point me?
How is the qmail-popbull man page (included in the patch) failing you?
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not what your country
521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
Charles Leeds writes:
> We were audited and one of the findings was that our qmail server allowed
> addresses with the pipe symbol in them, which was reported in our audit as a
> bad practice.
Sounds like a good time to pick new auditors.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not what your country
521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
Jeff Russell, AIT writes:
> Quick question?
>
> Does qmail support MIME?
Depending on what you mean, the answer is either definitely yes or
definitely no.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not what your country
521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
Hi All,
I'm new the list and hopefully have an easily answered questions, which
is :
How do I apply the coorect options to get rblsmtpd to work with qmail.
This is my current tcpserver command line :
/usr/local/bin/tcpserver -v -u 101 -g 100 0 smtp
/var/qmail/bin/qmail-smtpd &
I want to use relays.mail-abuse.org and my rblsmtpd is located in
/opt/software/bin/rblsmtpd
Can anyoone help at all?
Many thanks,
Kevin Smith
Hi All,
Is there anyone who knows about how to setup rblsmtpd ?
I've tried loads of different sources and I can't seem to find a way to
set-up qmail to bloke relay spam to my server.
This my current start-up for qmail in /etc/init.d :
/usr/local/bin/tcpserver -v -u 101 -g 100 0 smtp
/var/qmail/bin/qmail-smtpd &
I have tried the following combinations :
Here is the rblsmtpd help prompt :
rblsmtpd [ -b ] [ -R ] [ -r domain ] [ -t timeout ] smtpd [ arg ...
]
And in theory this should work :
/usr/local/bin/tcpserver -v -u 101 -g 100 0 smtp
/opt/software/bin/rblmstpd /var/qmail/bin/qmail-smtpd &
But, ir doesn't bloke reply spam from the test from RSS list?
Any ideas?
Regards,
Kevin Smith
Lemon Lainey Design UK
http://www.lemonlaineydesign.com
Hi all,
When I tried running qmail-clean, both when all other qmail daemons are
stopped and when the daemons are running, it seems to hang. i.e. as you hit
the carriage return, it will just keep running.
Is it alright to stop qmail then remove the ffg. subdirectories under:
/tmp/queue/local/nn
/tmp/queue/remote/nn
/tmp/queue/mess/nn
where nn is some number.
If this is ok to do, are there any directories that I need to remove?
Thanks!
Andrew De Chavez
Web Development SA
E*Offering
Ph. 415-618-6217
On Thu, Feb 03, 2000 at 02:07:43PM -0800, DeChavez , Andrew wrote:
> When I tried running qmail-clean, both when all other qmail daemons are
> stopped and when the daemons are running, it seems to hang. i.e. as you hit
> the carriage return, it will just keep running.
Don't run qmail-clean. It's not meant for humans to run. If you feel that you
must run it, read the man page.
> Is it alright to stop qmail then remove the ffg. subdirectories under:
> /tmp/queue/local/nn
> /tmp/queue/remote/nn
> /tmp/queue/mess/nn
>
> where nn is some number.
>
> If this is ok to do, are there any directories that I need to remove?
What problem are you trying to solve? What makes you think that you need to
remove directories?
Chris
yeah right...check the man page!
I need to clean out obsoleted emails that are spooled, because, for some
non-qmail reason, didn't get sent right away. Right now, here's what I do to
clean it up....
/etc/init.d/qmail stop
cd /tmp/queue/remote
for i in `ls`
do
rm ${i}/2* # cause they usually start with 2
done
I do the same thing with mess, locals...
Is there another way to do it?
I'm not sure what those numbered-subdirs are for. Some of them have last
modification date of several months ago....
-a
P.S. Does anybody know when the Qmail book is gonna be published?
Thanks!
-----Original Message-----
From: Chris Johnson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 03, 2000 2:14 PM
To: DeChavez , Andrew
Cc: [EMAIL PROTECTED]
Subject: Re: qmail-clean does not work
On Thu, Feb 03, 2000 at 02:07:43PM -0800, DeChavez , Andrew wrote:
> When I tried running qmail-clean, both when all other qmail daemons are
> stopped and when the daemons are running, it seems to hang. i.e. as you
hit
> the carriage return, it will just keep running.
Don't run qmail-clean. It's not meant for humans to run. If you feel that
you
must run it, read the man page.
> Is it alright to stop qmail then remove the ffg. subdirectories under:
> /tmp/queue/local/nn
> /tmp/queue/remote/nn
> /tmp/queue/mess/nn
>
> where nn is some number.
>
> If this is ok to do, are there any directories that I need to remove?
What problem are you trying to solve? What makes you think that you need to
remove directories?
Chris
On Thu, Feb 03, 2000 at 03:32:20PM -0800, DeChavez , Andrew wrote:
> I need to clean out obsoleted emails that are spooled, because, for some
> non-qmail reason, didn't get sent right away.
Why do you need to remove them from the queue? qmail will do that itself once
they're in there for longer than the queue lifetime. If you'd like the queue
lifetime to be shorter, see the qmail-send man page and read about
queuelifetime.
> Right now, here's what I do to clean it up....
>
> /etc/init.d/qmail stop
> cd /tmp/queue/remote
> for i in `ls`
> do
> rm ${i}/2* # cause they usually start with 2
> done
>
> I do the same thing with mess, locals...
> Is there another way to do it?
If you're really anxious for these messages to be out of the queue before
they've expired on their own, find the message in the queue/info/* directory
and touch -t it to some early date (touch -t 01010000 should work). qmail-send
will try to send it one more time, and then it'll decide it's too old and
bounce it.
Chris
Which file/process does qmail check the files in queue/info/* against?
How about files under queue/mess/* queue/remote/* queue/local/* ?
Can I do this (touch -t) while qmail is up?
-a
-----Original Message-----
From: 'Chris Johnson' [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 03, 2000 3:53 PM
To: DeChavez , Andrew
Cc: [EMAIL PROTECTED]
Subject: Re: qmail-clean does not work
On Thu, Feb 03, 2000 at 03:32:20PM -0800, DeChavez , Andrew wrote:
> I need to clean out obsoleted emails that are spooled, because, for some
> non-qmail reason, didn't get sent right away.
Why do you need to remove them from the queue? qmail will do that itself
once
they're in there for longer than the queue lifetime. If you'd like the queue
lifetime to be shorter, see the qmail-send man page and read about
queuelifetime.
> Right now, here's what I do to clean it up....
>
> /etc/init.d/qmail stop
> cd /tmp/queue/remote
> for i in `ls`
> do
> rm ${i}/2* # cause they usually start with 2
> done
>
> I do the same thing with mess, locals...
> Is there another way to do it?
If you're really anxious for these messages to be out of the queue before
they've expired on their own, find the message in the queue/info/* directory
and touch -t it to some early date (touch -t 01010000 should work).
qmail-send
will try to send it one more time, and then it'll decide it's too old and
bounce it.
Chris
On Thu, Feb 03, 2000 at 04:11:07PM -0800, DeChavez , Andrew wrote:
> Which file/process does qmail check the files in queue/info/* against?
I don't know what this means.
> How about files under queue/mess/* queue/remote/* queue/local/* ?
Don't worry about them. When the message is bounced, they'll go away.
> Can I do this (touch -t) while qmail is up?
I'm pretty sure it's safe, though I know someone will correct me if I'm wrong.
Chris
I meant:
Which file/process does qmail compare the files in queue/info/* against?
You suggested that I do touch -t 01010000 so that files in the subdirs
queue/info/* will become older than.....????....
tnx!
-a
-----Original Message-----
From: Chris Johnson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 03, 2000 4:15 PM
To: DeChavez , Andrew
Cc: [EMAIL PROTECTED]
Subject: Re: qmail-clean does not work
On Thu, Feb 03, 2000 at 04:11:07PM -0800, DeChavez , Andrew wrote:
> Which file/process does qmail check the files in queue/info/* against?
I don't know what this means.
> How about files under queue/mess/* queue/remote/* queue/local/* ?
Don't worry about them. When the message is bounced, they'll go away.
> Can I do this (touch -t) while qmail is up?
I'm pretty sure it's safe, though I know someone will correct me if I'm
wrong.
Chris
older than the current time, obviously.
shag
----- Original Message -----
From: DeChavez , Andrew <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thu 3 Feb 2000 16.22
Subject: RE: qmail-clean does not work
I meant:
Which file/process does qmail compare the files in queue/info/* against?
You suggested that I do touch -t 01010000 so that files in the subdirs
queue/info/* will become older than.....????....
tnx!
-a
-----Original Message-----
From: Chris Johnson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 03, 2000 4:15 PM
To: DeChavez , Andrew
Cc: [EMAIL PROTECTED]
Subject: Re: qmail-clean does not work
On Thu, Feb 03, 2000 at 04:11:07PM -0800, DeChavez , Andrew wrote:
> Which file/process does qmail check the files in queue/info/* against?
I don't know what this means.
> How about files under queue/mess/* queue/remote/* queue/local/* ?
Don't worry about them. When the message is bounced, they'll go away.
> Can I do this (touch -t) while qmail is up?
I'm pretty sure it's safe, though I know someone will correct me if I'm
wrong.
Chris
On Thu, Feb 03, 2000 at 04:22:00PM -0800, DeChavez , Andrew wrote:
> I meant:
>
> Which file/process does qmail compare the files in queue/info/* against?
That's exactly what you said the first time.
> You suggested that I do touch -t 01010000 so that files in the subdirs
> queue/info/* will become older than.....????....
See the man page for touch. touch -t 01010000 will set the date of the file to
midnight on January 1. That'll make qmail think it's been in the queue for too
long, so it'll bounce it.
Chris
This is what I do to clean the queue:
find /var/qmail/queue -type f -name '[0-9]*' -exec touch -d 19900101 '{}'
';'
Then, if I'm in a hurry, I
kill -ALRM
then qmail-send process. This is safe to do with qmail running, AFAIK.
-o-o-
I had this wild thought that the queuelifetime value is compared with when
the qmail daemons were started, such that if I recently started qmail
(/etc/init.d/qmail start) and if I have a queuelifetime of 7 days, then
everything spooled, including the obsoleted messages, will get sent....
Thanks for all your reponse!
-a
-----Original Message-----
From: Chris Johnson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 03, 2000 4:32 PM
To: DeChavez , Andrew
Cc: [EMAIL PROTECTED]
Subject: Re: qmail-clean does not work
On Thu, Feb 03, 2000 at 04:22:00PM -0800, DeChavez , Andrew wrote:
> I meant:
>
> Which file/process does qmail compare the files in queue/info/* against?
That's exactly what you said the first time.
> You suggested that I do touch -t 01010000 so that files in the subdirs
> queue/info/* will become older than.....????....
See the man page for touch. touch -t 01010000 will set the date of the file
to
midnight on January 1. That'll make qmail think it's been in the queue for
too
long, so it'll bounce it.
Chris
DeChavez , Andrew writes:
> P.S. Does anybody know when the Qmail book is gonna be published?
Well, I was just working on it yesterday....
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not what your country
521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
On Thu, 3 Feb 2000 15:12:00 -0500 (EST) , Russell Nelson writes:
> [EMAIL PROTECTED] writes:
> > I believe that ext2 honors fsync() as well (but not in 2.3 yet).
> > Could someone who knows more confirm? The metadata is still
> > asyncronous though so FFS with softupdates is probably better.
>
> ext2 has always honored fsync. You fsync a file, and its data goes
> off to disk. You fsync a directory and its data goes off to disk.
> The only reason this surprises anyone is because the BSD hackers
> decided that fsyncing a file should also fsync the directory the file
> resides in.
What use is syncing the data to disk, if you can't
get to it after a crash? It might as well have just
stayed in cache otherwise....
--
Chris Mikkelson | "Unfortunately, simplicity is a complicated mess
[EMAIL PROTECTED] | of a concept." --Taner Edis
[EMAIL PROTECTED] writes:
> On Thu, 3 Feb 2000 15:12:00 -0500 (EST) , Russell Nelson writes:
> > ext2 has always honored fsync. You fsync a file, and its data goes
> > off to disk. You fsync a directory and its data goes off to disk.
> > The only reason this surprises anyone is because the BSD hackers
> > decided that fsyncing a file should also fsync the directory the file
> > resides in.
>
> What use is syncing the data to disk, if you can't
> get to it after a crash? It might as well have just
> stayed in cache otherwise....
fsync the data if you want the data on disk.
fsync the directory if you want the metadata on disk.
What's complicated or difficult about that?
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not what your country
521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
On Thu, 3 Feb 2000 23:15:41 -0500 (EST) , Russell Nelson writes:
> [EMAIL PROTECTED] writes:
> > What use is syncing the data to disk, if you can't
> > get to it after a crash? It might as well have just
> > stayed in cache otherwise....
>
> fsync the data if you want the data on disk.
> fsync the directory if you want the metadata on disk.
>
> What's complicated or difficult about that?
It's not difficult -- just overly complicated, compared
to the standard
- fsync the file if you want the file on disk
Why require two separate fsync() calls when one
will do?
Further, what is the point if the first fsync() call
is useless without the second, and vice versa?
(If the data is on disk, but the on-disk metadata is
not sufficient to locate it, then the data is, for
all practical purpose, useless.)
--
Chris Mikkelson | Einstein himself said that God doesn't roll dice. But
[EMAIL PROTECTED] | he was wrong. And in fact, anyone who has played role-
| playing games knows that God probably had to roll quite
| a few dice to come up with a character like Einstein.
| -- Larry Wall
[EMAIL PROTECTED] writes:
> Why require two separate fsync() calls when one
> will do?
Because it's faster to only do the one. What is the point of spending
10% of your disk throughput taking steps to prevent something that
never happens? Your machine is more likely to be destroyed in a
terrorist attack than to lose a file on an ext2 filesystem due to a
system crash. Call out the National Guard!
> Further, what is the point if the first fsync() call
> is useless without the second, and vice versa?
Because the ext2 filesystem has the ability to rebuild the file from
the data. That's why I've been running the same filesystem for the
last five years with *NO* lost files. I've outgrown that disk, but I
still keep it mounted. And I've done device driver development on my
system and crashed it a number of times. And my current system
suffers from insufficient cooling, so if I'm playing an MP3 and doing
disk activity at the same time, it crashes. It's gotten a lot better
since I put silicone grease on the heat sink.
Crashing used to scare the bejeezus out of me until I realized that
the bad reputation for losing Unix filesystems in crashes came from
SYS V, not Linux.
--
-russ nelson <[EMAIL PROTECTED]> http://russnelson.com
Crynwr sells support for free software | PGPok | "Ask not what your country
521 Pleasant Valley Rd. | +1 315 268 1925 voice | can force other people to
Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | do for you..." -Perry M.
Hi Folks,
I'm trying to put together a solution for a custom application for a
client.
Essentially for each email sent I want to generate a confirming email
back
to the sender and to a third party with date, time, and file size. I
need
this to occur immediately and automatically.
Any thoughts on this? Or where it should be integrated and the easies
solution?
Thanks,
How do I create a Maildir directory when I am adding a user?
I am running FreeBSD 3.4 with qmail 1.03 and it's various goodies installed
from the ports collection. I want to use the $HOME/Maildir with qmail. How
do I create this directory automatically when I add a user via the adduser
program?
Thanks in advance.
Max
e. [EMAIL PROTECTED]
On Thu, Feb 03, 2000 at 06:03:40PM -0800, Max wrote:
> How do I create a Maildir directory when I am adding a user?
>
> I am running FreeBSD 3.4 with qmail 1.03 and it's various goodies installed
> from the ports collection. I want to use the $HOME/Maildir with qmail. How
> do I create this directory automatically when I add a user via the adduser
> program?
# cd /usr/share/skel && /var/qmail/bin/maildirmake Maildir
That's it. Any new user will get a fresh new Maildir in his home directory.
Chris
> # cd /usr/share/skel && /var/qmail/bin/maildirmake Maildir
Or, this may be appropriate (and shorter ;) --
# /var/qmail/bin/maildirmake /etc/skel/Maildir
Check your system for where "skel" (the skeleton directory
structure for new users) resides. I would assume there
would only be one "skel" directory.
~Patrick
I know that this is not a real solution, but it needs to be done.
I need a 'goomailfrom' ie: people or domains that exist in the list is
allowed to relay. I suppose it is something opposit for 'badmailfrom'
that dont allow certain people or domains to mail us.
POP-before-SMTP relay and relay certain IP's is not working as the
firewall doesn't give me the correct IP's =(
Please advice ASAP
Michael Boman
--
W I Z O F F I C E . C O M P T E L T D - Your Online Wizard
16 Tannery Lane, Crystal Time Building, #06-00, Singapore 347778
Voice : (65) 844 3228 [ext 118] Fax : (65) 842 7228
Pager : (65) 92 93 29 49 ICQ : 5566009
eMail : [EMAIL PROTECTED] URL : http://www.wizoffice.com
On Fri, Feb 04, 2000 at 01:12:59PM +0800, Michael Boman wrote:
> I know that this is not a real solution, but it needs to be done.
>
> I need a 'goomailfrom' ie: people or domains that exist in the list is
> allowed to relay. I suppose it is something opposit for 'badmailfrom' that
> dont allow certain people or domains to mail us.
Yes, it's a bad thing to do, but I have a patch to do it.
http://www.palomine.net/qmail/relaymailfrom.html.
Chris
I want to configure qmail-local to deliver mail to /var/spool/mail.
The /usr/share/man/cat5/dot-qmail.0 file tells you how to write a
.qmail file to change delivery, however its too difficult for me to comprehe
nd.
Can someone help me here?
Thanks in advance,
Kristina
P.S I do not want to use /bin/mail or procmail for /var/spool/mail delivery.
I want to use qmail-local.
Hi,
Is it possible to set a databytes file for a specific user that will
overide the system wide databytes file??
Many Thanks
Tonino
On Fri, Feb 04, 2000 at 10:19:59AM +0200, TAG wrote:
> Is it possible to set a databytes file for a specific user that will
> overide the system wide databytes file??
You could use the qmail-smtp AUTH patch and hack it. It looks
pretty easy to do. I almost did it myself but then decided I
didn't need it.
Neil
--
"The more original a discovery, the more obvious it seems afterward."
-- Arthur Koestler
Hi folks,
I have some problem with vpopmail and .qmail. I've tried to make an user
autorespond (vacation-like-behaviour) so when a person send an email to
[EMAIL PROTECTED] it automatically respond to that email and that email
automatically copied to user's Maildir.
First I make an experiment making a
/home/vpopmail/domains/pampi.dnet.net.id/.qmail-test-auto contains:
| /var/qmail/autorespond 1000 5
/var/vpopmail/domains/myvirtualdomain.com/user/message
/var/vpopmail/domains/myvirtualdomain/user
&[EMAIL PROTECTED]
the /var/vpopmail/domains/pampi.dnet.net.id/user/message contain the
autorespond message.
It works...
but when I tried to move it into user directory using .qmail it generates error
message like this:
949652062.130628 info msg 45487: bytes 496 from <[EMAIL PROTECTED]> qp 22508
uid 502 949652062.287103 starting delivery 1070: msg 45487 to local
[EMAIL PROTECTED] 949652062.287178 status: local
1/10 remote 0/20 949652063.547500 delivery 1070: success: did_0+0+1/
949652063.547540 status: local 0/10 remote 0/20
949652063.547571 end msg 45487
949652185.550513 new msg 45487
949652185.550538 info msg 45487: bytes 495 from <[EMAIL PROTECTED]> qp 22545 uid 502
949652185.559655 starting delivery 1071: msg 45487 to local
[EMAIL PROTECTED]
949652185.559725 status: local 1/10 remote 0/20
949652186.449084 new msg 45488
949652186.449109 info msg 45488: bytes 620 from <[EMAIL PROTECTED]> qp 22553 uid 508
949652186.615074 starting delivery 1072: msg 45488 to local
[EMAIL PROTECTED]
949652186.615146 status: local 2/10 remote 0/20
949652186.737615 new msg 45489
949652186.737638 info msg 45489: bytes 620 from <[EMAIL PROTECTED]> qp 22557 uid 508
949652186.786520 starting delivery 1073: msg 45489 to local
[EMAIL PROTECTED]
949652186.786631 status: local 3/10 remote 0/20
949652186.786661 delivery 1071: success:
AUTORESPOND:_Failed_to_change_into_directory./did_0+0+1/
949652186.786724 status: local 2/10 remote 0/20
949652186.786754 delivery 1072: failure:
This_message_is_looping:_it_already_has_my_Delivered-To_line._(#5.4.6)/
949652186.806686 status: local 1/10 remote 0/20
949652186.806723 end msg 45487
949652186.823530 bounce msg 45488 qp 22561
949652186.824181 end msg 45488
949652186.825479 new msg 45487
949652186.826015 info msg 45487: bytes 1188 from <> qp 22561 uid 507
949652186.927245 starting delivery 1074: msg 45487 to remote [EMAIL PROTECTED]
949652186.928018 status: local 1/10 remote 1/20
949652187.262329 delivery 1073: success:
POP_user_does_not_exist,_but_will_deliver_to_/home/vpopmail/domains/pampi.dnet.net.id/postmaster/did_0+0+1/
I can't figure out what's wrong. It said that autorespond failed to change into
directory, i've tried to suid root autorespond program but it doesn't work, so
I think there's no permission problem. Is there anything to do with vpopmail
program to deal with .qmail and autorespond program?
thanks in advance.
regards,
pampi
|
how do i unsubscribe from this list
|
Hi,
There seems to be something wrong but I can't figure out what.
I've setup Qmail-1.03, AVP 3.0 Beta 2 and compiled amavis with "configure
--enable-qmail". I followed the instructions on www.unixzone.com/virus and
even applied the "error in Kaspersky AVP call" fix. When I try so send an
email there is a loop and there's no local delivery. What could be wrong?
Regards,
Erwin
-----Oorspronkelijk bericht-----
Van: Rainer Link [SMTP:[EMAIL PROTECTED]]
Verzonden: Monday, January 31, 2000 3:05 PM
Aan: [EMAIL PROTECTED]
Onderwerp: Re: Qmail anti-virus package?
Erwin van Kroonenburg wrote:
Hi!
> I was wondering if there is an anti-virus update or package for qmail to
check
> incoming mail for virusses.
Short question, short answer :-)
See http://www.unixzone.com/virus/
HTH
best regards,
Rainer Link
--
Rainer Link, eMail: [EMAIL PROTECTED], WWW: http://rainer.w3.to/
Student of Communication Engineering/Computer Networking, University of
Applied Sciences,Furtwangen,Germany,http://www.ce.is.fh-furtwangen.de/
Hi there,
i've checked the mailinglist but found nothin (or i'm to silly today ;o) ) .
I have a virtual-domain "n-online.net".
Now all mail arrives at our qmail-server and vmailmgr is running.
Now i have to reroute only a few [EMAIL PROTECTED] adresses to an internal IP-Adress.
the easyest would be to put "n-online.net:192.168.250.1" into smtproutes, but thats
not what i want ! it should be something like "[EMAIL PROTECTED]:192.168.250.1".
The original sender and recipient must stay intact, that's the problem!
Mail to [EMAIL PROTECTED] must be simply routed to 192.168.250.1 keeping all headers
and so
on (like smtproutes).
Is there a solution?
Thanks for your help,
Thomas
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 4 Feb 00, at 11:43, Puck wrote:
> The original sender and recipient must stay intact, that's the
> problem!
Is that really neccessary?
> Is there a solution?
Sure there is. You need two qmail installations for that
(edit conf-home, and recompile/reinstall).
The "main" installation has n-online.de as virtual domain. The virtual
domain .qmail files look like
.qmail-specialuser:
|/var/qmail2/bin/forward "$USER@$HOST"
.qmail-default
some-local-delivery-command
The second qmail installation has n-online.de in smtproutes. It
does not listen on port25 - therefore it doesn't need rcpthosts and
stuff. You need to care about bounces of locally generated
messages (otherwise qmail complains about "I am the best A or
MX but the domain is not in my locals").
You can even avoid the Delivered-To: header line for the forwarded
message by changing the invocation to
|env DTLINE="" /var/qmail2/bin/forward "$USER@$HOST"
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBOJq+KVMwP8g7qbw/EQKaswCfRtboQ/T59YQzDsICcb4OLDYsatQAoJYl
doU/ZcryZxoLIgt34YYvSLrn
=hOJL
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
