Directories in top groups, posted by Stephen A. Wood on Mon Apr 18 17:02:20 2005
|
I am trying to unify several existing logbook collections that run on
seperate servers under a single server using groups. For a top group, under
"[global topgroupname]", I would like to redefine the resource directory or
|
Re: Directories in top groups, posted by Stefan Ritt on Mon Apr 18 21:57:19 2005
|
> I am trying to unify several existing logbook collections that run on
> seperate servers under a single server using groups. For a top group, under
> "[global topgroupname]", I would like to redefine the resource directory or
|
Link To command..., posted by Tim Iskander on Mon Apr 18 17:57:38 2005
|
Is it possible to create a Link To command (ala Copy To, Move To) that
would allow you to reference an entry in another log book without copying it?
This would be handy as the info would be kept current in both log books.
|
|
Re: Link To command..., posted by Stefan Ritt on Mon Apr 18 19:27:09 2005
|
> Is it possible to create a Link To command (ala Copy To, Move To) that
> would allow you to reference an entry in another log book without copying it?
> This would be handy as the info would be kept current in both log books.
|
|
Mail not sent but message says it has been sent, posted by Mikael Salonvaara on Sun Apr 17 09:35:30 2005
|
If my email host refuses to send the email (476 connections denied), we
still get the message that the email has been sent - and no error message.
|
|
Re: Mail not sent but message says it has been sent, posted by Stefan Ritt on Mon Apr 18 09:04:21 2005
|
> If my email host refuses to send the email (476 connections denied), we
> still get the message that the email has been sent - and no error message.
>
|
|
logbook clone, posted by Emiliano Gabrielli on Thu Apr 14 12:38:04 2005
|
When I create a new logbook (I used an existing one as a template) elog
does not works anymore...
|
|
Re: logbook clone, posted by Stefan Ritt on Fri Apr 15 22:26:06 2005
|
> When I create a new logbook (I used an existing one as a template) elog
> does not works anymore...
|
MIME encoding of mail?, posted by Michael Husbyn on Thu Feb 10 09:03:02 2005
|
Hello,
This software is very good :) I like it, but I have some trouble with some
|
|
Re: MIME encoding of mail?, posted by Stefan Ritt on Sat Feb 12 18:00:48 2005
|
What you can try is to debug the communication between elogd and the SMTP
server. Just turn on logging via
|
|
Re: MIME encoding of mail?, posted by Michael Husbyn on Thu Apr 14 15:07:18 2005
|
> What you can try is to debug the communication between elogd and the SMTP
> server. Just turn on logging via
>
|
|
Re: MIME encoding of mail?, posted by Stefan Ritt on Thu Apr 14 15:42:44 2005
|
> What I can see is that it sends with charset=US-ASCII, even if the characters are
> non-US.
|
|
Re: MIME encoding of mail?, posted by Michael Husbyn on Fri Apr 15 15:12:55 2005
|
> > What I can see is that it sends with charset=US-ASCII, even if the characters are
> > non-US.
>
|
|
Re: MIME encoding of mail?, posted by Stefan Ritt on Fri Apr 15 15:25:30 2005
|
So you tell me that the message body is ok with Norwegian characters, it's only the subject?
That would mean that outlook interpretes the charset only for the message body, but not for
the subject. So if you have characters with an ASCII value greater than 127, your mail
|
|
Re: MIME encoding of mail?, posted by Stefan Ritt on Fri Apr 15 15:57:53 2005
|
Ok, I found it. It's in RFC2047 at
http://www.faqs.org/rfcs/rfc2047.html
|
|
Re: MIME encoding of mail?, posted by Stefan Ritt on Fri Apr 15 21:10:27 2005
|
I implemented this, but found some problems. If I encode the subject like
Subject: =?ISO-8859-1?Q?ורז?=
|
|
Re: MIME encoding of mail?, posted by Michael Husbyn on Fri Apr 15 21:31:26 2005
|
> I implemented this, but found some problems. If I encode the subject like
>
> Subject: =?ISO-8859-1?Q?ורז?=
|
|
Re: MIME encoding of mail?, posted by Stefan Ritt on Fri Apr 15 21:49:00 2005
|
> If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
> Maybe that could be a solution?
|
|
Re: MIME encoding of mail?, posted by Michael Husbyn on Fri Apr 15 22:24:49 2005
|
> > If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
> > Maybe that could be a solution?
>
|
|
Re: MIME encoding of mail?, posted by Stefan Ritt on Fri Apr 15 21:14:05 2005
|
> Subject: Testing ורז
>
> Becomes
|
|
Conditional conditions?, posted by Steve Woughter on Tue Apr 12 16:07:12 2005
|
Can conditional attributes be assigned as conditions?
Arbitraty Example:
|
|
Re: Conditional conditions?, posted by Stefan Ritt on Wed Apr 13 10:06:56 2005
|
> Can conditional attributes be assigned as conditions?
Well, I guess the question was: "Can you implement this?" I'm sure that you
|
XML password files, replication & FreeBSD, posted by G on Tue Apr 12 01:05:20 2005 
|
Ok this really is 2 questions.
1)
|
|
Re: XML password files, replication & FreeBSD, posted by Stefan Ritt on Tue Apr 12 09:30:51 2005
|
> I have been running ELOG on FreeBSD no problem for a year now,
> but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine
> with a few warnings (see attached logs).
|
|
Re: XML password files, replication & FreeBSD, posted by G on Wed Apr 13 00:40:55 2005
|
> > I have been running ELOG on FreeBSD no problem for a year now,
> > but this new version 2.5.8-x doesn't seem to wanna work, it compiles fine
> > with a few warnings (see attached logs).
|
|
Re: XML password files, replication & FreeBSD, posted by Stefan Ritt on Wed Apr 13 09:06:46 2005
|
> Ok, i see, the problem for me now is that this attribute name has been in use for
> half a year or so by me. So now I have 100's of logbook entries with the old name
> in them, if I change it's name then all old logbook entries will show up with that
|
|
Default Date Format, posted by David Egolf on Mon Apr 11 23:01:37 2005
|
Hello,
I downloaded the latest file and installed but the version number stayed at
|
|
Re: Default Date Format, posted by Stefan Ritt on Tue Apr 12 09:13:27 2005
|
> I downloaded the latest file and installed but the version number stayed at
> 2.5.8-2 and did not change to -3.
|