u someone doesnt use DNSSEC... its been hijacked me thinks
http://www. medicalbits. nl/ really? :)
On Tue, 2013-10-29 at 14:05 +1100, m...@electronico.nc wrote:
> Hi all,
> Please excuse me for this message but I can't find the pigeonhole
> sources available anymore.
> This page :
Hi all,
Please excuse me for this message but I can't find the pigeonhole
sources available anymore.
This page : http://pigeonhole.dovecot.org/download.html
Points to (for latest sources) :
http://www.rename-it.nl/dovecot/2.2/dovecot-2.2-pigeonhole-0.4.2.tar.gz
And it seems that : www.rename-i
On 29/10/2013 03:19, Robert Schetterer wrote:
https://perot.me/encrypt-specific-incoming-emails-using-dovecot-and-sieve
I got worried, laughed, and stopped reading at:
"not only do you not have to edit any Postfix configuration (which by
itself is an exercise in patience),"
As you kno
On 29/10/2013 10:10, Michael Orlitzky wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/28/2013 04:10 PM, Reindl Harald wrote:
php_admin_value open_basedir /var/www/$domain/$host/
php_admin_value upload_tmp_dir /var/www/$domain/$host/tmp
php_admin_value session.save_path /var/www/$dom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/28/2013 04:10 PM, Reindl Harald wrote:
>>
>> php_admin_value open_basedir /var/www/$domain/$host/
>> php_admin_value upload_tmp_dir /var/www/$domain/$host/tmp
>> php_admin_value session.save_path /var/www/$domain/$host/tmp
>> php_admin_value
On 2013-10-28 20:23, Reindl Harald wrote:
Am 28.10.2013 20:14, schrieb Douglas Mortensen:
However, it would be nice to know that even if we were breached, the
emails on the server were encrypted and would be completely useless to
an attacker.
This type of encryption is ideal and some regulation
Am 28.10.2013 20:49, schrieb Michael Orlitzky:
> On 10/28/2013 03:14 PM, Douglas Mortensen wrote:
>> If a customer has vulnerable PHP code on a website, some of these
>> will allow a remote file upload. I have seen cases where they upload
>> a PHP script that is a sort of web-based console/shell
On 10/28/2013 03:14 PM, Douglas Mortensen wrote:
> If a customer has vulnerable PHP code on a website, some of these
> will allow a remote file upload. I have seen cases where they upload
> a PHP script that is a sort of web-based console/shell to the server
> (file-system, etc.). It provides sever
On 28/10/2013 19:14, Douglas Mortensen wrote:
So given that type of scenario, if filesystem permissions
weren't correct, or some new exploit surfaced that allowed someone
bypass or elevate to root, then they could theoretically have
access to the entire fileystem including where emails are s
Am 28.10.2013 20:14, schrieb Douglas Mortensen:
> So given that type of scenario, if filesystem permissions weren't
> correct, or some new exploit surfaced that allowed someone bypass or elevate
> to root, then they could theoretically have access to the entire fileystem
> including where
Currently our dovecot servers are on our webhosting linux boxes. We are using
the LAMP stack to host websites, and also doing email with postfix & dovecot on
these systems. We provide this as a hosting setup for 100+ accounts/websites on
a single server (a multi-tenant setup). Each customer has
On 10/28/2013 12:02 PM, Douglas Mortensen wrote:
> Hi,
>
> We have clients with various security & compliance requirements.
> Although not required, it would be ideal to have messages encrypted
> at rest.
You can rule out a lot of the crazier options by answering the questions,
(a) What attack s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 28.10.2013 17:02, schrieb Douglas Mortensen:
> Hi,
>
> We have clients with various security & compliance requirements.
> Although not required, it would be ideal to have messages encrypted
> at rest. We already use SSL/TLS to secure the transmis
W dniu 18.12.2012 23:10, Timo Sirainen pisze:
> On 19.12.2012, at 0.06, Marcin Mirosław wrote:
>
I'd like to ask is this behavior correct?
>>>
>>> You're using Dovecot as simple imapc proxy without local mails? Then
>>> yeah, what else could it really do?
>>
>> Here is problem, I'm using loc
Ah, gutted. Neither are an option right now.
Thanks for your help anyway.
-Mark
On 28 October 2013 15:13, /dev/rob0 wrote:
> On Mon, Oct 28, 2013 at 01:43:48AM +0100, IT geek 31 wrote:
> > I've been following the wiki document at
> > http://wiki2.dovecot.org/Replication, but I've become stu
Hi,
We have clients with various security & compliance requirements. Although not
required, it would be ideal to have messages encrypted at rest. We already use
SSL/TLS to secure the transmission of most email. However, it would be nice to
have them encrypted sitting on our server. Is anyone do
Just in case someone else has the same problem, I had to change the
following two variables
mail_home = /mnt/home/imapd/%d/%n
mail_location = dbox:/mnt/home/imapd/%d/%n
to
mail_home = /mnt/home/imapd/%d/%n
mail_location = dbox:~/
"When mail_location begins with%h or~/, its permissions are co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Oct 2013, LuKreme wrote:
hi Timo,
I *think* I figured it out, the mailboxes that were causing the errors
each had a file in them named “:,2” since removing those and removing
the dovecot-uidlist the problem hasn’t returned.
if the Mai
On Mon, Oct 28, 2013 at 01:43:48AM +0100, IT geek 31 wrote:
> I've been following the wiki document at
> http://wiki2.dovecot.org/Replication, but I've become stuck.
>
> I'm running version 2.1.3 on NetBSD 5.2 (v2.2+ isn't available as a
> package yet, and compiling my own is well outside my whee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 27 Oct 2013, Charles Marcus wrote:
As a result of learning of the new 'Intro' App introduced by LinkedIn, and
discussing how to block SMTP access to my postfix server from these clients,
I'm now interested in doing the same for dovecot.
R
On 10/27/2013 1:21 PM, Charles Marcus wrote:
Bottom line desire is to avoid scraping/hijacking email stored on my
dovecot server by any client other than a users client.
I don't think IMAP has a "client identification" component in its
protocol, at least one that's in widespread and "compatib
Hi,
is it possible to run a script right after the IMAP/POP3 session was started? I
know about post-login scripting but this is probably not what i'm looking for.
I need to run a script which will know PID of process running IMAP session (so
it must be already started). Thank you.
azur
Am 28.10.2013 11:34, schrieb Андрей Кумыков:
> Is it possible to disable unsecure POP3 protocol at all in Dovecot 2.1?
> There was "protocols" option in 1.x version, and there was separate pop3 and
> pop3s modules
110/143 are not unsecure because the way to go these
days should be http://en.wikip
Hi to all.
Is it possible to disable unsecure POP3 protocol at all in Dovecot 2.1?
There was "protocols" option in 1.x version, and there was separate pop3 and
pop3s modules.
There is no "pop3s" in configuration files in 2.1.
El 26/10/13 17:10, Timo Sirainen escribió:
On 24.10.2013, at 13.41, Angel L. Mateo wrote:
amateo_adm@myotis51:~$ sudo doveadm search -u vlo mailbox
BORRADOS.INBOX.MNCS
doveadm(vlo): Error: Syncing mailbox BORRADOS.INBOX.MNCS failed: Message
has been copied too many times (59306 + -1)
Looks
Hi Lucas,
Thanks for your response. I have done that, and when logged into both
servers as the vmail I can SSH to the other server and am not challenged
for a password (I'm using keys).
However when I restart Dovecot I get the following error:
Oct 28 10:36:11 server1 dovecot: dsync-local(vmail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Oct 2013, Andrzej A. Filip wrote:
How to configure dovecot to use different default mail_location for
system (uid<1_000) and normal users (uid>=1_000)?
I want to to use by default
* classic mailbox in standard location for system users
*
27 matches
Mail list logo