As far as SPF goes, the patches they provide do not mix with qmail-ldap. Your only option seems to be to just do dns changes.
> -----Original Message----- > From: Felipe Augusto van de Wiel [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 09, 2006 11:28 AM > To: [email protected] > Subject: Implementing SRS (possible approaches!?) > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > Recently, I start receiving bounce messages from some mails > that we forward for another domain complaining about SPF. I was > pointed to openspf.org [1]why page that shows me that: > > > If your mail was correctly sent, but was rejected because > it passed through a forwarding service, you can either > mail the final destination address directly (it should be > shown in the bounce message) or you ask the forwarder to > implement SRS. If neither of these suggestions is > practical, change your "-all" to "?all" until a more > comprehensive approach to sender authentication involving > cryptography solves the forwarding problem for good. For > more information on this problem, see pages 15-16 of the > SPF Whitepaper. > > > I tried to search around to find some information about SRS > with qmail-ldap, but I only found [2]this article and, first > looking, I do not like the approach. > > I would like to check a couple of things: > > a) Is there another approach to solve the problem? > > If using SPF solve the problem, I prefer to use it, > instead of rewrite all my messages. Maybe add a > rewrite rule or something like that in the mails I > am forwarding? > > > b) If there is no other way to go and implement SRS is the > only way, somebody already did that? Could point me to > docs, scripts and/or references? > > > Thanks in advance, kind regards! > > References: > 1.http://www.openspf.org/why.html > 2.http://wooledge.org/~greg/qmail-srs.html > - -- > Felipe Augusto van de Wiel <[EMAIL PROTECTED]> > Coordenadoria de Tecnologia da Informação (CTI) - SEDU/PARANACIDADE > http://www.paranacidade.org.br/ Phone: (+55 41 3350 3300) > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (GNU/Linux) > Comment: Using GnuPG with Debian - http://enigmail.mozdev.org > > iD8DBQFEYLUXCj65ZxU4gPQRAjnXAJwKHYfsSsyZeOUz3uZNqn7IWBincQCeMaUF > 77sSRIXc5wfEd6nDYLjnwbM= > =8WSN > -----END PGP SIGNATURE-----
