sup talk - Sep 2008 - CCing to self mail id when composing mail

Hi All,

Two queries:

First:
=====I have configured the ask for CC and I want to CC to
myself. I am using sendmail for sending mail. However
I am not receiving mail copy to myself. I tried bcc, and
specifying my mail id in to field as well.

Is it sup or sendmail which is removing the self id?
any ideas?

Second:
======Can I configure sup to always include self mail id in CC
when composing new mail or replying to any other mail.


Thanks for any help.
Regards,
Manish

Reformatted excerpts from Manish Sapariya''s message of
2008-09-03:
> I have configured the ask for CC and I want to CC to myself. I am
> using sendmail for sending mail. However I am not receiving mail copy
> to myself. I tried bcc, and specifying my mail id in to field as well.
> 
> Is it sup or sendmail which is removing the self id?  any ideas?
It''s probably your sendmail setup. Sup is just passing that stuff
through unchanged. You can try enabling logging on sendmail''s end
somehow...
> Can I configure sup to always include self mail id in CC when
> composing new mail or replying to any other mail.
I believe the before-edit hook can be used for this. Place something
like the following in ~/.sup/hooks/before-edit.rb:

  header["Cc"] = my at email.address

(untested!)
-- 
William <wmorgan-sup at masanjin.net>

Excerpts from Manish Sapariya''s message of Wed Sep 03 08:03:03 -0400
2008:
> Is it sup or sendmail which is removing the self id?
> any ideas?
I don''t know if this is related, but I have noticed that sup is a
little
bit too smart for itself.  I sometimes also CC myself.  Though these
messages appear in my procmail.log, sup seems to recognize that they are
a duplicate of a message already in the index, and silently hides them.

So: check your procmail (or whatever) log to really see whether you are
getting a copy.
~d

Reformatted excerpts from Daniel Wagner''s message of
2008-09-03:
> I don''t know if this is related, but I have noticed that sup is a
> little bit too smart for itself.  I sometimes also CC myself.  Though
> these messages appear in my procmail.log, sup seems to recognize that
> they are a duplicate of a message already in the index, and silently
> hides them.
Oh yeah. Sup collapses dupes. That would do it.

That''s another interesting lesson I''ve learned about email in
the
process of writing Sup. Two messages with the same message id are more
likely than not to NOT be exactly the same message. For example, any
time you get a message both cc''ed and through a mailing list,
they''ll
have the same message id, but the mailing list one will probably have
extra content (ML signatures and taglines) and different headers.
-- 
William <wmorgan-sup at masanjin.net>

Excerpts from William Morgan''s message of Mon Sep 08 20:47:43 +0200
2008:
> Reformatted excerpts from Daniel Wagner''s message of 2008-09-03:
> > I don''t know if this is related, but I have noticed that sup
is a
> > little bit too smart for itself.  I sometimes also CC myself.  Though
> > these messages appear in my procmail.log, sup seems to recognize that
> > they are a duplicate of a message already in the index, and silently
> > hides them.
> 
> Oh yeah. Sup collapses dupes. That would do it.
> 
> That''s another interesting lesson I''ve learned about
email in the
> process of writing Sup. Two messages with the same message id are more
> likely than not to NOT be exactly the same message. For example, any
> time you get a message both cc''ed and through a mailing list,
they''ll
> have the same message id, but the mailing list one will probably have
> extra content (ML signatures and taglines) and different headers.
Do you get a conclusion, concerning email-tools design?

-- 
Nicolas Pouillard aka Ertai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL:
<http://rubyforge.org/pipermail/sup-talk/attachments/20080908/266c08d5/attachment.bin>