Postsrsd and spamassassin SPF check

[fisher006]

Hello, when I'm using postsrsd with spamassassin SPF checks all e-mail have SPF_FAIL=0.001

I'm trying with use_newest_received_spf_header 1 but this same issue

spamassassin have problem with reconize SPF for mail's with SRS headers

Jan 10 09:15:24 mail3 amavis[5068]: (05068-01-3) SA dbg: spf: checking EnvelopeFrom (helo=mx45-71.futurehost.pl, ip=91.244.71.45, envfrom=srs0=pqle=ef=networkmasters.pl=piotr.rosciszewski@mail3.pl)

[roehling]

The SPF_FAIL means that the domain you are using for your SRS has a SPF record that excludes your mail server. You should double-check your DNS configuration.

[fisher006]

When i disable postsrsd this same domain validates OK - i supose the problem is with this:

Jan 10 09:15:24 mail3 amavis[5068]: (05068-01-3) SA dbg: spf: checking EnvelopeFrom (helo=mx45-71.futurehost.pl, ip=91.244.71.45, envfrom=srs0=pqle=ef=networkmasters.pl=piotr.rosciszewski@mail3.pl)

when i disable postsrs headers looks like:

Jan 10 09:15:24 mail3 amavis[5068]: (05068-01-3) SA dbg: spf: checking EnvelopeFrom (helo=mx45-71.futurehost.pl, ip=91.244.71.45, envfrom=account@networkmasters.pl)

[fisher006]

Info from spamassassin mailing list:

You may need to setup second instance of Postfix with PostSRS to do the sender rewriting after SA.

The problem I had with PostSRS is that it rewrote the sender address even if it was not needed. So maybe setting up a second Postfix instance just for those addresses that are being forwarded would have solved my problem but I decided to not use PostSRS in the end. I just didn't have enough of a forwarding problem to justify the side effects for my particular mail flow.

it is possible to resolve this issue?

[roehling]

Closing this issue, since it seems to be stale. Feel free to reopen.