Let me see if I can explain your entire email.
Ensuring that email flows freely between our mail complex and other top mail
provider complexes is a support issue correct. Actually setting up the
system to monitor and to ensure the support people get the data they need is
operations/engineering.
We like automating a lot of our procedures as our mail complex isn't staffed
24/7. Right now we have a script that monitors incoming mail sent from
probes across the us. It monitors how long it takes the email to first hit
the IronPort's, then how long it takes to hit the Brightmail, then how long
it takes to hit the MTA's. Our script uses pop3 to grab the email and parse
the headers we send from the probes (or in this case from the complex to the
pop accounts). Yes I do realize some are webmail (AOL, MSN, Gmail), but even
a lot of the webmail providers do have pop3 servers.
Our intent here is not not only verify that the email got there but that it
got there in a reasonable time (lets face it email is becoming a more
imporant part of life/business today).
As fair as teaching the support guys to go look at the mail queue, would you
honestly want them to be doing that? We have over 65 mail machines and
should I trust them with checking them every 10 min? Since we are not
staffed 24/7 what happeneds if we have all gone home? The way we have it
setup if the mail never reaches the complex tier-1 gets a page, 15 minutes
later if the problem still isn't solved tier-2 gets a page. I believe
automating the system rather then trutsing a staff member to check it and to
pray that it dosen't break during the night is a much better way of doing
it.
<quote who="Hosman, Ross">
We like automating a lot of our procedures as our mail complex isn't
staffed
24/7.
That's not surprising.
Right now we have a script that monitors incoming mail sent from
probes across the us. It monitors how long it takes the email to first hit
the IronPort's, then how long it takes to hit the Brightmail, then how
long
it takes to hit the MTA's.
Reverse the wires, the rest of the internet would appreciate it.
You missed the point of my previous email. Thousands of hours are wasted
by engineers dealing with abuse that is not insignificantly caused by
Charter.
And now "Charter" (not you, but Charter) is asking for some free accounts
so they can enhance their "mail complex."
You *are* Charter and netops *is* a two-way street, please act
accordingly. Don't just say it isn't your department because guess what,
it's all of our departments.
-david
If getting mail from your mail complex is important to remote mail complex A then talk to remote mail complex A and arrange something. If remote mail complex A doesn't care, or doesn't return your mail, then maybe mail complex A doesn't think your mail complex is worth worrying about (or perhaps you are sufficiently notable that it's worth blocking mail from you without generating bounce complexes).
Unless your mail complex is sufficiently big that remote mail complex A's customers are going to care (i.e. generate support complex load above the noise floor) I wouldn't hold my breath complex waiting for anybody to expend effort to help you with any of this for free.
There isn't really any solution complex you're going to magically find from the NANOG list complex beyond the suggestion complex that has already been put forward (that of purchasing standard retail pop3 mailbox complexes from the other provider complexes you're interested in, and running text complexes between them and your mail complex.)
Joe
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1