On 21/06/16 10:47, Benny Pedersen wrote:
> On 2016-06-21 00:42, Peter wrote:
>> On 19/06/16 14:22, Paul R. Ganci wrote:
>>> I am running CentOS 7 which runs postfix chroot.
>>
>> No it does not.
>>
>> If your postfix is running chroot on CentOS 7 (or indeed any version of
>> CentOS or RHEL, etc) th
On 2016-06-21 00:42, Peter wrote:
On 19/06/16 14:22, Paul R. Ganci wrote:
I am running CentOS 7 which runs postfix chroot.
No it does not.
If your postfix is running chroot on CentOS 7 (or indeed any version of
CentOS or RHEL, etc) then eitehr you have (1) modified the config
yourself to make
On 20/06/16 02:56, Wietse Venema wrote:
> 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 problem
On 19/06/16 14:22, Paul R. Ganci wrote:
> I am running CentOS 7 which runs postfix chroot.
No it does not.
If your postfix is running chroot on CentOS 7 (or indeed any version of
CentOS or RHEL, etc) then eitehr you have (1) modified the config
yourself to make it chroot, (2) installed postfix pa
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/po
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
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
Tu
On 06/14/2016 08:02 AM, Wietse Venema wrote:
Paul R. Ganci:
On 06/14/2016 04:28 AM, Wietse Venema wrote:
Paul R. Ganci:
If the MYSQL library was handling the host name resolution
then why does the postmap -q query succeed? Shouldn't both queries fail?
Perhaps you are running postmap as RO
Paul R. Ganci:
> On 06/14/2016 04:28 AM, Wietse Venema wrote:
> > Paul R. Ganci:
> >> anyone know what I am missing in that it seems postfix did resolve the
> >> IP address when communicating with the mysql database?
> > The host lookup is done by the MSQL library.
> That doesn't seem correct to me
On 06/14/2016 04:28 AM, Wietse Venema wrote:
Paul R. Ganci:
anyone know what I am missing in that it seems postfix did resolve the
IP address when communicating with the mysql database?
The host lookup is done by the MSQL library.
That doesn't seem correct to me because with hosts =
server-1.e
Paul R. Ganci:
> I changed the line hosts = server-1.example.com to use an IP address
> instead hosts = 192.168.1.200 and everything started working. Does
> anyone know what I am missing in that it seems postfix did resolve the
> IP address when communicating with the mysql database?
The host l
I changed the line hosts = server-1.example.com to use an IP address
instead hosts = 192.168.1.200 and everything started working. Does
anyone know what I am missing in that it seems postfix did resolve the
IP address when communicating with the mysql database?
On 06/13/2016 07:52 PM, Paul R.
12 matches
Mail list logo
