From: Andreas Schwab <schwab@linux-m68k.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: "loopback" email setup for testing?
Date: Sat, 26 Jul 2014 14:23:12 +0200 [thread overview]
Message-ID: <874my4wbpr.fsf@igel.home> (raw)
In-Reply-To: <87k370s4iy.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 26 Jul 2014 20:12:05 +0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> I'm doing a bunch of email testing, and feel sort of stupid littering
> one email account with bogus "test #24" messages from another, over and
> over again. Not to mention it would be nice to be able to test gnus and
> related functions while offline.
You don't need to be online to be able to deliver mail locally.
> I've never used the unix mail spool -- is this something I could do
> locally, in a way that gnus wouldn't know the messages weren't going
> anywhere?
You could add a procmail rule that just discards the mails.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2014-07-26 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 12:12 Eric Abrahamsen
2014-07-26 12:23 ` Andreas Schwab [this message]
2014-07-26 12:42 ` Eric Abrahamsen
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=874my4wbpr.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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;
as well as URLs for NNTP newsgroup(s).