Re: [vchkpw] unable to read /etc/tcp.smtp.cdb: out of memory
It worked .. many thanks Christopher Chan wrote: Tariq Azad wrote: I am having following error in log tail -f /var/log/qmail/qmail-smtpd/current warning: dropping connection, unable to read /etc/tcp.smtp.cdb: out of memory on building the cdb file the error disappears for a while but comes up after 5 min or less. Try increasing the amount of memory allowed by tcpserver in your qmail-smtpd run file. !DSPAM:475cfb2932001340983422!
Re: [vchkpw] Qmail Courier-Imap (authlib) and Vpopmail trouble
On Dec 8, 2007, at 4:26 PM, Thiago Camargo Martins Cordeiro wrote: My system is: uname -a Linux devel 2.6.18-xen #1 SMP Mon Dec 3 18:30:06 BRST 2007 x86_64 GNU/Linux I got the same problem on x86_32 too. Always inside a PVM of XEN, out of XEN, vchkpw works fine. I do a workarround with my patched qmail (AUTH_CDB patch) from JMS qmail patch, onchance script maintain a /var/qmail/control/auth.cdb in sync with vpopmail user db, so I can login via smtp-auth with AUTH_CDB qmail patch. But I'd like to see vchkpw working fine inside a virtual machine... :) Is it possible to compile and install vchkpw with debugging information, so we can find out which call to strstr() called the segfault? Or is it the getrlimit() call from the strace? Maybe you could email me a more detailed trace off-list and I'll try to find the section of code that's actually crashing? If you grep through the ChangeLog for 64, you'll see that we've made various changes to support 64-bit over the past few years. I'm guessing that this is another 64-bit issue, maybe one that only comes up on machines with lots of RAM? -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ !DSPAM:475d7c7332006819015875!
Re: [vchkpw] Qmail rejection of overquota messages instead of bouncing
On Dec 9, 2007, at 6:03 AM, [EMAIL PROTECTED] wrote: I'm using John Simpsons last combined patch... I'm trying to know if I could any way... cause qmail to reject messages at smtp dialogue if users we're trying to deliver is overquota instead of bouncing it... black lists are nowadays becoming quite crazy IMHO but they're know blacklisting this servers who bounce overquota... well infact now all servers that bounce directly... it would be a nice idea to reject messages for overquoted mailboxes... I've proposed the following solution, a few times over the years, and I still think it's a good one. It would fit your needs (and most people's needs) well. Someone needs to make a qmail-smtpd patch that calls an external program to verify an account. That way, there's a single qmail-smtpd patch and you can come up with whatever program (chkuser, validrcptto, etc.) you want to verify an account. You'd pass in the sender's address and the attempted recipient address. The program can have different exit codes for different conditions, and can even output a custom reject message. This would allow for handling lots of conditions: * Temporary failure, user is over quota * Permanent failure, user is over quote * Permanent failure, account does not exist * Permanent failure, account closed, please use [EMAIL PROTECTED] instead * Accepted * Accepted (by catchall) * Rejected, this account does not accept mail from [EMAIL PROTECTED] Hopefully someone with some time on their hands will take this on. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ !DSPAM:475d7dd032002197873115!
Re: [vchkpw] Qmail rejection of overquota messages instead of bouncing
On Mon, 2007-12-10 at 09:56 -0800, Tom Collins wrote:
On Dec 9, 2007, at 6:03 AM, [EMAIL PROTECTED] wrote:
I'm using John Simpsons last combined patch... I'm trying to know if I
could any way... cause qmail to reject messages at smtp dialogue if
users
we're trying to deliver is overquota instead of bouncing it...
black lists
are nowadays becoming quite crazy IMHO but they're know
blacklisting this
servers who bounce overquota... well infact now all servers that
bounce
directly... it would be a nice idea to reject messages for overquoted
mailboxes...
I've proposed the following solution, a few times over the years, and
I still think it's a good one. It would fit your needs (and most
people's needs) well.
Someone needs to make a qmail-smtpd patch that calls an external
program to verify an account. That way, there's a single qmail-smtpd
patch and you can come up with whatever program (chkuser,
validrcptto, etc.) you want to verify an account.
You'd pass in the sender's address and the attempted recipient
address. The program can have different exit codes for different
conditions, and can even output a custom reject message. This would
allow for handling lots of conditions:
* Temporary failure, user is over quota
* Permanent failure, user is over quote
* Permanent failure, account does not exist
* Permanent failure, account closed, please use [EMAIL PROTECTED]
instead
* Accepted
* Accepted (by catchall)
* Rejected, this account does not accept mail from [EMAIL PROTECTED]
Hopefully someone with some time on their hands will take this on.
I went looking into this thinking chkuser would be a perfect place for the
basic quota check.
Of course that would be sort of vpopmail specific, but lo and behold, it's
already in there.
'chkuser.c' v.2.0.8
if (vmaildir_readquota(tmp_path.s,format_maildirquota \
(user_passwd-pw_shell)) \
= maxmbxquota_limit) {
retstat = CHKUSER_ERR_MBXFULL;
}
It's not as encompassing as Tom was envisioning, but it does do what the parent
is looking for..
Rick
--
Tom Collins - [EMAIL PROTECTED]
Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/
QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/
!DSPAM:475d9b3732008013718122!
Re: [vchkpw] Qmail rejection of overquota messages instead of bouncing
Rick Romero wrote:
I went looking into this thinking chkuser would be a perfect place for the
basic quota check.
Of course that would be sort of vpopmail specific, but lo and behold, it's
already in there.
'chkuser.c' v.2.0.8
if (vmaildir_readquota(tmp_path.s,format_maildirquota \
(user_passwd-pw_shell)) \
= maxmbxquota_limit) {
retstat = CHKUSER_ERR_MBXFULL;
}
It's not as encompassing as Tom was envisioning, but it does do what the parent
is looking for..
Rick
I thought this used to work back in the days when we used CDB, but does
it still work today (using SQL at least?)
on my production it still generates a new bounce, as it does on my test
server...
Connected to fox.
Escape character is '^]'.
220 fox ESMTP
mail from: [EMAIL PROTECTED]
250 ok
rcpt to: [EMAIL PROTECTED]
250 ok
data
354 go ahead
blah
..
250 ok 1197328261 qp 12808
and yes david is well over quota :)
Dec 11 09:11:06 fox qmail-send: delivery 65: failure: user_is_over_quota//
Dec 11 09:11:06 fox qmail-send: status: local 0/200 remote 0/200
Dec 11 09:11:06 fox qmail-send: bounce msg 131246 qp 12818
Chkusr accepts it like any other user found message...
Antonio perhaps I missed a config option to force this? (or has
it been so long since i needed to install it, it never actually did it
and I'm remembering wrong?
!DSPAM:475dc95932001899111700!
Re: [vchkpw] Qmail rejection of overquota messages instead of bouncing
Rick Romero wrote: I went looking into this thinking chkuser would be a perfect place for the basic quota check. snip Of course that would be sort of vpopmail specific, but lo and behold, it's already in there. snip It's not as encompassing as Tom was envisioning, but it does do what the parent is looking for.. It should be improving soon. Antonio Nati has requested three new bits in gid_flags, and I plan to add them for the next release... as soon as I can find time. As I recall, two of them were quota related. Rick !DSPAM:475dd35b32004515697174!
Re: [vchkpw] Qmail rejection of overquota messages instead of bouncing
Quey wrote:
Rick Romero wrote:
I went looking into this thinking chkuser would be a perfect place
for the basic quota check.
Of course that would be sort of vpopmail specific, but lo and behold,
it's already in there.
'chkuser.c' v.2.0.8
if (vmaildir_readquota(tmp_path.s,format_maildirquota \
(user_passwd-pw_shell)) \
= maxmbxquota_limit) {
retstat =
CHKUSER_ERR_MBXFULL;
}
It's not as encompassing as Tom was envisioning, but it does do what
the parent is looking for..
Rick
I thought this used to work back in the days when we used CDB, but
does it still work today (using SQL at least?)
on my production it still generates a new bounce, as it does on my
test server...
Connected to fox.
Escape character is '^]'.
220 fox ESMTP
mail from: [EMAIL PROTECTED]
250 ok
rcpt to: [EMAIL PROTECTED]
250 ok
data
354 go ahead
blah
..
250 ok 1197328261 qp 12808
and yes david is well over quota :)
Dec 11 09:11:06 fox qmail-send: delivery 65: failure:
user_is_over_quota//
Dec 11 09:11:06 fox qmail-send: status: local 0/200 remote 0/200
Dec 11 09:11:06 fox qmail-send: bounce msg 131246 qp 12818
Chkusr accepts it like any other user found message...
Antonio perhaps I missed a config option to force this? (or has
it been so long since i needed to install it, it never actually did it
and I'm remembering wrong?
no matter, I found what I did wrong, I ommited the variable in tcp.smtp
file :)
it now works as stated.
But I agree it would be nice to do by default without adding into that
file if it is defined.
!DSPAM:475de0f732001316991813!
Re: [vchkpw] Qmail rejection of overquota messages instead of bouncing
Rick Romero wrote: I went looking into this thinking chkuser would be a perfect place for the basic quota check. snip Of course that would be sort of vpopmail specific, but lo and behold, it's already in there. snip It's not as encompassing as Tom was envisioning, but it does do what the parent is looking for.. It should be improving soon. Antonio Nati has requested three new bits in gid_flags, and I plan to add them for the next release... One of the finest thing in vpopmail IMHO would be to set a list with wich each vpopmail is compatible with each courier-imap this is a bit difficult to see... and you have to do lots of tests... and if you set one vpopmail version with one courier-imap and with time one of them become buggy it's a problem to change one of them version... another thing would be nice too to correct would be that vpopmail not to let permanent connections against mysql because else if no one has poped in courier-imap for some time... courier-imap hangs because the connection he opened to mysql trough vpopmail is being closed because inactivity... congrats for so nice software :) as soon as I can find time. As I recall, two of them were quota related. Rick !DSPAM:475e387b32002078760001!
