[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mkvalidrcptto error
- To: John Simpson <jms1@xxxxxxxx>
- Subject: Re: mkvalidrcptto error
- From: Christopher Weimann <cweimann@xxxxxxxxx>
- Date: Thu, 03 Jul 2008 19:03:09 -0400
- Cc: Qmail List <qmail@xxxxxxxxxxxxx>
- Delivered-to: de5-qmail@sws5.ornl.gov
- Delivered-to: mailing list qmail@list.cr.yp.to
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=brmPJgF6uPVE7cf+j8Js6nGPuqwd0NeoB9Wc5tMfSGo=; b=nXAb9acXFwojj4GPHSeTZhGD08ceglYwnlLUK6QYXPhlcbL8o/n0wOPPL5SW15efTm tjKjQkLzuyX6h0a5TbmqD+d0hLkhMg2xhxYsXqwFbmQ3JK+Y12OYKb2rHBhNaxkwu94v Hmhy/x2r7zFs2JKnupQ+yBZWdn0VrS4UfEido=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=qfkTjddRtPeth052mjFCYRx3iF+w0yydtZbRK2mElLzNNcHbL0gWIUCdDU0ztNPJDX k0UAy54+VN7t72/3rkL1NKjgieggWCwzZi5ePY9OPBBGJlHiJyKHR8BqXle0i7fVynIx Knvety3tF4c2NUGmSKk2512KaHpDFfIaUVau8=
- In-reply-to: <DC802B1F-8B78-4DE2-90E2-0F5F953AB115@jms1.net>
- Mailing-list: contact qmail-help@list.cr.yp.to; run by ezmlm
- References: <e9d09d5d0806261303t33dff150n141646a103475f56@mail.gmail.com> <E85C0A64-4F11-4631-998A-CE0E034FA6BE@jms1.net> <e9d09d5d0807030907p498734f0w5adf9241511a294c@mail.gmail.com> <DC802B1F-8B78-4DE2-90E2-0F5F953AB115@jms1.net>
Well, its different :)
On Thu, Jul 3, 2008 at 2:51 PM, John Simpson <jms1@xxxxxxxx> wrote:
>>
>> jet# ./mkvalidrcptto.test | egrep "joe|nowhere.mil"
>> Virtual domain "nowhere.mil" will not reject mail to non-existent
>> mailboxes.
>> joe@localhost
>> joe-foo-joe@localhost
>> @nowhere.mil
>> jet# ls /home/joe/.qmail*
>> /home/joe/.qmail-foo-joe
>> jet#
>>
>> It seems to think I have a /home/joe/.qmail-foo-default file. I would
>> expect it to only accept mail for joe@xxxxxxxxxxxx
>
> it doesn't inspect the contents of the home directory at all. however, after
> re-reading "man dot-qmail" (i don't normally use system users for mailboxes
> at all, so this stuff isn't as fresh in my mind as it should be) i can see
> that it needs to.
>
> i've just updated it, please try again.
>
jet# ./mkvalidrcptto.test
ERROR: no appropriate .qmail file exists in "joe-foo" home directory,
for virtual domain "nowhere.mil"
> again, thanks for letting me know... i'd much rather make the script
> correctly handle all of these (as i think of them) "edge cases", than have
> to tell people to look elsewhere simply because they don't do things exactly
> the same way i do (i.e. with a zero-byte "locals" file, and every domain,
> including the "me" domain, managed by vpopmail.)
>
In my situation I have one customer might have multiple domains. They will have
different people responsible for the billing@ addresses for each
domain but they
only have one account on the mail server. Therefore the first domain
might have
/home/joe/.qmail-foo-billing and /home/joe/.qmail-bar-billing and
those two files
have different delivery instructions in them. Some clients have a
-default file
besides the -billing one but the sane ones do not. I'm pretty sure
one even has
a -default for one domain but not the others.
As far as this being an edge case I'm not really sure how else I would do it :)