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


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Apr 24 01:17:44, всего сообщений: 7124
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 137 из 7124 ======================================= FTSC_PUBLIC =
От   : mark lewis                       1:3634/12.71       07 Nov 13 09:57:16
Кому : Alexey Vissarionov                                  07 Nov 13 09:57:16
Тема : FSP-1038.001
FGHI : area://FTSC_PUBLIC?msgid=1:3634/12.71+27b9d268
На   : area://FTSC_PUBLIC?msgid=2:5020/545+527a1f23
= Кодировка сообщения определена как: CP866 ==================================
==============================================================================
On Wed, 06 Nov 2013, Alexey Vissarionov wrote to Michiel van der Vlist:

AV>> to detect EAI_ADDRFAMILY returned by getaddrinfo() or NO_ADDRESS
AV>> returned by archaic gethostbyname()
AV>> Once faced, that may be solved by either:
AV>> 1. Updating the mailer.
MV> Which will not be possible for many mailers.

AV> Ancient mailers are unable to use IPv6 at all.

not only ancient mailers but also older OSes... and this is exactly the reason for using the flag ;)

AV>> 2. Checking that manually.
MV> The idea of the nodelist is that mailers can find the required
MV> information without human intervention.

AV> "can find" == "is fresh enough to know about ${subj}"
AV> If it can process ${subj}, it can process EAI_ADDRFAMILY as well.

wrong... my ancient mailer reads and processes any flags, normal or user... some it can do things with automatically (eg: CM) while others have to be configured but flags are recognised as it does not try to maintain some internal list of valid flags like other software (and people) try to do...

AV>> So leaving it up to sysops seems to be the best solution. And,
AV>> of course, we should recommend checking for EAI_ADDRFAMILY to
AV>> the developers.
MV> Of course. But that won't help the syops that use abandonware.

AV> Once again: that abandonware is not IPv6 capable.

my mailer is not IPv4 capable but it talks to other mailers via IPv4 (FTN over telnet) quite readily... mailers do not need to support any specific transport format outside of FTN stuff... if they can talk to a FOSSIL driver, then they have an advantage in that they can communicate over most any transport format (eg: POTS, ISDN, TELNET, VMODEM, etc...)... the mailer only needs to be able to talk to the FOSSIL and let the FOSSIL speak the necessary format for the pipe...

)\/(ark

--- FMail/Win32 1.60
* Origin:  (1:3634/12.71)

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