How do we make Squeak use our own email server? Is it a matter of simply specifying the correct server name in the correct place?
How do mail servers know that the password request email was sent directly from Squeak and therefore to block it? I'm still learning, thanks.
On Sun, Sep 6, 2020 at 12:03 PM Levente Uzonyi leves@caesar.elte.hu wrote:
Hi All,
(CC'd board as well)
I have restarted the image. It seemed to have been locked up by trying to send a password recovery email directly from the server instead of using our own mail server[1]. This is bad practice and the IP of the server has been rightfully added to some spam blacklists, hence the blocked image (which expects that email sending always succeeds...). Outgoing emails should go through our own mail server. This needs to be changed ASAP, as I suppose a few more password reminders will result in a locked up image again.
Levente
[1] Relevant parts of the stack trace in case someone wants to have a look at the image:
SMUtilities class>>mail:subject:message: SMUtilities class>>mailPassword:for: [] in SMSqueakMapView>>mailnewpassword {[username value isEmptyOrNil ifFalse: [account := model accountForUsername...]}
On Sat, 5 Sep 2020, David T. Lewis wrote:
Forwarding to the box-admins list.
The web interface for map.squeak.org is not responding, and updating a SqueakMap Package Loader from Squeak is not working. Presumably the server needs to be bumped.
I'm not sure who has the keys to this?
Thanks, Dave
On Sat, Sep 05, 2020 at 03:44:45PM -0400, Phil B wrote:
It doesn't appear to be responding to requests (gateway time-out)