> Without any generally available information about the existing email > infrastructure, it's hard to make targeted comments about how to fix > what is obviously broken with this system which literally nobody with > the ability to fix cares about. That means a either a conversation > (which should be a shared experience (therefore internals@) or an > essentially open request for "I'd like to help, but I'll need the > ability to poke around to figure out wtf is going on".
Our smtp servers are actually quite well maintained by Sascha and company. Which is a somewhat new thing, so if you are saying this has been going on for years, the mail servers changed completely in there somewhere. And they are quick to respond to specific problems if you send a useful description of the issue to systems@ For example, last week a specific @php.net address apparently pissed off the Internet and our smtp servers were being hammered with thousands of messages per minute for this one person. Sascha was on the ball and had the attack filtered quickly. Nobody here even noticed, I am sure. We could definitely need a volunteer who knows ezmlm-idx and perhaps modernize the config there, but on the smtp servers front things are under control. I am sure Sascha and his team would love to see concrete examples (as in with full headers) of any messages rejected at the smtp level. -Rasmus
