Looking for a test mail generator (unthreaded)

[Stephen Swaney]

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-
> bounces at lists.mailscanner.info] On Behalf Of Jay R. Ashworth
> Sent: Tuesday, September 09, 2008 10:11 AM
> To: mailscanner at lists.mailscanner.info
> Subject: Re: Looking for a test mail generator (unthreaded)
> 
> On Mon, Sep 08, 2008 at 09:27:55PM +0200, Hugo van der Kooij wrote:
> > Jay R. Ashworth wrote:
> > > I am not having a good day today.  Twice.  In 5 minutes...
> > >
> > > Unthreadjacked:
> > >
> > >
> > > To test a new installation before a cutover, I'm trying to find
> (out
> > > whether anyone has written) a program that can send a bunch of
> email to a
> > > SMTP server, logging what it does (both logical and session level),
> so
> > > that I can check that the results are what they should be.
> >
> > A sender only has the view of what it communicates with the receiver.
> > Whatever happens after the receiver takes over is anyone's guess. But
> it
> >  not of any concern to the sender anymore.
> >
> > So I fail to see how you could do l this on a session level from the
> sender.
> 
> Would you be happier if I said "conversation level"?
> 
> > I would say that just doing a darn good job of configuring things
> right
> > and bring it to live is the best test.
> 
> It's not *your* email.
> 
> Executives are *insecure*.
> 
> > I have written some code to do a keepalive check to see if the whole
> > spam and AV chain works. The sending part is peanuts in perl. The
> > verificaton part was the tough part.
> >
> > The chain goes like:
> >
> > TEST server ==> Spam box ==> AV box ==> TEST server
> >
> > So I end up by getting what I did send out if nothing breaks down.
> But
> > it is a twist in that I need to configure an extra domain into my
> > customer configuration to do this.
> 
> Sure.  But that's exactly the reason I want to do it the way I want to
> do
> it: I don't want to have to do *two* analyses: what should have
> happened
> to each incoming mail and what *did* -- I want to *know* what should
> have
> happened, because I have a list with message IDs that tells me, so all
> I
> have to do is check the expected targets and look to see if the
> messages
> are there.
> 
> Cheers,
> -- jra

Jay,

Simply setup another mail hub with test accounts.  A simple sendmail server
delivering to local users would work just fine.

The use Roundhouse to duplicate the feed. The feed goes first to your real
mail hub for delivery as normal.

Send the duplicate feed to the test server which should be configured to 1)
send test messages to the test mail hub and 2) dev-null the rest.

Seems this would be simple to set up and meet your requirements.

Best regards,

Steve

Steve Swaney
steve at fsl.com
Office Phone: 202 595-7760 ext. 601