On 05.01.2018, at 14:30, David T. Lewis lewis@mail.msen.com wrote:
Thanks Tobias,
On Fri, Jan 05, 2018 at 09:31:31AM +0100, Tobias Pape wrote:
Hi Dave,
On 05.01.2018, at 01:21, David T. Lewis lewis@mail.msen.com wrote:
I am only guessing, but stepping through the smtp interaction in a debugger tells me that an optional username/password may be exchanged in the smtp protocol. The squeaksource.com image does not supply this, possibly because it originally sent mail via box2.squeak.org, and now via mail.squeak.org (???).
Is a username/password required for the client on dan.box.squeak.org to connect to the smtp server at mail.squeak.org?
Sorry I did not step in earlier.
Yes. I configured the mailer to _relay_ for our boxen, so that there's no user/pw interchange. What would it be in the first place?
I was just taking a wild guess there, thanks for the clarification.
Also, You could try localhost, there's an exim running that uses mail. as a smarthost.
Well d'oh! I am an idiot. I thought I had tried that a long time ago, but apparently not. I just ran a test with localhost and it works fine.
I wonder, because it had worked up until now???
It has never worked since the move to Rackspace. I had disabled the mail delivery in the squeaksource.com image to prevent problems (VMMaker is on source.squeak.org now, and I'm not sure that anyone would care about the mail notifications anyway).
But it turns out that there are occasional error conditions in SqueakSource for which the image tries to send mail to the box-admins list, which (due to the mail failures) results in a recursive error condition that eventually locks up the image.
I'll update the squeaksource.com image to relay the mail via localhost. That will resolve the problem of occasional image lockups.
Thank you!
\o/
:D -t