Okay, I'm in general agreement with folks who are begging for work to
continue on a solution to the forwarding problem. So I've looked at SRS
and SES in the past, but admittedly haven't looked at either of them
either closely enough or recently enough. And even then, I only briefly
tried an SRS socket map that didn't work out (nothing major...my bad for
not looking into it further and reporting it) I think because I'm
hosting more than one virtual domain.
My basic question is, though I understand the principle difference
between SRS and SES (SRS rewrites MAIL FROM for forwarded mail where SES
rewrites MAIL FROM for all outgoing mail), does SES solve, or attempt to
solve the same forwarding problem that SRS does? Because if it does,
I'm wondering why time is being spent on SRS when SES provides the
additional protection of preventing false bounces even when implemented
unilaterally.
I ask because I'm on too many mailing lists as it is. If there are
mailing lists for both, I'm probably only going to pick one. I'm just
at a loss as to which one I should join. I'll look up where to sign up
for them myself. I'm just looking for a little guidance as to what to
spend my time with. I'll stay open to changing my mind about it later
if need be, but given the noise level on this list for the past many
weeks, I will *only* consider technical info, not personality info.
--
-Paul Iadonisi
Senior System Administrator
Red Hat Certified Engineer / Local Linux Lobbyist
Ever see a penguin fly? -- Try Linux.
GPL all the way: Sell services, don't lease secrets