Re: Want to change Entry time when using Copy To, posted by Michael Husbyn on Thu Mar 31 21:42:58 2005
|
> > 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?
|
Re: Want to change Entry time when using Copy To, posted by Michael Husbyn on Thu Mar 31 22:06:37 2005
|
> > 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.
|
|
Re: Want to change Entry time when using Copy To, posted by Michael Husbyn on Thu Mar 31 22:22:40 2005
|
> > 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.
> >
|
|
Re: Want to change Entry time when using Copy To, posted by Michael Husbyn on Thu Mar 31 22:49:08 2005
|
> > or your idea is good as well.
>
> Ok, I implemented a 'Duplicate' command (see this forum for example). I guess this is clearer
|
|
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 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 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 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?
>
|