Hello,

The problem is that SIMS does not check destination address thoroughly
enough when it looks like the address should be relayed through a host in
the Client Hosts list.

It needs an option similar to one found in CommuniGate Pro relaying
settings: relay to clients all addresses or just simple ones (without %
hacks.)

I'll see if that can be implemented in SIMS.


on 12.01.2003 09:50, Joe Wagner at [EMAIL PROTECTED] wrote:

> At Thu, 09 Jan 2003 20:37:58,  Larry Stone <[EMAIL PROTECTED]> wrote:
>>> Now how are you getting that to work? Here's what I get then I try that via
>>> telnet on my secondary going to my primary:
>>>> 571 <[EMAIL PROTECTED]@hypertouch.com> we do not relay.
>>>> 571 <[EMAIL PROTECTED]@67.41.229.20> we do not relay.
>>>> 571 <[EMAIL PROTECTED]@[67.41.229.20]> we do not relay.
>> 
>> Is 67.41.229.20 the address of your SIMS server? Is it in the Client Hosts
>> list?
>> 
>> Try using the address of another host in the Client Hosts list and see what
>> message you get (and use the third form of address above).
> 
> 
> Ah ha, bingo! Thanks. Since I had recently switch DSL providers I hadn't my
> primary's new address entered in the secondary's client host list.  Adding
> my primary's IP address to the secondary client list does allow me to do
> this two stage relay. Interesting. There is a fair chance I might have been
> bitten by that at some point. It is sometimes handy to enter a trusted
> network's range of IP addresses as a trusted client.  Now I will endeavor
> to remember to leave out my secondary's IP address if I ever need to do
> that again.
> 
> Yes, I guess I would think that it doesn't make much sense for the client
> list to be used to OK transmissions from email from any random connecting
> machine rather than just from connecting clients.  Is it an easy fix to
> exclude the client host when checking for permission for a .smtp router entry?

-- 
Best regards,
Dmitry Akindinov

=======================================================================
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]>

Reply via email to