Re: [toaster] checkuser problem
Hello, no settings found in whole source. here is my chkuser_settings.h file. I'm ussing qmail-toaster-0.8.3. Thank you. --- Lampa 2007/5/9, tonix (Antonio Nati) <[EMAIL PROTECTED]>: At 23.32 09/05/2007, you wrote: Hello, i found weird behaviour if checkuser with smtp auth If user is autheticated, there is not checked if dest domain is valid (maybe if recips exists) - eg possible to send email to invalid domain. trying to send email to [EMAIL PROTECTED]' (yes at end is ') - is not valid email, i know but tell this to some non technical people ;) non auth user @4000464239dd28198a84 CHKUSER accepted sender: from <[EMAIL PROTECTED]::> remote rcpt <> : sender accepted @4000464239dd28c98164 CHKUSER rejected relaying: from <[EMAIL PROTECTED]::> remote rcpt <[EMAIL PROTECTED]'> : client not allowed to relay auth user @40004642390d107ee0a4 CHKUSER accepted sender: from <[EMAIL PROTECTED]:[EMAIL PROTECTED]:> remote rcpt <> : sender accepted @40004642390d113305d4 CHKUSER relaying rcpt: from <[EMAIL PROTECTED]:[EMAIL PROTECTED]:> remote rcpt <[EMAIL PROTECTED]'> : client allowed to relay from log, non auth user cannot send email to bad domain but auth can. Maybe i have wrong settings of checkuser. Yes, probably you have disabled chkuser for authenticated users. Check is there is any option like CHKUSER_DISABLE_VARIABLE enabled. Ciao, Tonino Thank you for your help. --- Lampa chkuser_settings.h Description: Binary data
Re: [toaster] checkuser problem
At 23.32 09/05/2007, you wrote: Hello, i found weird behaviour if checkuser with smtp auth If user is autheticated, there is not checked if dest domain is valid (maybe if recips exists) - eg possible to send email to invalid domain. trying to send email to [EMAIL PROTECTED]' (yes at end is ') - is not valid email, i know but tell this to some non technical people ;) non auth user @4000464239dd28198a84 CHKUSER accepted sender: from <[EMAIL PROTECTED]::> remote rcpt <> : sender accepted @4000464239dd28c98164 CHKUSER rejected relaying: from <[EMAIL PROTECTED]::> remote rcpt <[EMAIL PROTECTED]'> : client not allowed to relay auth user @40004642390d107ee0a4 CHKUSER accepted sender: from <[EMAIL PROTECTED]:[EMAIL PROTECTED]:> remote rcpt <> : sender accepted @40004642390d113305d4 CHKUSER relaying rcpt: from <[EMAIL PROTECTED]:[EMAIL PROTECTED]:> remote rcpt <[EMAIL PROTECTED]'> : client allowed to relay from log, non auth user cannot send email to bad domain but auth can. Maybe i have wrong settings of checkuser. Yes, probably you have disabled chkuser for authenticated users. Check is there is any option like CHKUSER_DISABLE_VARIABLE enabled. Ciao, Tonino Thank you for your help. --- Lampa
Re: [toaster] checkuser problem
At 23.32 09/05/2007, you wrote: Hello, i found weird behaviour if checkuser with smtp auth If user is autheticated, there is not checked if dest domain is valid (maybe if recips exists) - eg possible to send email to invalid domain. trying to send email to [EMAIL PROTECTED]' (yes at end is ') - is not valid email, i know but tell this to some non technical people ;) non auth user @4000464239dd28198a84 CHKUSER accepted sender: from <[EMAIL PROTECTED]::> remote rcpt <> : sender accepted @4000464239dd28c98164 CHKUSER rejected relaying: from <[EMAIL PROTECTED]::> remote rcpt <[EMAIL PROTECTED]'> : client not allowed to relay auth user @40004642390d107ee0a4 CHKUSER accepted sender: from <[EMAIL PROTECTED]:[EMAIL PROTECTED]:> remote rcpt <> : sender accepted @40004642390d113305d4 CHKUSER relaying rcpt: from <[EMAIL PROTECTED]:[EMAIL PROTECTED]:> remote rcpt <[EMAIL PROTECTED]'> : client allowed to relay from log, non auth user cannot send email to bad domain but auth can. Maybe i have wrong settings of checkuser. Yes, probably you have disabled chkuser for authenticated users. Check is there is any option like CHKUSER_DISABLE_VARIABLE enabled. Ciao, Tonino Thank you for your help. --- Lampa
Re: [toaster] simscan: connect error 2
/home/vpopmail/etc/tcp.smtp ?? 127.:allow,RELAYCLIENT="" :allow,QMAILQUEUE="/var/qmail/bin/simscan",NOP0FCHECK="1" ACK.
[toaster] checkuser problem
Hello, i found weird behaviour if checkuser with smtp auth If user is autheticated, there is not checked if dest domain is valid (maybe if recips exists) - eg possible to send email to invalid domain. trying to send email to [EMAIL PROTECTED]' (yes at end is ') - is not valid email, i know but tell this to some non technical people ;) non auth user @4000464239dd28198a84 CHKUSER accepted sender: from <[EMAIL PROTECTED]::> remote rcpt <> : sender accepted @4000464239dd28c98164 CHKUSER rejected relaying: from <[EMAIL PROTECTED]::> remote rcpt <[EMAIL PROTECTED]'> : client not allowed to relay auth user @40004642390d107ee0a4 CHKUSER accepted sender: from <[EMAIL PROTECTED]:[EMAIL PROTECTED]:> remote rcpt <> : sender accepted @40004642390d113305d4 CHKUSER relaying rcpt: from <[EMAIL PROTECTED]:[EMAIL PROTECTED]:> remote rcpt <[EMAIL PROTECTED]'> : client allowed to relay from log, non auth user cannot send email to bad domain but auth can. Maybe i have wrong settings of checkuser. Thank you for your help. --- Lampa
RE: [toaster] simscan: connect error 2
> Thanks Noel and Bill > By the way where do you put this entry > > export QMAILQUEUE=/var/qmail/bin/simscan > export NOP0FCHECK=1 > export SIMSCAN_DEBUG=2 > > Sorry asking such a dumb question. > > Regards. > > -Original Message- > From: Bill Shupp [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 10, 2007 3:13 AM > To: toaster@shupp.org > Subject: Re: [toaster] simscan: connect error 2 > > Noel Sanchez wrote: >>> Hi All, >>> >>> I am using the latest toaster version and getting this error, is it >>> normal? and i noticed email with this error doesn't go through. I read >>> mail archive said this error was fix with the version of 1.3x. Really >>> need help on this. >>> >>> Thanks in Advance. >>> >>> >>> >>> >> I had a siliar problem and followed this advice and found a fix: >> >> http://osdir.com/ml/mail.qmail.simscan/2007-01/msg2.html >> >> > > It appears that it's related to the new "p0f passive finger printing > with poor mans greylisting for unknown windows senders" feature. Can > anyone attest to how useful this is? I've not looked at it closely yet. > > Regards, > > Bill > > /home/vpopmail/etc/tcp.smtp ?? 127.:allow,RELAYCLIENT="" :allow,QMAILQUEUE="/var/qmail/bin/simscan",NOP0FCHECK="1"
Re: [toaster] simscan: connect error 2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bill Shupp wrote: > It appears that it's related to the new "p0f passive finger printing > with poor mans greylisting for unknown windows senders" feature. Can > anyone attest to how useful this is? I've not looked at it closely yet. Inter7 is pulling this out of simscan. I believe they have a patch for qmail-queue instead, but I'm not 100% certain. Either way, when the new version is released, p0f will not be part of it. (Tho a bunch of bugfixes and features will be! yay!) > Regards, > > Bill - -- - --- Jason 'XenoPhage' Frisvold Engine / Technology Programmer [EMAIL PROTECTED] RedHat Certified - RHCE # 803004140609871 MySQL Pro Certified - ID# 207171862 MySQL Core Certified - ID# 205982910 - --- "Something mysterious is formed, born in the silent void. Waiting alone and unmoving, it is at once still and yet in constant motion. It is the source of all programs. I do not know its name, so I will call it the Tao of Programming." -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGQiEjhR5xme3cl74RAk0YAKDFGXLgdfo0NwNuMagku4hlTGgWVwCgoL1L /OMUVpLe6aXnVUqR0kaHEBs= =Qfdz -END PGP SIGNATURE-
RE: [toaster] simscan: connect error 2
Thanks Noel and Bill By the way where do you put this entry export QMAILQUEUE=/var/qmail/bin/simscan export NOP0FCHECK=1 export SIMSCAN_DEBUG=2 Sorry asking such a dumb question. Regards. -Original Message- From: Bill Shupp [mailto:[EMAIL PROTECTED] Sent: Thursday, May 10, 2007 3:13 AM To: toaster@shupp.org Subject: Re: [toaster] simscan: connect error 2 Noel Sanchez wrote: >> Hi All, >> >> I am using the latest toaster version and getting this error, is it >> normal? and i noticed email with this error doesn't go through. I read >> mail archive said this error was fix with the version of 1.3x. Really >> need help on this. >> >> Thanks in Advance. >> >> >> >> > I had a siliar problem and followed this advice and found a fix: > > http://osdir.com/ml/mail.qmail.simscan/2007-01/msg2.html > > It appears that it's related to the new "p0f passive finger printing with poor mans greylisting for unknown windows senders" feature. Can anyone attest to how useful this is? I've not looked at it closely yet. Regards, Bill
Re: [toaster] simscan: connect error 2
Noel Sanchez wrote: >> Hi All, >> >> I am using the latest toaster version and getting this error, is it >> normal? and i noticed email with this error doesn't go through. I read >> mail archive said this error was fix with the version of 1.3x. Really >> need help on this. >> >> Thanks in Advance. >> >> >> >> > I had a siliar problem and followed this advice and found a fix: > > http://osdir.com/ml/mail.qmail.simscan/2007-01/msg2.html > > It appears that it's related to the new "p0f passive finger printing with poor mans greylisting for unknown windows senders" feature. Can anyone attest to how useful this is? I've not looked at it closely yet. Regards, Bill
Re: [toaster] simscan: connect error 2
> Hi All, > > I am using the latest toaster version and getting this error, is it > normal? and i noticed email with this error doesn't go through. I read > mail archive said this error was fix with the version of 1.3x. Really > need help on this. > > Thanks in Advance. > > > I had a siliar problem and followed this advice and found a fix: http://osdir.com/ml/mail.qmail.simscan/2007-01/msg2.html I also noticed that some of my permissions on /etc/mail/spamassassin/.spamassassin/bayes* were wrong.
[toaster] simscan: connect error 2
Hi All, I am using the latest toaster version and getting this error, is it normal? and i noticed email with this error doesn't go through. I read mail archive said this error was fix with the version of 1.3x. Really need help on this. Thanks in Advance.