mailing list archives

I?ve noticed that in some systems when you send a message via SMTP, it will put a copy in the user?s Sent mailbox.  Most of them don?t however, necessitating that I do an IMAP APPEND to get the message in Sent.  Is there a good/any way to tell when the APPEND is necessary?  Right now I?m doing it all the time which is resulting in double copies in the Sent mailbox for systems that do it automatically.

Ian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4383 bytes
Desc: not available
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20130113/9a77be69/attachment.p7s>

I suppose this might be more likely as an SMTP response code (though I can?t find a defined one) than an IMAP capability or some such, but maybe someone on this list knows anyway?  <wishful_thinking>

Ian

On Jan 13, 2013, at 4:31 PM, Ian Anderson <iana@apple.com> wrote:

> I?ve noticed that in some systems when you send a message via SMTP, it will put a copy in the user?s Sent mailbox.  Most of them don?t however, necessitating that I do an IMAP APPEND to get the message in Sent.  Is there a good/any way to tell when the APPEND is necessary?  Right now I?m doing it all the time which is resulting in double copies in the Sent mailbox for systems that do it automatically.
> 
> Ian_______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4383 bytes
Desc: not available
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20130113/812a45c3/attachment.p7s>

On 13 Jan 2013 19:32, "Ian Anderson" <iana@apple.com> wrote:
>
> I?ve noticed that in some systems when you send a message via SMTP, it
will put a copy in the user?s Sent mailbox.  Most of them don?t however,
necessitating that I do an IMAP APPEND to get the message in Sent.  Is
there a good/any way to tell when the APPEND is necessary?  Right now I?m
doing it all the time which is resulting in double copies in the Sent
mailbox for systems that do it automatically.
>

No, there isn't, as far as I know. You can, on some systems, tell which is
the Sent mailbox, and you could watch it for a new message, I suppose. I
bet systems supporting special use mailboxes don't do the automatic append,
though.

On other systems, the "correct" method for sending a message is to first
append it, and then submit by BURL.

Finally, Alexey had a postaddress extension which allowed you to do the
append by using a special address during submission.

Dave.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20130114/4539f306/attachment.html>

There isn't a good way, but there's always head-on brute force.

When you store a message in Sent, store the message-id into a little 
database on the side. You don't have to take very good care if it, any 
sort of crap db will do, even an ascii file in a cache directory. When 
you look at Sent for other reasons, see if the message-ids in that db 
are all duplicated in Sent, and if most of them are, stop writing to 
Sent from then on. See? The solution isn't difficult at all, merely a 
little nauseating ;)

Have a nice day.

Arnt

How often do you re-test to make sure the server is still working the same way?  If the Id response changes?

Bron (more likely to be a user or admin changing server config... it does happen)

On Tue, Jan 15, 2013, at 12:58 AM, Arnt Gulbrandsen wrote:
> There isn't a good way, but there's always head-on brute force.
> 
> When you store a message in Sent, store the message-id into a little 
> database on the side. You don't have to take very good care if it, any 
> sort of crap db will do, even an ascii file in a cache directory. When 
> you look at Sent for other reasons, see if the message-ids in that db 
> are all duplicated in Sent, and if most of them are, stop writing to 
> Sent from then on. See? The solution isn't difficult at all, merely a 
> little nauseating ;)
> 
> Have a nice day.
> 
> Arnt
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol
-- 
  Bron Gondwana
  brong@fastmail.fm