qmail Digest 5 Oct 2000 10:00:01 -0000 Issue 1144

Topics (messages 49902 through 49951):

SPAM is not a big deal if you are getting only SPAM
        49902 by: Petr Danecek
        49909 by: OK 2 NET - Andr� Paulsberg
        49910 by: Petr Novotny
        49917 by: Petr Danecek
        49920 by: OK 2 NET - Andr� Paulsberg
        49921 by: Andy Bradford
        49924 by: Erwin Hoffmann
        49925 by: dsr.bbn.com
        49945 by: Petr Novotny
        49946 by: Petr Novotny
        49947 by: Martin Jespersen
        49948 by: Petr Novotny

Re: Qmail not sending to Certain Servers
        49903 by: Dave Sill

Re: VirutalDomain - Forward - No Directories
        49904 by: Dave Sill
        49905 by: Javier Szyszlican
        49906 by: Dave Sill
        49918 by: Javier Szyszlican

Re: BestWinblozeMailClient
        49907 by: Jan Knepper
        49915 by: Justin Bell

Re: my pop3 is very slow
        49908 by: Simo Lakka
        49923 by: Alexander Jernejcic

Re: Best Winbloze Mail Client?
        49911 by: Jon Rust
        49916 by: David Dyer-Bennet

Re: Qmail not delivering...
        49912 by: Kris Kelley
        49914 by: Jonathan Fanti

Masquerading hostnames with exceptions
        49913 by: Mike Jackson

Server side message filtering?
        49919 by: Brice Ruth

Best Keyboard (was: Best Winbloze Mail Client?)
        49922 by: Robin S. Socha

NFS without a user database?
        49926 by: Kris Kelley
        49927 by: Peter van Dijk
        49928 by: markd.bushwire.net
        49929 by: Michael Boyiazis
        49930 by: Peter van Dijk
        49931 by: Peter van Dijk
        49932 by: Kris Kelley
        49933 by: Peter van Dijk

Test
        49934 by: Subba Rao

A couple newbie install questions
        49935 by: Carey

qmail with cyrus
        49936 by: Casey Allen Shobe

assign file?
        49937 by: Eddie Greer

qmail-pop3d logging?
        49938 by: Jon Rust

Re: Test (Duplicate copies)
        49939 by: Subba Rao
        49940 by: Peter Green

Qmail Basics
        49941 by: Daniel Knights
        49944 by: Clemens Hermann

Please teach me how to control with qmail server ?
        49942 by: nast.home.nimc.go.jp

Volunteers for a multilog patch?
        49943 by: Brett Randall

Clustering Qmail
        49949 by: Thomas Ackermann
        49950 by: Gjermund Sorseth
        49951 by: Brett Randall

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,

SPAM is not a big deal if you are getting only SPAM. It is much worse when
you are getting thousands and thousands of failure messages.

This is exactly what happened to me: some smart guy has a huge list of
emails addresses which are intended to be his spam victims. Tousands of
them are not working any more, because the list is out-dated, but the
error messages have to end somewhere, don't they? 
Ok, we pick up some existing domain.com and then we wiil randomly generate
[EMAIL PROTECTED] So, all this mess ends up in the postmasters mail.
Apart from these, you find there also tons of threats that people will
suit me for spamming.

My question is:

1) is there a way out?
2) can qmail reject email based on "Received: " envelope? I want it not to
bounce a message back, if there is the bad.host.com listed in the Received
line.

Thank you for you suggestions and comments,
Sincerely
Petr Danecek


-- 







> SPAM is not a big deal if you are getting only SPAM.
> It is much worse when you are getting thousands and thousands of failure messages.
>
> This is exactly what happened to me: some smart guy has a huge list of
> emails addresses which are intended to be his spam victims.
> Tousands of them are not working any more, because the list is out-dated,
> but the error messages have to end somewhere, don't they?
> Ok, we pick up some existing domain.com and then we wiil randomly generate
> [EMAIL PROTECTED] So, all this mess ends up in the postmasters mail.
> Apart from these, you find there also tons of threats that people will
> suit me for spamming.

Are your server being used as a Relay for these messages,
or are the SPAMMERS simply using your domain to forge their envelope sender.


> My question is:
>
> 1) is there a way out?

Yes, it's however mighty complexed and for most people unacceptable.

You have to "compromize" your security so that your service to your users
are balancing right where you and your users are happy,
secondly you have to "compromize" security to insure that your work day
is less than 24 hours everyday while still making your server maximum safe.


> 2) can qmail reject email based on "Received: " envelope?
>    I want it not to bounce a message back,
>    if there is the bad.host.com listed in the Received line.

You can only purge them automaticly, I'm not sure that's to smart.
The best is to reject based on envelope sender or recipient,
that way you can tell the "offening" server that you rejected the message.
(This is done throug the files control/badmailfrom and control/badrcptto.)

BTW: would it be possible to see one COMPLETE
     bounce message you are having trouble with.


MVH Andr� Paulsberg






-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4 Oct 2000, at 16:04, OK 2 NET - André Paulsberg wrote:

> Are your server being used as a Relay for these messages,
> or are the SPAMMERS simply using your domain to forge their envelope
> sender.

The latter. (It happened to quite a few domains in .cz, lately. I have 
been busy accepting, refusing and deleting a gigabyte of 
bounces/double-bounces over our pathetic 64kbit line for most of 
the previous week.)

> > 2) can qmail reject email based on "Received: " envelope?
> >    I want it not to bounce a message back,
> >    if there is the bad.host.com listed in the Received line.
> 
> You can only purge them automaticly, I'm not sure that's to smart. The
> best is to reject based on envelope sender or recipient, that way you
> can tell the "offening" server that you rejected the message. (This is
> done throug the files control/badmailfrom and control/badrcptto.)

badmailfrom doesn't help as all the incoming messages are 
bounces, MAIL FROM:<>

badrcptto might help, together with some heurestics. (There were 
way-too-many forms of [EMAIL PROTECTED]) goodrcptto might 
help better :-)

I just changed my ~alias/.qmail-default to
|fastforward -d /etc/aliases.cdb; exit 0
to keep my mailbox clean (and my old harddisk from suffering, 
queue from growing, and the load never was more than 4.55 :-) - 
most of the load coming (probably) from SYN cookies).

> BTW: would it be possible to see one COMPLETE
>      bounce message you are having trouble with.

I have stored about five thousand of them. The basic pattern is 
simple: Some faked Received line, then someone at 
saturn.bbn.com (a DSL? dial-up?), then some open relay in .cn, .jp 
or .kr domains (I have seen quite a few of them) and then the 
recipient, bouncing the message back. I can post one of the 
messages, but which one? Don't want to be unfair to the remaining 
open relays :-)


A few people suggested to sue the spammer for misusing 
antek.cz's name. Can anyone suggest how? I am not US-based 
and our company is not US-based. Is it a crime to fake the return 
address (meaning I can mail my evidence to the authorities) or am I 
on my own to sue the spammer? If the latter, I can see no chance 
of that happening...

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2 -- QDPGP 2.61a
Comment: http://community.wow.net/grt/qdpgp.html

iQA/AwUBOdst0VMwP8g7qbw/EQJQ3QCg6WYhempP1c4tAVJ5XLeurfYb0AAAoO9K
C26AB4w1TOY53sA5VceAeO78
=G/YD
-----END PGP SIGNATURE-----






> > > 2) can qmail reject email based on "Received: " envelope?
> > >    I want it not to bounce a message back,
> > >    if there is the bad.host.com listed in the Received line.
> > 
> > You can only purge them automaticly, I'm not sure that's to smart. The
> > best is to reject based on envelope sender or recipient, that way you
> > can tell the "offening" server that you rejected the message. (This is
> > done throug the files control/badmailfrom and control/badrcptto.)
> 
> badmailfrom doesn't help as all the incoming messages are 
> bounces, MAIL FROM:<>
> 
> badrcptto might help, together with some heurestics. (There were 
> way-too-many forms of [EMAIL PROTECTED]) goodrcptto might 
> help better :-)

Badrcptto does not look at the 'Received:' lines, does it?
A good solution might be to patch qmail so that it will not bounce a
message back if it sees a suspicious 'Received:' line in the header. What
is the best way to do this?

> 
> I just changed my ~alias/.qmail-default to
> |fastforward -d /etc/aliases.cdb; exit 0
> to keep my mailbox clean (and my old harddisk from suffering, 
> queue from growing, and the load never was more than 4.55 :-) - 
> most of the load coming (probably) from SYN cookies).

This is simple and efficient. Thanks!


> > BTW: would it be possible to see one COMPLETE
> >      bounce message you are having trouble with.
> 
> I have stored about five thousand of them. The basic pattern is 
> simple: Some faked Received line, then someone at 
> saturn.bbn.com (a DSL? dial-up?), then some open relay in .cn, .jp 
> or .kr domains (I have seen quite a few of them) and then the 
> recipient, bouncing the message back. I can post one of the 
> messages, but which one? Don't want to be unfair to the remaining 
> open relays :-)

Yes, this is the same guy. All emails' source looks like 
PPPa14-ResaleKansasCity1-4R7102.saturn.bbn.com


> A few people suggested to sue the spammer for misusing 
> antek.cz's name. Can anyone suggest how? I am not US-based 
> and our company is not US-based. Is it a crime to fake the return 
> address (meaning I can mail my evidence to the authorities) or am I 
> on my own to sue the spammer? If the latter, I can see no chance 
> of that happening...

Usually you would contact people responsible for the domain 
saturn.bbn.com. No responses so far.

Petr





>> You can only purge them automaticly, I'm not sure that's to smart.
>> The best is to reject based on envelope sender or recipient,
>> that way you can tell the "offening" server that you rejected the message.
>> (This is done throug the files control/badmailfrom and control/badrcptto.)
>
> badrcptto might help, together with some heurestics.
> (There were way-too-many forms of [EMAIL PROTECTED])
> goodrcptto might help better :-)

For now I recommend putting all known forged addresses in badrcptto,
this is the only "easy" way to avoid any high volum traffic over a 64kbps line.


>> BTW: would it be possible to see one COMPLETE
>>      bounce message you are having trouble with.
>
> I have stored about five thousand of them.
> The basic pattern is simple:
> Some faked Received line, then someone at saturn.bbn.com (a DSL? dial-up?),
> then some open relay in .cn, .jp or .kr domains
> (I have seen quite a few of them) and then the recipient,
> bouncing the message back.
> I can post one of the messages, but which one?
> Don't want to be unfair to the remaining open relays :-)

Block them with ORBS ;D


> A few people suggested to sue the spammer for misusing antek.cz's name.
> Can anyone suggest how?

Not me, but I'm sure you can get a lawyer to help you with this.


MVH Andr� Paulsberg






On Wed, 04 Oct 2000 16:16:49 -0000, Petr Danecek wrote:

> Badrcptto does not look at the 'Received:' lines, does it?
> A good solution might be to patch qmail so that it will not bounce a
> message back if it sees a suspicious 'Received:' line in the header. What
> is the best way to do this?

I don't believe badrcptto is a valid control file (at least not for 
qmail).  Is it part of a patch?  Is it an undocumented *feature*? :-)  
So, unless it is part of something you have crafted or an add-on to 
qmail then it is probably not being used at all...

Andy





Hi,

At 16:16 4.10.2000 +0000, Petr Danecek wrote:
>
>
>> > > 2) can qmail reject email based on "Received: " envelope?
>> > >    I want it not to bounce a message back,
>> > >    if there is the bad.host.com listed in the Received line.
>> > 
>> > You can only purge them automaticly, I'm not sure that's to smart. The
>> > best is to reject based on envelope sender or recipient, that way you
>> > can tell the "offening" server that you rejected the message. (This is
>> > done throug the files control/badmailfrom and control/badrcptto.)
>> 
>> badmailfrom doesn't help as all the incoming messages are 
>> bounces, MAIL FROM:<>
>> 
>> badrcptto might help, together with some heurestics. (There were 
>> way-too-many forms of [EMAIL PROTECTED]) goodrcptto might 
>> help better :-)
>
>Badrcptto does not look at the 'Received:' lines, does it?
>A good solution might be to patch qmail so that it will not bounce a
>message back if it sees a suspicious 'Received:' line in the header. What
>is the best way to do this?
>
>> 
>> I just changed my ~alias/.qmail-default to
>> |fastforward -d /etc/aliases.cdb; exit 0
>> to keep my mailbox clean (and my old harddisk from suffering, 
>> queue from growing, and the load never was more than 4.55 :-) - 
>> most of the load coming (probably) from SYN cookies).
>
>This is simple and efficient. Thanks!
>
>
>> > BTW: would it be possible to see one COMPLETE
>> >      bounce message you are having trouble with.
>> 
>> I have stored about five thousand of them. The basic pattern is 
>> simple: Some faked Received line, then someone at 
>> saturn.bbn.com (a DSL? dial-up?), then some open relay in .cn, .jp 
>> or .kr domains (I have seen quite a few of them) and then the 
>> recipient, bouncing the message back. I can post one of the 
>> messages, but which one? Don't want to be unfair to the remaining 
>> open relays :-)
>
>Yes, this is the same guy. All emails' source looks like 
>PPPa14-ResaleKansasCity1-4R7102.saturn.bbn.com
>

If this address is in the "MAIL From:" you can give my SPAMCONTROL patch a
trial. Here, you are free to do as pattern match on the sender.
>
>> A few people suggested to sue the spammer for misusing 
>> antek.cz's name. Can anyone suggest how? I am not US-based 
>> and our company is not US-based. Is it a crime to fake the return 
>> address (meaning I can mail my evidence to the authorities) or am I 
>> on my own to sue the spammer? If the latter, I can see no chance 
>> of that happening...
>
>Usually you would contact people responsible for the domain 
>saturn.bbn.com. No responses so far.
>

The patch includes a DNS MX lookup. Maybe that helps.


http:/www.fehcom.de/qmail_en.html

cheers.
eh.
>Petr
>
>
+-----------------------------------------------------------------------+
|  fff        hh         http://www.fehcom.de        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  |
+-----------------------------------------------------------------------+




On Wed, Oct 04, 2000 at 04:17:05PM +0200, Petr Novotny wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 4 Oct 2000, at 16:04, OK 2 NET - Andr� Paulsberg wrote:
> 
> > Are your server being used as a Relay for these messages,
> > or are the SPAMMERS simply using your domain to forge their envelope
> > sender.
> > BTW: would it be possible to see one COMPLETE
> >      bounce message you are having trouble with.
> 
> I have stored about five thousand of them. The basic pattern is 
> simple: Some faked Received line, then someone at 
> saturn.bbn.com (a DSL? dial-up?), then some open relay in .cn, .jp 
> or .kr domains (I have seen quite a few of them) and then the 
> recipient, bouncing the message back. I can post one of the 
> messages, but which one? Don't want to be unfair to the remaining 
> open relays :-)

<std.disclaimer>

Anything in .saturn.bbn.com is a dialup port sold to a virtual ISP, that
is, a company which may or may not own any modems of their own, but buy
access to Genuity's (formerly BBN's) dialup pool.

We don't have any particular control over them, but every single user
is a client of one of our clients, and our contracts have strong anti-spam
terminology.

Problems should be sent first to the client ISP, if available from headers,
and if not, to [EMAIL PROTECTED]

-dsr-






-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4 Oct 2000, at 16:01, [EMAIL PROTECTED] wrote:

> Problems should be sent first to the client ISP, if available from
> headers, and if not, to [EMAIL PROTECTED]

<sarcasm>
Thanks for the advice.
</sarcasm>

In that case, you might want to ask what happened to report
BBN-DDQV54204. I haven't heard a word from bbn.com, except the 
automatic ticket.

I did report it more than a week ago, at the moment the first double 
bounce appeared in my mailbox.

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2 -- QDPGP 2.61a
Comment: http://community.wow.net/grt/qdpgp.html

iQA+AwUBOdwjvVMwP8g7qbw/EQJB1QCWNXcLWrpT84noQpY75yVfmHRZtACgnDve
5eRD7fmlDwRmKb6UnbAh1EY=
=OILh
-----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]




-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4 Oct 2000, at 19:45, OK 2 NET - André Paulsberg wrote:

> Block them with ORBS ;D

You don't get it. I got most of the bounces from yahoo.com, 
msn.com, aol.com, excite.com etc. Those machines are *not* 
open relays; they tried to deliver mail for local users, and then 
bounced the undeliverable messages back (to me, sadly).


-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2 -- QDPGP 2.61a
Comment: http://community.wow.net/grt/qdpgp.html

iQA/AwUBOdwqkFMwP8g7qbw/EQLidACfXlnYmuToE5vv9PxLzfQM1WyCExoAn0Ry
tW2zC4mzBWY/zp9JJqHpX1V6
=dx83
-----END PGP SIGNATURE-----




I've been watching this thread on the sideline, and it seems to me, that
the problem is that your box accepts to receive mail to adresses that
doesn't exist on your server, and thus floods your postmaster (you) am i
right?

If this is so, then all you really have to do is this:

remove .qmail-default

make .qmail-postmaster inot a script that looks up if the reciving
adress is valid, othervise send it to /dev/null

/Martin


Petr Novotny wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 4 Oct 2000, at 19:45, OK 2 NET - Andr� Paulsberg wrote:
> 
> > Block them with ORBS ;D
> 
> You don't get it. I got most of the bounces from yahoo.com,
> msn.com, aol.com, excite.com etc. Those machines are *not*
> open relays; they tried to deliver mail for local users, and then
> bounced the undeliverable messages back (to me, sadly).
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 6.5.2 -- QDPGP 2.61a
> Comment: http://community.wow.net/grt/qdpgp.html
> 
> iQA/AwUBOdwqkFMwP8g7qbw/EQLidACfXlnYmuToE5vv9PxLzfQM1WyCExoAn0Ry
> tW2zC4mzBWY/zp9JJqHpX1V6
> =dx83
> -----END PGP SIGNATURE-----




-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 5 Oct 2000, at 10:27, Martin Jespersen wrote:

> I've been watching this thread on the sideline, and it seems to me,
> that the problem is that your box accepts to receive mail to adresses
> that doesn't exist on your server, and thus floods your postmaster
> (you) am i right?

The storm is (fortunately) over. I have solved the load on the box by 
changing my .qmail-default to
|fastforward -d /etc/aliases.cdb; exit 0
It kept the load down, and kept my inbox (almost) clean.

But still the trafic was killing the line. (And, for the record, refusing 
the data after seeing RCPT TO, before accepting DATA, with alikes 
of "badrcptto" patch, might cut the bandwidth down by perhaps 30 
or 50%, but would not solve the problem.)


[What really hurts is that we're paying each transmitted megabyte. 
Fortunately, the ISP agreed to waive about 40% of the usual price 
for these extra megabytes. You know, the ISP has been hit by the 
same spammer, faking also their domain as a return address...]

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.2 -- QDPGP 2.61a
Comment: http://community.wow.net/grt/qdpgp.html

iQA/AwUBOdwxiFMwP8g7qbw/EQK+LQCdH3BkBtimwuwoChnlBYdlXE0KHIUAoMLB
wMvw/ov7sKHNbAOeHBw3LOuG
=gqm4
-----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]




"Kathleen Farber" <[EMAIL PROTECTED]> wrote:

>Thank you everyone for your quick responses.  For once I'm glad to know it's
>not me.  Any where I could do some reading on how to read qmail logs? Maybe
>then I'd understand some of this a little more when issues arise.

http://Web.InfoAve.Net/~dsill/lwq.html#logs

-Dave




<[EMAIL PROTECTED]> wrote:

>~alias/.qmail means pepe's Home Directory
>o /var/qmail/alias ? 

~username means username's home directory.

>The problems is that I need this with 1600+ domains.

http://Web.InfoAve.Net/~dsill/lwq.html#fastforward

-Dave




tnx Dave,

I'll explain it again.

I've a Redirection service in Argentina. (web.net.ar)
We redirect subdomains (pepe.web.net.ar) to the user
personal home page in, for example (members.xoom.com/~pepe).
That's Ok.. only web.

But we (with Sendmail) redirect the subdomain mail too.
[EMAIL PROTECTED]
to for example [EMAIL PROTECTED]

We are changing server's (http://wna.szysz.com.ar) so I install qmail
(Qmail+MySql)
the POP3/SMTP is doing great.
But I couldn't find the way to do the same we do with Sendmail.

We have 1600+ clients. in a Database (MySql), they aren't static. So I've
New clients every day.

I Don't want to create a localuser for each, because they dont check mail
here, I only want to redirect, to rewrite the TO: address.

I try it modifiing the control files but I coundn't find the way.

I was thinking in touching the code... but is very complex.

Any Solution?

Javier

----- Original Message -----
From: "Dave Sill" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 04, 2000 9:56 AM
Subject: RE: VirutalDomain - Forward - No Directories


> <[EMAIL PROTECTED]> wrote:
>
> >~alias/.qmail means pepe's Home Directory
> >o /var/qmail/alias ?
>
> ~username means username's home directory.
>
> >The problems is that I need this with 1600+ domains.
>
> http://Web.InfoAve.Net/~dsill/lwq.html#fastforward
>
> -Dave






"Javier Szyszlican" <[EMAIL PROTECTED]> wrote:

>But we (with Sendmail) redirect the subdomain mail too.
>[EMAIL PROTECTED]
>to for example [EMAIL PROTECTED]
>
>...
>
>We have 1600+ clients. in a Database (MySql), they aren't static. So I've
>New clients every day.
>
>I Don't want to create a localuser for each, because they dont check mail
>here, I only want to redirect, to rewrite the TO: address.

control/virtualdomains:
  pepe.web.net.ar:alias-pepe

~alias/.qmail-pepe-default:
  &[EMAIL PROTECTED]

So for each subdomain you need one virtualdomains entry and one .qmail 
file. If that's unacceptable, you can do something like:

control/virtualdomains:
  pepe.web.net.ar:alias-subdomain-pepe

~alias/.qmail-subdomain-default:
  |script_that_looks_up_pepes_address_in_db_and_forwards_to_it

Which will requires one virtualfomains entry per subdomain, but only
one .qmail file.

-Dave




Tnx Dave,

I'll try this, and the fastforward solutions today.
I'll inform the list the result.

Thanks a lot.

Javier

-----Mensaje original-----
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]En nombre
de Dave Sill
Enviado el: Wednesday, October 04, 2000 10:21 AM
Para: [EMAIL PROTECTED]
Asunto: Re: VirutalDomain - Forward - No Directories


"Javier Szyszlican" <[EMAIL PROTECTED]> wrote:

>But we (with Sendmail) redirect the subdomain mail too.
>[EMAIL PROTECTED]
>to for example [EMAIL PROTECTED]
>
>...
>
>We have 1600+ clients. in a Database (MySql), they aren't static. So I've
>New clients every day.
>
>I Don't want to create a localuser for each, because they dont check mail
>here, I only want to redirect, to rewrite the TO: address.

control/virtualdomains:
  pepe.web.net.ar:alias-pepe

~alias/.qmail-pepe-default:
  &[EMAIL PROTECTED]

So for each subdomain you need one virtualdomains entry and one .qmail 
file. If that's unacceptable, you can do something like:

control/virtualdomains:
  pepe.web.net.ar:alias-subdomain-pepe

~alias/.qmail-subdomain-default:
  |script_that_looks_up_pepes_address_in_db_and_forwards_to_it

Which will requires one virtualfomains entry per subdomain, but only
one .qmail file.

-Dave





Jos Okhuijsen wrote:

> Right, messenger is nice. It drops short on 1 major for us:
> Trying to add a second pop account:  "You can have multiple
> mail servers if they are IMAP servers. You are now using a pop
> server" While inside we could go POP, i can't change the outside
> offerings, and they aren't POP.

What you can do is create a second profile and restart messenger when you have
to change to a different account. I have been doing that for years. (Once you
have more than one profile you can select them at startup.)
I considered this a small inconvenience for staying away from crap like
Outlook Express...

This feature however has been added in version 6.0 which is in beta right now.

Don't worry, be Kneppie!
Jan


--
Jan Knepper
Smartsoft, LLC
88 Petersburg Road
Petersburg, NJ 08270
U.S.A.

http://www.smartsoft.cc/
http://www.mp3.com/pianoprincess

Phone : 609-628-4260
FAX   : 609-628-1267
FAX   : 303-845-6415 http://www.fax4free.com/

Phone : 020-873-3837 http://www.xoip.nl/ (Dutch)
FAX   : 020-873-3837 http://www.xoip.nl/ (Dutch)

In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <[EMAIL PROTECTED]>






Eudora isn't too bad, and the sponsored mode lets you use multiple POP/IMAP
accounts etc....

On 04 21, Jos Okhuijsen wrote:
# Hi Jan & Brett
# 
# Right, messenger is nice. It drops short on 1 major for us: 
# Trying to add a second pop account:  "You can have multiple
# mail servers if they are IMAP servers. You are now using a pop 
# server" While inside we could go POP, i can't change the outside 
# offerings, and they aren't POP. 
# 
# To be honest: Many years ago i tried to get GNUS up and running,
# and i am still recovering from the dent in my self esteem after giving up. 
# It was simply too damm difficult. But he, i'll give it a try once more,
# and try to create a workable setup for my users. That with a standard 
# install could be a worthwile proposition. 
# 
# Regards,
# 
# Jos
# 
# 
# 

-- 
Justin Bell





re

i tried with:

-R: Do not attempt to obtain $TCPREMOTEINFO from the remote host. To avoid
loops, you must use this option for servers on TCP ports 53 and 113

.. option, and with some else. But its slow anyway, i tried with
inetd, and that was very fast, but i dont want to use inetd :)
(ideas?)

-zrx






hi,
try to add -H to your tcpservers options list

 -H     Do not look up the remote host name.

;) a

==============================================
Alexander Jernejcic              
email:[EMAIL PROTECTED]

begin LOVE-LETTER-UND-NIX-DAZUGELERNT.txt.vbs
I am a Signature, not a Virus!
end

==============================================

> -----Original Message-----
> From: Simo Lakka [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 04, 2000 3:34 PM
> To: Charles Cazabon
> Subject: Re: my pop3 is very slow
> 
> 
> 
> re
> 
> i tried with:
> 
> -R: Do not attempt to obtain $TCPREMOTEINFO from the remote host. To avoid
> loops, you must use this option for servers on TCP ports 53 and 113
> 
> .. option, and with some else. But its slow anyway, i tried with
> inetd, and that was very fast, but i dont want to use inetd :)
> (ideas?)
> 
> -zrx
> 
> 




On Wed, Oct 04, 2000 at 10:13:09AM -0500, Brett Randall wrote:
<snip>
> point-and-click most WB users like, but I personally like keyboard 
> functionality more, even if the standard QWERTY keyboard sucks arse big 
> time). Hey that's an idea. Why don't we change the standard Windows client 
> to a ported GNUS and change the keyboards to Dvorak's! That should increase 
> work efficiency by about 400%!
> 
> Oh well, to dream of the future
> 
> /BR

Urban legend. There have been studies that show QWERTY isn't all that
bad. _The Economist_ in particular ran a story about a study comparing
Dvorak and QWERTY and found no advantage either way.

The misconception comes from the statement that the keyboard was
designed to slow typists down. Not quite. It was designed to prevent the
hammers from getting tangled up. Doing so doesn't necessarily mean the
typist will be slower.

jon




Jon Rust <[EMAIL PROTECTED]> writes on 4 October 2000 at 08:00:56 -0700
 > On Wed, Oct 04, 2000 at 10:13:09AM -0500, Brett Randall wrote:
 > <snip>
 > > point-and-click most WB users like, but I personally like keyboard 
 > > functionality more, even if the standard QWERTY keyboard sucks arse big 
 > > time). Hey that's an idea. Why don't we change the standard Windows client 
 > > to a ported GNUS and change the keyboards to Dvorak's! That should increase 
 > > work efficiency by about 400%!
 > > 
 > > Oh well, to dream of the future
 > > 
 > > /BR
 > 
 > Urban legend. There have been studies that show QWERTY isn't all that
 > bad. _The Economist_ in particular ran a story about a study comparing
 > Dvorak and QWERTY and found no advantage either way.

http://www.economist.com/displayStory.cfm?Story_ID=196071

Thanks for the pointer; I know I've seen several debunkings of the
Dvorak claims, but I couldn't lay hands on one quickly when Brett's
claim came through.

 > The misconception comes from the statement that the keyboard was
 > designed to slow typists down. Not quite. It was designed to prevent the
 > hammers from getting tangled up. Doing so doesn't necessarily mean the
 > typist will be slower.

All the very-fast typists I know use Qwerty (and I know one who tests
over 150 WPM).
-- 
David Dyer-Bennet / Welcome to the future! / [EMAIL PROTECTED]
Photos: http://dd-b.lighthunters.net/ 
SF: http://www.dd-b.net/dd-b/ Minicon: http://www.mnstf.org/minicon/




> I have a working qmail configuration, but one problem, when trying to
> send a message to myself on another mail server within our network I get
> the following:
>
> @4000000039dae1e6378f3a7c status: local 0/10 remote 4/20
> @4000000039dae20d396054e4 delivery 84: deferral:
> Connected_to_195.40.11.130_but_connection_die
> d._(#4.4.2)/
> @4000000039dae20d3960cdfc status: local 0/10 remote 3/20
> @4000000039dae5a001f2488c delivery 85: deferral:
> Connected_to_195.40.11.130_but_connection_die
> d._(#4.4.2)/
> @4000000039dae5a001f2c58c status: local 0/10 remote 2/20
> @4000000039dae5fe39f90aa4 delivery 86: deferral:
> Connected_to_195.40.11.130_but_connection_die
> d._(#4.4.2)/
> @4000000039dae5fe39f98b8c status: local 0/10 remote 1/20
> @4000000039dae696395fdbcc delivery 87: deferral:
> Connected_to_195.40.11.130_but_connection_die
> d._(#4.4.2)/
> @4000000039dae69639604d14 status: local 0/10 remote 0/20

Have you tried doing a manual SMTP session with the other machine?  That is,
have you tried telnetting to port 25 and entering a few SMTP commands?  If
this doesn't work, then your problem probably isn't specific to qmail
(perhaps a routing problem).  Try it and find out.

---Kris Kelley





Upon more inspection it was actually the remote mail server that was
causing problems. The server I was trying to send messages to has to
NICs one on 213.87.7.* network and the other on 195.40.11.* network, but
as the qmail server was also on the 2131.86.7.* network this confussed
the remote server, and it rejected the connection. i.e. It expected
213.86.7.* machines to connect to its NIC on the same network, not to
the NIC on the 195.40.11.130.

Thanks for all the sugestions.

Jon. 

Kris Kelley wrote:
> 
> > I have a working qmail configuration, but one problem, when trying to
> > send a message to myself on another mail server within our network I get
> > the following:
> >
> > @4000000039dae1e6378f3a7c status: local 0/10 remote 4/20
> > @4000000039dae20d396054e4 delivery 84: deferral:
> > Connected_to_195.40.11.130_but_connection_die
> > d._(#4.4.2)/
> > @4000000039dae20d3960cdfc status: local 0/10 remote 3/20
> > @4000000039dae5a001f2488c delivery 85: deferral:
> > Connected_to_195.40.11.130_but_connection_die
> > d._(#4.4.2)/
> > @4000000039dae5a001f2c58c status: local 0/10 remote 2/20
> > @4000000039dae5fe39f90aa4 delivery 86: deferral:
> > Connected_to_195.40.11.130_but_connection_die
> > d._(#4.4.2)/
> > @4000000039dae5fe39f98b8c status: local 0/10 remote 1/20
> > @4000000039dae696395fdbcc delivery 87: deferral:
> > Connected_to_195.40.11.130_but_connection_die
> > d._(#4.4.2)/
> > @4000000039dae69639604d14 status: local 0/10 remote 0/20
> 
> Have you tried doing a manual SMTP session with the other machine?  That is,
> have you tried telnetting to port 25 and entering a few SMTP commands?  If
> this doesn't work, then your problem probably isn't specific to qmail
> (perhaps a routing problem).  Try it and find out.
> 
> ---Kris Kelley

-- 
ICMP - The protocol that likes to go: PING!




Hello,
 I have set up "~/control/defaulthost example.com" to send all outgoing mail
as [EMAIL PROTECTED], regardless of what the user enters in his email
client. I want to force this, with the exception of one user who uses
multiple addresses such as [EMAIL PROTECTED], [EMAIL PROTECTED], and
[EMAIL PROTECTED] depending on who he is sending the email to. It's not
really an option to put environment variables on his machine and make him
change them everytime he wants to send an email with a different outgoing
address. Is there a way to achieve this with the qmail control files?

Please advise.

Thanks,
Mike





Greetings,

I use Netscape Messenger quite extensively and I noticed that when I
setup mail filters, there's a greyed out box indicating that it  knows
about server side message filters ... is there a module for qmail that
enables this feature?

Regards,
Brice Ruth





* David Dyer-Bennet <[EMAIL PROTECTED]> writes:

> All the very-fast typists I know use Qwerty (and I know one who tests
> over 150 WPM).

<URL:http://attrition.org/gallery/ms/win2k-kbd.jpg>
-- 
Robin S. Socha <http://socha.net/>
<URL:http://attrition.org/gallery/ms/ms-keys.gif>




Is there a way to make qmail defer messages in the event of an NFS outage
that does *not* involve creating a user database?

The project I am working on involves three mail servers, each with an NFS
connection to the user directories.  No user information is stored locally
on any of the machines; I use a modified version of qmail-getpw to validate
user names via the network (my company is willing to sacrifice the necessary
local bandwidth for this to work).  Because there is no local storage of
information, keeping the user database updated would involve a periodic
query across the network for an updated list of user names.  My company
feels/hopes that we will be servicing enough users to make this approach
impractical, as users will be constantly added and removed from the system.

So far my results have been successful.  All is well when the network is
behaving itself, and qmail defers messages properly when qmail-getpw fails
due to a bad network connection.  A contingency for a failed NFS mount is
one of my last hurdles to getting this all in place.  I'm open to any ideas,
from .qmail tricks to code patching.

---Kris Kelley





On Wed, Oct 04, 2000 at 03:18:35PM -0500, Kris Kelley wrote:
[snip]
> So far my results have been successful.  All is well when the network is
> behaving itself, and qmail defers messages properly when qmail-getpw fails
> due to a bad network connection.  A contingency for a failed NFS mount is
> one of my last hurdles to getting this all in place.  I'm open to any ideas,
> from .qmail tricks to code patching.

Ok, let's do this out of order.
.qmail tricks - doing a deferral from ~alias/.qmail-default if the user
seems valid?

Or, *duh*: the homedir check is in qmail-getpw. Since you've already
modified it, modify it some more :)

Greetz, Peter
-- 
dataloss networks
'/ignore-ance is bliss' - me




On Wed, Oct 04, 2000 at 10:38:33PM +0200, Peter van Dijk wrote:
> On Wed, Oct 04, 2000 at 03:18:35PM -0500, Kris Kelley wrote:
> [snip]
> > So far my results have been successful.  All is well when the network is
> > behaving itself, and qmail defers messages properly when qmail-getpw fails
> > due to a bad network connection.  A contingency for a failed NFS mount is
> > one of my last hurdles to getting this all in place.  I'm open to any ideas,
> > from .qmail tricks to code patching.
> 
> Ok, let's do this out of order.
> .qmail tricks - doing a deferral from ~alias/.qmail-default if the user
> seems valid?
> 
> Or, *duh*: the homedir check is in qmail-getpw. Since you've already
> modified it, modify it some more :)

Right. But he may not actually have to check for the existance of HOME currently
and in any event there is a timing window between qmail-getpw and the 
invocation of qmail-local. So it may disappear after the check in qmail-getpw.

Having said all that, qmail-local exit with a *temp* error if it cannot
stat the home directory, so I'm not sure what the exact problem is. If the
nfs home is gone, then this stat() should fail at some point and defer
the delivery.

The only general problem is that the NFS timeouts may clog the concurrencylocal
limits, but then if you have no homes, there's nothing to delivery anyway.



code frgament:

 if (stat(".",&st) == -1)
   strerr_die3x(111,"Unable to stat home directory: ",error_str(errno),". (#4.3.0)");

doc fragment:

 111 means that the delivery
     failed  but  should  be  tried again in a little while (soft
     error).


Regards.




since you have already gone into qmail-getpw.c, 
play with it a bit more.  what we did was modify
it to exit 111 if a control file exists in /var/qmail/control/...

hmm.  i guess this only works when you know ahead
of time you'll be bring stuff down or have noticed a
major problem occurring.    markd seems to have a
good solution for intermittent NFS problems.

-- 
Michael Boyiazis
[EMAIL PROTECTED]
Mail Architect, NetZero, Inc.

> -----Original Message-----
> From: Kris Kelley [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 04, 2000 1:19 PM
> To: QMail Mailing List
> Subject: NFS without a user database?
> 
> 
> Is there a way to make qmail defer messages in the event of 
> an NFS outage
> that does *not* involve creating a user database?
> 






On Wed, Oct 04, 2000 at 01:40:53PM -0700, [EMAIL PROTECTED] wrote:
[snip]
> > 
> > Ok, let's do this out of order.
> > .qmail tricks - doing a deferral from ~alias/.qmail-default if the user
> > seems valid?
> > 
> > Or, *duh*: the homedir check is in qmail-getpw. Since you've already
> > modified it, modify it some more :)
> 
> Right. But he may not actually have to check for the existance of HOME currently
> and in any event there is a timing window between qmail-getpw and the 
> invocation of qmail-local. So it may disappear after the check in qmail-getpw.

That's what I thought, I considered a race attack, but there is none.
qmail-local *defers* on homedir failures. Only qmail-getpw actually
*bounces* on homedir failures.

He's using a *modified* qmail-getpw, not a rewritten one. The homedir
check is probably just still in there.

> Having said all that, qmail-local exit with a *temp* error if it cannot
> stat the home directory, so I'm not sure what the exact problem is. If the
> nfs home is gone, then this stat() should fail at some point and defer
> the delivery.

Yeah, that's because qmail-getpw does the bouncing.

> The only general problem is that the NFS timeouts may clog the concurrencylocal
> limits, but then if you have no homes, there's nothing to delivery anyway.

That depends. Where I work we have homedirs spread over about 40
userservers, which means indeed one can be down while the others are up.
I modified my checkpassword replacements (which uses files in the
homedir) to kill itself after 1 second, just because of broken NFS
stuff.

Greetz, Peter
-- 
dataloss networks
'/ignore-ance is bliss' - me




On Wed, Oct 04, 2000 at 01:50:51PM -0700, Michael Boyiazis wrote:
> since you have already gone into qmail-getpw.c, 
> play with it a bit more.  what we did was modify
> it to exit 111 if a control file exists in /var/qmail/control/...

Hmm nice thought, that means remote deliveries are still working, and
the todo queue isn't growing either because you don't have to shutdown
qmail itself.

> hmm.  i guess this only works when you know ahead
> of time you'll be bring stuff down or have noticed a
> major problem occurring.    markd seems to have a
> good solution for intermittent NFS problems.

Nope, he's missing points. Modifying qmail-getpw is the way :)

Greetz, Peter
-- 
dataloss networks
'/ignore-ance is bliss' - me




Peter van Dijk and markd wrote:
> > > Or, *duh*: the homedir check is in qmail-getpw. Since you've already
> > > modified it, modify it some more :)
> >
> > Right. But he may not actually have to check for the existance of HOME
currently
> > and in any event there is a timing window between qmail-getpw and the
> > invocation of qmail-local. So it may disappear after the check in
qmail-getpw.
>
> That's what I thought, I considered a race attack, but there is none.
> qmail-local *defers* on homedir failures. Only qmail-getpw actually
> *bounces* on homedir failures.
>
> He's using a *modified* qmail-getpw, not a rewritten one. The homedir
> check is probably just still in there.
>
> > Having said all that, qmail-local exit with a *temp* error if it cannot
> > stat the home directory, so I'm not sure what the exact problem is. If
the
> > nfs home is gone, then this stat() should fail at some point and defer
> > the delivery.
>
> Yeah, that's because qmail-getpw does the bouncing.

Makes sense.  Okay, so if I make qmail-getpw either not do a directory
check, or handle the results differently, then there shouldn't be any lost
or bounced email, even if the NFS mount happens to disappear between
qmail-getpw and qmail-local.  Correct?

> > The only general problem is that the NFS timeouts may clog the
concurrencylocal
> > limits, but then if you have no homes, there's nothing to delivery
anyway.
>
> That depends. Where I work we have homedirs spread over about 40
> userservers, which means indeed one can be down while the others are up.

There will only be one server for user directories, at least to begin with.
So, yeah, hitting the concurrencylocal limit won't be an issue.

Michael Boyiaz's idea is a good one too.  Sounds like it would make planned
outages easy to wade through.

Thanks for the input!

---Kris Kelley





On Wed, Oct 04, 2000 at 04:22:42PM -0500, Kris Kelley wrote:
[snip]
> > Yeah, that's because qmail-getpw does the bouncing.
> 
> Makes sense.  Okay, so if I make qmail-getpw either not do a directory
> check, or handle the results differently, then there shouldn't be any lost
> or bounced email, even if the NFS mount happens to disappear between
> qmail-getpw and qmail-local.  Correct?

Correct.

If you're using users/assign, qmail-getpw is skipped, but qmail-local
isn't. Empirical proof that qmail-local doesn't bounce on broken homedirs :)

> > > The only general problem is that the NFS timeouts may clog the
> concurrencylocal
> > > limits, but then if you have no homes, there's nothing to delivery
> anyway.
> >
> > That depends. Where I work we have homedirs spread over about 40
> > userservers, which means indeed one can be down while the others are up.
> 
> There will only be one server for user directories, at least to begin with.
> So, yeah, hitting the concurrencylocal limit won't be an issue.

Good.

> Michael Boyiaz's idea is a good one too.  Sounds like it would make planned
> outages easy to wade through.

Jups, think I'm gonna steal that one a bit :)

Greetz, Peter
-- 
dataloss networks
'/ignore-ance is bliss' - me




If you receive this note, please ignore.

Thank you for you patience.
-- 

Subba Rao
[EMAIL PROTECTED]




Hello all,

Problem 1: When starting qmail under svscan via the startup script (I'm
using Life With Qmail as my guide), I get errors complaining about being
unable to acquire a lock of certain files:
Supervise: fatal: unable to acquire qmail-send/supervise/lock: temporary
failure
Supervise: fatal: unable to acquire log/supervise/lock: temporary failure
Supervise: fatal: unable to acquire qmail-smtpd/supervise/lock: temporary
failure
Supervise: fatal: unable to acquire log/supervise/lock: temporary failure

My guess is that this is a permission or ownership problem? I tried
chmodding the directories the lock files are in to 777 and deleted the lock
files, but no dice. Any ideas?

Problem 2: When I manually start qmail (no svscan running), I am able to
connect to port 110, but only for a moment. It immediately disconnects me
like so:
Trying my.ip.address...
Connected to dellhost.wierd.ip.address (my.ip.address)
Escape character is '^]'.
Connection closed by foreign host.

I am able to manually run qmail-popup like this:
/var/qmail/bin/qmail-popup host /bin/checkpassword pwd

Do you think my problem has to do with my pop3 entry in inetd.conf? What
should my entry to inetd.conf look like? Thanks for any help anyone can
offer.

Gregg





Recently I was reading the cyrus-imap howto, and the included excerpt 
included instructions for sendmail or postfix.  What's the equivalent I need 
for qmail?  Thanks.

<exerpt>

6.3 More configuration file editing

Edit /etc/services and check for the following lines. If they do not exist, 
add them:         pop3    110/tcp
        imap    143/tcp
        imsp    406/tcp
        kpop    1109/tcp
        sieve   2000/tcpEdit /etc/inetd.conf and comment out any imap and 
pop3 lines and add the following:         imap    stream  tcp     nowait  
cyrus   /usr/cyrus/bin/imapd    imapd
        pop3    stream  tcp     nowait  cyrus   /usr/cyrus/bin/imapd    
pop3dEdit /etc/sendmail.mc with care not to add extra spaces and add the 
following lines(do not copy and paste directly from this text as the tabs 
won't be added correctly):   MAILER(local)
  MAILER(cyrus)
  define(`confLOCAL_MAILER',`cyrus') 
  LOCAL_RULE_0
  R$=N                   $: $#local $: $1
  R$=N < @ $=w . >       $: $#local $: $1
  Rbb + $+ < @ $=w . >   $#cyrusbb $: $1 Use tabs to separate the data (i.e. 
R$=N has three tabs between it and $: $#local $: $1) Then run: m4 sendmail.mc 
> sendmail.cfEdit /etc/group and add the user daemon to the mail group.6.4 If 
you use postfix instead of sendmail

Postfix is a mail-deliver alternative to sendmail. Most linux installations 
use sendmail by default. If you use postfix, ignore configuration #3 from the 
last section and uncomment or add the following line in 
/etc/postfix/master.cf 

cyrus   unix    -       n       n       -       -       pipe    flags=R 
user=cyrus      argv=/usr/sbin/cyrdeliver -e -m ${extension} ${user}

Also add or uncomment this line in /etc/postfix/main.cf 

</excerpt>

-- 
Casey Allen Shobe / ASI Technologies
[EMAIL PROTECTED] / [EMAIL PROTECTED]
UIN: 1494523 / IRC: cshobe / http://cshobe.myip.org
Slackware 7.1 / Linux Echelon-Pro 2.4.0-test8 i686




Hello everyone,

I using qmail 1.03 with vpopmail and sqlwebmail.

Question 1 - When I add a new user via qmailadmin I see the user in
/var/vpopmail/domain/nameofdomain/user.  but the /var/qmail/users/assign
file only has one entry (the one it created when I added the domain.  Is the
assign file supposed to be updated every time I add a new virtual user. I
manually run qmail-newu, no luck.

Question 2 - Every time I send a email to a virtual user it get stuck in the
queue and the log file says "unable to change dir #4.2.1

I'm running the pop3 daemon as vpopmail.


Any help would be greatly appreciated


TIA

Eddie Greer







I've set-up pop3d using supervise and tried to get it to log
/something/, however nothing ever comes out. I'm very interested to see
the number of concurrent connections similar to the way the other qmail
programs do (send and smtpd). Any way to do it?

Here's my pop3d/run file:

   #!/bin/sh
   
   QMAILDUID=`id -u qmaild`
   NOFILESGID=`id -g qmaild`
   
   exec tcpserver -R -x/etc/tcp.pop3d.cdb 0 pop3 \
   /var/qmail/bin/qmail-popup mail.vcnet.com \
   /var/qmail/bin/checkpoppasswd /var/qmail/sbin/relay-ctrl-allow \
   /var/qmail/bin/qmail-pop3d Maildir 2>&1

Here's my pop3d/log/run file:

   #!/bin/sh
   exec /usr/local/bin/setuidgid qmaill \
   /usr/local/bin/multilog t /var/log/pop3d

I take it qmail-pop3d just isn't verbose like qmail-send and
qmail-smtpd?

Thanks,
jon






On  0, Subba Rao <[EMAIL PROTECTED]> wrote:
> If you receive this note, please ignore.
> 
> Thank you for you patience.

I have sent this earlier note to test duplicate subscription. It looks like
qmail list server accepts subscriptions from the same address without checking
the subscription status. That was the reason why I have been getting duplicate
copies.

I don't know who the list admin is, but I hope he sees this note.

Thank you.
-- 

Subba Rao
[EMAIL PROTECTED]
http://pws.prserv.net/truemax/




also sprach subb3:
> On  0, Subba Rao <[EMAIL PROTECTED]> wrote:
> > If you receive this note, please ignore.
> > 
> > Thank you for you patience.
> 
> I have sent this earlier note to test duplicate subscription. It looks like
> qmail list server accepts subscriptions from the same address without checking
> the subscription status. That was the reason why I have been getting duplicate
> copies.

You might check the full headers of each of the apparent duplicates. More
than likely, the Return-Path: header will differ; usually, you have more
than one address subscribed to the list.

/pg
-- 
Peter Green : Gospel Communications Network, SysAdmin : [EMAIL PROTECTED]
---
(It's sorta like sed, but not. It's sorta like awk, but not. etc.)
Guilty as charged. Perl is happily ugly, and happily derivative.
--- Larry Wall in <[EMAIL PROTECTED]>





Hi all,
I am just starting to build our first qmail internet email server, and am
having alot of problems with getting qmail to run.
Basically everything about qmail works. I've gone through the INSTALL file
and am running Maildir and all mail locally on the server is working fine.
It's the setting up of the pop mail services that has me stumped.
Ive taken the steps from the FAQ regarding pop3d setup, and have installed
tcpserver and checkpassword successfully, but still no luck. I've entered
the following into SUSE's boot.local file: (As told by the FAQ - domain is
an example)

tcpserver 0 pop3 /var/qmail/bin/qmail-popup qmail-popup lisp.com.au
/bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir &
(all in one line)

But that just makes the system lockup and eventually time out when the
boot.local service tries to run upon system startup. Now, the FAQ states
that if tcpserver is installed then you shouldnt have a line in the
inetd.conf file on pop3. So I have removed the line as shown in the FAQ:

pop3 stream tcp nowait root /var/qmail/bin/qmail-popup qmail-popup
lisp.com.au /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir

Even though if I have this line running and the boot.local line removed the
system boots ok, and i can check mail from another computer via email
client software (O.E.5), i just cant send.

I'm running SUSE 6.4 with qmail 1.03. If SUSE is the problem then someone
please tell me that SUSE is no good and that I should switch to redhat.

Any help in this matter would be appreciated eternally. Better yet, if
anyone knows of good docs on setting up "qmail for internet email" then
could you please let me know.

Regards,

Daniel
___________________________________________________________
Daniel Knights
Highway Internet Services               ABN: 14 088 130 269
Part of the LiSP Group          http://www.lisp.com.au
Servicing the Dubbo, Mudgee, Coonabarabran, Gilgandra, Warren,
Wellington and surrounding areas.
Enquiries 02 6372 3645          129 Market St, Mudgee 2850





Hi Daniel

I was faced the same problem two months ago and I was provided with
great help from the list. My big problems were problems in the config
files. Especially your tcp-server problems seem to occur for this
reason. So I sent you my startup script for tcpserver. I have the same
Configuration as you so you should have not a big problem to adapt it to
your setup.

Just call it in the appropriate rc.x level and everything should be
fine.

The documentation you asked for is Dave sills Life with qmail. I think
you yet found it. When I had problems I was also looking for further
documentation but finally I discouvered that you could really everything
to work with LWQ.

hth

/ch




Please teach me how should I control with qmail server to be able to be received
      mails only through the router on witch Virus check is active.

my mail address is :

      [EMAIL PROTECTED]






G'day all

I'm in need of some sanity. Does a patch exist, or does anyone want to make
one, to make multilog rotate logs based on time rather than file size? I
hope that I don't even have to start explaining why...The word
'standardisation' comes to mind. It's like comparing America to Australia.
Why do America have to make everything back-to-front for us? The same goes
for multilog... I want to be able to archive logs easily, analyse them
easily. Tell me how I can do that if I am limited by file size. A bulk
e-mail that I'm not expecting will wipe my files out of existance. Sure I
can make the number of files I keep bigger, but is that really a fix? More
its an unnecessary hassle getting in the way. Using tai64 time format, I
kind of understand. It makes some degree of sense, even if it is annoying to
read straight out. But size-based log rotation with no option for time? OK
someone's been smoking some big time drugs here... Oh and before you say try
the !processor directive, I did but to no avail...There is probably a whole
paragraph of information on it spanned across the Internet. Great. No
examples anywhere really though...

Thanks for perusing this query

/BR

Manager
InterPlanetary Solutions
http://ipsware.com/






do there exist any solutions for clustering qmail to build high-volume-servers
??
i`m looking for some tools or patches to do load-balancing, put pop-boxes on
more than one server, use more than one smtp-server...
help???

thx





>do there exist any solutions for clustering qmail to build high-volume-servers
>i`m looking for some tools or patches to do load-balancing, put pop-boxes on
>more than one server, use more than one smtp-server...
>help???

There are several server load balancer solutions available. I use the
'ServerIron' product from Foundry Networks (www.foundrynet.com), it seems
to perform very well. You also have Alteon (www.alteonwebsystems.com),
cisco, and others.

These boxes are regular layer-2 switches. In addition to
switching packets like other switches, they perform load balancing.
One way they can do this is to reply to ARP requests
for the IP addresses your mail server is known by on the Internet.
Your router will therefore send all incoming IP packets to the ethernet
address of the switch. The switch will pick up a packet, choose the
front-end mail processor (FEP) it thinks has the lowest load at the moment,
put that ethernet address on the packet instead of its own and put
the packet back on the wire for the FEP to pick up.

The switch also monitors the FEP's and routes connection requests to
other working servers if a FEP is discovered to be faulty. This makes error
situations and maintainance downtime invisible to the clients.

-- 
Gjermund Sorseth




None as such..I have been meaning to write a HOWTO for something similar but
this year has just been crazy...maybe next year. BUT some suggestions:

- Look into a NFS/NIS combination (I use this for a distributed e-mail
system currently spanning a city, soon to be spanning several locations on
the planet)
- AFS (Andrew File System) also looks interesting for some real hard-core
distributed, clustered work

There are probably other ideas, but those are the two I would look into
first.

/BR

Manager
InterPlanetary Solutions
http://ipsware.com/


> -----Original Message-----
> From: Thomas Ackermann [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 05, 2000 6:50 PM
> To: MailingList Qmail
> Subject: Clustering Qmail
>
>
> do there exist any solutions for clustering qmail to build
> high-volume-servers
> ??
> i`m looking for some tools or patches to do load-balancing, put
> pop-boxes on
> more than one server, use more than one smtp-server...
> help???
>
> thx
>



Reply via email to