I've been polling my fidonet hub for over a week now and I'm not getting any mail back in although mail seems to be going out. Is there something on my end I'm over looking that could cause this issue? When I contacted my fidonet rep he tells me according to his system all my requests have been answered.
The fallowing fidopoll log is what I get every time I poll

Jul 17 08:57:56 FIDOPOLL Version 1.12 A39 2018/04/21 Jul 17 08:57:56 Scanning 1:396/45 Jul 17 08:57:56 Queued 0 files (0 bytes) to 1:396/45 Jul 17 08:57:56 Polling BINKP node 1:396/45 by IPV4 Jul 17 08:57:56 Connecting to sursum-corda.com Jul 17 08:57:57 Using address 173.14.206.213 Jul 17 08:57:57 Connected IPV4 to 173.14.206.213 Jul 17 08:57:57 S: NUL SYS SmokyThing BBS Jul 17 08:57:57 S: NUL ZYZ Gandor Jul 17 08:57:57 S: NUL VER Mystic/1.12A39 binkp/1.0 Jul 17 08:57:57 S: ADR 1:19/35@fidonet Jul 17 08:57:57 C: NUL OPT MB CRC MD5
CRAM-MD5-c61a861d96268df125043366ec8b447d UTF8
Jul 17 08:57:57 C: NUL SYS Sursum Corda! BBS Jul 17 08:57:57 System Sursum Corda! BBS Jul 17 08:57:57 C: NUL ZYZ Marc W. Lewis Jul 17 08:57:57 SysOp Marc W. Lewis Jul 17 08:57:57 C: NUL LOC Huntsville, AL Jul 17 08:57:57 Location Huntsville, AL Jul 17 08:57:57 C: NUL NDL CM,XA,INA:sursum-corda.com,ITN,IBN,IFT Jul 17 08:57:57 Info NDL CM,XA,INA:sursum-corda.com,ITN,IBN,IFT Jul 17 08:57:57 C: NUL TIME 2018/07/17 08:57:57 -6:00 Jul 17 08:57:57 Info TIME 2018/07/17 08:57:57 -6:00 Jul 17 08:57:58 C: NUL VER Internet Rex 2.67 beta 1a OS/2 (binkp/1.1) Jul 17 08:57:58 Mailer Internet Rex 2.67 beta 1a OS/2 (binkp/1.1) Jul 17 08:57:58 C: ADR 1:396/45.0@fidonet 1:19/0.0@fidonet 1:19/5.0@fidonet 1:96/0.0@fidonet 1:396/3.0@fidonet 901:1/5.0@dixienet Jul 17 08:57:58 S: PWD Jul 17 08:57:58 C: OK Jul 17 08:57:58 S: EOB Jul 17 08:57:58 C: EOB Jul 17 08:57:58 Session ended (0 sent, 0 rcvd, 0 skip)

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: SmokyThing BBS (21:2/118)

On 07/17/18, Gandor pondered and said...

I've been polling my fidonet hub for over a week now and I'm not getting any mail back in although mail seems to be going out. Is there something

OK

on my end I'm over looking that could cause this issue? When I contacted

Have you confirmed your node is actually connected to echomail areas at this HUB? So there's packeting being tossed and held for you there? What does the HUB admin say to that question? Have you managed to get an Areafix query to
and back from the HUB to confirm you're connected to echomail areas you want
at this HUB?

Jul 17 08:57:58 C: ADR 1:396/45.0@fidonet 1:19/0.0@fidonet 1:19/5.0@fidonet 1:96/0.0@fidonet 1:396/3.0@fidonet 901:1/5.0@dixienet Jul 17 08:57:58 S: PWD Jul 17 08:57:58 C: OK Jul 17 08:57:58 S: EOB Jul 17 08:57:58 C: EOB Jul 17 08:57:58 Session ended (0 sent, 0 rcvd, 0 skip)

Yep connect seems fine but perhaps nothing is being held for you re my ideas above?

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Advances warning this is a long one ... SORRY

This is confusing as hell. About 4:30pm its now almost 7pm my time as I type this. I got a netmail from the fidonet admin. The messaged said.....

<Snip>
Subj : 00130023.HLO

Attached is a list of everything that's been transmitted to you over the last week or two. Not sure what's going on with that. Everything you see in the list with a tilde (~) in front of it has been transmitted. <snip>

This file I found in /echomail/in/ it has 40 lines most with (~) on them
but I haven's seen any mail in over a week

I go these other messages as well
Subj : 0179000A.WE0 0179000A.TU0
Subj : 0179000A.TH0 0179000A.SU0
Subj : 0179000A.SA0 0179000A.MO0

<snip>
Subj : 0179000A.FR2
Hello Shannon!

Attached are all the back-ups of mail bundles previously transmitted to you. <snip>


I don't know how attachments are suppose to work. I've never gotten one via netmail but what looks like happened in the log file is the mailin.ini
imported all the mail in the attached files. So I got a butt load of mail in the fido echoes.

Have you confirmed your node is actually connected to echomail areas at this HUB? So there's packeting being tossed and held for you there? What does the HUB admin say to that question?

He said that I was auto linked to the sysop and Test Area and everything else was on hold. Witch makes sense
(I also resumed everything on hold)

Have you managed to get an
Areafix query to and back from the HUB to confirm you're connected to echomail areas you want at this HUB?

Until that mass message dump today I got back like 3 replies from Areafix and
I sent a ton. I found like 30ish replies today

Yep connect seems fine but perhaps nothing is being held for you re my ideas above?

Yeah I don't get it. the fidonet admin is saying it's been sent yet my logs
say otherwise.
I sent another request to Areafix it look about 10 min to come back so maybe it's fixed I'm gonna send this message anyway just in case it's not

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: SmokyThing BBS (21:2/118)

On 07/17/18, Gandor pondered and said...

Subj : 00130023.HLO

Attached is a list of everything that's been transmitted to you over the last week or two. Not sure what's going on with that. Everything you
see in the list with a tilde (~) in front of it has been transmitted. <snip>

This file I found in /echomail/in/ it has 40 lines most with (~) on them but I haven's seen any mail in over a week

I go these other messages as well
Subj : 0179000A.WE0 0179000A.TU0
Subj : 0179000A.TH0 0179000A.SU0
Subj : 0179000A.SA0 0179000A.MO0

So the xxx.hlo file is a Binkley style pointer file that is used in BinkP sessions to indicate what packets are to be sent to another BinkP enabled
node when a polling event occurs. Think of the file as an index so the items within were sitting in the HUBs echomail\outbound.

Normally a BinkP enabled mailer will remove this *.hlo file when
files/packets are exchanged. The messages (from fido) that you seek were in
the packets such as 0179000A.WE0 etc.

The *.hlo extension means HOLD so those packets would have been held until
you poll. If the file extension had been *.clo then they would have been sent immediately to your system (CRASH).

If those did end up in your Mystic inbound then Mystic would have processed them but if those packets were unable to be imported you would see an error message in the mutil logging at the time they were processed. You may well
find them in your bad files directory as I think Mystic author g00r00 changed the behaviour recently to do this as opposed to deleting them.

I don't know how attachments are suppose to work. I've never gotten one via netmail but what looks like happened in the log file is the
mailin.ini imported all the mail in the attached files. So I got a butt load of mail in the fido echoes.

Ah ok, I should have read all of this first :)

He said that I was auto linked to the sysop and Test Area and everything else was on hold. Witch makes sense
(I also resumed everything on hold)

I'm not 100% sure what he means by on hold in this case, you're either linked to the echo areas or your not but it sounds like your linked to a few anyways so thats a start..

Until that mass message dump today I got back like 3 replies from
Areafix and I sent a ton. I found like 30ish replies today

I wonder if his system was having issues?

Yep connect seems fine but perhaps nothing is being held for you re m ideas above?

Yeah I don't get it. the fidonet admin is saying it's been sent yet my logs say otherwise.
I sent another request to Areafix it look about 10 min to come back so maybe it's fixed I'm gonna send this message anyway just in case it's
not

OK hopefully you're running... but hey you're most welcome to a Fidonet feed also from 3:770/1 which is the HUB I run. In the end you can pull echomail
etc. from whom you like and many opt to take multiple feeds to ensure redundancy in their echomail feed should a system they use go down or not
carry a certain echomail area etc. The main thing with Fido is that you poll your designated HUB once a day to check for any routed netmail that may be
held there for your node.

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I wonder if his system was having issues?

yep that what I was thinking but I wanted to explore all avenues on my end so as not to upset anyone... usually its my fault anyway for doing something stupid and forgetting I did it.

OK hopefully you're running... but hey you're most welcome to a Fidonet feed also from 3:770/1 which is the HUB I run. In the end you can pull echomail etc. from whom you like and many opt to take multiple feeds to ensure redundancy in their echomail feed should a system they use go
down or not carry a certain echomail area etc.

I might just take you up on that.

The main thing with Fido

is that you poll your designated HUB once a day to check for any routed netmail that may be held there for your node.

Yeah I have it set to poll at 3am every day and I have been manually polling
a few time a day too just to make sure...

--- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
* Origin: SmokyThing BBS (21:2/118)