Re: [vchkpw] Problems to get e-mail when domain names are capitalized

2005-01-05 Thread Alex Pleiner
* Walter Souto R. Junior [EMAIL PROTECTED] [2005-01-05 03:08]:

 rcpt to: [EMAIL PROTECTED]
 533 sorry, your envelope recipient has been denied (#5.7.1)

 Any ideas?

Walter,

this error message is not in vanilla qmail. So I guess, you are using
some kind of badrcptto-patch (qregex?). Please show us this patch and
the contents of it's config file (control/badrcptto?) 

Alex

-- 
Alex Pleinerzeitform Internet Dienste
mailto:[EMAIL PROTECTED]  Fraunhoferstraße 5
PGP S/MIME: http://key.zeitform.de/ap   64283 Darmstadt, Germany
Tel./Fax: +49 (0) 6151 155-635 / -634   http://www.zeitform.de
Jabber: [EMAIL PROTECTED]


Re: [vchkpw] Problems to get e-mail when domain names are capitalized

2005-01-05 Thread Walter Souto R. Junior
Hi Alex,
this error message is not in vanilla qmail. So I guess, you are using
some kind of badrcptto-patch (qregex?). Please show us this patch and
the contents of it's config file (control/badrcptto?)
I just look into it moments before I get your message. Yes I'm using some  
kind of regex patch. Currently I have one file named badmailto. Follow  
it's contents:

# must not contain invalid characters,
# brakets or multiple @'s
[\W\D!%#:\*\^]
[\(\)]
[\{\}]
@.*@
I setup this server almost based on Shupp's toaster version 0.5. So I'm  
using his patch that contains qregex.patch-20020129, but the code is  
blended with another patches. I see that this patch is really old, but  
says on the readm file that qregex is case insentive.

I found this version of the patch here:
http://alex.zeitform.de/qmail/qmail_single_patches/qregex.patch-20020129
Thanks for any help,
--
Walter.


Re: [vchkpw] Problems to get e-mail when domain names are capitalized

2005-01-05 Thread Alex Pleiner
* Walter Souto R. Junior [EMAIL PROTECTED] [2005-01-05 14:18]:
 Hi Alex,


 this error message is not in vanilla qmail. So I guess, you are using
 some kind of badrcptto-patch (qregex?). Please show us this patch and
 the contents of it's config file (control/badrcptto?)

 I just look into it moments before I get your message. Yes I'm using some  
 kind of regex patch. Currently I have one file named badmailto. Follow  
 it's contents:

 # must not contain invalid characters,
 # brakets or multiple @'s
 [\W\D!%#:\*\^]
 [\(\)]
 [\{\}]
 @.*@

Drop or fix the first non-comment line. It does not work. 

Explanation: Your regex.h does not support \W and \D (see regex(7), GNU
regex manual). That means, the regex code drops connections with
recipient domains containing uppercase W and D chars (see your example
smtp session). 

I was falling to the same trap and notified the patch author (Evan) to request
removal of this example. I didn't get an answer, but Andrew, who now
maintains this patch, removed it from README.qregex. 

BTW, there is an updated version with further enhancements at:
http://www.arda.homeunix.net/store/qmail/qregex-20040725.patch 

 I setup this server almost based on Shupp's toaster version 0.5. So I'm  
 using his patch that contains qregex.patch-20020129, but the code is  
 blended with another patches. I see that this patch is really old, but  
 says on the readm file that qregex is case insentive.

Maybe Bill should get a notification also

 I found this version of the patch here:
 http://alex.zeitform.de/qmail/qmail_single_patches/qregex.patch-20020129

Funny, this is my little site. :-)

Alex


-- 
Alex Pleinerzeitform Internet Dienste
mailto:[EMAIL PROTECTED]  Fraunhoferstraße 5
PGP S/MIME: http://key.zeitform.de/ap   64283 Darmstadt, Germany
Tel./Fax: +49 (0) 6151 155-635 / -634   http://www.zeitform.de
Jabber: [EMAIL PROTECTED]


Re: [vchkpw] Problems to get e-mail when domain names are capitalized

2005-01-05 Thread Walter Souto R. Junior
Hi Alex,
Drop or fix the first non-comment line. It does not work.
Explanation: Your regex.h does not support \W and \D (see regex(7), GNU
regex manual). That means, the regex code drops connections with
recipient domains containing uppercase W and D chars (see your example
smtp session).
Ok! Now I have:
[!%#:*^(){}]
[\(\)]
[\{\}]
@.*@
And everything works fine!
I found this version of the patch here:
http://alex.zeitform.de/qmail/qmail_single_patches/qregex.patch-20020129
Funny, this is my little site. :-)
Wow! I just google for that! Thanks a lot.
[]s,
--
Walter.


[vchkpw] valias

2005-01-05 Thread mkinikoglu
hi all



i use mysql +vpopmail.

i have valias table and it works.



in qmail i have an alias file like this

# cat .qmail-listname

|/home/sympa/bin/queue listname@mynetgrup.com



so how can i create an alias in valias table for this type .qmail
alias?



is it possible to create a row like this : 



listname - @group.com - /home/sympa/queue [EMAIL PROTECTED]



i tried it but it didn't work. is there anyway to do this?



thanks





mr boyu deimeyecek email adresinizi imdi
aln: Mynet Email Plus





Re: [vchkpw] Problems to get e-mail when domain names are capitalized

2005-01-05 Thread Jeremy Kitchen
On Tuesday 04 January 2005 04:20 pm, X-Istence wrote:
 On Jan 4, 2005, at 11:48 AM, Jeremy Kitchen wrote:
  On Tuesday 04 January 2005 09:13 am, Walter Souto R. Junior wrote:
  Hi,
 
  My regitrar always capitalize the name of domains for the contacts
  (e.g.
  name@DOMAIN.TLD and the messages he send to me never comes. I try
  to
  change the the e-mail and I get the message normally, but after the
  confirmation, the system of the registrar capitalizes the domain
  again...
 
  domains have no case sensitivity.  DoMaIn.TlD is the same as
  domain.tld,
  DOMAIN.TLD, dOmAIN.tlD, etc.  Technically, local parts can be case
  sensitive,
  but qmail converts all local parts to lowercase (as I believe most
  other UNIX
  mtas do as well).  On a qmail system, LaRRY is the same as larry,
  lArRy,
  LarRy, etc, they're all delivered to 'larry'

 So if i have a user whose username is GlaanieBoy, he would not recv any
 email? Since he does not have email enabled on his account it is not a
 problem, but i am asking in case that is true, which would mean i could
 only create accounts with lowercase letters.

that is correct.  However you can mak an account glaanieboy and any mail to 
GlaanieBoy would go there.

-Jeremy

-- 
Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc.
  [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 815.776.9465 int'l
  kitchen @ #qmail #gentoo on EFnet IRC ++ scriptkitchen.com/qmail
 GnuPG Key ID: 481BF7E2 ++ jabber:[EMAIL PROTECTED]


pgpUBvp1jCtoE.pgp
Description: PGP signature


Re: [vchkpw] [OT] maildrop and clamd-stream-client

2005-01-05 Thread Charles Sprickman
On Tue, 4 Jan 2005, Jeremy Kitchen wrote:
On Monday 03 January 2005 08:48 pm, Charles Sprickman wrote:
Hi,
I'll apologize in advance here, this is really a maildrop question, but
after posting there three times I haven't received an answer to what
should be a simple question (not even an admonishment or flame from Mr.
Sam)...
I found a nice network-ready clamd client that I want to use:
ftp://victor.teaser.fr/pub/lwa/clamd-stream-client/
That allows me to do virus-scanning on another set of boxes; all the other
clients assume a local clamd server, which is no good.
It's pretty simple, you feed it a message and it returns a clean exit code
if there's no virus.  If there is a virus it prints the name to STDOUT and
exits with exitcode 65.  Simple, right?
that's not even compatible with clam{d,}scan
According to the docs, it emulates sendmail exit codes, which I think 
means mail.local exit codes.  Either way, it's easy enough to check in 
maildrop, or if need be to change in the source.

those tools use 0 for clean, 1 for virus, and 2 for non-virus.  Having
different tools using different exit codes is a maintanence nightmare waiting
to happen.
I only have one maildrop filter to maintain, so I can live with that.
So I hacked together a simple rule in my local mailfilter rule like so to
test it:
[snip]
now my question is: why aren't you doing this at the queue level so you can
simply reject viruses at the smtp level?  This would be a much simpler
design, and you could easily do all of the logging / tracking that you
wanted.
I have some people that want virus filtering, some that don't...
Any ideas on the backtick problem?
Thanks,
Charles
just my two cents.
-Jeremy
--
Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc.
 [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 815.776.9465 int'l
 kitchen @ #qmail #gentoo on EFnet IRC ++ scriptkitchen.com/qmail
GnuPG Key ID: 481BF7E2 ++ jabber:[EMAIL PROTECTED]


Re: [vchkpw] debugging quota problems

2005-01-05 Thread Charles Sprickman
On Tue, 14 Dec 2004, Andrew Niemantsverdriet wrote:
Hi,
On Tue, 2004-12-14 at 13:39, Charles Sprickman wrote:
Hi all,
Today I started looking at a problem that one of our staff was having
after we finally found one customer with the same problem.  Basically
these users just lost their quota usage meter in squirrelmail.  I'd put
off looking at it since I thought it was probably an issue with the plugin
- the plugin just sends an IMAP command to the IMAP server (tag
GETQUOTAROOT INBOX) and then parses the output, prints it in MB/% and
draws a simple graph in the folder list frame.
However today I tried talking directly to the imap server (Courier IMAP
3.0.7) and found that it too was having issues reporting the quota:
a01 OK LOGIN Ok.
a02 GETQUOTAROOT INBOX
* QUOTAROOT INBOX ROOT
* QUOTA ROOT ---
a02 OK GETQUOTAROOT Ok.
To contrast it with a working account:
a01 OK LOGIN Ok.
a02 getquotaroot INBOX
* QUOTAROOT INBOX ROOT
* QUOTA ROOT (STORAGE 125149 307200)  ---
a02 OK GETQUOTAROOT Ok.
Bear in mind that both accounts have quotas and vuserinfo (vpopmail 5.4.7)
correctly reports the quota.
Which still is quite curious...
I dug through the Courier changelogs and saw no recent mention of any
quota reporting issues.
I can temporarily fix this by deleting the maildirsize file in the
user's Maildir.  Is there some chance that vpopmail is straying a bit from
maildir++ standards?  Is there any way to debug this?

I too am having this problem, after reading this I decided to take a
look. Same problem, so I would love to hear what can be done to fix
this.
Well, it's all bad news.  All the accounts I'm finding with this problem 
use maildrop as the final delivery agent (for spam checking), so that kind 
of takes vpopmail out of the picture.  So for now I'm going to don my 
asbestos undies and subscribe to the Courier list.  It seems like the 
error has to be in either Courier-IMAP or Maildrop, as those are the only 
two things that touch the maildirsize file in the normal course of 
operations...

Charles
--
_
/-\ ndrew