1. Rob Mitchell sends a message
to vprusers@byte.c
om, a mailing list on our SMTP server.
2. The message fans out
to 300 recipients, including user@X.com, who receives mail at Company Y, the Internet service provider for Company X.
3. Periodically, X connects to Y and runs
the utility Pullmail (pullmail@swsoft.co.uk,
http://www.net-shopper.co.uk
) to fetch X's mail from Y's server (using POP3) and redistribute it to the users at X.
4. The header address
(To: vprusers@byte.com), now incorrectly transformed into an envelope address, forms a mail loop.
Company X's incorrect use of a mail router created the potential for an explosion. However, my own failure to protect a list account put the torch to it. I'm thankful I was able to stop it on the third iteration.
Rob Mitchell and Dave Egan were even more thankful.
Flexible C++
Matthew Wilson
My approach to software engineering is far more pragmatic than it
is
theoretical--and no language better exemplifies this than C++.
BYTE Digest editors every month analyze and evaluate the best articles from Information Week, EE Times, Dr. Dobb's Journal, Network Computing, Sys Admin,
and dozens of other CMP publications—bringing
you critical news and information about wireless communication,
computer security, software development, embedded systems,
and more!
