previously on this list Kevin Chadwick contributed:
when trying to view the presentation with xombrero I enabled
javascript but the controls do not appear and using the url bar is
a bit cumbersome.
Print works well though; printing the whole presentation as a pdf
If the only nameserver entry in /etc/resolv.conf is say 127.0.0.1 or
localhost such as when using unbound couldn't opensmtpds resolver read
that line and chroot without issues like dhcp changes?
--
___
'Write programs that do
On Thu, 7 Aug 2014 19:39:28 +0200
Alexander Schrijver wrote:
Yeah I'm not sure whether it is worth the effort but I was thinking if
a user has set a localhost as the nameserver then can we be very close
to certain that they are not going to change the resolv.conf?
Having two DNS
On Thu, 7 Aug 2014 20:41:39 +0200
Gilles Chehade wrote:
Nope there's currently no way to turn chrooting for the lookup process.
It's not really a resolver thing, we could have the resolver code in a
chroot with some refactoring, but we need a process that does not run
chrooted for other
I am not talking about submission which I guess is what the smtps
option is for and I know GPG is the best method and I also know that
spamd causes plain text transmissions.
With STARTTLS I believe there is a clear text race where an attacker can
create a response stating STARTTLS is unsupported
I may have come across some information about rewriting envelopes but I
am struggling to find it right now.
With OpenSMTPD you can use bob+compa...@bobs.com, which is great.
My existing server however already uses bob-compa...@bobs.com and on
that system I can specify the character after which
Assuming it's correct I wonder if something along the lines of the
following would improve the makemap man page virtual domains section.
I tried a few different things to get majordomo and the power
of virtual domains working, including a second deliver to mda before
noticing the 'extension'
On Sat, 28 Mar 2015 08:55:24 -0700
Seth wrote:
If the filesystem supports case sensitivity then I can understand users
expecting the current behaviour but it doesn't seem practical to me and
I couldn't see a format specifier to lowercase deliveries to Maildir
expanding to just TAG.
On Sat, 28 Mar 2015 08:55:24 -0700
Seth wrote:
If the filesystem supports case sensitivity then I can understand users
expecting the current behaviour but it doesn't seem practical to me and
I couldn't see a format specifier to lowercase deliveries to Maildir
expanding to just TAG.
On Wed, 08 Apr 2015 13:27:48 -0700
Seth wrote:
Do you have a test email address we can try sending something to which
uses that server?
Sent privately
Also, whether this hangs
/usr/bin/openssl s_client -connect mx5.demon.co.uk:25 -starttls smtp
-CAfile /etc/ssl/cert.pem
Starttls.info
On Wed, 08 Apr 2015 19:55:52 -0700
Seth wrote:
Also, whether this hangs
/usr/bin/openssl s_client -connect mx5.demon.co.uk:25 -starttls smtp
-CAfile /etc/ssl/cert.pem
I ran the command above on an OpenBSD 5.6-release host and it stopped
responding at the 250 8BITMIME line at the
For a minute I thought the following was possible that my old server
couldn't do. I know gpg is the solution but getting people to use it
can sometimes be easy and sometimes impossible and so there are times
when you are on the border of what you are comfortable sending in plain
text.
accept
On Thu, 09 Apr 2015 09:54:17 -0700
Seth wrote:
On my 5.6 box it stops at CONNECTED and the traffic shows client hello
like for OpenSMTPD (well actually a certificate receipt can be seen in
the encrypted traffic but not much more).
Only thing I can think of is that you're running a
http://marc.info/?l=openbsd-miscm=142842356024311w=2
When I looked at the actual traffic it appeared that it gets one step
further and the connection actually stops at OpenSMTPD sending a client
hello via STARTTLS with no further response from the other side.
If someone can say it happens to
> This impact all users who upgrade to OpenSSL 1.0.2f and will cause smtpd
> to crash as soon as the RSA engine is used (ie: whenever there's crypto)
>
> A quick workaround is to not upgrade to 1.0.2f yet and maybe ask OpenSSL
> why a "patchlevel" release contains more than patches.
>
>
I sent my elansys one direct, should I have posted it to the list?
On Sun, 6 Aug 2017 14:32:16 +0200
> The next question would be ...why does it work for other ppl?
I use system accounts and some scripts but if you need a database then
I can't help. It's not actually that difficult once you work it out to
sync system pwd.db files actually and you get the
Is it possible to have both?
letsencrypt for tls on port 25 for remote servers to verify
and tls-require verify auth on port 587 permitting self signed certificates
signed by myca only for client authentication without any risk of arbitrary CAs
providing forged certificates.
Perhaps I can move
Perhaps stunnel may work for port 25, though I guess I would lose some of
opensmtpds priv sep features
19 matches
Mail list logo
