From: Vojtech Aschenbrenner <v@asch.cz>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Detection of messages with Fake Sender
Date: Fri, 03 Aug 2012 13:49:02 +0200 [thread overview]
Message-ID: <1343994446-sup-8999@x220> (raw)
In-Reply-To: <1343904276-sup-842@x220>
Excerpts from Vojtech Aschenbrenner's message of 2012-08-02 12:47:12 +0200:
> Hello folks.
>
> Is there any convenient way to detect, which messages has sender marked
> as "Sup Auto-generated Fake Sender" so I can delete them manually from
> filesystem? I think, that it could be some old encrypted messages for
> which I don't have a key anymore or some corrupted messages. When I
> display detailed header there is a exception:
Already solved. I didn't find a solution with sup-sync to report a bad
message so I wrote a script to detect corrupted raw message.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2012-08-03 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 10:47 Vojtech Aschenbrenner
2012-08-03 11:49 ` Vojtech Aschenbrenner [this message]
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=1343994446-sup-8999@x220 \
--to=v@asch.cz \
--cc=sup-talk@rubyforge.org \
/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