-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 4 Mar 2010, Charles Marcus wrote:

Interesting, and yes, apparently this would suffice as a workaround for
individual users, but imo the less configuring that needs to be done *in
the client* the better - most importantly, there is less chance of
problems from a user configuration error. I'd prefer to just uncheck the
'Save a copy' option, and let the save to sent happen totally on the
server side.

Configure postfix to add the BCC to all messages in the MSA or all authentificated or however you can identify your users apart others.

2) you know that, if to send the message failed, the message is not
sent, in opposite to differ from "upload to Sent via IMAP failed" in the
second stage.

Sorry, I don't understand what you mean here (language problem most
likely)...

Traditionally the MUA first transmits the message first via SMTP to a MTA or MSA, then via IMAP into the Sent folder.

If the first step succeeds, but the second does not, my users are worried that the message has not been sent and try again. The error message, however, states correctly that the message was sent successfully, but could not been uploaded into the sent folder.

One disadvantage:

1) If the message is accepted, but for what reason ever is discarded by
the MTA, the data is lost.

Why would it be accepted then discarded? Anyway, in such a case the data
is lost regardless, right?

Because, traditionally, the message is transmitted via IMAP, too, it is in the Sent folder. Well, a MSA should not discard a message in the first place :-)

Regards,

- -- Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBS4/NGL+Vh58GPL/cAQI4WAf9Eha5u6sRNyyPdYl2IuJCwI0/vxDLpWvO
KB6EO1YJZe3+mbb38i13twXaBOV0NM5gdemRQ80ptdFpJ/uVc62Tm7FkdpHpzfNI
9W9vLPbuPXr4XNvs8Hy0/LecrQ4U2Qp9kmQTCSEieZXMJPEq5CAGkX2Q1H67rmxH
tEt7RuiMnaOF7DERW2wwyE7WPwO3yVFxChzkR6x56fBfkmoaRarxLSGXBh9SS1c3
GKf+9n3z0OUhhJ1pDPC4nPYU8SUBQx2fFBhLxUzntc+JtSzPPvGqs18HJ/UHhmdy
Wl0rBTvFSiRGJO4XqJYd8rw2C5O/CwiUTGjv6dFBW3OuFbZ5pyX8JA==
=Rbcg
-----END PGP SIGNATURE-----

Reply via email to