Hello Kim,

>> This round of polling continued until I seen it happening and issued
>> the command 'bbbs bom d 1:14/5'.

> Polling loop can happen if:
> 1) You have crashmail to nodenumber X, but remote doesn't present that
> nodenumber as primary / AKA.

Fortunately in this particular situation both systems are under my control.
Heck, the 
PC's are sitting next to each other. :-)

In this case actual crash mail isn't necessary. All I have to do is tell
BBBS to poll 
1:14/5 which is the primary AKA that Mystic presents and it will poll. And according 
to the logs complete the poll. Then immediately poll again, and again...

> 2) Mail session is not fully completed and that poll message still exists.
> If your above "bbbs bom d 1:14/5" helps then it's not case
#1, as primary is
> 1:14/5.

Yes, entering the "bbbs bom d 1:14/5" looks to stop the polling loop.

>Unfortunately BBBS doesn't log enough to see if it's case #2. Can you get
debug
>logs from remote site? Does it disconnect incoming connection for some reason?

With Mystic there are several levels of logging which includes
"Debug". I will increase
the log level and see what it can tell me and keep you posted.

I did also notice that this only happens when BBBS polls a Mystic system. If mystic 
polls BBBS no such polling loop occurs. As a temporary workaround I started having 
Mystic do the polling. Which I will change back for testing purposes.

Jeff

--- BBBS/Li6 v4.10 Toy-4