On Sat, 09 May 2015, Wilfred van Velzen wrote to Ed Vance:

 EV> That isn't what I saw when I wrote my reply to You.
 EV> What I see at the top of this message for the {at}MSGID: is
 EV> , I was surprised to
 EV> see the part after the {at} symbol was changed to numbers that meant the
 EV> Routing Information for Mikes' BBS.

 WvV> A MSGID is supposed to have the nodenumber in it in Fidonet. 

actually, the phrasing is 

  "address of the originating system"

not

  "fidonet address of the originating system"

there is a huge difference ;) 

 WvV> The definition is:

 WvV> MSGID

 WvV>      A MSGID line consists of the string "^AMSGID:" (where ^A is a
 WvV>      control-A (hex 01) and the double-quotes are not part of the 
 WvV>     string),  followed by a space,  the address of the originating
 WvV>      system,  and a serial number unique to that message on the   
 WvV>   originating system,  i.e.:

 WvV>           ^AMSGID: origaddr serialno

 WvV> So Mike's system probably sets it that way when it leaves the
 WvV> system to his links in fidonet.

sbbs (sbbsecho actually) has a different form of MSGID but it does conform
to the spec... it just happens to carry additional information along with
it...

 EV> Has the Origin Line in this message been changed to capcity2 yet?

 WvV> Nope still the same.

 EV> I haven't seen any reply from Mike in the echo that I posted the
 EV> message to tell him about it.

 WvV> Hmm, Mike doesn't seem very active on his system... That happens.
 WvV> :-( 

if mike is a truck driver, he may be out on the road a few weeks at the
time... there are numerous sysops that have RL jobs as long haul truck
drivers... of course, this time of year, he may be on vacation... there's
any number of reasons for RL to take precedence ;) 

)\/(ark