Hello Internals,
I receive the following error when saving an RFC:
There was an unexpected problem communicating with SMTP: Unexpected return code - Expected: 250, Got: 554 | 554 5.5.2 <[i:p:v:6::addr]>: Helo command rejected: invalid ip address
From what I can gather, whatever SMTP server it is connecting to doesn't understand ipv6 addresses.
— Rob
Hello Internals,
I receive the following error when saving an RFC:
There was an unexpected problem communicating with SMTP: Unexpected return code - Expected: 250, Got: 554 | 554 5.5.2 <[i:p:v:6::addr]>: Helo command rejected: invalid ip address
From what I can gather, whatever SMTP server it is connecting to doesn't understand ipv6 addresses.
— Rob
It's best to email systems@ with this kind of issues. To diagnose this, do you get this every time you save something?
And it really helps to have really accurate timings of when it happens as the log is so noisey.
cheers
Derick
Hello Internals,
I receive the following error when saving an RFC:
There was an unexpected problem communicating with SMTP: Unexpected return code - Expected: 250, Got: 554 | 554 5.5.2 <[i:p:v:6::addr]>: Helo command rejected: invalid ip address
From what I can gather, whatever SMTP server it is connecting to doesn't understand ipv6 addresses.
— Rob
It's best to email systems@ with this kind of issues. To diagnose this, do you get this every time you save something?
Thanks! I'm not sure if I am a member of that list or not; one way to find out.
And it really helps to have really accurate timings of when it happens as the log is so noisey.
cheers
Derick
It looks like it was at 19:07 GMT, today. Thankfully, the HTML source includes the current time of the last update. It only appears when saving and leaving the "minor changes" box unchecked.
— Rob
Hello Internals,
I receive the following error when saving an RFC:
There was an unexpected problem communicating with SMTP: Unexpected return code - Expected: 250, Got: 554 | 554 5.5.2 <[i:p:v:6::addr]>: Helo command rejected: invalid ip address
From what I can gather, whatever SMTP server it is connecting to doesn't understand ipv6 addresses.
— Rob
It's best to email systems@ with this kind of issues. To diagnose this, do you get this every time you save something?Thanks! I'm not sure if I am a member of that list or not; one way to find out.
It's not a list, just an alias @php.net.
And it really helps to have really accurate timings of when it happens as the log is so noisey.
It looks like it was at 19:07 GMT, today. Thankfully, the HTML source includes the current time of the last update. It only appears when saving and leaving the "minor changes" box unchecked.
I'll give it a look in the next few days.
cheers
Derick
I receive the following error when saving an RFC:
There was an unexpected problem communicating with SMTP:
Unexpected return code - Expected: 250, Got: 554 | 554 5.5.2
<[i:p:v:6::addr]>: Helo command rejected: invalid ip addressFrom what I can gather, whatever SMTP server it is connecting to
doesn't understand ipv6 addresses.It's best to email systems@ with this kind of issues. To diagnose
this, do you get this every time you save something?Thanks! I'm not sure if I am a member of that list or not; one way to
find out.It's not a list, just an alias @php.net.
And it really helps to have really accurate timings of when it
happens as the log is so noisey.It looks like it was at 19:07 GMT, today. Thankfully, the HTML source
includes the current time of the last update. It only appears when
saving and leaving the "minor changes" box unchecked.I'll give it a look in the next few days.
I had a look just now, and tried it out. But I can't reproduce the
error.
cheers,
Derick
I receive the following error when saving an RFC:
There was an unexpected problem communicating with SMTP: Unexpected return code - Expected: 250, Got: 554 | 554 5.5.2 <[i:p:v:6::addr]>: Helo command rejected: invalid ip address
From what I can gather, whatever SMTP server it is connecting to doesn't understand ipv6 addresses.
I had the same issue just the other day. I assume the edit notification
can't be sent. This should be reported to systems.php.net, but maybe
one of these people is reading here.
Christoph