MH> The migration went through like it was planned. We changed the IP MH> address behind the existing hostname entry and minutes later, the MH> first connections went to the new system. That worked for a lot of MH> systems, but not for all of them.
MH> To facilitate possible future migrations, i'd like to discuss that. MH> These are the errors i've noticed:
MH> - Some systems still connect to the old system, even if the DNS end MH> the nodelist entry points to the correct destination. Why is that, MH> that these systems seem to have been configured to ignore the nodelist MH> and connect to what ever was configured? What's the benefit of a MH> nodelist when the content is not used?
MH> - Some of these systems who connect to the old system, send me the MH> PKTs for 2:301/1, even when i'm NOT presenting that address in my MH> Bink. Makes no sense to me, especially not from a security MH> perspective. The mailer should only send PKTs to a destination system MH> if the desired address is presented by the receiving system & the MH> session password matches.
MH> I've noticed some of these systems are running D'Bridge. Were these MH> issues ever discussed and/or adresseed? Or are these simply sysop's MH> errors?
MH> Best wishes & have a nice evening, MH> Matthias
MH> BTW: The actual cleanup (netmailing affected sysops) takes much more MH> time than the migration took.
it was working for a while for me (2:371/0), but i don't get any mail from Alisha's system since a few days.
