Hello All, 
Is this the place to ask a question about how to configure Internet Rex?

I have indicated to Antonio that I would be reaching out in fidoland for an
answer to this issue. 

I have a downlink of mine trying to send a netmail message 
He is using wildcat 4.20 and the Platinum Xpress mailer, he is also using
Internet Rex, of which I seriously think that is where the issue is. 
I do not believe that it is configured correctly, but I do not use this, so I
do not know enough to assist.

I will try to explain below the best I can, without being confusing. 
Also I am sorry for any repeated ideas or suggestions within the request for
help, I was trying to get the downlink to realize where I believe the issue
is and also not to modify his software configurations to have the destination
of the intended address to be within his setup. 

I also greatly appropriate any assistance that can be provided.  Please feel
free to reach out to me here or via a email.  My address is gdeyss@twc.com    I
use Mystic BBS Alpha 39. 
(It would be so much simpler if the node was also running Mystic but I was
trying to help with his current choices of software and make them work
together. 

What is happening is the message is sitting in my c:\mystic\echomail directory

Below I was explaining that the location to use the destination address would
be only in the message header just before construction the message body. 

The place to use 1:275/91 should be defined is within your message header
within the two field after the name when you write the netmail. it should not
be defined anywhere in any of your software or any of it's configurations.

Thanks
Greg

On 5/20/2018 2:25 PM, Antonio Rico wrote:
> Hi,
>  
> this is what we talked about. all mail addressed to 1:275/91 needs to be
send to 1:267/0 so you can forward the netmail.
>  
> Regards.
>
> From: Gregory Deyss [mailto:gdeyss@twc.com]
> Sent: Saturday, May 19, 2018 11:42 PM
> To: downlink my node
> Subject: Re: netmail issue resolved
>
> why do you have a 1:275/91 in your route setup?
> what program is this that you are using that this is from ?
> It should read your node 1:267/152  to 1:267/0
>
the netmail node that your writing to will be defined within your netmail
header and should not be anywhere in your configuration. 


This is what my downlink has indicated to resolve the issue, 
here he suggests that he is using the default method. 

TARGET        ROUTE METHOD             TO            EVENT

1:* 2:* 3:* 4:* 5:* 6:* Direct to target
Default Event >> >>
1:275/91 Default 1:267/0 Default Event

 >> >> I put that. Expanded it looks like
so.
>> Mail Address To   : 1:275/91
>> Route Method      : Default
>> Send To Address   : 1:267/0
>> Route Event       : Default Event
>>
>> From: Gregory Deyss [mailto:gdeyss@twc.com]
>> Sent: Saturday, May 19, 2018 10:19 PM
>> To: Antonio Rico
>> Subject: Re: netmail issue resolved
>>
Any mailer that is to be considered fidonet complaint would have to handle
routing rules, including platinum xpress.

using the 1:267/0 is not a work around but the correct node to utilize on all
occasions when sending routed netmail. as 1:267/150 is just as node, just as
yours is.


>> On 5/19/2018 1:24 PM, Antonio Rico wrote:
>>
>>     Hi,
>>
>>     cool not sure if PX supports routing rules.
>>
>>     sending it for /0 is a nice work around in the meantime.
>>
>>     Regards.
>>
>>     From: Gregory Deyss [mailto:gdeyss@twc.com]
>>     Sent: Saturday, May 19, 2018 12:26 PM
>>     To: Antonio Rico
>>     Subject: netmail issue resolved
>>
>>     Antonio,
>>
>>     Below I am going to share with you a message that resolves the netmail
>>     issue. changes need to be made on where your sending and directing the
>>     netmail to. You need to send the netmail to 1:267/0 not to 1:267/150 
>>     if what is advised is followed, there should not any more issues with
>>     netmail
>>    


This is from my log within Mystic 
He is also flying or sending the aka that is not within my system. 
I am the Hub here in Upstate NY 1:267/0

>> >>    
+ May 18 18:23:08    Waiting for BUSY nodes
>>     - May 18 18:23:08    LINKS:
>>     - May 18 18:23:08    Node 14 1:267/156@fidonet
>>     - May 18 18:23:08    Node 5 1:267/152@fidonet
>>     - May 18 18:23:08    Node 1 1:266/512@fidonet
>>     - May 18 18:23:08    Node 2 21:1/100@fsxnet
>>     ! May 18 18:23:08    Import from c:\mystic\echomail\in\
>>     ! May 18 18:23:08    000118CE.PKT does not match an AKA (1:275/91)
>>     ! May 18 18:23:08    FIDONET.PKT does not match an AKA (1:275/91)
>>     + May 18 18:23:08  Results: 0 echo, 0 net, 0 dupes, 0 tossed in 0.03s
>>     + May 18 18:23:08  Shutdown Normal (0)
>>
>
>>     The issue here is the netmail packets are being sent to your system
>>     but addressed to 1:275/91 which is an aka you don't fly.
>>
>>     The sending system should check the way he's sending them to your
>>     fido address (your his hub right?) so he should have a routing
>>     rule set up to route zone 1 netmail via you at 1:267/0
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The following is what he needs to do right, how is this done within Internet
Rex. 

>>     If his system knows that It should set the netmail up so that
>>     although the final intended recipient will be 1:275/91 the
>>     netmail will be constructed to be sent via 1:267/0


I suggested that he would use the address of 1:275/91 within his message
header only, not to be included in any setup nor in a any configuration of
any software, but only using the send to address within the message header
and then send this or crash this to me at 1:267/0 the netmail should be sent
to its destination through routed netmail.

Like the below explanation.

>>
>>     Mystic will see the netmail it gets is addressed to it, also see
>>     the netmail is for some other address then route it onwards


















 the only place the
1:275/91 should be defined is within your message header within the two field
after the name when you write the netmail. it should not be defined anywhere
in any of your software or any of it's configurations.

Thanks
Greg

On 5/20/2018 2:25 PM, Antonio Rico wrote:
> Hi,
>  
> this is what we talked about. all mail addressed to 1:275/91 needs to be
send to 1:267/0 so you can forward the netmail.
>  
> Regards.
>
> From: Gregory Deyss [mailto:gdeyss@twc.com]
> Sent: Saturday, May 19, 2018 11:42 PM
> To: Antonio Rico
> Subject: Re: netmail issue resolved
>
> why do you have a 1:275/91 in your route setup?
> what program is this that you are using that this is from ?
> It should read your node 1:267/152  to 1:267/0
>
> the netmail node that your writing to will be defined within your netmail
header and should not be anywhere in your
> configuration.
>
>
>
> On 5/19/2018 11:29 PM, Antonio Rico wrote:
>>
>> Hi,
>>
>> TARGET        ROUTE METHOD             TO            EVENT
>>
>> 1:* 2:* 3:* 4:* 5:* 6:*ΓöéDirect to target        Γöé            
ΓöéDefault Event
>>
>> 1:275/91     ΓöéDefault                 Γöé1:267/0      ΓöéDefault Event
>>
>> I put that. Expanded it looks like so.
>>
 Route Setup
 Mail Address To   : 1:275/91
 Route Method      : Default

>> Send To Address   : 1:267/0
>> Route Event       : Default Event


Sure we can do a team view. >> >> Regards. >> >> From: Gregory Deyss
[mailto:gdeyss@twc.com] >> Sent: Saturday, May 19, 2018
10:19 PM
>> To: Antonio Rico
>> Subject: Re: netmail issue resolved
>>
>> Any mailer that is to be considered fidonet complaint would have to handle
routing rules, including platinum xpress.
>>
>> using the 1:267/0 is not a work around but the correct node to utilize on
all occasions when sending routed netmail.
>> as 1:267/150 is just as node, just as your is.
>>
>> Thanks
>> Greg
>>
>>  
>>
>> On 5/19/2018 1:24 PM, Antonio Rico wrote:
>>
>>     Hi,
>>
>>     cool not sure if PX supports routing rules.
>>
>>     sending it for /0 is a nice work around in the meantime.
>>
>>     Regards.
>>
>>     From: Gregory Deyss [mailto:gdeyss@twc.com]
>>     Sent: Saturday, May 19, 2018 12:26 PM
>>     To: Antonio Rico
>>     Subject: netmail issue resolved
>>
Below I am going to share with you a message that resolves the netmail issue.
changes need to be made on where your sending and directing the netmail to. You
need to send the netmail to 1:267/0 not to 1:267/150 if what is advised is
followed, there should not any more issues with netmail

     . ______ 
   _()___
  ( Gregory | 
 /-OO-----OO'

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/64)
 * Origin: Capital Station BBS (1:267/150)