relay_domains vs virtual_mailbox

Prev: SMTP Greet Pause (re: Feature 20090228)
Next: Coping with relayed spam?

From: Steve Heaven on 4 Sep 2009 03:04

We have a domain where some users have local mailboxes and some are
passed on to an MS Exchange box.
In the transport map we have:

user1(a)mydomain.co.uk virtual:
user2(a)mydomain.co.uk virtual:
user3(a)mydomain.co.uk virtual:
mydomain.co.uk smtp:[remote.mydomain.co.uk]

We have mydomain.co.uk in virtual_mailbox_domains for the local users
and in relay_domains for those users relayed to the Exchange box. But
then we get

warning: do not list domain mydomain.co.uk in BOTH
virtual_mailbox_domains and relay_domains

in the logs.

If we dont need the domain in both lists which one should it be in?

Thanks

Steve

--
thorNET
Internet Services, Consultancy & Training
www.thornet.co.uk

From: Victor Duchovni on 4 Sep 2009 12:32

On Fri, Sep 04, 2009 at 08:04:06AM +0100, Steve Heaven wrote:

> We have a domain where some users have local mailboxes and some are
> passed on to an MS Exchange box.
> In the transport map we have:
>
> user1(a)mydomain.co.uk virtual:
> user2(a)mydomain.co.uk virtual:
> user3(a)mydomain.co.uk virtual:
> mydomain.co.uk smtp:[remote.mydomain.co.uk]
>
> We have mydomain.co.uk in virtual_mailbox_domains for the local users
> and in relay_domains for those users relayed to the Exchange box. But
> then we get
>
> warning: do not list domain mydomain.co.uk in BOTH
> virtual_mailbox_domains and relay_domains
>
> in the logs.
>
> If we dont need the domain in both lists which one should it be in?

Go with relay_domains, rewrite virtual mailbox users into
user(a)virtual.invalid via virtual_alias_maps, and list virtual.invalid
in virtual_mailbox_domains.

List actual relay users in relay_recipient_maps, and the users aliased
to virtual.invaliud virtual_alias_maps. This takes care of recipient
validation.

--
Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomo(a)postfix.org?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.

From: Steve Heaven on 7 Sep 2009 04:15

On Fri, 2009-09-04 at 12:32 -0400, Victor Duchovni wrote:

> List actual relay users in relay_recipient_maps, and the users aliased
> to virtual.invaliud virtual_alias_maps. This takes care of recipient
> validation.

We dont know the actual users on the relayed domains. One of the reasons
they are relayed in so that the client's sysadmins have control of the
user base via MS Exchange.

--
thorNET
Internet Services, Consultancy & Training
www.thornet.co.uk

From: Sahil Tandon on 7 Sep 2009 11:50

On Mon, 07 Sep 2009, Steve Heaven wrote:

> On Fri, 2009-09-04 at 12:32 -0400, Victor Duchovni wrote:
>
> > List actual relay users in relay_recipient_maps, and the users aliased
> > to virtual.invaliud virtual_alias_maps. This takes care of recipient
> > validation.
>
> We dont know the actual users on the relayed domains. One of the reasons
> they are relayed in so that the client's sysadmins have control of the
> user base via MS Exchange.

You should not accept mail for invalid recipients. Use existing
functionality to build a cache/database of valid recipients "on the fly".
See: http://www.postfix.org/ADDRESS_VERIFICATION_README.html#recipient

--
Sahil Tandon <sahil(a)tandon.net>

From: Steve Heaven on 8 Sep 2009 03:52

--=-y7+IGMkIR5mLlMkA2S5o
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

On Mon, 2009-09-07 at 11:50 -0400, Sahil Tandon wrote:

>
> You should not accept mail for invalid recipients. Use existing
> functionality to build a cache/database of valid recipients "on the fly".
> See: http://www.postfix.org/ADDRESS_VERIFICATION_README.html#recipient

We have no way of knowing if the recipient address is valid or not as we
are only acting as a relay for the final destination.
We cannot build a database of recipients on the fly as that information
is held on the various servers of our clients, to which we do not have
access.

--
thorNET

Internet Services, Consultancy & Training
www.thornet.co.uk

--=-y7+IGMkIR5mLlMkA2S5o
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
On Mon, 2009-09-07 at 11:50 -0400, Sahil Tandon wrote: 
 
<BLOCKQUOTE TYPE=CITE>
<PRE>

You should not accept mail for invalid recipients. Use existing
functionality to build a cache/database of valid recipients "on the fly".
See: <A HREF="http://www.postfix.org/ADDRESS_VERIFICATION_README.html#recipient">http://www.postfix.org/ADDRESS_VERIFICATION_README.html#recipient</A>
</PRE>
</BLOCKQUOTE>
<PRE>

</PRE>
We have no way of knowing if the recipient address is valid or not as we are only acting as a relay for the final destination. 
We cannot build a database of recipients on the fly as that information is held on the various servers of our clients, to which we do not have access. 
 
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- 
thorNET
<PRE>
Internet Services, Consultancy & Training
<A HREF="http://www.thornet.co.uk">www.thornet.co.uk</A>
</PRE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>

--=-y7+IGMkIR5mLlMkA2S5o--

| Next | Last
Pages: 1 2 3
Prev: SMTP Greet Pause (re: Feature 20090228)
Next: Coping with relayed spam?

relay_domains vs virtual_mailbox_domains