Re: Message ID and trouble ticketing system, posted by David Pilgram on Fri Mar 7 21:53:28 2008
|
>>Stefan Ritt wrote:
>>
>>Ok, now I got the point, also Richard had the same problem. Assume we have 10 threads, and thus
>>ticket numbers 1-10. Now we get a reply to #2, which then pops up to the top of the list. A new
>>message increments the top entry of all entries, and then wrongly gives a new #3, instead of #11.
>>
>>I fixed this in SVN revision 2073, where elogd searches *all* logbook entries for the largest
>>index, then increments this one by one. The fix will be contained in the next release.
>
>----
>
>Great! Thanks Stefan, off to download right now!
>
>Great program, by the way, but don't think you need to be told that yet again!
---
Oh ho!
I've tried this on an existing database, where most entries do not have a ticket #. The previous entry #
(previous in ID sense) is T00550, say. But when I start a new thread, the ticket # is T00001. Is it being put
out by no entry for ticket # in most of the database?
LATER UPDATE.
On a small database (12 entries, with 45 comments in total), this worked as expected if most or all entries have ticket numbers, even if the previous (by id #) had not had a ticket number. (I had to edit every entry to put in ticket numbers).
The only thing I can think of is the number of entries that don't have a ticket #, or a line in the .log file entry saying "Ticket: " but am looking further into this.
(BTW, am posting this way to get around the proxy server problem I have!) |
Problems with elog client, posted by Yoshio Imai on Wed Apr 9 14:41:12 2008
|
Hi!
Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog client with -e <id> option. The only console output is "Error transmitting message". Submitting an entry via the client is not problem.
Running the server with -v option does not yield any output at the time of the edit attempt. Running the client with -v option also doesn't help, because whatever the other options, only the help page is printed out and nothing else done. Btw, there is now a conflict between -s for "use SSL" and -s for the "subdir" option.
Any ideas?
Yoshio |
Re: Problems with elog client, posted by Stefan Ritt on Wed Apr 9 23:03:53 2008
|
| Yoshio Imai wrote: |
|
Since our upgrade to elog 2.7.3, it is not possible any more to edit an existing elog entry using the elog client with -e <id> option. The only console output is "Error transmitting message". Submitting an entry via the client is not problem.
Running the server with -v option does not yield any output at the time of the edit attempt. Running the client with -v option also doesn't help, because whatever the other options, only the help page is printed out and nothing else done. Btw, there is now a conflict between -s for "use SSL" and -s for the "subdir" option.
Any ideas?
|
The problem had to do with the integration of native SSL into elog/elogd. I tried to fix it in revision 2099. Please give it a try. I have not tried yet the SSL mode, but I changed the -s for "subdir" to -d not to collide with SSL. |
|
Problem with Email Notification, posted by mike cianci on Sat Mar 1 07:40:18 2008
|
Sorry to bother you with this, but I am not a programmer and this is probably a simple question but I need some help if someone has the time.
Under Global I have the command - SMTP host = smtp.comcast.net
ELOG responds with - Error sending Email via "smtp.comcast.net": 5.1.0 sender rejected : invalid sender domain
|
|
Re: Problem with Email Notification, posted by Stefan Ritt on Sat Mar 1 15:08:07 2008
|
| mike cianci wrote: |
|
Sorry to bother you with this, but I am not a programmer and this is probably a simple question but I need some help if someone has the time.
Under Global I have the command - SMTP host = smtp.comcast.net
ELOG responds with - Error sending Email via "smtp.comcast.net": 5.1.0 sender rejected : invalid sender domain
|
Your SMTP server does not accept the email send request from ELOG. That can have many reasons. Most systems are set up so that they do not accept SPAM. To do that, they do various checking of the sender address etc. Maybe you need an "Email from = mike2.cianci@comcast.net" in your config file to have a "real" sender address. Some more information you can get if you start elogd interactively in a DOS box with the "-v" flag, because then you will see all the debugging output of the communication between elogd and your SMTP server. |
|
Quick filter by ID, posted by David Pilgram on Tue Mar 4 14:03:00 2008
|
Hi,
I've just upgraded from 2.6.2 to 2.7.3.
In my config file, I have
Quick filter: Date, ID.
When starting 2.7.3, across the top I now get
"Error: Attribute "ID" for quick filter not found"
followed by an entry box.
If an ID is typed into that box, it sort of finds the right entry (+/- a few on occasion).
I cannot see any documented change that would affect how the Quick filter works. Any clues? Thanks. |
|
Re: Quick filter by ID, posted by Stefan Ritt on Thu Mar 6 15:06:35 2008
|
> Hi,
>
> I've just upgraded from 2.6.2 to 2.7.3.
>
> In my config file, I have
>
> Quick filter: Date, ID.
>
> When starting 2.7.3, across the top I now get
>
> "Error: Attribute "ID" for quick filter not found"
> followed by an entry box.
>
> If an ID is typed into that box, it sort of finds the right entry (+/- a few on occasion).
>
> I cannot see any documented change that would affect how the Quick filter works. Any clues? Thanks.
Actually it is nowhere written the 'ID' for a quick filter should work. After investigating, I realize that it
worked previously "by accident". I added in meantime some test so there is a warning for quick filter attributes
which do not exist, and that's what you got. I loosened this test for 'ID' now in the current SVN version, so it
can be used. It does however not display the single entry you want, but a page containing that entry (which then
is displayed in bold). If you want exactly one entry, just add it's ID to the URL, like
https://midas.psi.ch/elogs/Forum/65767
for your previous entry. |
Re: Quick filter by ID, posted by David Pilgram on Fri Mar 7 13:12:37 2008
|
> > Hi,
> >
> > I've just upgraded from 2.6.2 to 2.7.3.
> >
> > In my config file, I have
> >
> > Quick filter: Date, ID.
> >
> > When starting 2.7.3, across the top I now get
> >
> > "Error: Attribute "ID" for quick filter not found"
> > followed by an entry box.
> >
> > If an ID is typed into that box, it sort of finds the right entry (+/- a few on occasion).
> >
> > I cannot see any documented change that would affect how the Quick filter works. Any clues? Thanks.
>
> Actually it is nowhere written the 'ID' for a quick filter should work. After investigating, I realize that it
> worked previously "by accident". I added in meantime some test so there is a warning for quick filter attributes
> which do not exist, and that's what you got. I loosened this test for 'ID' now in the current SVN version, so it
> can be used. It does however not display the single entry you want, but a page containing that entry (which then
> is displayed in bold). If you want exactly one entry, just add it's ID to the URL, like
>
> https://midas.psi.ch/elogs/Forum/65767
>
> for your previous entry.
Thanks Stefan! |
|