No backups for that file that I can find. Although there probably are on one of the other systems. Have to check.
There is over 400 GB of space available on the disk. Now for the interesting part. At 1 am this morning, postsrsd was not working so i removed it from main.cf. At noon today, I reenabled it again on the test system and it just worked. I then enabled it on the production system and it worked. All I did was to enable syslog logging, add a couple local domains, and disabled chroot. None of those should have changed anything, but it did - or it just needed more time to think about what it should be doing ;-) -- Doug > On Dec 6, 2023, at 09:07, Bill Cole via Postfix-users > <postfix-users@postfix.org> wrote: > > On 2023-12-06 at 04:00:21 UTC-0500 (Wed, 6 Dec 2023 01:00:21 -0800) > Doug Hardie via Postfix-users <bc...@lafn.org> > is rumored to have said: > >> I just upgraded FreeBSD from 13.2 to 14.0. Postfix just picked up and ran >> fine. However postsrsd is causing me a few issues. I get the impression >> that postsrsd got updated, but I can't tell for sure. At the moment, the >> version is 2.0.8. The config files (conf and conf.sample) all had dates of >> 14 Nov so I suspect they were replaced. I don't know what the original files >> contained anymore. > > And you have no backups? > > This is actually my most common reason for needing backups: when I've whacked > a config file and need to get back to a last working config. It's not exactly > common, but it is more frequent than catastrophic disk death... > >> main.conf included: >> >> sender_canonical_maps = tcp:localhost:10001 >> sender_canonical_classes = envelope_sender >> recipient_canonical_maps = tcp:localhost:10002 >> recipient_canonical_classes= envelope_recipient,header_recipient >> >> I got errors that postfix couldn't connect to 10001. There was nothing >> listening to either port. >> >> I changed postsrsd.conf: >> >> chroot-dir = "" >> >> That got rid of the port errors. But now postfix gave an error about the >> tcp mapping. >> >> >> I changed main.conf to: >> >> sender_canonical_maps = socketmap:unix:srs:forward >> sender_canonical_classes = envelope_sender >> recipient_canonical_maps = socketmap:unix:srs:reverse >> recipient_canonical_classes = envelope_recipient, header_recipient >> >> and now postifx logs: Dec 6 00:02:44 test postfix/cleanup[2365]: warning: >> socketmap:unix:srs:forward lookup error for "wa6...@arrl.net". Postfix >> returns: 451 4.3.0 Error: queue file write error. > > I have no positive suggestions of a solution but that error does not seem > like something a socketmap error should be able to generate from the service > side, as opposed to Postfix itself. How is your disk space doing? > > > -- > Bill Cole > b...@scconsult.com or billc...@apache.org > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > Not Currently Available For Hire > _______________________________________________ > Postfix-users mailing list -- postfix-users@postfix.org > To unsubscribe send an email to postfix-users-le...@postfix.org _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
