MV>>> Title: The INO4 flag. AV>> As I already told, it's useless. MV> Yes, I know your POV. If you are right, then this proposal will go MV> the way that most proposals have gone: to the reference library.
Most likely...
MV> If not, we may see this flag in the nodelist some day. Time will MV> tell.
Yes.
AV>> One single not-really-a-problem raises only when the nodelist AV>> line contains INA:f.q.d.n flag, as the old mailers may be unable 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.
Ancient mailers are unable to use IPv6 at all.
AV>> 2. Checking that manually. MV> The idea of the nodelist is that mailers can find the required MV> information without human intervention.
"can find" == "is fresh enough to know about ${subj}" If it can process ${subj}, it can process EAI_ADDRFAMILY as well.
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.
Once again: that abandonware is not IPv6 capable.
-- Alexey V. Vissarionov aka Gremlin from Kremlin gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii
... god@universe:~ # cvs up && make world --- /bin/vi * Origin: http://openwall.com/Owl (2:5020/545)
