From: daniel.wagner@gmail.com (Daniel Wagner)
Subject: [sup-talk] CCing to self mail id when composing mail
Date: Thu, 04 Sep 2008 01:53:27 -0400 [thread overview]
Message-ID: <1220507464-sup-1482@buckwheat> (raw)
In-Reply-To: <48BE7CF7.1090103@gslab.com>
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
next prev parent reply other threads:[~2008-09-04 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 12:03 Manish Sapariya
2008-09-04 3:29 ` William Morgan
2008-09-04 5:53 ` Daniel Wagner [this message]
2008-09-08 18:47 ` William Morgan
2008-09-08 19:29 ` Nicolas Pouillard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1220507464-sup-1482@buckwheat \
--to=daniel.wagner@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox