RE: Weird problem with srs-socketmapd.0.32rc3.pl

Mark <[email protected]> Fri, 23 Dec 2005 11:55:23 GMT
Newsgroups gmane.mail.spam.srs.general
Organization Asarian-host
Message-ID <[email protected]>
> -----Original Message-----
> From: Robert Muchnick [mailto:[email protected]]
> Sent: donderdag 22 december 2005 22:30
> To: [email protected]
> Subject: [srs-discuss] Weird problem with srs-socketmapd.0.32rc3.pl
>
> I set up the 0.32rc3 installation on multiple servers and tested them to
> be sure SRS was working and mails were getting through, especially for-
> warding through one mail server in particular (call it "tampa") which
> handles a particularly important forwarded email address. Most of the
> testing was done from my servers, which all publish and run SPF1. Every-
> thing was okay as of yesterday. SRS was working when "tampa" received
> mail from servers with SPF (mine) and those without SPF (yahoo.com).
>
> Now I'm getting the old SPF broken forward problem on mail sent to the
> forwarding address on "tampa": '[sending domain] does not designate ["-
> tampa" IP address] as permitted sender'.
>
> Daemon srs-socketmapd is running and there have been exactly NO configu-
> ration changes to sendmail since I started it after the SRS installa-
> tion, when it *was* working.
>
> Anybody have a pointer where I should look as to why this spontaneous
> meltdown of rewriting? Thanks.

Hello Robert,

What exactly is not working? There are many new ways to invoke the
rewriting (all variations on options regarding class=w). To start with the
most obvious question: you did regenerate your sendmail.cf, right? (with
an option from the new m4).

It would help if you showed me a header, or part of the sendmail log, to
see with what sort of rewriting is occuring, and for what domains. It may
be that no rewriting takes place, or rewriting for a domain in class w for
which no SPF record exists.

Feel free to contact me off-list about it, if you so desire.

- Mark 
 
        System Administrator Asarian-host.org
 
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx