From: David Woodhouse <dwmw2@infradead.org>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Administrivia.
Date: Tue, 12 Mar 2002 16:45:11 +0000 [thread overview]
Message-ID: <15927.1015951511@redhat.com> (raw)
In-Reply-To: <200203121640.g2CGeRg28441@vindaloo.ras.ucalgary.ca>
rgooch@ras.ucalgary.ca said:
> Hm. I note that formail tends to look at the From: address, which
> IMHO is the correct thing to do.
No. The From address is not the SMTP reverse-path. This message, for
example, has a From address dwmw2@infradead.org but the SMTP reverse-path,
to which errors should go, is dwmw2@redhat.com. (Unless it goes through
the list, in which case the reverse-path gets changed to linux-mtd-admin@,
so that errors in list delivery go to the list admin, not the original
sender.)
> > At least tell us what kind of crap you've seen... >
> http://lists.infradead.org/pipermail/linux-mtd/2002-March/004413.html
> Huh? This virus scanner is looking at the To: address?!?
Or something equally stupid. Hence abuse@ their ISP getting CC'd on the
complaint.
--
dwmw2
next prev parent reply other threads:[~2002-03-12 16:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 9:17 Administrivia David Woodhouse
2002-03-12 16:05 ` Administrivia Richard Gooch
2002-03-12 16:14 ` Administrivia David Woodhouse
2002-03-12 16:40 ` Administrivia Richard Gooch
2002-03-12 16:45 ` David Woodhouse [this message]
2002-03-12 16:51 ` Administrivia Richard Gooch
2002-03-12 16:59 ` Administrivia David Woodhouse
2002-03-12 17:05 ` Administrivia Richard Gooch
-- strict thread matches above, loose matches on Subject: below --
2002-07-18 14:04 Administrivia David Woodhouse
2004-08-16 15:06 Administrivia David Woodhouse
2004-08-16 15:12 ` Administrivia David Woodhouse
2004-08-19 14:17 Administrivia David Woodhouse
2020-08-21 21:29 Administrivia Paul Moore
2020-08-21 21:35 Administrivia Paul Moore
2020-08-21 21:56 ` Administrivia Casey Schaufler
2020-08-21 22:03 ` Administrivia Paul Moore
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=15927.1015951511@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rgooch@ras.ucalgary.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.