Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции ENET.SYSOP
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции ENET.SYSOP с датами от 10 Jul 13 21:42:12 до 13 Sep 24 12:11:54, всего сообщений: 12549
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 2153 из 12549 ====================================== ENET.SYSOP =
От   : Oleg Pevzner                     2:46/50            25 Feb 15 23:49:12
Кому : All                                                 25 Feb 15 23:49:12
Тема : Re: File requesting with binkd
FGHI : area://ENET.SYSOP?msgid=2:46/50+54ee450b
= Кодировка сообщения определена как: CP1125 =================================
Ответ: area://ENET.SYSOP?msgid=2:280/464+54ef1a9a
==============================================================================
* Forwarded from ECHOLOOPS by Oleg Pevzner (2:46/50).
* Originally by: Wilfred van Velzen (2:280/464), 25 Feb 15 22:26.
* Originally to: Michiel van der Vlist.

Pkt from             : 1:123/500
Original pkt from    : 2:221/1
PATH                 : 280/464 154/10 123/500
Original PATH        : 280/464 203/0 221/1
Msg arrived          : Wed Feb 25 23:40:04 2015
Original msg arrived : Wed Feb 25 23:40:04 2015
@AREA:BINKD
Hi,

On 2015-02-25 21:26:37, Michiel van der Vlist wrote to Wilfred van Velzen:
  about: "File requesting with binkd":

WV>> I think you don't want to create incompatibilities between different
WV>> BSO mailers, they should all act the same,

MvdV> That is why the proposed autosendreq should be a configurable option...

Agreed.

But is there a real need for this new behaviour, even if it's more logical?

Current utilities that create .req files don't need it. They all do it the current way (otherwise it wouldn't work). It's only a little bit more convenient if you are creating .req files by hand, because you don't have to also create a .?lo file...

Bye, Wilfred.


-+- FMail-W32-1.69.1.95-B20140716
 + Origin: Native IPv6 connectable node (2:280/464)

Hello everybody.

   Lately I've been getting reports of loops in this echo. Here's  an example of this... Who is the source of these errors?

Oleg

--- GoldED+/LNX 1.1.5-b20110320
* Origin: R46 <--> R50 EchoMail Exchange (2:46/50)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.054505 секунды