开云体育

linbpq64 forwarding problems personal messages.

Boudewijn (Bob) Tenty VE3TOK All Messages By This Member #42896 The problem is that personal messages to the same destination are not always forwarded. One is forwarded and the other not and all have exactly the address. I tried several version of linbpq64, from those released in August to the last one of December with the same negative result. The effected message is not always put in the queue ready to be forwarded with the next forwarding cycle. I can only force it by putting it in the queue (yellow) for that particular forwarding partner and in that case it is delivered. With other words, they are not always put in the queue. Remember, they have all the same destination address. What is causing this behaviour? Bob (Boudewijn) VE3TOK -- There is nothing permanent except change -Heraclitus
Niels PD9Q All Messages By This Member #42897 开云体育 Hi Bod, I don't know the answer, but I'm curious what the route trace looks like in the BBS log. Of a message that does get into the queue and of a message that doesn't get into the queue. All the best in 2025 73 Niels Op 31-12-2024 om 07:20 schreef Boudewijn (Bob) Tenty VE3TOK: toggle quoted message Show quoted text The problem is that personal messages to the same destination are not always forwarded. One is forwarded and the other not and all have exactly the address. I tried several version of linbpq64, from those released in August to the last one of December with the same negative result. The effected message is not always put in the queue ready to be forwarded with the next forwarding cycle. I can only force it by putting it in the queue (yellow) for that particular forwarding partner and in that case it is delivered. With other words, they are not always put in the queue. Remember, they have all the same destination address. What is causing this behaviour? Bob (Boudewijn) VE3TOK
Mark Taylor All Messages By This Member #42898 By not forwarding a message BPQ is telling you that it cannot find a route to the recipient. ? If you created the message in both cases and the values are as you say then it is a situation that cannot happen. We've all been there... ? But, If the messages were just passing through your BBS then look at the R lines in the messages to see from which BBS you received the messages. Particularly if you received one of the message from the BBS of the addressee.? Your BBS will not send the message back to the same BBS from which you received it, and if it is your only route to that person then BPQ has no other place to send it.? If that is the case then it would indicate a mis-configuration of his BBS, not yours. ? One possibility is that your BBS received a message for that station and forwarded it to him. He received another message addressed to him from someone else' BBS, and his BBS sent it to you even though it was addressed to him. Again, a mis=configuration of his BBS, not yours. ? ? Yes, the log will probably help if you still have them. ? ? -- 73, Mark, N5MDT Montgomery, Texas ? ? ?
Boudewijn (Bob) Tenty VE3TOK All Messages By This Member #42924 开云体育 Hi Niels, Just normal, when that message goes out and it uses the exact route as configured as it is the only configured route to that destination. Another message with the same destination, exact same address, never goes in the queue. Message exchange between BPQ and FBB side of the Netrom link is:? FF? in the end. (No, message to send). I have to go over that trace again. Also all the best for 2025 en een prettige jaarwisseling! 73, Bob (Boudewijn) VE3TOK On 12/31/24 03:27, Niels PD9Q wrote: Hi Bod, I don't know the answer, but I'm curious what the route trace looks like in the BBS log. Of a message that does get into the queue and of a message that doesn't get into the queue. All the best in 2025 73 Niels Op 31-12-2024 om 07:20 schreef Boudewijn (Bob) Tenty VE3TOK: The problem is that personal messages to the same destination are not always forwarded. One is forwarded and the other not and all have exactly the address. I tried several version of linbpq64, from those released in August to the last one of December with the same negative result. The effected message is not always put in the queue ready to be forwarded with the next forwarding cycle. I can only force it by putting it in the queue (yellow) for that particular forwarding partner and in that case it is delivered. With other words, they are not always put in the queue. Remember, they have all the same destination address. What is causing this behaviour? Bob (Boudewijn) VE3TOK -- There is nothing permanent except change -Heraclitus

Previous Topic Next Topic