| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1097
|
Mon Apr 18 09:04:21 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.5.8-4 | Re: Mail not sent but message says it has been sent |
> 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.
>
> How do I or can I send authentication information to the email server?
This is not implemented right now, since the SMTP server at our institute does
not use authentication, so I could not test it. If you give me access to a
SMTP server with authentication, I could implement it. |
|
1096
|
Sun Apr 17 09:35:30 2005 |
 | Mikael Salonvaara | hmsalonv@syr.edu | Bug report | Windows | 2.5.8-4 | Mail not sent but message says it has been sent |
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.
How do I or can I send authentication information to the email server? |
|
1095
|
Fri Apr 15 22:26:06 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.5.8-2 | Re: logbook clone |
> When I create a new logbook (I used an existing one as a template) elog
> does not works anymore...
Fixed in CVS. |
|
1094
|
Fri Apr 15 22:24:49 2005 |
| Michael Husbyn | michaelh@online.no | Question | Linux | 2.5.8-3 | Re: MIME encoding of mail? |
> > 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 |
|
1093
|
Fri Apr 15 21:49:00 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.8-3 | Re: MIME encoding of mail? |
> 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. |
|
1092
|
Fri Apr 15 21:31:26 2005 |
| Michael Husbyn | michaelh@online.no | Question | Linux | 2.5.8-3 | Re: MIME encoding of mail? |
> 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 |
|
1091
|
Fri Apr 15 21:14:05 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.6-1 | Re: MIME encoding of mail? |
> Subject: Testing ורז
>
> Becomes
> Subject: IKT sak =?UNKNOWN?B?KDYwKTo=?= Testing =?UNKNOWN?B?5fjm?=
>
> config:
> Use Email Subject = IKT sak ($message id): $Tittel
You could put the encoding there manually:
Use Email Subject = =?ISO-8859-1?Q?IKT sak ($message id): $Tittel?=
would this work? |
|
1090
|
Fri Apr 15 21:10:27 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.8-3 | Re: MIME encoding of mail? |
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. |