Forum Moderators: open
I was in the process of doing the final upgrade to the email system and a couple of things went wrong (have to rewrite some code). I tried to roll back to what we had, but some new data files are not compat with the old routines and it would take longer to write a conversion back than to just move forward.
The email subsystem is the toughest one of board routines to work on because it is very difficult to emulate a working environment offline.
I've got it done, but was a bit shy about putting it online in midweek. With a scripted mass mailer like the notification system is, the potential disaster scenarios numerous.
It's the toughest set of routines for me to work on since, I can't emulate the online environment (no sendmail equiv for winders). It has to be 99% right the first time. The days of being able to tweak stuff on the fly are gone.
I think I'll do it 4-5am my time tomorrow and see how it goes.
I can't emulate the online environment (no sendmail equiv for winders)
i think i read in the activestate perl documentation (last year's version) that there is at least one 3rd party sendmail module for perl on windows systems. a quick check of the latest version online now appears to say that sendmail is included in activeperl. i've stickymailed you the URL.
you could also install the Blat module and use that for sending email from perl on windows. when you have tested offline, you can change the couple of lines of blat for a couple of lines to call sendmail instead.
Good luck Brett.
How will we know when it is working?
I don't get email notification any more.
Getting that worked out was a major change. We've grown so much this fall that it crept up faster than I'd planned. The last week of Nov, we did more in a day, than we'd done in a weeks time in August. I had to deal with some very time consuming core things asap to stay online.
E is next on list...
