Hi !
I downloaded postfix-2.7.0 and I need to manually build it.
The goal is to place everything in a different folder than usual :
/opt/postfix
To do that at the make install, I set the root_folder at /opt/postfix
and then at the next questions, the default choice is good for me.
However,
Stan Hoeppner a écrit :
Gregory BELLIER put forth on 3/2/2010 6:03 AM:
Hi !
I downloaded postfix-2.7.0 and I need to manually build it.
The goal is to place everything in a different folder than usual :
/opt/postfix
http://www.postfix.org/INSTALL.html
4.4 - Overriding built-in
Hi.
if I copy an existing cipher in OpenSSL and rename it, it will act as if
it is a new cipher.
Would I need to build postfix against this new OpenSSL to be able to use
the new cipher? I think it's not required but I have a doubt.
How does the TLS negociation work ? I guess it is done by Pos
Victor Duchovni a écrit :
On Wed, Mar 24, 2010 at 11:09:44AM +0100, Gregory BELLIER wrote:
if I copy an existing cipher in OpenSSL and rename it, it will act as if it
is a new cipher.
On the wire SSL ciphers have numeric ids, not names. If you "rename"
a cipher, it just c
mouss a écrit :
$ ldd /usr/local/libexec/postfix/smtpd
/usr/local/libexec/postfix/smtpd:
...
libssl.so.7 => /usr/local/lib/libssl.so.7 (0x2810a000)
libcrypto.so.7 => /usr/local/lib/libcrypto.so.7 (0x2815)
...
if you rebuild openssl but provide the same ABI, then it's ok. If
Victor Duchovni a e'crit:
On Thu, Mar 25, 2010 at 10:31:40AM +0100, Gregory BELLIER wrote:
At this point, you really need to step back, take a deep breath, and
use OpenSSL as-is.
As I said, it's to learn. If I do nothing then it's pointless.
No need to cha
Hi all !
I would like to set up authentication between 2 postfix hosted on Debian
Lenny and until now it doesn't work.
Here is a log sample :
warning: SASL authentication failure: No worthy mechs found
SASL authentication failed; cannot authenticate to server
10.0.0.6[10.0.0.6]: no mechanism
Victor Duchovni a écrit :
Try again, with a more useful log sample, and configuration settings
for the receiving side. The log sample should include multiple lines
of logging from the SMTP client, showing any TLS handshake, ...
Alright, please take a look at the end of this email for the
c
I managed to have an authentication but it's really weird. I'm on Debian
Lenny.
In /etc/default/saslauthd on both mta1 and mta2, I have :
START=yes
DESC="SASL Authentication Daemon"
NAME="saslauthd"
MECHANISMS="shadow"
MECH_OPTIONS=""
THREADS=5
OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd
Victor Duchovni a écrit :
On Tue, Apr 20, 2010 at 12:21:35PM +0200, Gregory BELLIER wrote:
Did you read the logs?
I did.
Why are you offering CRAM-MD5 and NTLM on mta1, when only PLAIN works?
Because in my file sasl/smtpd.conf, every time I set a mech_list, it
doesn't work.
Hi !
I managed to make it work. Finally ! Thank you Victor !
However, I've done dozen of tests and I found a weird behaviour when
authenticating and I can reproduce it every time.
This is a test sample I've done. Obviously to have a success, the
login/password in sasl_passwd.db and the login
11 matches
Mail list logo
