Re: mysql local_recipient_map
Paul R. Ganci: > I am running CentOS 7 which runs postfix chroot. Everything works as > expected in this mode except for the mysql configuration. [] > I am okay with the setup as it is now however can you elaborate on > what additional setup I would need to get the mysql database to work Turn off chroot (edit master.cf, then do "postfix reload"). If RedHat decides to turn on chroot, then it is is their responsibility, not mine, to figure out what nsswitch, pam, etc. files are needed under /var/spool/postfix, and to keep those files in sync with the base operating system. Wietse
Re: mysql local_recipient_map
On 06/19/2016 07:26 AM, Wietse Venema wrote: Turn off chroot (edit master.cf, then do "postfix reload"). If RedHat decides to turn on chroot, then it is is their responsibility, not mine, to figure out what nsswitch, pam, etc. files are needed under /var/spool/postfix, and to keep those files in sync with the base operating system. Sorry I didn't mean to offend if I did. As I said there is no issue running chroot. The setup works just fine and has for months now. Only recently did I try to use the mysql database with the local_recipient_maps and saw the issue I did. I am happy with my solution but was curious and thought you had some magic. Thanks for your help. -- Paul (ga...@nurdog.com) Cell: (303)257-5208
Re: mysql local_recipient_map
Paul R. Ganci: > On 06/19/2016 07:26 AM, Wietse Venema wrote: > > Turn off chroot (edit master.cf, then do "postfix reload"). If RedHat > > decides to turn on chroot, then it is is their responsibility, not > > mine, to figure out what nsswitch, pam, etc. files are needed under > > /var/spool/postfix, and to keep those files in sync with the base > > operating system. > Sorry I didn't mean to offend if I did. As I said there is no issue No offense taken. It just is a recurring problem with Linux distros that turn on chroot without providing the necessary files to make things like mysql work properly. Postfix 3.0 makes it harder to turn on chroot; hopefully that will end these problems. > running chroot. The setup works just fine and has for months now. Only > recently did I try to use the mysql database with the > local_recipient_maps and saw the issue I did. I am happy with my > solution but was curious and thought you had some magic. Except that the mysql support won't work unless you do one of the following: a) you turn off chroot in Postfix. b) you add some files under /var/spool/postfix, the details of which change with the distribution and version, and which are discovered by stracing programs until all errors are accounted for. > Thanks for your help. You're welcome. Wietse
ot: exempting black listed domain for a user?
I have a user who can not receive emails as his correspondent's domain is currently on multiple rbls. As an interim measure, should I look at temporarily allowing this domain? Or, is that a bad idea, shouldn't consider such temp workarounds? domain in question: Checking ckchaiseree.com which resolves to119.59.120.56 against 107 known blacklists... Listed 7 times. Blacklist Reason LISTED CBL 119.59.120.56 was listed LISTED ivmSIP 119.59.120.56 was listed LISTED ivmSIP24 119.59.120.56 was listed LISTED Protected Sky 119.59.120.56 was listed LISTED SORBS SPAM 119.59.120.56 was listed LISTED Spamhaus ZEN 119.59.120.56 was listed LISTED UCEPROTECTL2 119.59.120.56 was listed On 20 June 2016 6:21:20 AM GMT+02:00, "S R." wrote: Dear Voytek Can you please check the supplier chaiseeree cannot send e-mail to us -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
