On Mar 3, 2009, at 10:38 AM, Jake Vickers wrote:
This is a known problem with BIS server and there is not a work- around that I am aware of.
the problem is that BIS uses SRS address rewriting (http://www.openspf.org/SRS ), and our elderly version of ezmlm doesn't know how to deal with SRS.
i requested an update of ezmlm a little while back (http://www.mail-archive.com/[email protected]/msg20471.html ); unfortunately i haven't yet had the time to build a test toaster to try and package up a more recent ezmlm, i apologize. i'll see if i can make this happen sometime soon.
Bruce Guenter pushed changes to the ezmlm-idx trunk last spring that enabled SRS support:
commit 286b9518da1d4d3b8944aafbf32410bbdfd88b0e Author: Bruce Guenter <[email protected]> Date: Thu May 29 22:23:31 2008 -0600 Added support for decoding sender addresses mangled by SRS. CHANGES.idx | 2 + ... 20 files changed, 107 insertions(+), 15 deletions(-) create mode 100644 sender.c create mode 100644 sender.h create mode 100644 tests/400-decode-senderthis patch made it into ezmlm-idx-7.0.0, and hey, there's an RPM available!
http://ezmlm.org/archive/7.0.0/i can't imagine it would be a drop-in replacement, given that quite a lot has changed between our version of ezmlm and that one (the biggest being that ezmlm can now store its list configs in a DB rather than in list directories), but there is a pretty clearly documented upgrade path.
i will dig into this problem some more once i have the time; however, if anyone else cares about having access to a more modern ezmlm, please speak up! i could use the moral support :)
-steve --If this were played upon a stage now, I could condemn it as an improbable fiction. - Fabian, Twelfth Night, III,v
smime.p7s
Description: S/MIME cryptographic signature
