On Fri, 23 Mar 2001, Dan Ringrose wrote:
> Here's a fuller picture of my attempts to get email notification working.
> As I am new to the list, to smalltalk, and to swikis, please don't hesitate
> to tell me if this sort of request isn't really what this list is for.
Neither will I hesitate to tell you this: This sort of request is
*exactly* what this list is for (among other things). Alas, responses are
on a "have time for" basis :) But I have some time!
> > From: Bijan Parsia <[EMAIL PROTECTED]>
> > We need some VM, image, and Swiki version info.
> according to the package readme I'm using: Comanche 4.7 / Swiki Beta 12 on
> a macintosh, with system 9.1
Two pieces missing: the "VM" version (this would be the Squeak
*application*) and the "Image" version (this is the think you loaded
comanche into, or the Squeak "document").
> > See my question about hitting "override" rather than "inherit" in the
> > admin.
> Using the admin mode in the browser I've gone through and set alertsender
> and alertserver to override for each swiki. I update after each change. No
> notification.
Good, it's not that. Erhm...You have entered email address in the
"notifications" box of the page that wants notification, yes? (Sorry, just
trying to be thorough.)
> I then went to the server machine itself, hit save & exit,
> and then restarted ComSwiki - still no notifications.
That shouldn't be necessary (just FYI).
> > Second, see if you can use Celeste to send mail. If you can, that at least
> > helps narrow things down.
> I'm afraid I don't know what Celeste is.
Celeste is the built-in POP/SMTP/Mail client.
> Of course it is possible I don't
> really need email notification, but it seems so tempting.
Even if you don't *need* it, you should have it! It's a bug that needs
fixing.
Right now, I suspect three possible points of failure:
1) The setting isn't getting set or read properly.
Seems unlikely, as I would guess that this would show up
on every platform and I just tested my Win2000 box's swiki and
...well it didn't work until I put in the right SMTP host :)
But it did work, in the end.
2) Something's wrong with SMTPSocket or the socket prims.
Seems unlikely, using Celeste or that bit of
test SMTPSocket code from a workspace could rule this out.
3) Something's wrong with some aspect of your setup.
We've been ruling that out, and it seems odd
that Adam would have the same problem. However, for example,
some mailhosts won't do various sorts of relaying, so if
you don't have the alertSender right (or a variety of other
things) it might fail.
One thing to try, if you can, is to open up a Transcript window (World
menu->open->Transcript) and then edit a notifying page. On save, *if*
notification isn't failing at 1, you'll see a little dialogue which looks
something like:
"connecting to your.mail.host...220 your.mail.host ESMTP Sendmail
version; Fri, 23 Mar 2001 14:37:03 -0500 (EST)
250 your.mail.host Hello [your.server.machine], pleased to meet you
250 <[EMAIL PROTECTED]>... Sender ok
250 <[EMAIL PROTECTED]>... Recipient ok
354 Enter mail, end with "." on a line by itself
250 OAA14337 Message accepted for delivery
221 your.server.host closing connection"
If you're *not* getting this, well, I'll have a better idea where to go
next ;)
> I'm sure you all have better things to do than solve my problems, but I
> appreciate your help. Dan
Your problems are *our* problems until we figure out who's *really* to
blame :)
Cheers,
Bijan.
