Hello,

One of my downlinks seem to be "skipping" all the packets I send them:

20:49:31 2-Location NATAL,RN 20:49:31 2-Info NDL 115200,TCP,BINKP 20:49:31 2-Info TIME Thu Apr 07 2022 20:49:30 GMT-0300 20:49:31 2-Mailer BinkIT/1.45,JSBinkP/1.70/Linux binkp/1.1 20:49:31 2-Sending: fd2fff39.su0 (15,589 bytes) 20:49:31 2-Sending: fd2fff39.sa3 (1,930 bytes) 20:49:32 2-Session ended (0 sent, 0 rcvd, 2 skip)

Is there a way to override that skip request?

... That's not a bug, it's an undocumented feature

--- Mystic BBS v1.12 A47 2021/12/25 (macOS/64)
* Origin: Saturn's Orbit BBS - Private System (4:801/188)

Re: Skip packets
By: Flavio Bessa to All on Thu Apr 07 2022 08:56 pm

One of my downlinks seem to be "skipping" all the packets I send them:
Is there a way to override that skip request?

No.

Skipping is the downlink's system saying "I dont want what you are sending me", or "I cant take what you are sending me now, because..." (eg: disk full).

You should talk to the downlink to find out why they are skiping items you have queued for them.


...ëîåï
--- SBBSecho 3.15-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

Hello,

I have a system that works as a Hub for my region at Fidonet.

One of the nodes that connects with me always skip the packets we exchange... The last message I get is always:

Session ended: (0 sent, 0 rcvd, 2 skip)

The impression that I have is that he never receives echomail due to that.

Is this some kind of configuration at his side?

Regards,
Flavio

... Everyone is entitled to my opinion!

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - Back from the ashes (4:801/188)

I have a system that works as a Hub for my region at Fidonet.

One of the nodes that connects with me always skip the packets we exchange... The last message I get is always:

Session ended: (0 sent, 0 rcvd, 2 skip)

It could be there is no free space so the node can't store more files. It could also be that files with the same filename exist in the nodes inbound already.

The best way to get to the bottom of something like this is to compare logs with your linked node.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi Flavio,

On 15 Apr 24 23:00, Flavio Bessa wrote to All:
about: "Skip packets":

I have a system that works as a Hub for my region at Fidonet.

One of the nodes that connects with me always skip the packets we exchange... The last message I get is always:

Session ended: (0 sent, 0 rcvd, 2 skip)

The impression that I have is that he never receives echomail due to that.

Is this some kind of configuration at his side?

Probably. Is it a secure session? Should be in the logs. Of maybe his disk is full. Which mailer is used, on both sides?

Wilfred.

--- FMail-W64 2.3.2.1-B20240412
* Origin: point@work (2:280/464.112)

Hi Alan,

On 15 Apr 24 19:29, Alan Ianson wrote to Flavio Bessa:
about: "Skip packets":

It could also be that files with the same filename exist in the nodes inbound already.

Binkd always tries to rename files if that is the case. It even has an option for this:

# Rename style if file with the same name already exists in inbound
# rename-style [postix|extension]
#
# 'postfix' append number at the end of filename, after dot (default)
# example: file.ext -> file.ext.1
# 'extension' change filename extension
# example: file.ext -> file.ex0
#
# Not applied to *.pkt, arcmail, *.tic, *.req - only filename is changed
# for these file types.


I don't know about other mailers.


Wilfred.

--- FMail-W64 2.3.2.1-B20240412
* Origin: point@work (2:280/464.112)

It could also be that files with the same filename exist in the nodes
inbound already.

Binkd always tries to rename files if that is the case. It even has an option for this:

# Rename style if file with the same name already exists in inbound
# rename-style [postix|extension]
#
# 'postfix' append number at the end of filename, after dot (default)
# example: file.ext -> file.ext.1
# 'extension' change filename extension
# example: file.ext -> file.ex0
#
# Not applied to *.pkt, arcmail, *.tic, *.req - only filename is changed
# for these file types.

I don't know about other mailers.

Yep, I don't know what mailer is on the other end or the reason for skipping files.

The log should say why and then a solution can be found.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 16 Apr 2024, Wilfred van Velzen said the following...

Probably. Is it a secure session? Should be in the logs. Of maybe his
disk is full. Which mailer is used, on both sides?

Session is not secure, and he is using BinkIT (his system runs Synchronet over Linux)

I will schedule some troubleshooting session with him to check.

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - Back from the ashes (4:801/188)

On 15 Apr 2024, Alan Ianson said the following...

The best way to get to the bottom of something like this is to compare logs with your linked node.

Thanks, I will schedule a troubleshooting session with him.

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - Back from the ashes (4:801/188)

On 16 Apr 2024, Wilfred van Velzen said the following...

I don't know about other mailers.

I will ask for his config files as well, I really don't think that there is a disk full here, because it would appear quickly for other things, there might be something with the renaming...

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - Back from the ashes (4:801/188)

Hi Flavio,

On 2024-04-16 11:14:47, you wrote to me:

Probably. Is it a secure session? Should be in the logs. Of maybe his
disk is full. Which mailer is used, on both sides?

Session is not secure,

That could be the problem!

and he is using BinkIT (his system runs Synchronet over Linux)

I will schedule some troubleshooting session with him to check.

--- Mystic BBS v1.12 A48 (macOS/64)

The default in Mystic (if I remember correctly) is not to allow unsecure sessions.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.1-B20240412
* Origin: FMail development HQ (2:280/464)

Hello Flavio!

16 Apr 24 11:14, you wrote to Wilfred van Velzen:

Session is not secure, and he is using BinkIT (his system runs Synchronet over Linux)

I will schedule some troubleshooting session with him to check.

If the system with the files has a password set, and the collection systen
does not provide a password, a unsecure session is opened.
As no password is offered, waiting files are onot offered. The
collecting system can deliver files, that will be put in the unsecure
inbound.

So the other side either does not offer a password, or a different password.
That is my observation.

Kees

--- GoldED+/LNX 1.1.5--b20180707
* Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

On 15 Apr 2024, Alan Ianson said the following...

It could be there is no free space so the node can't store more files.
It could also be that files with the same filename exist in the nodes inbound already.

At the end, the files already existed at the nodes inbound directory, so after he deleted the originals, they were able to go through.

Thanks to everyone, your hints were very helpful! I asked him a copy of his binkit config so we can see if the renaming option is present as suggested.

Regards,
Flavio

--- Mystic BBS v1.12 A48 (macOS/64)
* Origin: Saturn's Orbit BBS - Back from the ashes (4:801/188)