Text 342, 106 rader
Skriven 2012-07-12 15:03:13 av mark lewis (1:3634/12.0)
    Kommentar till text 285 av Nicholas Boel (10275.fidonews)
Ärende: .fidonet
================
 > really? you don't see anything wrong?

 NB> Nope.

then you are not reading it properly...

 > The originating address should be specified in a form that
 > constitutes a valid return address for the originating network.

 NB> And If synchronet is setup correctly, it was a valid return address
 NB> for my system. 

for the NETWORK not your system... netmail travels TO: someone on a destination
FTN addressed system... this information is pulled from the MSGID line by most
FTN editors because it is supposed to be a valid path back to the writer of the
message containing the MSGID...

 NB> There's an option in the tosser to import any netmail (ie: 
 NB> *@1:154/10) to me. I don't have this option set, because it would 
 NB> get in the way of areafix and external filefix support.

many tossers have something similar but it is for moving the sysop's netmail to
another netmail area... most all tossers also have the ability to import user's
netmail into yet another netmail area on the BBS so they can do private
netmail, too... these are two different and seperate functions...

 > "Access_Denied#pharcyde.foobar@1:4/9" as the valid return address... this 

 NB> How is having any network name before the node number valid? Either
 NB> way, per my previous paragraph, that would work as well as what I
 NB> do present as the MSGID. 

noooo... why? because the message number and the messagebase name mean nothing
to anyone or anything outside of your BBS software... there is no reason for it
to be out here in the wild... some might consider it a security flaw in that it
leaks configuration information about your message base setup but that's
something else entirely...

 > address... your address is 1:154/10... 10186.fidonews means nothing to any
 >  editors out here... it is definitely not part of the address used to send
 >  private netmail to you... if you see nothing wrong, then why can i not
 > write a netmail to you as "Nicholas Boel, 10186.fidonews@1:154/10" which
 > is how the MSGID is designed to be used??? do you see the problem now?

 NB> It shouldn't mean anything to editors out there. It should only be
 NB> a means of sending netmail to my system. If configured for it, I
 NB> would get that netmail.  

right... so tell us what the routing systems will do with a netmail addressed
to you and being sent to 10196.fidonews@1:154/10 please...

that is provided that they just take the originating address field as it is
written and do not attempt to parse it at all... that's also providing that the
destination address is accepted by the editor, the bbs, the mail tosser, and
the mailer without choking any of them...

 NB> I see what you're saying, but I don't have the need or use for it,
 NB> as I can just type in a name and netmail address and send netmail.
 NB> I don't have to be in a specific JAM echo to send network-specific
 NB> netmail, either. 

right... but is that when replying via netmail to an echomail message? most
software uses the MSGID originating address to prefill the message header
information... the TO: name is pulled from the FROM: field and the address is
pulled from the MSGID unless it doesn't exist and then it may be pulled from
elsewhere finally ending up being pulled from the origin line...

 NB> By all means, the Synchronet developers are alive and active. You
 NB> know this because you post in some of the Syhnchronet echos. Bring
 NB> it up to them and see what they say about it.

as mentioned before, i have... you quoted my words in the next paragraph ;)

 > this has been brought up numerous times before with those developers but
 > just like other things, quote initials for example, they get ignored or
 > start to turn into some huge almight argument battle crap... i've quit
 > trying because i'm tired of arguing... they're right and everyone else is
 > wrong...

 NB> There's a bit of stubbornness in everyone.

yes... and sometimes youthful stubbornness, too ;)

 > it is caused by your software creating a non-standard address field in its
 >  MSGID which causes other editors, unless they are specifically coded to
 > handle this non-standard format, to pull what looks close to use in the
 > address they display for your system...

 NB> I'm midway through setting up another software that I sometimes
 NB> hook up as a point system, so I'm not all that worried about it
 NB> anyways.

most sysops are not worried or bothered by things like this... they only want
to use their software to do what they like to do... that's life... some are
technical oriented and others not...

 NB> But by all means, if it irks you to that point, bring it up to
 NB> them. I've mentioned it to them and one of them wants the spec
 NB> reference. That is all so far.

they are perfectly aware of the spec and the problem... they have been for
years...

)\/(ark

 * Origin:  (1:3634/12)