Joao Prado Maia wrote:
>>"Dear
>>user, this is in response to the issue you reported from ."
>
> Hmm, that is indeed a bug, but without more information it is hard to
> diagnose what the problem is.
I found this one. It's the "Tool Caption" variable on the General Setup
page, which ships empty and I didn't know what a tool caption was. On
the web, it defaults to "Eventum" if this is blank, but the email just
prints the empty value.
> I'm guessing from that message that you
> were using the issue auto-creation feature when this happened?
Yes, it's the "New Issue Created" message:
"This is an automated message sent at your request from ."
> I don't have a self-signed imap
> server to play with right now, but maybe this will fix your problem.
Well as it happens I do, so I will definitely check this out. It won't
talk to SSL & TLS IMAP at all right now.
Here's the POP3-(SSL|TLS)-self-signed:
Error while connecting to the email server - Can't open mailbox
{mail.phx3.nearlyfreespeech.net:995/pop3/ssl/novalidate-cert}INBOX:
invalid remote specification
Error while connecting to the email server - Can't open mailbox
{mail.phx3.nearlyfreespeech.net:995/pop3/tls/novalidate-cert}INBOX:
invalid remote specification
Is that INBOX supposed to be on there for POP?
Here's IMAP:
Error while connecting to the email server - Can't open mailbox
{mail.phx3.nearlyfreespeech.net:993/imap/ssl/novalidate-cert}INBOX:
invalid remote specification
Error while connecting to the email server - Can't open mailbox
{mail.phx3.nearlyfreespeech.net:993/imap/tls/novalidate-cert}INBOX:
invalid remote specification
Also, out of curiosity, what is the difference between "IMAP" and "IMAP,
no TLS?"
And, while I'm at it, wouldn't it be neat if, in conjunction with IMAP
servers, one could specify an alternate folder for "Leave Copy of
Messages on Server?"
>>4) It takes weird errors about "bad message number" in the
>>cron job (I
>>think it's the one that reads the mail, not the one that sends it.)
>
> What type of server are you using? POP3 or IMAP?
Yeah, happens with both. I thought that was odd.
Here's a silly question. Provided the backend MySQL server is
accessible from both, is there any reason that the cron stuff that
interacts with email has to be on the same server as the site?
> If you still have copies of those emails that are replies but Eventum
> doesn't recognize those as such, please send that to me privately. I'll
> take a look at the headers and see what the problem is.
That's done.
Looking at the code I think it may be a philosophical difference. To
me, if you send an email to the ticket system's email address, it ought
to take any possible excuse to associate that email with an existing
ticket. Based on the comments in the relevant file and the approach you
are taking it sounds like you are more concerned with preventing people
from forging their way onto tickets.
Perhaps a good compromise would be if it's got a valid ticket # in the
subject header but the checks don't like its header pedigree, leave it
unassigned rather than automatically opening a new ticket. I was
thinking to do this, but to add a customizable tag to the ticket number,
say [JDW182] for mine.
Hey, I'm curious, what happens if a person on email notification for a
ticket has an out-of-office autoresponder enabled and the auto-update of
tickets via email is also enabled?
>>I'll try to capture any fun errors I come across.
>
> Yes, send those in.
Will do.
> Hmm, strange that you find it slow. We don't have any problems with it
> running on a much bigger dataset. Is the interface slow on a particular
> set of pages?
Don't worry about it. Let me rule out the other stuff first. I've seen
some PHP apps, portals and forum software, that can be configured to
print the number of DB queries it took to build a page and the total
time spent executing them. That would be a handy bit of info to have.
> No implications -- the database will just contain a lot of broken
> foreign records.
Perhaps there could be a nice "hidden" status added where lonely tickets
would go to die, and stop showing up in the reports and whatnot.
>>- It tries in a couple of places to change timeout values
>>when running
>>in safe_mode, which is a no-no. Other than that, it seems to
>>work fine
>>in safe mode.
>
> If you can give more details on this, I'll see if this can be fixed.
I ended up commenting out "set_time_limit(0)" in:
config.inc.php
manage/check_email_settings.php
manage/projects.php
But while grep'ing to find these, I noticed
include/pear/Net/SmartIRC.php had already been there, done that, so I
changed them to "@set_time_limit(0)" instead of "#set_time_limit(0)"
which is obviously the better solution.
> We would be happy to accept your patches :)
Your enthusiasm is awesome! I'll see if bitkeeper is something that
wants to play in my sandbox.
Thanks for all your help!
Jeff
--
Jeff Wheelhouse
jdw@stripped
