Re: secondary router question...light dawns on (my) thick skull?

[Technical Support, Stalker Labs]

Hello,

On Tue, May 15, 2001, 15:07:32 GMT
  Bill Cole, <[EMAIL PROTECTED]> wrote:

>At 4:24 PM +0400 5/15/01, Technical Support, Stalker Labs wrote:
>>Hello,
>>
>>On Tue, May 15, 2001, 10:47:14 GMT
>>   Joe Wagner, <[EMAIL PROTECTED]> wrote:
>>
>>>Dmitry Akindinov stroll across the digital landscape and wrote:
>>>>  >> domain1.com.  MX 10 mail.domain1.com.
>>>>  >> domain1.com.  MX 20 mail2.domain1.com.
>>>>  >> domain1.com.  MX 20 mail3.domain1.com.
>>>>  >>
>>>>  >> My router entry on the secondaries re:
>>>>  >> domain1.com = domain1.com.smtp
>>>>
>>>>With the .smtp suffix the right part should be A or CNAME record name - MX
>>>>lookups are not done for names endinf with .smtp
>>>Oh, I didn't know that, thanks Dmitry.  I see...just to make sure then:
>>>
>>>The router on the secondaries shown above should still be:
>>>           domain1.com = mail.domain1.com.smtp
>>
>>This is OK, but not necessary - the server may get the same info
>>from DNS MX records.
>
>I must be confused...
>
>Isn't some router entry essential for a server that otherwise isn't
>an open relay to act as a secondary MX?

Well, router sets the 'safe' flag and relaying will be allowed. But my personal 
preference is to list secondaries (or the primary on secondaries) in the Client Hosts 
list. This way relaying will be allowed as well and some checks (eg. RBL) will be 
skipped also.

>FWIW, I also don't understand why the RHS name part of a '.smtp' rule
>is treated strictly as a hostname instead of as a domain name. It
>seems to me that it would be useful to have a semantic for "deliver
>domain X as SMTP would dictate for domain Y" or even just "skip the
>router for this domain" (the X=Y reduction) but I don't understand
>why the .smtp feature exists if that's not what it is. For example,
>what would the difference be between these two router lines:
>
>domain1.com = mail.domain1.com.smtp
>
>*@domain1.com = *[EMAIL PROTECTED]
>
>
>
>I guess the bottom line for me is simple: it would be a good thing to
>have a way of making SIMS act as a normal relay for recipients in a
>domain without having to duplicate DNS information in the SIMS router.

The .smtp suffix was supposed to make SIMS to skip MX resolution. In the current 
versions it just prevents the address from further modifications by the router.

In your example the first line will route a message to a host with DNS A record 
mail.domain1.com.

The second line reads correctly as
<*@domain1.com> = *[EMAIL PROTECTED]

may cause problems if there's an MX record for mail.domain1.com; also this syntax 
allows for routing of complex addresses like [EMAIL PROTECTED]

I would recommend the following:

domain1.com = [EMAIL PROTECTED]

>
>--
>Bill Cole
>[EMAIL PROTECTED]
>
>
>#############################################################
>This message is sent to you because you are subscribed to
>  the mailing list <[EMAIL PROTECTED]>.
>To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
>To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
>To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
>Send administrative queries to  <[EMAIL PROTECTED]>
>
>

Sincerely,
Stalker Technical Support

=======================================================================
When answering to letters sent to you by the tech.support staff, make
sure the original message you have received is included into your reply.

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>