This is a test from my uplink to see mailflow.

--- QScan/PCB v1.20a / 01-0462
* Origin: Christian Fellowship | cfbbs.no-ip.com 856-933-7096 (1:266/512)

Hi! Jason,

On 02 Nov 2021, Jason Bock said the following...

@MSGID: 1:266/512@fidonet.org 60233287
@SEEN-BY: 15/0 19/10 36 50/109 106/201 116/18 120/302 331 124/5009
129/12 102
@SEEN-BY: 129/125 160 165 134/101 153/757 7715 203/0 218/700 221/1 6 360 222/2
@SEEN-BY: 230/150 152 240/1120 250/1 261/1 38 100 220 1466 266/32 75 420 512
@SEEN-BY: 266/618 267/152 154 155 311 275/100 280/464 5003 5555 282/1056 1060
@SEEN-BY: 291/100 111 292/854 301/1 320/119 219 335/364 340/400 341/66 396/45
@SEEN-BY: 423/81 460/58 463/68 467/888 640/1321 1384 712/848 801/161 189 @SEEN-BY: 3634/12 4500/1 5000/111 5001/100 5005/49 5019/40 5020/846 1042 2047
@SEEN-BY: 5020/2140 4441 5058/104 5064/56 5080/102 5083/444
@PATH: 266/512 261/38 5020/1042 221/6 1
This is a test from my uplink to see mailflow.

--- QScan/PCB v1.20a / 01-0462
* Origin: Christian Fellowship | cfbbs.no-ip.com 856-933-7096

Cheers,
Paul.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/32)
* Origin: Quinn's Rock vBox - sunny-side up on the desktop (3:640/1384)

Hi, Jason!

02 ­®ï 21 16:34, Jason Bock -> All:

@MSGID: 1:266/512@fidonet.org 60233287
This is a test from my uplink to see mailflow.

Got it...

--- QScan/PCB v1.20a / 01-0462
* Origin: Christian Fellowship | cfbbs.no-ip.com 856-933-7096 (1:266/512) SEEN-BY: 15/0 19/36 50/109 106/201 116/18 120/302 331 124/5009 129/12 102 125
SEEN-BY: 129/160 165 153/757 7715 218/700 221/1 6 360 222/2 230/150 152 SEEN-BY: 240/1120 250/1 261/1 38 100 220 1466 266/32 75 420 512 618 267/152
SEEN-BY: 267/154 155 311 275/100 280/464 5555 282/1056 1060 291/100 111 301/1
SEEN-BY: 320/119 219 335/364 340/400 341/66 396/45 460/58 256 1124 5858 463/68
SEEN-BY: 467/888 640/1321 712/848 801/161 189 3634/12 4500/1 4600/140 5000/111
SEEN-BY: 5001/100 5005/49 5019/40 5020/846 1042 2047 2140 4441 5054/30 SEEN-BY: 5058/104 5064/56 5080/102 5083/444
@PATH: 266/512 261/38 5020/1042 221/6 460/58

Have nice nights.
Stas Mishchenkov.

--- „®ªâ®à ¯«®å®£® ­¥ ¯®á®¢¥âã¥â, ­® ¨ å®à®è¥£® ­¥ à §à¥è¨â.
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5

On 3.11.2021 9.01, Wilfred van Velzen wrote:

And here are the ones from my dupe area:

= DUP_MSGS (2:280/464) ========================================================
From : Jason Bock 1:266/512 2021-11-02 16:34:00
To : All
Subj : Test from uplink ===============================================================================
AREA:FIDOTEST
@Via 2:280/464 @20211102.230544.970.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815

Via line in echomail? Is this some Fmail internal thing for dupearea?

'Tommi

---
* Origin: nntp://news.fidonet.fi (2:221/6.0)

Hi Tommi,

On 2021-11-03 10:33:50, you wrote to me:

= DUP_MSGS (2:280/464)
========================================================
From : Jason Bock 1:266/512 2021-11-02
16:34:00
To : All
Subj : Test from uplink
=========================================================================
======
AREA:FIDOTEST
@Via 2:280/464 @20211102.230544.970.UTC FMail-lnx64(Toss)
2.1.0.18-B20170815

Via line in echomail? Is this some Fmail internal thing for dupearea?

Indeed it is. They are added to messages that are moved to the dupes area. So you know the exact time the dupe arrived/was-processed, without having to dive in the logs.

A Via kludge line seems appropriate for this, because it already is a fidonet standard, for this exact purpose. But maybe I should have "renamed" it to something like "@Received" or "@Processed" to avoid these questions. ;-)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi Jason!

02 Nov 2021 16:34, from Jason Bock -> All:

@MSGID: 1:266/512@fidonet.org 60233287
This is a test from my uplink to see mailflow.

SEEN-BY: 15/0 19/36 102/127 103/705 106/201 116/18 120/302 331
124/5009
SEEN-BY: 124/5016 129/12 102 125 160 165 134/100 153/105 135 757 7715 SEEN-BY: 154/10 203/0 218/700 221/0 6 222/2 230/150 152 240/1120 5832 SEEN-BY: 250/1 261/1 38 100 220 1466 266/32 75 420 512 618 267/67 152 SEEN-BY: 267/154 155 311 275/100 280/464 5003 5555 282/1056 1060
291/100
SEEN-BY: 291/111 292/854 8125 301/1 310/31 320/119 219 340/400 341/66 SEEN-BY: 341/234 396/45 423/120 460/58 640/1321 712/848 770/1 801/161 SEEN-BY: 801/189 2452/250 3634/12 5020/1042
@PATH: 266/512 261/38 153/757 280/464

CU, Ricsi

... The more unpredictable the world is the more we rely on predictions!
--- GoldED+/LNX
* Origin: For every expert there is an opposite expert. (2:310/31)

Hello, Wilfred van Velzen.
On 03/11/2021 9.44 you wrote:

Hi Tommi,
On 2021-11-03 10:33:50, you wrote to me:

= DUP_MSGS (2:280/464)
========================================================
From : Jason Bock 1:266/512 2021-11-02
16:34:00
To : All
Subj : Test from uplink
=========================================================================
======
AREA:FIDOTEST
@Via 2:280/464 @20211102.230544.970.UTC FMail-lnx64(Toss)
2.1.0.18-B20170815

Via line in echomail? Is this some Fmail internal thing for dupearea?

Indeed it is. They are added to messages that are moved to the dupes area. So you know the exact time the dupe arrived/was-processed, without having to dive in the logs.
A Via kludge line seems appropriate for this, because it already is a fidonet standard, for this exact purpose. But maybe I should have "renamed" it to something like "@Received" or "@Processed" to avoid these questions. ;-)

Or you should not quote it to avoid these questions. :D

Tommi

--- HotdogEd/2.13.5 (Android; Google Android; rv:1) Hotdoged/1632905978000 HotdogEd/2.13.5
* Origin: nntp://news.fidonet.fi (2:221/10.0)

Hi Tommi,

On 2021-11-03 12:50:23, you wrote to me:

AREA:FIDOTEST
@Via 2:280/464 @20211102.230544.970.UTC FMail-lnx64(Toss)
2.1.0.18-B20170815

Via line in echomail? Is this some Fmail internal thing for dupearea?

Indeed it is. They are added to messages that are moved to the dupes
area. So you know the exact time the dupe arrived/was-processed,
without having to dive in the logs. A Via kludge line seems
appropriate for this, because it already is a fidonet standard, for
this exact purpose. But maybe I should have "renamed" it to something
like "@Received" or "@Processed" to avoid these questions. ;-)

Or you should not quote it to avoid these questions. :D

Too much "work"! ;-)

And maybe it inspires other software developers to do something similar.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Jason,

This is a test from my uplink to see mailflow.

It made it to Arkansas.

Daryl

=== MultiMail/Win v0.52
... There are a bunch of internet scams. Send me $10 to find out about them. --- SBBSecho 3.14-Win32
* Origin: The Thunderbolt BBS - Little Rock, Arkansas (1:2320/33)

On 3.11.2021 14.09, Wilfred van Velzen wrote:

??>>>> AREA:FIDOTEST
??>>>> @Via 2:280/464 @20211102.230544.970.UTC FMail-lnx64(Toss)
??>>>> 2.1.0.18-B20170815
TK>>> Via line in echomail? Is this some Fmail internal thing for dupearea?
WV>> Indeed it is. They are added to messages that are moved to the dupes
WV>> area. So you know the exact time the dupe arrived/was-processed,
WV>> without having to dive in the logs. A Via kludge line seems
WV>> appropriate for this, because it already is a fidonet standard, for
WV>> this exact purpose. But maybe I should have "renamed" it to something
WV>> like "@Received" or "@Processed" to avoid these questions. ;-)

TK> Or you should not quote it to avoid these questions. :D

Too much "work"! ;-)

Sure. ;-)

But what actually is the value of that @Via line? When saved the dupe message to JAM base the time stamp will stored there. And the node number should be known.. :)

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1
* Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/360.0)

Hi Tommi,

On 2021-11-03 18:04:05, you wrote to me:

??>>>> AREA:FIDOTEST
??>>>> @Via 2:280/464 @20211102.230544.970.UTC FMail-lnx64(Toss)
??>>>> 2.1.0.18-B20170815
TK>>> Via line in echomail? Is this some Fmail internal thing for
dupearea?
WV>> Indeed it is. They are added to messages that are moved to the
dupes
WV>> area. So you know the exact time the dupe arrived/was-processed,
WV>> without having to dive in the logs. A Via kludge line seems
WV>> appropriate for this, because it already is a fidonet standard,
for
WV>> this exact purpose. But maybe I should have "renamed" it to
something
WV>> like "@Received" or "@Processed" to avoid these questions. ;-)

But what actually is the value of that @Via line? When saved the dupe message to JAM base the time stamp will stored there. And the node number should be known.. :)

My dupes are in the Hudson database. It's also usefull when forwarding messages from the dupe database. That information would be lost if you forwarded from a Jam database (without the kludge).

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Jason,

This is a test from my uplink to see mailflow.

It made it to Arkansas.

Daryl

=== MultiMail/Win v0.52
... There are a bunch of internet scams. Send me $10 to find out about them.
--- SBBSecho 3.14-Win32
* Origin: The Thunderbolt BBS - Little Rock, Arkansas (1:2320/33)

Thank you!

---
* Origin: SiliconUnderground - Rochester, NY - siliconu.com (1:267/311)

This is a test from my uplink to see mailflow.

--- QScan/PCB v1.20a / 01-0462
* Origin: Christian Fellowship | cfbbs.no-ip.com 856-933-7096

(1:266/512)

Looks like it made it here.

... Tagline II: The Sequel.
--- Wildcat! v8.0.454.12 (May 9 2021), Editor Mod v2.1
* Origin: Omicron Theta * Southaven MS * winserver.org (1:116/18)