-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Allen Akin wrote:
| The first problem is "to" sources in the incoming filter. Since "to" | sources only match the envelope recipient, and SRS changes the envelope | recipient fairly drastically, a lot of my old patterns no longer work. | I'm watching the logs and changing them manually, but this seems risky | because the kind of rewriting that SRS does isn't completely | standardized. | | The second problem is with confirmations. When someone responds to a | confirmation request, SRS rewrites their envelope sender to a unique | value, with the result that TMDA sends them another confirmation | request! I've already had someone horribly confused by this. For now, | I'm just manually adjusting the pending queue when the first | confirmation arrives, but I can't always do that quickly enough to avoid | the confusion.
I sent Allen a test message, and this is what I witnessed.
1. My envelope sender was rewritten on the way to TMDA, so TMDA responded to some ickiness @bounce2.pobox.com
2. TMDA responds to the ickiness, and bounce2 rewrites it back to my real address so the challenge arrives just fine.
3. I replied to the confirmation address, and I got a "Confirmation accepted" back, so I assume that Allen received my test email (confirm, Allen?).
At this point, Allen has probably whitelisted the icky rewritten address, not my real address. When I send another email, TMDA blocks it and challenges me again because the new email comes from a new (differently icky) envelope sender.
For this to all work as it's supposed to, TMDA needs to detect the rewritten address and treat it differently somehow. Not being much of an SRS-head, I'm not show how that would work. I suppose someone could put a SRS-decoder wrapper around tmda-incoming so that it sees the "proper" $SENDER environment variable, and that would take care of it, but I'm just guessing.
As for why your 'to' input filters aren't working, I can't tell what's going on there. I don't see what SRS has to do with it.
Hope this helps (though I don't see how).
Kyle.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3-nr1 (Windows XP) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBI7f2zS7R/flctWYRAvbeAJ9pb8Dt/mtYNqQHOX843DDOGqQ9FwCggPdo x1tRnJuUmX66eGUxMSj55y8= =AhLE -----END PGP SIGNATURE----- _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
