I dont know what is wrong with your setup but it works here.

till wrote:

On 6/3/07, till klimpong@gmail.com wrote:

...

1. When I select a message in message view, and click reply/reply all,

the subject and recipients are lost when the compose screen loaded. Message is there, also quoted etc..

Anyone else noticed this? I debugged compose.inc and as far as I can tell it returns the correct info into $MESSAGE from the imap calls - but the information is not used in/applied to the template. Anyone fluent with $OUTPUT->parse ? ;)

Thanks, Till

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete this material from any computer.

In accordance with industry regulations, all messages are retained and are subject to monitoring.

This message has been scanned for viruses and dangerous content and is believed to be clean.

Securities offered through Cantella & Co., Inc., Member NASD/SIPC. Home Office: 2 Oliver Street, 11th Floor, Boston, MA 02109 Telephone: (617)521-8630

On 6/3/07, till klimpong@gmail.com wrote:

On 6/3/07, Chris Richardson techlist@cantella.com wrote:

...

I dont know what is wrong with your setup but it works here.

Are you using RC1?

Cause I downloaded it again today and with the standard skin - no edits, it doesn't work. As soon as I click "reply" or "reply-all" it loads the compose screen, but the to, subject and the date/from on the message body are missing.

The subject for example says: "Re:" - to is completely empty. The top of the message body say: "On , wrote:".

(Sorry for all the noise on the list today.)

But here is the fix/outcome: The functions which render the form expect $MESSAGE['subject'] for example, but looking at $MESSAGE, the structure inside the array/object is nested and looks like $MESSAGE['structure']->headers['subject']

I have no idea why that is the case here and apparently not for anyone else.

This shouldn't depend on the MTA though because Mail_Mime is supposed to provide a unified API.

Till

On 6/4/07, Thomas Bruederli roundcube@gmail.com wrote:

2007/6/3, till klimpong@gmail.com:

...

On 6/3/07, till klimpong@gmail.com wrote:

...

The subject for example says: "Re:" - to is completely empty. The top of the message body say: "On , wrote:".

(Sorry for all the noise on the list today.)

But here is the fix/outcome: The functions which render the form expect $MESSAGE['subject'] for example, but looking at $MESSAGE, the structure inside the array/object is nested and looks like $MESSAGE['structure']->headers['subject']

According to these lines from program/steps/mail/compose.inc

$MESSAGE['headers'] = &$IMAP->get_headers($msg_uid); $MESSAGE['structure'] = &$IMAP->get_structure($msg_uid); $MESSAGE['subject'] = $IMAP->decode_header($MESSAGE['headers']->subject); $MESSAGE['parts'] = $IMAP->get_mime_numbers($MESSAGE['structure']);

The subject is copied from the message headers. If the message is displayed correctly then this should also fetch the message headers since the same method is used.

...

I have no idea why that is the case here and apparently not for anyone else.

This shouldn't depend on the MTA though because Mail_Mime is supposed to provide a unified API.

This is not correct. RoundCube now uses the message structure provided by the IMAP server and does not rely on Mail_Mime anymore. Fetching the message structure instead of the whole message (with large attachments) is much more efficient.

Yeah, I am not sure if there is a glitch when all the assigning takes place. At least in my case the assigning doesn't work. I am not sure if it's due to the reference, globals and/or race conditions. No idea, but I'll look into this today.