Re: [vchkpw] Re: strange behaviour in local delivery

2004-03-04 Thread Tom Collins 
On Mar 4, 2004, at 4:20 AM, Jan Reilink wrote:
I'll test with vpopmail ver 5.2.2. when this server goes live on March 
13, unfortunaly I can't test it sooner.
5.2.2 includes many bug fixes to 5.2.1.  Anyone using 5.2.1 that 
doesn't want to upgrade to 5.4 should at least upgrade to 5.2.2.

http://vpopmail.sf.net/

--
Tom Collins  -  [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/

Re: [vchkpw] Re: strange behaviour in local delivery

2004-03-04 Thread Jeremy Kitchen 
On Thu, 2004-03-04 at 09:25, Jan Reilink wrote:
> Maurice Snellen wrote:
> 
> > On Thursday, March 04, 2004 at 12:20 Jan Reilink wrote:
> > 
> >>Yes, but what about:
> >>:/var/vpopmail/domains/example.com# cat .qmail-default
> >>| /var/vpopmail/bin/vdelivermail '' [EMAIL PROTECTED]
> > 
> >>:/var/vpopmail/domains/anotherexample.com# cat .qmail-postmaster
> >>&[EMAIL PROTECTED]
> > 
> > As long as /var/vpopmail/domains/anotherexample.com/postmaster exists,
> > this will not work as it has preference over the .qmail-postmaster
> > file.
> > 
> 
> Thanks, this clarifies a lot.

but it's wrong.

-Jeremy

-- 
Jeremy Kitchen
Systems Administrator
[EMAIL PROTECTED]
Kitchen @ #qmail on EFNet - Join the party!
.
Inter7 Internet Technologies, Inc.
www.inter7.com
866.528.3530 toll free
847.492.0470 int'l
847.492.0632 fax
GNUPG key ID: 93BDD6CE

Re: [vchkpw] Re: strange behaviour in local delivery

2004-03-04 Thread Jeremy Kitchen 
On Thu, 2004-03-04 at 09:13, Maurice Snellen wrote:
> On Thursday, March 04, 2004 at 12:20 Jan Reilink wrote:
> 
> > Yes, but what about:
> > :/var/vpopmail/domains/example.com# cat .qmail-default
> > | /var/vpopmail/bin/vdelivermail '' [EMAIL PROTECTED]
> 
> > :/var/vpopmail/domains/anotherexample.com# cat .qmail-postmaster
> > &[EMAIL PROTECTED]
> 
> As long as /var/vpopmail/domains/anotherexample.com/postmaster exists,
> this will not work as it has preference over the .qmail-postmaster
> file.

no, because qmail-local will call .qmail-postmaster before it calls
.qmail-default

man dot-qmail

-Jeremy
-- 
Jeremy Kitchen
Systems Administrator
[EMAIL PROTECTED]
Kitchen @ #qmail on EFNet - Join the party!
.
Inter7 Internet Technologies, Inc.
www.inter7.com
866.528.3530 toll free
847.492.0470 int'l
847.492.0632 fax
GNUPG key ID: 93BDD6CE

Re: [vchkpw] Re: strange behaviour in local delivery

2004-03-04 Thread Jan Reilink 
Maurice Snellen wrote:

On Thursday, March 04, 2004 at 12:20 Jan Reilink wrote:

Yes, but what about:
:/var/vpopmail/domains/example.com# cat .qmail-default
| /var/vpopmail/bin/vdelivermail '' [EMAIL PROTECTED]

:/var/vpopmail/domains/anotherexample.com# cat .qmail-postmaster
&[EMAIL PROTECTED]
As long as /var/vpopmail/domains/anotherexample.com/postmaster exists,
this will not work as it has preference over the .qmail-postmaster
file.
Thanks, this clarifies a lot.

--
Met vriendelijke groet / Best regards,
Jan Reilink, VEVIDA Nederland BV
Postbus 329, 9700 AH GRONINGEN, +31(0)50 - 5492234

[vchkpw] Re: strange behaviour in local delivery

2004-03-04 Thread Maurice Snellen 
On Thursday, March 04, 2004 at 12:20 Jan Reilink wrote:

> Yes, but what about:
> :/var/vpopmail/domains/example.com# cat .qmail-default
> | /var/vpopmail/bin/vdelivermail '' [EMAIL PROTECTED]

> :/var/vpopmail/domains/anotherexample.com# cat .qmail-postmaster
> &[EMAIL PROTECTED]

As long as /var/vpopmail/domains/anotherexample.com/postmaster exists,
this will not work as it has preference over the .qmail-postmaster
file.

In that case, you'd have to move your .qmail-postmaster to
/var/vpopmail/domains/anotherexample.com/postmaster and rename it to
simply .qmail

This may require you to upgrade your vpopmail though. I'm not exactly
sure as of which version .qmail files in virtual domain accounts are
supported.

-- 
Greetings,
Maurice

Re: [vchkpw] Re: strange behaviour in local delivery

2004-03-04 Thread Jan Reilink 
Maurice Snellen wrote:

On Thursday, February 26, 2004 at 11:46 Jan Reilink wrote:
[local delivery, catch-all, forwards]
Is this a known issue, is there a solution?
The problem is that you are setting the catchall for example.com to a
postmaster address.
As you are probably aware, upon creating a domain with vadddomain,
there is one e-mail account which is always created and cannot be
deleted with qmailadmin: postmaster.
What you need to be aware of, is that the catch-all only works for
e-mail sent to addresses within a domain that are _NOT_ already
defined as forwards or regular accounts. Thus, your setup will always
fail as the postmaster account is always there.
Yes, but what about:
:/var/vpopmail/domains/example.com# cat .qmail-default
| /var/vpopmail/bin/vdelivermail '' [EMAIL PROTECTED]
:/var/vpopmail/domains/anotherexample.com# cat .qmail-postmaster
&[EMAIL PROTECTED]
?

Email sent directly to [EMAIL PROTECTED] is nicely forwarded 
to [EMAIL PROTECTED], but email sent to [EMAIL PROTECTED] (which is caught 
by the catch-all [EMAIL PROTECTED]) is delivered locally to 
this Maildir.

In our system, postmaster@ is a normal emailaddress which can be used by 
the customer.

You could remedy this by setting the catch-all address of example.com
to an non-existant address in example2.com, such as
[EMAIL PROTECTED]
True, I already knew about this solution but "it doesn't fit in our 
system", because it involves manually adding and editing dot-qmail files 
(trust me, you don't want to do this for +20.000 virtual domains :-)

Someone on the qmail mailinglist answerd:


Update vpopmail to ver. 5.2.2 and it will magically work, I
ran into this last weekend.

I'll test with vpopmail ver 5.2.2. when this server goes live on March 
13, unfortunaly I can't test it sooner.

Anyway, thanks for your answer.

--
Met vriendelijke groet / Best regards,
Jan Reilink, VEVIDA Nederland BV
Postbus 329, 9700 AH GRONINGEN, +31(0)50 - 5492234

[vchkpw] Re: strange behaviour in local delivery

2004-03-02 Thread Maurice Snellen 
On Thursday, February 26, 2004 at 11:46 Jan Reilink wrote:

> /var/vpopmail/domains/example.com# cat .qmail-default
> | /var/vpopmail/bin/vdelivermail '' [EMAIL PROTECTED]

> /var/vpopmail/domains/example2.com# cat .qmail-default
> | /var/vpopmail/bin/vdelivermail '' [EMAIL PROTECTED]

> Is this a known issue, is there a solution?

The problem is that you are setting the catchall for example.com to a
postmaster address.

As you are probably aware, upon creating a domain with vadddomain,
there is one e-mail account which is always created and cannot be
deleted with qmailadmin: postmaster.

What you need to be aware of, is that the catch-all only works for
e-mail sent to addresses within a domain that are _NOT_ already
defined as forwards or regular accounts. Thus, your setup will always
fail as the postmaster account is always there.

You could remedy this by setting the catch-all address of example.com
to an non-existant address in example2.com, such as
[EMAIL PROTECTED]

-- 
Greetings,
Maurice