> > What I want is to have the Entry time to be updated to the time it was
> > copyed, not the original entry time. Moved To should perhaps retain its
> > original time?
> 
> You can achieve that by using "Edit", and then check "Resubmit as new entry",
> then click "Submit".

The idea is good, but it does not work for me. What happens when I do this is
that I get a new ID, but the old ID is deleted.... It disappears from the list,
and if you try to access it manually it says that it is deleted.

Bug then? My config?

Best regards
Michael

> > The idea is good, but it does not work for me. What happens when I do this is
> > that I get a new ID, but the old ID is deleted.... It disappears from the list,
> > and if you try to access it manually it says that it is deleted.
> 
> Right, that how it's supposed to be. Same would happen if you move the entry. It's
> deleted from the old place and resubmitted as a new entry. Otherwise you would have
> your entry twice, and that is certainly not what you want. How come you access it
> manually? If you access it through the list, everything should be fine. I even
> update the references if there are replies to this entry, so the replies still
> point to the right entry.

But I want a duplicate entry of the entry.... so that I can reuse the text and other
items and just change the entrys that need to be changed.

E.g, you have a work request from one user with some kind of solution on it, then you
get a similar request from another user and you want to have almost the same
information in a new entry. Then you just want to create a copy of the old case and
change whatever needs to be changed.

I'm not sure if you understand what I tries to do?


Best regards
Michael

> > But I want a duplicate entry of the entry.... so that I can reuse the text and other
> > items and just change the entrys that need to be changed.
> > 
> > E.g, you have a work request from one user with some kind of solution on it, then you
> > get a similar request from another user and you want to have almost the same
> > information in a new entry. Then you just want to create a copy of the old case and
> > change whatever needs to be changed.
> > 
> > I'm not sure if you understand what I tries to do?
> 
> Now I understand. What you ask for is not possible right now, but I put it on the
> wishlist. The best would be to add a new command "Duplicate" to the menu, which lets you
> do exactly what you want.

Thank you!

Or what I understand with "Resubmit as new entry", keep the old and create a new entry.
Perhaps you can trigger behavior of resubmit with a switch?
Duplicate Resubmit = 1
(default to 0 - old behavior)

or your idea is good as well.

Or just update the Entrytime if you are using Copy To:
EntryUpdate Copy To = 1

with also solves my case.

(and switch for Move To as well?)


Have a nice evening,

Best regards
Michael

> > or your idea is good as well.
> 
> Ok, I implemented a 'Duplicate' command (see this forum for example). I guess this is clearer
> than modifying some of the existing functionality like 'resubmit' or 'copy to'. With 'copy to'
> you probably want to keep all information from the original entry, including the submission
> time, when you move it from one logbook into an other. So if we put an 'EntryUpdate Copy To',
> this would not be possible any more. The new version is under CVS.


Wow! You are really fast!

I'm going to try it now!

This works for me :)


Thanks for quick response Stefan!


Best regards
Michael

> What you can try is to debug the communication between elogd and the SMTP
> server. Just turn on logging via
> 
> Logfile = log.txt
> Logging level = 3
> 
> After sending email, you see the conversation in log.txt. Maybe this gives you
> some hints.


I run with loggin level = 6:
14-Apr-2005 14:50:16 [pc-0460] {ikt} Email from elog@..... to
Michael.Husbyn@.....,, SMTP host smtp......:
14-Apr-2005 14:50:16 [pc-0460] {ikt} 220 backup...... ESMTP Sendmail
8.12.11/8.12.11; Thu, 14 Apr 2005 14:59:18 +0200
14-Apr-2005 14:50:16 [pc-0460] {ikt}
14-Apr-2005 14:50:16 [pc-0460] {ikt} HELO njord......
14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 backup...... Hello njord......
[10.138.224.221], pleased to meet you
14-Apr-2005 14:50:16 [pc-0460] {ikt} MAIL FROM: elog@.....
14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 2.1.0 elog@........ Sender ok
14-Apr-2005 14:50:16 [pc-0460] {ikt} RCPT TO: <Michael.Husbyn@.....>
14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 2.1.5 <Michael.Husbyn@.....>... Recipient ok
14-Apr-2005 14:50:16 [pc-0460] {ikt} DATA
14-Apr-2005 14:50:16 [pc-0460] {ikt} 354 Enter mail, end with "." on a line by itself
14-Apr-2005 14:50:16 [pc-0460] {ikt} To: Michael.Husbyn@.....,
14-Apr-2005 14:50:16 [pc-0460] {ikt} From: elog@.....
Subject: IKT sak (110): Testing רזו
14-Apr-2005 14:50:16 [pc-0460] {ikt} X-Mailer: Elog, Version 2.5.8-3
14-Apr-2005 14:50:16 [pc-0460] {ikt} X-Elog-URL: http://njord......:8090/ikt/110
14-Apr-2005 14:50:16 [pc-0460] {ikt} X-Elog-submit-type: web|elog
14-Apr-2005 14:50:16 [pc-0460] {ikt} Date: Thu, 14 Apr 2005 14:50:16 +0200
14-Apr-2005 14:50:16 [pc-0460] {ikt} Content-Type: TEXT/PLAIN; charset=US-ASCII

14-Apr-2005 14:50:16 [pc-0460] {ikt} .
14-Apr-2005 14:50:16 [pc-0460] {ikt} 250 2.0.0 j3ECxI8e003851 Message accepted for
delivery
14-Apr-2005 14:50:16 [pc-0460] {ikt} QUIT
14-Apr-2005 14:50:16 [pc-0460] {ikt} 221 2.0.0 backup...... closing connection
14-Apr-2005 14:50:16 [pc-0460] {ikt} READ entry #110

--

Sorry for the late reply btw, I've removed some information in the log (server names)

What I can see is that it sends with charset=US-ASCII, even if the characters are
non-US.

Only outlooks have problem with understanding if the subject is not mime encoded.

Ideas?

Best regards
Michael Husbyn

> > What I can see is that it sends with charset=US-ASCII, even if the characters are
> > non-US.
> 
> That's the key point. I changed it such that elog uses now the charset defined in the
> configuration file, now it should work fine. Can you give it a try? The new version is
> under CVS.

Tried it now, using the same charset I get when sending email from Mutt: (this is right)
Subject: Testing =?iso-8859-1?B?+Obl?=
To: michael.husbyn@.........
Message-id: <20050415125415.GA30539@njord........>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
Content-disposition: inline
User-Agent: Mutt/1.4.1i

When sending from Elog with the same subject (from the same server):
Subject: IKT sak =?UNKNOWN?B?KDExMCk6?= Testing =?UNKNOWN?B?+Obl?=
To: Michael.Husbyn@............
Message-id: <200504151304.j3FD4aKP006491@njord..................>
MIME-version: 1.0
X-Mailer: Elog, Version 2.5.8-3
Content-type: TEXT/PLAIN; charset=iso-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
X-Elog-URL: http://njord................:8090/ikt/110
X-Elog-submit-type: web|elog


--

So the subject needs some change. In my example I left out what Elog inserts before
the subject I put in Elog.

Just for the fun, changed my old subject (in elog) to the one Mutt formatted it to:
Testing =?iso-8859-1?B?+Obl?=

And then I get what I want... ;)


Best regards
Michael Husbyn

> I implemented this, but found some problems. If I encode the subject like
> 
> Subject: =?ISO-8859-1?Q?ורז?=
> 
> it displays well unde MS Outlook, but not under Mozilla Thunderbird or pine,
> which both display the full text (including the ISO...). So it looks like
> there is no single solution which satisfies all mail programs. It should at
> least work for Outlook and Thunderbird, so if anyone has an idea please let me
> know.

If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
Maybe that could be a solution?

Best regards
Michael

> > If I read the RFC correctly when you use B encoding you are using BASE64 encoding.
> > Maybe that could be a solution?
> 
> Indeed it is. Works for all email programs I know. So I added that to elog, new
> version is committed to CVS. Let me know if it works for you.


Stefan! You are *THE MAN* :)

It works :)

You are indeed "speedy gonzales" ;)

Thank you very much!


Best regards
Michael 'very impressed' Husbyn