-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I'm wondering the status of integrating SRS with Postfix. I don't
care if it's a patch or policy daemon or whatever, as long as it
works. I know there is a patch "out there" for 2.1 but I've heard
that it isn't stable and broken (in addition to being old). If not,
I might write one, but it wouldn't be a [pretty] patch because I
haven't touched C/C++ in years. Anyway, I'm not even sure this is
the source/fix to my problem, though it seems to be to me. I'm
hoping someone can confirm this and offer advice or something.

I'm not an expert on SPF or SRS but I generally know how they work.
This is my problem, please bear with me. :) I'm hosting a web site
and email for "example.com". On their site they have a link that
sends email to <>. I have, in my virtual_alias_maps,
a map sending mail for <> to
<>,<>. "other.com"'s email is
(apparently) hosted by ISP.com (not the real server), say
"smtp.ISP.com".

When any random site visitor, say <>, sends mail to
<>, it expands the address as it should. It is
received properly by <>, but my SMTP server gets a
message from "smtp.ISP.com" saying it was rejected due to SPF. What
I'm thinking is that ISP.com is looking up the SPF records for
"wtfspf.com", seeing that my server isn't listed, and rejects based
on that. Is this correct?

If so, how can I fix this? The way I see it, I can:

1. Implement SRS.
2. Get wtfspf.com to add me to their SPF record (not likely).

The latter option would be true for anyone sending mail to
<>, though, so that's not really viable
whatsoever...are there other options? :/

Thanks,
Josh
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDOGPTV/+PyAj2L+IRAvj0AJ9Xsouu/LuemzFyoku+WVxfulCRKACdEfoE
fcn6pt8nIOKfqgQeyKC8CW0=
=PnXr
-----END PGP SIGNATURE-----