Sujet : Re: sender rewrining advice
De : gtaylor (at) *nospam* tnetconsulting.net (Grant Taylor)
Groupes : comp.mail.sendmailDate : 23. Mar 2024, 06:41:42
Autres entêtes
Organisation : TNet Consulting
Message-ID : <utlmi6$iv4$1@tncsrv09.home.tnetconsulting.net>
References : 1 2 3 4 5 6 7 8
User-Agent : Mozilla Thunderbird
On 3/22/24 23:10, Grant Taylor wrote:
From memory -- I'll look some time this weekend -- the SRS routine that I'm using uses the local-host-names file (class w) as part of the test to determine if envelope senders should be rewritten or not.
What I have is based off of the following, which is now available via Archive.org
Link - SRS integration with sendmail
- https://web.archive.org/web/20051221183047/
http://srs-socketmap.info/sendmailsrs.htmThe collection of files is basically two versions of very similar solutions. I've used both.
N.B. I originally drafted this reply with the files attached, but I've since removed them and will send them in a follow up. They /should/ be forthcoming shortly.
I have sym-links in /usr/share/sendmail/cf/hack directory pointing to the m4 files in the /etc/mail/srs directory.
Towards the end of my sendmail.mc file I have the following line:
I'm currently using the perlsrs-old.m4.
HACK(`perlsrs-old')dnl
Both perlsrs.m4 and socketmap.m4 rely on the socketmapd.0.31.pl file running as a daemon listening on a local Unix socket. -- I used this for a while, but abandoned it because I got tired of needing to manually start it after updates. I should have written an init script, but c'est la vie.
So I switched to perlsrs-old.m4 which forks a copy of envfrom2srs.pl or srs2envto.pl as necessary.
I've never had any problems with the overhead of forking the Perl processes. SpamAssassin, ClamAV, and the IMAP daemon take up FAR more resources than the SRS solution.
It looks like line 37 of the perlsrs-old.m4 is what references the class w map (where local-host-names gets loaded into). So I would think that you could create a new class and load contents of a different file into the class and for reference.
I don't remember the specifics about the socketmapd solutions (perlsrs.m4 and socketmap.m4) but I know that they did work and that I didn't notice any less overhead with the long running daemon vs forking.
According to mailstats, my server has been averaging 15.5 k messages a day for the last month (10k min and 19k max). I'm on a small Linode w/ 2 GB of memory. -- This really doesn't make an impact and it's not like it's a big system.
-- Grant. . . .