Re: Am I backscattering?
On Jan 31, 2015, at 9:29 PM, Bill Cole postfixlists-070...@billmail.scconsult.com wrote: Which doesn't mean you don't have some other Postfix binaries lurking... Good point. There are files in /usr/sbin/ and in /usr/local/sbin/ and it appears that the command directory is set to the latter, which appears to be 2.10.5 Seeing what breaks if I switch the command directory. I would *never* have found that. -- 'Begone From This Place Or I Will Smite Thee!' he [the god] commanded. 'Why?'
Re: Am I backscattering?
LuKreme: $ postfix reload postfix/postlog: fatal: bad string length 2 1: recipient_delimiter = +_ postsuper: fatal: bad string length 2 1: recipient_delimiter = +_ mail /etc/postfix] $ postconf recipient_delimiter mail_version recipient_delimiter = +_ mail_version = 2.11.3 No such problems here. % bin/postconf mail_version recipient_delimiter mail_version = 2.11.3 recipient_delimiter = +_ # bin/postsuper -v # bin/postlog foo postfix/postlog: foo I suppose you have a Frankenstein Postfix installation, with some parts coming from different bodies? I wouldn?t think so unless postmaster did something very odd. # postsuper -v Try using an absolute pathname. How many postsuper programs are on your system? # find / -name postsuper Wietse
Re: Am I backscattering?
Am 01.02.2015 um 10:01 schrieb LuKreme: On Jan 31, 2015, at 9:29 PM, Bill Cole postfixlists-070...@billmail.scconsult.com wrote: Which doesn't mean you don't have some other Postfix binaries lurking... Good point. There are files in /usr/sbin/ and in /usr/local/sbin/ and it appears that the command directory is set to the latter, which appears to be 2.10.5 Seeing what breaks if I switch the command directory. I would *never* have found that. if you build software from source build native packages for your OS, that cleans up things and avoids the system pulling the OS vendors version which conflicts with something below /usr/local on most distributions the package is pulled because requirement of /usr/sbin/sendmail of other packages as dependency i am using a self built postfix RPM based on the Fedora SPEC since doing more than relay from localhost with postfix and it's always the newest version and installed below /usr as like a distribution package
Re: Am I backscattering?
On 01 Feb 2015, at 03:13 , li...@rhsoft.net wrote: if you build software from source build native packages for your OS, that cleans up things and avoids the system pulling the OS vendors version which conflicts with something below /usr/local I normally do that, but in this case I was upgrading everything in preparation for moving to FreeBSD 9.3. I made sure to tell portmaster to install into /usr/sbin and /etc/postfix instead of /usr/local/… but I had forgotten that years ago I’d installed postfix in /usr/local/… in the first place. 2.11 has been painless so far, and the ability to specify two delimiters has been worth the effort. -- I do not feel obliged to believe that same God who endowed us with sense, reason, and intellect had intended for us to forego their use.
Re: Am I backscattering?
On Jan 31, 2015, at 4:55 PM, LuKreme krem...@kreme.com wrote: On Jan 31, 2015, at 4:23 PM, Wietse Venema wie...@porcupine.org wrote: LuKreme: Jan 26 14:49:53 mail postfix/pipe[44273]: E64DA50D3A1: to=oq6+2nbq@*munged*.com, orig_to=oq6_2nbq@*munged*.com, relay=dovecot, delay=0.13, delays=0.1/0.01/0/0.03, dsn=5.1.1, status=bounced (user unknown) That will produce backscatter. Why did you accept an unknown recipient? I don’t know, that’s what I was trying to find. Everything I have about queue ID E64DA50D3A1 in maillog was posted in the original message. Oh, wait, i think I just found it in an old pre map. Off to test. Yes, the old PCRE map was the problem. IN trying to fix it, I went to change the recipient_delimiter $ postfix reload postfix/postlog: fatal: bad string length 2 1: recipient_delimiter = +_ postsuper: fatal: bad string length 2 1: recipient_delimiter = +_ mail /etc/postfix] $ postconf recipient_delimiter mail_version recipient_delimiter = +_ mail_version = 2.11.3 -- Q: Does anyone know how many LOCs were in the Space Shuttle' codebase? A: 45. It was written in perl (paraphrased Slashdot discussion)
Re: Am I backscattering?
LuKreme: Jan 26 14:49:53 mail postfix/pipe[44273]: E64DA50D3A1: to=oq6+2nbq@*munged*.com, orig_to=oq6_2nbq@*munged*.com, relay=dovecot, delay=0.13, delays=0.1/0.01/0/0.03, dsn=5.1.1, status=bounced (user unknown) That will produce backscatter. Why did you accept an unknown recipient? Wietse
Re: Am I backscattering?
LuKreme: On Jan 31, 2015, at 4:55 PM, LuKreme krem...@kreme.com wrote: On Jan 31, 2015, at 4:23 PM, Wietse Venema wie...@porcupine.org wrote: LuKreme: Jan 26 14:49:53 mail postfix/pipe[44273]: E64DA50D3A1: to=oq6+2nbq@*munged*.com, orig_to=oq6_2nbq@*munged*.com, relay=dovecot, delay=0.13, delays=0.1/0.01/0/0.03, dsn=5.1.1, status=bounced (user unknown) That will produce backscatter. Why did you accept an unknown recipient? I don?t know, that?s what I was trying to find. Everything I have about queue ID E64DA50D3A1 in maillog was posted in the original message. Oh, wait, i think I just found it in an old pre map. Off to test. Yes, the old PCRE map was the problem. IN trying to fix it, I went to change the recipient_delimiter $ postfix reload postfix/postlog: fatal: bad string length 2 1: recipient_delimiter = +_ postsuper: fatal: bad string length 2 1: recipient_delimiter = +_ mail /etc/postfix] $ postconf recipient_delimiter mail_version recipient_delimiter = +_ mail_version = 2.11.3 No such problems here. % bin/postconf mail_version recipient_delimiter mail_version = 2.11.3 recipient_delimiter = +_ # bin/postsuper -v # bin/postlog foo postfix/postlog: foo I suppose you have a Frankenstein Postfix installation, with some parts coming from different bodies? Wietse
Re: Am I backscattering?
On Jan 31, 2015, at 4:23 PM, Wietse Venema wie...@porcupine.org wrote: LuKreme: Jan 26 14:49:53 mail postfix/pipe[44273]: E64DA50D3A1: to=oq6+2nbq@*munged*.com, orig_to=oq6_2nbq@*munged*.com, relay=dovecot, delay=0.13, delays=0.1/0.01/0/0.03, dsn=5.1.1, status=bounced (user unknown) That will produce backscatter. Why did you accept an unknown recipient? I don’t know, that’s what I was trying to find. Everything I have about queue ID E64DA50D3A1 in maillog was posted in the original message. Oh, wait, i think I just found it in an old pre map. Off to test. -- Ah we're lonely, we're romantic / and the cider's laced with acid / and the Holy Spirit's crying, Where's the beef? / And the moon is swimming naked / and the summer night is fragrant / with a mighty expectation of relief
Re: Am I backscattering?
On Jan 31, 2015, at 5:21 PM, Wietse Venema wie...@porcupine.org wrote: LuKreme: On Jan 31, 2015, at 4:55 PM, LuKreme krem...@kreme.com wrote: On Jan 31, 2015, at 4:23 PM, Wietse Venema wie...@porcupine.org wrote: LuKreme: Jan 26 14:49:53 mail postfix/pipe[44273]: E64DA50D3A1: to=oq6+2nbq@*munged*.com, orig_to=oq6_2nbq@*munged*.com, relay=dovecot, delay=0.13, delays=0.1/0.01/0/0.03, dsn=5.1.1, status=bounced (user unknown) That will produce backscatter. Why did you accept an unknown recipient? I don?t know, that?s what I was trying to find. Everything I have about queue ID E64DA50D3A1 in maillog was posted in the original message. Oh, wait, i think I just found it in an old pre map. Off to test. Yes, the old PCRE map was the problem. IN trying to fix it, I went to change the recipient_delimiter $ postfix reload postfix/postlog: fatal: bad string length 2 1: recipient_delimiter = +_ postsuper: fatal: bad string length 2 1: recipient_delimiter = +_ mail /etc/postfix] $ postconf recipient_delimiter mail_version recipient_delimiter = +_ mail_version = 2.11.3 No such problems here. % bin/postconf mail_version recipient_delimiter mail_version = 2.11.3 recipient_delimiter = +_ # bin/postsuper -v # bin/postlog foo postfix/postlog: foo I suppose you have a Frankenstein Postfix installation, with some parts coming from different bodies? I wouldn’t think so unless postmaster did something very odd. # postsuper -v postsuper: name_mask: ipv4 postsuper: inet_addr_local: configured 2 IPv4 addresses postsuper: queue: defer postsuper: queue: bounce postsuper: queue: maildrop postsuper: queue: incoming postsuper: queue: active postsuper: queue: deferred postsuper: queue: hold postsuper: queue: flush # postlog foo postfix/postlog: foo # postconf recipient_delimiter recipient_delimiter = +_ # postfix reload postfix/postlog: fatal: bad string length 2 1: recipient_delimiter = +_ postsuper: fatal: bad string length 2 1: recipient_delimiter = +_ # ls -lsa /usr/sbin/post* 400 -rwxr-xr-x 1 root wheel 203012 Jan 25 12:21 /usr/sbin/postalias 192 -rwxr-xr-x 1 root wheel 97216 Jan 25 12:21 /usr/sbin/postcat 520 -rwxr-xr-x 1 root wheel 262156 Jan 25 12:21 /usr/sbin/postconf 328 -rwxr-sr-x 1 root maildrop 165092 Jan 25 12:21 /usr/sbin/postdrop 168 -rwxr-xr-x 1 root wheel 84360 Jan 25 12:21 /usr/sbin/postfix 184 -rwxr-xr-x 1 root wheel 92804 Jan 25 12:21 /usr/sbin/postkick 176 -rwxr-xr-x 1 root wheel 89604 Jan 25 12:21 /usr/sbin/postlock 168 -rwxr-xr-x 1 root wheel 84632 Jan 25 12:21 /usr/sbin/postlog 408 -rwxr-xr-x 1 root wheel 206036 Jan 25 12:21 /usr/sbin/postmap 192 -rwxr-xr-x 1 root wheel 97944 Jan 25 12:21 /usr/sbin/postmulti 408 -rwxr-sr-x 1 root maildrop 206532 Jan 25 12:21 /usr/sbin/postqueue 200 -rwxr-xr-x 1 root wheel 101720 Jan 25 12:21 /usr/sbin/postsuper 336 -rwxr-xr-x 1 root wheel 168984 Jan 25 12:21 /usr/sbin/posttls-finger And yes, the 25th is when I installed postfix 2.11.3 -- FRIDAYS ARE NOT PANTS OPTIONAL Bart chalkboard Ep. AABF23
Re: Am I backscattering?
On 31 Jan 2015, at 21:10, LuKreme wrote: On Jan 31, 2015, at 5:21 PM, Wietse Venema wie...@porcupine.org wrote: LuKreme: On Jan 31, 2015, at 4:55 PM, LuKreme krem...@kreme.com wrote: On Jan 31, 2015, at 4:23 PM, Wietse Venema wie...@porcupine.org wrote: LuKreme: Jan 26 14:49:53 mail postfix/pipe[44273]: E64DA50D3A1: to=oq6+2nbq@*munged*.com, orig_to=oq6_2nbq@*munged*.com, relay=dovecot, delay=0.13, delays=0.1/0.01/0/0.03, dsn=5.1.1, status=bounced (user unknown) That will produce backscatter. Why did you accept an unknown recipient? I don?t know, that?s what I was trying to find. Everything I have about queue ID E64DA50D3A1 in maillog was posted in the original message. Oh, wait, i think I just found it in an old pre map. Off to test. Yes, the old PCRE map was the problem. IN trying to fix it, I went to change the recipient_delimiter $ postfix reload postfix/postlog: fatal: bad string length 2 1: recipient_delimiter = +_ postsuper: fatal: bad string length 2 1: recipient_delimiter = +_ mail /etc/postfix] $ postconf recipient_delimiter mail_version recipient_delimiter = +_ mail_version = 2.11.3 No such problems here. % bin/postconf mail_version recipient_delimiter mail_version = 2.11.3 recipient_delimiter = +_ # bin/postsuper -v # bin/postlog foo postfix/postlog: foo I suppose you have a Frankenstein Postfix installation, with some parts coming from different bodies? I wouldn’t think so unless postmaster did something very odd. # postsuper -v postsuper: name_mask: ipv4 postsuper: inet_addr_local: configured 2 IPv4 addresses postsuper: queue: defer postsuper: queue: bounce postsuper: queue: maildrop postsuper: queue: incoming postsuper: queue: active postsuper: queue: deferred postsuper: queue: hold postsuper: queue: flush # postlog foo postfix/postlog: foo # postconf recipient_delimiter recipient_delimiter = +_ # postfix reload postfix/postlog: fatal: bad string length 2 1: recipient_delimiter = +_ postsuper: fatal: bad string length 2 1: recipient_delimiter = +_ # ls -lsa /usr/sbin/post* 400 -rwxr-xr-x 1 root wheel 203012 Jan 25 12:21 /usr/sbin/postalias 192 -rwxr-xr-x 1 root wheel 97216 Jan 25 12:21 /usr/sbin/postcat 520 -rwxr-xr-x 1 root wheel 262156 Jan 25 12:21 /usr/sbin/postconf 328 -rwxr-sr-x 1 root maildrop 165092 Jan 25 12:21 /usr/sbin/postdrop 168 -rwxr-xr-x 1 root wheel 84360 Jan 25 12:21 /usr/sbin/postfix 184 -rwxr-xr-x 1 root wheel 92804 Jan 25 12:21 /usr/sbin/postkick 176 -rwxr-xr-x 1 root wheel 89604 Jan 25 12:21 /usr/sbin/postlock 168 -rwxr-xr-x 1 root wheel 84632 Jan 25 12:21 /usr/sbin/postlog 408 -rwxr-xr-x 1 root wheel 206036 Jan 25 12:21 /usr/sbin/postmap 192 -rwxr-xr-x 1 root wheel 97944 Jan 25 12:21 /usr/sbin/postmulti 408 -rwxr-sr-x 1 root maildrop 206532 Jan 25 12:21 /usr/sbin/postqueue 200 -rwxr-xr-x 1 root wheel 101720 Jan 25 12:21 /usr/sbin/postsuper 336 -rwxr-xr-x 1 root wheel 168984 Jan 25 12:21 /usr/sbin/posttls-finger And yes, the 25th is when I installed postfix 2.11.3 Which doesn't mean you don't have some other Postfix binaries lurking... e.g.: # /usr/sbin/postlog foo postfix/postlog: fatal: bad string length 2 1: recipient_delimiter = -+ # postlog foo postfix/postlog: foo # which postlog /opt/local/sbin/postlog It is possible to get FrankenPostfix Syndrome in a variety of ways. It seems clear from your command demos that whatever you are running as postfix in an interactive shell is calling different (old) postlog and postsuper binaries that differ from the ones you get from calling the unqualified executable name in an interactive shell. That's odd but not impossible. The postfix executable has a bunch of fixed paths hardcoded into it at build time, which can cause trouble and WILL if you try to move around a Postfix installation to somewhere it wasn't build for.
