Hello
I have to setup a "secured" email server
- encrypted filesystem
- SSL or TLS only for SMTP and IMAPS
- Talking only to some known other same-secured servers
Any info/links welcome !
Please do not start some flame war around this !
I've been ordered to set up such server and I KNOW there
On 10/22/2013 10:27 PM, Robin wrote:
> On 10/22/2013 3:22 PM, Noel Butler wrote:
>> But I agree with you on the rest, since of those 500K IP's Marc claims
>> to have I'd bet that 99% are hijacked innocent pc's/servers, and of
>> them, >75% would likely be a one time usage.
>
> This accords with ou
On 10/22/2013 3:22 PM, Noel Butler wrote:
But I agree with you on the rest, since of those 500K IP's Marc claims
to have I'd bet that 99% are hijacked innocent pc's/servers, and of
them, >75% would likely be a one time usage.
This accords with our own statistics. While it IS tempting to treat
On 23/10/2013 05:45, Rick Romero wrote:
IMHO, the problem with all out blocks on auth is the same as doing an
all
out block based on SPF - so many IPs are shared you can easily get
false
positives.
Blocks using SPF will not be FP's, they will be by your internal
decision, so will be a g
Zach,
Thanks for following up with the list, though I dont and wont touch
anything debian/, there are plenty here who
do, and may in time appreciate your feedback if they strike same.
On 23/10/2013 00:14, Zach La Celle wrote:
On 10/17/2013 09:23 AM, Zach La Celle wrote:
On 10/17/2013 05:25
22.10.2013 21:31, Marc Perkel:
> I would like to have a list of IPs (hacker list) that I can do a lookup
> on so that if anyone tries to authenticate to dovecot they always fail
> if they are on my list.
You could enable dovecot's tcpwrapper support for this.
Kind Regards,
Christian Schmidt
--
On 2013-10-22 14:52, Dan Langille wrote:
I received this message today, and remembered, you can't do that...
$ doveadm pw -s SHA512-CRYPT
Enter new password: doveadm(dan): Fatal: open(/dev/tty) failed: No
such file or directory
It seems if you have no tty, you can't create a password. Surely
Quoting Marc Perkel :
I would like to have a list of IPs (hacker list) that I can do a lookup
on so that if anyone tries to authenticate to dovecot they always fail
if they are on my list.
I have the list - and the list is available as a DNS blacklist.
I'd like to have it work with both local
Marc Perkel skrev den 2013-10-22 21:31:
Anyone else interested in this?
would you sell more ram later ?
basicly you like to have fail2ban to a central server logging via syslog
?
if yes create more rules to fail2ban and show it on a wiki
I would like to have a list of IPs (hacker list) that I can do a lookup
on so that if anyone tries to authenticate to dovecot they always fail
if they are on my list.
I have the list - and the list is available as a DNS blacklist.
I'd like to have it work with both local IP lists or RBL lookup
On 2013-10-22 14:54, Frank de Bot wrote:
Dan Langille wrote:
I received this message today, and remembered, you can't do that...
$ doveadm pw -s SHA512-CRYPT
Enter new password: doveadm(dan): Fatal: open(/dev/tty) failed: No such
file or directory
It seems if you have no tty, you can't create
Hi,
It sounds you have forgotten to mount /dev in the jail. You can consult
http://www.freebsd.org/doc/handbook/jails-build.html for all steps to do
this.
Regards,
Frank de Bot
Dan Langille wrote:
I received this message today, and remembered, you can't do that...
$ doveadm pw -s SHA512-
I received this message today, and remembered, you can't do that...
$ doveadm pw -s SHA512-CRYPT
Enter new password: doveadm(dan): Fatal: open(/dev/tty) failed: No such
file or directory
It seems if you have no tty, you can't create a password. Surely there
is a better way to do this?
Loo
When I tried to add this section, I got this error at restarting dovecot $
/usr/sbin/dovecot restartdoveconf: Warning: NOTE: You can get a new clean
config file with: doveconf -n > dovecot-new.confdoveconf: Warning: Obsolete
setting in /etc/dovecot/dovecot.conf:77: add auth_ prefix to all settin
When I tried to add this section, I got this error at restarting dovecot $
/usr/sbin/dovecot restartdoveconf: Warning: NOTE: You can get a new clean
config file with: doveconf -n > dovecot-new.confdoveconf: Warning: Obsolete
setting in /etc/dovecot/dovecot.conf:77: add auth_ prefix to all settin
On 10/17/2013 09:23 AM, Zach La Celle wrote:
> On 10/17/2013 05:25 AM, Noel Butler wrote:
>> On 17/10/2013 00:08, Zach La Celle wrote:
>>> Dovecot version 2.1.7
>>> Ubuntu 12.04.3 LTS
>>> Kernel 3.2.0-35-generic x86_64
>>>
>>> I'm not sure exactly when this started occurring, but sporatically users
Hello,Thanks for the link, I know how I can configure it from the wiki.. My
question is can I add this section completely by myself?I can't find this
section at all in dovecot.conf to modify it, and dovecot.masterusers file
doesn't exist too in etc configuration files, should I create it too?be
Folks,
Several questions packed into one email ;)
Can dovecot use TLS/SSL on LTMP inet socket?
Can I configure dovecot to only let an authenticated user deliver mail
via LMTP?
Can I tell dovecot to use a user/password for proxying LMTP connections?
All this is related to my quest to move fr
Hi Steffen,
Am 2013-10-22 10:05, schrieb Steffen Kaiser:
see http://wiki2.dovecot.org/PasswordDatabase/ExtraFields
Did, thanks. The errors I mentioned in my previous post are gone.
Still, proxying does not work as expected. Instead I get strange warnings:
Oct 22 12:06:51 server dovecot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 18 Oct 2013, Jogi Hofmüller wrote:
We are getting closer to the migration of our mailsystem. Now I have a
special question. We are successfully using
passdb {
driver = pam
}
and that is good. Now, how would I tell dovecot to proxy cert
> Od: Robert Schetterer
> Komu:
> Dátum: 22.10.2013 00:14
> Predmet: Re: [Dovecot] Strange output from LIST command
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Am 21.10.2013 22:11, schrieb azurIt:
>>> Od: Bron Gondwana Komu:
>>> Dátum: 17.10.2013 12:30 Predmet: Re:
>>> [Dovecot] Strang
21 matches
Mail list logo
