|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
Problem when testing tasklist tool
by Cristiane
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message Hello sakai-dev list,
I am a newbie to sakai, so I'm trying to follow the task list tool exercise in http://bugs.sakaiproject.org/confluence/display/BOOT/Task+List+Tool+Exercise I've checked out the code: https://source.sakaiproject.org/contrib/programmerscafe/tags/sakai-2.2/tasklist-iteration3-CSS/ I've done maven sakai to this project, it builds successfully, but I can't see the tasklist tool in worksite setup -> edit tools Does anyone know why I can't see the tasklist tool? Thanks, Cristiane Yaguinuma. ---------------------- This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a. sakai-dev) site. You can modify how you receive notifications at My Workspace > Preferences. |
|
|
Questioning "James" stability as a sakai subsystem for email messaging process.
by Duran Goodyear
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message I've been tasked with trying to determine the stability history of
"James" as an email subsystem in Sakai. I would like to hear if there is anyone out there that has experienced any failures of email archive, that has been able to determine if James is at fault, or suspected of being at fault. If you'll bear with me... Last week it came to my attention as the Sakai Administrator, that a significant percentage of emails sent to email archive addresses were not even making it to the sakai server. (20% - 30%) Below explains the scenario involving a successful delivery of a "email archive" message to its recipients. Our users have to use their uarts.edu email account to send email to sakai, it is tied in to their active directory name, so that the email account name is the same as their sakai username. this manages the permission level of who can send to email archive, since its the same username for everything... User sends an email via their valid email account, using a MAPI client, the OWA (outlook web access) client or an IMAP client. All mail (port 25) traffic from outside or domain is blocked at the firewall. Port 25 can come from anywhere on campus, which allows us to just use the internal mail server (mail.uarts.edu). Sendmail listens on port 25 for SMTP traffic from our exchange server. (or any other box on campus) /var/log/maillog reports all incoming email at this detail level --> Sep 12 08:52:43 sakai sendmail[18225]: l8CCqbc2018225: from=<DGoodyear@...>, size=948, class=0, nrcpts=1, msgid=<B7B505B8F8C92243A7F4BA58E315C40906C184CD@...>, proto=ESMTP, daemon=MTA, relay=[10.64.3.21] Sep 12 08:52:43 sakai sendmail[18241]: l8CCqbc2018225: to=<sakai.help@...>, delay=00:00:00, xdelay=00:00:00, mailer=esmtpjames, pri=120948, relay=localhost.uarts.edu. [127.0.0.1], dsn=2.0.0, stat=Sent (Message received) When a message is received by sendmail, that james recognizes as valid for its purposes, we see this in the ..../sakai/tomcat/sakai/logs/james-2007-09-12.log (james sets a new log file daily for us) 12/09/07 08:52:43 INFO smtpserver: Successfully spooled mail from DGoodyear@... for [sakai.help@...] What I've described above, results in a successful delivery to the distribution list of an email archive message. An unsuccessful delivery looks like this. User sends an email to a known valid email archive address (for example sakai.help@...). Sendmail never logs receiving an email. James Logging never logs receiving an email from sendmail. End receivers of the email archive messages never receive the message. Original sender never receives an NDR (Non Delivery Report). The email simply vanishes. This event, is completely inconsistent, and completely unrepeatable. It happens at one moment, and if you test the same problem case immediately, it works again. My theory is that simply put, the message never makes it to the sakai server, and is vanishing at some stage while it is still in exchange's hands. Our exchange admin is requesting a brain dump from everyone I can talk to about the stability of James and how it works with Sendmail. His opinion is that the Java based functionality is at fault for the missing messages... He additionally would like to know if anyone has used PostFix instead of Sendmail, and if there is any documentation for that. And, if Postfix could replace Sendmail AND James. Thank you for your thoughts on this matter. Any and all responses will help me out with this. ] duran goodyear ] web developer ] the university of the arts ] 215.717.6068 [see attachment: "message0.html", size: 5009 bytes] Attachments: message0.html https://collab.sakaiproject.org/access/content/attachment/3f09725b-ed91-4bdb-80a8-4b3a72e4ea1d/message0.html ---------------------- This automatic notification message was sent by Sakai Collab (https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a. sakai-dev) site. You can modify how you receive notifications at My Workspace > Preferences. |
|
|
|
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |