= Сообщение: 10491 из 12492 ===================================== ENET.SYSOP = От : Wilfred van Velzen 2:280/464 09 Apr 21 20:08:21 Кому : Kees van Eeten 09 Apr 21 20:08:21 Тема : Re: Mime encoded E-mail as fidonet transport FGHI : area://ENET.SYSOP?msgid=2:280/464+60709e75 На : area://ENET.SYSOP?msgid=2:280/5003.4+60705528 = Кодировка сообщения определена как: UTF-8 ================================== ============================================================================== Hi Kees,
On 2021-04-09 14:43:30, you wrote to All:
KvE> Quite a few nodes are listed with only IMI as their Fidonet KvE> transport. Inlike the use of carrier pigeons, very little seems to be KvE> documented on the use Mime encoded e-mail messages.
KvE> There is FSP-1015 but only one node flies the ISE flag. Moreover ISE KvE> requires quite some additional information te be present in the KvE> e-mail.
KvE> Are Fidonet packages/mailbundles using Mime encoded e-mail sent KvE> manually in e-mail as an attachment or as inline include.
What is the difference?
FMail can send mime/base64 encoded .pkt files, to a configured email address for a node, by directly talking to a configured smtp server.
KvE> Is additional text added to the meessage?
FMail can add a text from an external file to every email send this way.
KvE> How is autority to send such mail implemented,
I'm not sure what you mean. You put an email address into the configuration of a node, and then it's used to send all .pkt files for that node to that email address. The autority is the one doing the configuration, so that would be the sysop of the system.
KvE> or is fully relied on the Pkt password?
That's a separate configuration item for a node in FMail.
KvE> Is a common text used as Subject, to distinguish the mail from other KvE> mail.
In emails that FMail sends it's always: "Mail attach"
KvE> On the receiving side: are the packets removed by a process, or just KvE> extracted manually from the e-mail? How is the identity of the sender KvE> verified?
FMail has no function(s) for this. So you need an external tool or do it by hand, to get the .pkt files from received emails and put it into an inbound directory for FMail to proces. From there on it's the normal checks on a .pkt (Is it from a configured node, does the pkt password match if used)
KvE> Setting up processes for sending en receiving without safeguards, KvE> proved to be trivial when using a dedicated mailbox.
KvE> I am interested to hear how others wave implemented the use of IMI.
For FMail this was al coded by the original author, so I don't know if he implemented it from some kind of standard, and if he had just IMI nodes in mind as receivers, or if he just improvised it somehow... There are no clues in the source or doc files about this.
Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815 * Origin: FMail development HQ (2:280/464)
