[vchkpw] relay in vpopmail 5.4.6

2004-09-06 Thread Itamar Reis Peixoto



I have compiled vpopmail 5.4.6 with mysql 
support.
 
the configure says:

 tcpserver file = 
/home/vpopmail/etc/tcp.smtp open_smtp file = 
/home/vpopmail/etc/open-smtp

the relay table is stored in mysql


how can i use the -x option or other option to open 
relay.


i am using --enable-roaming-users=y 
option.

thank you.


Itamar Reis PeixotoAnalista 
ConsultorTreyNet Consultoria - UberlândiaTel : + 55 34 3231 
0598Cel: +55 38 9107 1250http://www.treynet.com.br


[vchkpw] Silly Qmail (Queue) Syndrome and Spamcontrol Patch

2004-09-06 Thread Devendra Singh
Dear Erwin,
Sorry for question not really related to Vpopmail.
It seems that I am hit by Silly Qmail (Queue) Syndrome.
I am using the Spamcontrol Patch v2.2.12 along with vpopmail-5.4.6, but 
have not used the experimental bigtodo.

Wished to apply the bigtodo. I would like to get clarified that whether you 
bigtodo is based on ext_todo patch or big-todo patch or both. I had not 
initially compiled the bigtodo thinking that it is experimental.

What do you suggest.
Thanks.
Devendra Singh


Re: [vchkpw] Silly Qmail (Queue) Syndrome and Spamcontrol Patch

2004-09-06 Thread Erwin Hoffmann
Hi,

At 20:11 06.09.04 +0530, you wrote:
Dear Erwin,

Sorry for question not really related to Vpopmail.

It seems that I am hit by Silly Qmail (Queue) Syndrome.

I am using the Spamcontrol Patch v2.2.12 along with vpopmail-5.4.6, but 
have not used the experimental bigtodo.

Wished to apply the bigtodo. I would like to get clarified that whether you 
bigtodo is based on ext_todo patch or big-todo patch or both. I had not 
initially compiled the bigtodo thinking that it is experimental.

What do you suggest.

Well. At first you have to tell why you think you are hit by the Silly
Qmail Syndrom. Any hints ?

Second. Apart from the big-todo enhencement, my implementation of Andre
Oppermann's performance enhancements dont work well. After investigation a
look of time and testing I didn't find any significant performance
improvement.
Note: The code in SPAMCONTROL is not the ext-big-todo; however it is based
of Andre's first suggestion to influence qmail's scheduler for mail
processing; which was buggy by itself.

Third. The best thing is to avoid bounces to non-existing accounts. 
Use my RECIPIENTS extension as part of Qmail or perhaps the real-rcptto
patch.

The forthcoming SPAMCONTROL version will include verion 0.42 of the
RECIPIENTS extension; check my Qmail page (http://www.fehcom.de/qmail.html).

regards.
--eh.


Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de/
Wiener Weg 8, 50858 Cologne | T: +49 221 484 4923 | F: ...24


Re: [vchkpw] maildrop+vpopmail help required

2004-09-06 Thread Rick van Vliet
Tanmaya Anand scribbled the following on 9/7/2004 11:00 AM:
Hi All,
 
I have netqmail+vpopmail+courier+sqwebmail.
This is working fine.
I have installed spamassassin  maildrop,
but unable to get it working.
 
Can anyone tell me contents of maildroprc
and other relevent info to get it working.
 
Thanks in advance,
Tanmay
 
Hi-
This doesn't help you with precisely your question, but *procmailrc* works very 
nicely on many systems.
Here's a resource that might help you with that setup
http://beret.net/vpopmail_procmail.php

And while you're at it, which part of the SA/maildrop isn't working? You might 
try google.com and search,
or...
look into archives for Spamassassin and/or maildrop for more specific help.

Rick



Re: [vchkpw] maildrop+vpopmail help required

2004-09-06 Thread Charles M. Gerungan
Hello Tanmaya,

Tue, 7 Sep 2004 21:30:36 +0530 UTC,  Tanmaya Anand wrote:

TA I have installed spamassassin   maildrop,
TA but unable to get it working.

Search Google for maildrop qmail vpopmail and look for a site by
Almqvist.

But are you really sure that you want to use SA from maildrop? I would
run it from qmail_queue.

-- 
Regards, Charles.


pgpJ3F5ifD4gW.pgp
Description: PGP signature


Re: [vchkpw] relay in vpopmail 5.4.6

2004-09-06 Thread Ken Jones
On Monday 06 September 2004 08:38 am, Itamar Reis Peixoto wrote:
 I have compiled vpopmail 5.4.6 with mysql support.

 the configure says:

 tcpserver file = /home/vpopmail/etc/tcp.smtp
 open_smtp file = /home/vpopmail/etc/open-smtp


 the relay table is stored in mysql


 how can i use the -x option or other option to open relay.

-x /home/vpopmail/etc/tcp.smtp.cdb is the compiled file
using the contents of /home/vpopmail/etc/tcp.smtp and
the contents of the relay table from mysql.

Ken Jones



 i am using --enable-roaming-users=y option.

 thank you.


 Itamar Reis Peixoto
 Analista Consultor
 TreyNet Consultoria - Uberlndia
 Tel : + 55 34 3231 0598
 Cel:  +55 38 9107 1250
 http://www.treynet.com.br


[vchkpw] vpopmail/qmail doublebounce issue

2004-09-06 Thread Tom Harrison
First time poster Have mercy on the neophyte!
Can anyone point me to the right documentation source for properly 
configuring vpopmail+qmail so that doublebounces don't hang in the queue?

My son had been managing this system, but got too busy, so I have to come 
up to speed just as Comcast decided that all the SPAM bouncing back out of 
our system was SPAM originating from our system, and quit allowing us to 
relay through their server.

Originally, to mollify the ISPs that refuse mail from floating IPs, we had 
smtproutes set thusly:

:SMTP.Comcast.Net
Fine, until they got tired of processing the SPAM bounces.
So, I peeled smtproutes back to:
AOL.Com:SMTP.Comcast.Net
...so that at least the AOL mail from us would get delivered.
Our server hosts several very small domains: TS5.Com, TS4.Com, and 
Christy9.Com. The system ME is mail.ts5.com.

I noticed after removing Comcast as the relay that the queue began filling 
with doublebounces, addressed to [EMAIL PROTECTED], and the log 
indicated tons of entries like this:

@400041372d553b41077c new msg 3794941
@400041372d553b410b64 info msg 3794941: bytes 11149 from [EMAIL PROTECTED] qp 
13481 uid 507
@400041372d5601445164 starting delivery 81338: msg 3794941 to remote 
[EMAIL PROTECTED]
@400041372d5601446cbc status: local 0/10 remote 2/20
@400041372d560fc141ac delivery 81338: deferral: 
Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
@400041372d560fc160ec status: local 0/10 remote 1/20
@400041372d580f829a9c starting delivery 81339: msg 3794751 to remote 
[EMAIL PROTECTED]
@400041372d580f82b5f4 status: local 0/10 remote 2/20
@400041372d581900bfcc delivery 81339: deferral: 
Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
@400041372d581900db24 status: local 0/10 remote 1/20
@

So, vpopmail knows that ts5.com is a local domain, but when the 
doublebounce is generated, it is treating [EMAIL PROTECTED] as a 
remote address. Am I reading that right?

(below: I have redacted the name of the relay server we are using, not 
because it is in any way an open relay -- it isn't, we run it, too -- but 
because the customer wants to remain private)

I temporarily worked around the problem by adding first the entry 
TS5.Com:SMTP.*.Net to smtproutes: no effect.
Then I added mail.TS5.Com:SMTP.*.Net, and the queue began to empty, 
but sent all the doublebounces to the default account [EMAIL PROTECTED] 
instead of to postmaster.

Obviously I don't understand all the flow here, but would sure appreciate 
it if someone could point me to (1) the right documentation to cover this, 
and (2) an appropriate patch to vpopmail+qmail to avoid such heavy SPAM 
issues, like a SMTP-time bounce that works with vpopmail, or other 
technique that works more effectively than receiving all the bad mail, then 
generating bounce messages for them.

'Cause I know sending doublebounces out to another qmail server, and back 
again, ain't the way it should be done!

Tom Harrison
* qmail-showctl *
[EMAIL PROTECTED] bin]# ./qmail-showctl -?
qmail home directory: /var/qmail.
user-ext delimiter: -.
paternalism (in decimal): 2.
silent concurrency limit: 120.
subdirectory split: 23.
user ids: 501, 502, 503, 0, 504, 505, 506, 507.
group ids: 501, 502.
badmailfrom: (Default.) Any MAIL FROM is allowed.
bouncefrom: (Default.) Bounce user name is MAILER-DAEMON.
bouncehost: (Default.) Bounce host name is mail.ts5.com.
concurrencylocal: (Default.) Local concurrency is 10.
concurrencyremote: (Default.) Remote concurrency is 20.
databytes: (Default.) SMTP DATA limit is 0 bytes.
defaultdomain: Default domain name is mail.ts5.com.
defaulthost: (Default.) Default host name is mail.ts5.com.
doublebouncehost: (Default.) 2B recipient host: mail.ts5.com.
doublebounceto: (Default.) 2B recipient user: postmaster.
envnoathost: (Default.) Presumed domain name is mail.ts5.com.
helohost: (Default.) SMTP client HELO host name is mail.ts5.com.
idhost: (Default.) Message-ID host name is mail.ts5.com.
localiphost: (Default.) Local IP address becomes mail.ts5.com.
locals:
me: My name is mail.ts5.com.
percenthack: (Default.) The percent hack is not allowed.
plusdomain: Plus domain name is mail.ts5.com.
qmqpservers: (Default.) No QMQP servers.
queuelifetime: Message lifetime in the queue is 86400 seconds.
rcpthosts:
SMTP clients may send messages to recipients at ts5.com.
SMTP clients may send messages to recipients at ts4.com.
SMTP clients may send messages to recipients at christy9.com.
morercpthosts: (Default.) No effect.
morercpthosts.cdb: (Default.) No effect.
smtpgreeting: (Default.) SMTP greeting: 220 mail.ts5.com.
smtproutes:
SMTP route: aol.com:SMTP.*.Net
SMTP route: ts5.com:SMTP.*.Net
SMTP route: mail.ts5.com:SMTP.*.Net
timeoutconnect: (Default.) SMTP client connection timeout is 60 seconds.
timeoutremote: (Default.) SMTP client data timeout is 1200 seconds.
timeoutsmtpd: (Default.) SMTP server data timeout is 1200 seconds.

Re: [vchkpw] Silly Qmail (Queue) Syndrome and Spamcontrol Patch

2004-09-06 Thread Devendra Singh
At 06/09/04 22:15 (), Erwin Hoffmann wrote:
Hi,
At 20:11 06.09.04 +0530, you wrote:
Dear Erwin,

Sorry for question not really related to Vpopmail.

It seems that I am hit by Silly Qmail (Queue) Syndrome.

I am using the Spamcontrol Patch v2.2.12 along with vpopmail-5.4.6, but
have not used the experimental bigtodo.

Wished to apply the bigtodo. I would like to get clarified that whether you
bigtodo is based on ext_todo patch or big-todo patch or both. I had not
initially compiled the bigtodo thinking that it is experimental.

What do you suggest.
Well. At first you have to tell why you think you are hit by the Silly
Qmail Syndrom. Any hints ?
Second. Apart from the big-todo enhencement, my implementation of Andre
Oppermann's performance enhancements dont work well. After investigation a
look of time and testing I didn't find any significant performance
improvement.
Note: The code in SPAMCONTROL is not the ext-big-todo; however it is based
of Andre's first suggestion to influence qmail's scheduler for mail
processing; which was buggy by itself.
Third. The best thing is to avoid bounces to non-existing accounts.
Use my RECIPIENTS extension as part of Qmail or perhaps the real-rcptto
patch.
The forthcoming SPAMCONTROL version will include verion 0.42 of the
RECIPIENTS extension; check my Qmail page (http://www.fehcom.de/qmail.html).
regards.
--eh.
Hi Erwin,
Thanks for nice reply.
I am attaching Queue Size graph (5 Minute Average) updated Tuesday, 7 
September 2004 at 0:50 (EDT).

You can notice between 0400 - 1000 hrs (EDT) a quite high Mail Queue. 
During that time period the smtpd is running to the tune of 100/100. But 
the send is running to the tune of local 3/15 remote 5/40. The messages in 
queue but not yet preprocessed goes on increasing in wild. When the smtpd 
runs to the tune of 85/100 its all okay. This has started happening on 
almost every start of the week, when huge volume of genuine + virus 
infected customers mails start pouring in.

I am not using RECIPIENTS extension, but using badrcptto for 
whitelisting mechanism, which works very well (might be a bit slow due to 
the reason that lookup is being done into txt database).

I am also using 
http://linux.voyager.hr/ucspi-tcp/tcpserver-limits-2004-07-25.diff patch to 
limit concurrent connection from single IP. This helps identifying Virus 
trodden computers and denying them connection (it's a boon).

I also have Caching-DNS on this Server (djbdns).
About the todo patches the comments of Dave Sill (of Qmail Handbook fame) 
are interesting to note in the thread:

Outbound email rate slows when inbound rate is high
http://groups.google.com/groups?hl=enlr=ie=UTF-8c2coff=1threadm=e6c47de7.0310091325.147cade4%40posting.google.comrnum=2prev=/groups%3Fq%3Dext-todo%26hl%3Den%26lr%3D%26ie%3DUTF-8%26c2coff%3D1%26selm%3De6c47de7.0310091325.147cade4%2540posting.google.com%26rnum%3D2
Also one can have a look at the thread
ext-todo and big-todo patches
http://groups.google.com/groups?hl=enlr=ie=UTF-8c2coff=1threadm=wx0lm56pfo0.fsf%40sws5.ctd.ornl.govrnum=1prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26c2coff%3D1%26q%3Ddave%2Bsill%2Bext-todo%2Band%2Bbig-todo
I tried to apply the patch 
http://www.nrg4u.com/qmail/ext_todo-20030105.patch over and above 
spamcontrol but it failed at:

patch p1  ext_todo-20030105.patch
patching file p1
patching file EXTTODO-INFO
patching file FILES
patching file Makefile
Hunk #2 succeeded at 713 (offset 8 lines).
Hunk #4 succeeded at 818 (offset 8 lines).
Hunk #5 succeeded at 1598 (offset 87 lines).
Hunk #6 succeeded at 1585 (offset 9 lines).
Hunk #7 succeeded at 1694 (offset 87 lines).
patching file TARGETS
Hunk #1 succeeded at 405 (offset 20 lines).
patching file hier.c
Hunk #1 succeeded at 115 with fuzz 1 (offset 7 lines).
patching file install-big.c
patching file qmail-send.c
Hunk #1 FAILED at 1215.
Hunk #2 succeeded at 1527 (offset 88 lines).
Hunk #3 succeeded at 1662 (offset 20 lines).
Hunk #4 succeeded at 1797 (offset 88 lines).
1 out of 4 hunks FAILED -- saving rejects to file qmail-send.c.rej
patching file qmail-start.c
patching file qmail-todo.c
It also might be possible that my disk speed be contributing a bit to the 
bottleneck. Current iostat figures are (not taken at the silly qmail 
syndrome time, I would take that figure to when I am hit again).

iostat -d -x /dev/hda2 2
Linux 2.4.18-18.7.x (slsp-da4p21)   09/07/2004
Device:rrqm/s wrqm/s   r/s   w/s  rsec/s  wsec/srkB/swkB/s 
avgrq-sz avgqu-sz   await  svctm  %util
/dev/hda20.03   2.27  1.85  0.37   14.98   21.73 7.4910.86 
16.57 0.13  208.66 171.08   3.79

Device:rrqm/s wrqm/s   r/s   w/s  rsec/s  wsec/srkB/swkB/s 
avgrq-sz avgqu-sz   await  svctm  %util
/dev/hda20.00   0.00  2.00  0.00   16.000.00 8.00 0.00 
8.00 0.15   75.00  50.00   1.00

Device:rrqm/s wrqm/s   r/s   w/s  rsec/s  wsec/srkB/swkB/s 
avgrq-sz avgqu-sz   await  svctm  %util
/dev/hda20.00   0.00  0.00  0.000.00