on 22/01/2014 05:22 πμ Benny Pedersen wrote the following:
> On 2014-01-21 16:03, Aggelos wrote:
>> Thanks for your comments, Benny.
>> The file was a bad mix of old configuration remnants :\
>> Does the following make more sense now?
>
> yes it does
>
> just that rfc-ignorant still have no data,
-Original Message-
From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Noel Jones
Sent: Tuesday, January 21, 2014 6:02 PM
To: postfix-users@postfix.org
Subject: Re: Virtual map restriction
On 1/21/2014 3:51 PM, Postfix wrote:
> Hi,
>
> I am using
Hi,
On a CentOS 6.5 box with a virtual_mailbox_domains,
virtual_mailbox_maps, virtual_alias_maps setup all accessing openldap I
added in main.cf (and restarted postfix afterwards):
recipient_delimiter = +
with the goal to get patrick+...@example.org working. Unfortunately
there is a problem
On Wed, Jan 22, 2014 at 04:59:25PM +0100, Patrick Lists wrote:
> On a CentOS 6.5 box with a virtual_mailbox_domains,
> virtual_mailbox_maps, virtual_alias_maps setup all accessing
> openldap I added in main.cf (and restarted postfix afterwards):
>
> recipient_delimiter = +
Anecdotal reporting is
On 2014.01.22 11.41, Chris Richards wrote:
Basically, I need to find out which users are connecting to port 25
instead of 587.
man 5 postconf. see syslog_name. also see the sample config which
comes with the software. this includes a submission config which uses
syslog_name
-ben
I apologize if this has already been asked, but my google-fu is not strong
enough to find the answer I am seeking.
Basically, I need to find out which users are connecting to port 25
instead of 587. I need to get the users off port 25 so I can stop
allowing logins on that port (this is a system I
Chris Richards:
> There is nothing in the logs that I can see which allows me to
> differentiate connections on port 25 and port 587. (I'm currently
> on Postfix 2.10.1 running on Gentoo Linux, if that makes a difference.)
Configure different "syslog" names for port 25 and submission.
Examples fr
Aha! See, I knew it would be something simple. I was just trying to
attack the problem the wrong way 'round.
I had actually been looking for a way to change what was shown in syslog,
but I was thinking in the context of the port name, not the service name.
Thanks guys!
Chris
On Wed, January 2
Hello,
I'm having some trouble getting a Comodo PositiveSSL certificate to work
correctly with Postfix 2.7.0.
I've attempted to follow the instructions at
http://www.postfix.org/postconf.5.html#smtpd_tls_cert_file :
"You should include the required certificates in the server certificate
file, th
Ben Johnson:
> But when I attempt to verify the certificate chain, I always receive
> "19:self signed certificate in certificate chain".
Does THE CLIENT PROGRAM know the root certificate? If it does not,
then that certificate is worth no more than any other self-signed
certificate.
Wietse
Hi Viktor,
TL;DR fixed, case closed.
On 22-01-14 17:18, Viktor Dukhovni wrote:
On Wed, Jan 22, 2014 at 04:59:25PM +0100, Patrick Lists wrote:
On a CentOS 6.5 box with a virtual_mailbox_domains,
virtual_mailbox_maps, virtual_alias_maps setup all accessing
openldap I added in main.cf (and resta
On Wed, Jan 22, 2014 at 03:07:33PM -0500, Ben Johnson wrote:
> I created the certificate with the following command:
>
> $ cat example_com.crt PositiveSSLCA2.crt AddTrustExternalCARoot.crt >
> /root/ssl/example.com.pem
To verify that the file is well-formed try the below:
openssl crl2pkcs7
On 1/22/2014 3:46 PM, Viktor Dukhovni wrote:
> On Wed, Jan 22, 2014 at 03:07:33PM -0500, Ben Johnson wrote:
>
Thanks for expanding upon Wietse's response, Viktor.
>> I created the certificate with the following command:
>>
>> $ cat example_com.crt PositiveSSLCA2.crt AddTrustExternalCARoot.crt >
On Wed, Jan 22, 2014 at 04:26:34PM -0500, Ben Johnson wrote:
> > No -CAfile or -CApath options in this command-line.
>
> I see. I had actually tried adding a -CApath, but I didn't think it was
> working correctly because no matter what path I supplied, the
> certificate always ended with (what I
On Wed, Jan 22, 2014 at 09:40:39PM +, Viktor Dukhovni wrote:
> > Verify return code: 0 (ok)
>
> The return code from the verify callback is not the certificate
> verification status. It just means the client is willing to keep
> going.
Sorry, small correction, in s_client when you see:
On 2014-01-22 17:41, Chris Richards wrote:
What am I missing here? I'm sure it's obvious to someone, but it's
completely blowing by me.
syslog_facility (mail) The syslog facility of Postfix logging.
syslog_name (postfix) The mail system name that is prepended to the
process name in syslog re
16 matches
Mail list logo
