On 28.09.2018 04:24, Adam Gold wrote:
> Hello everyone. I'm close to completing my first build of a mail
> server - Postfix, Dovecot, Postgres (I know, sounds like overkill),
> Rspamd with Redis and Unbound (please infer a mega lack of experience
> disclaimer). The model is standalone internet
On 28.09.2018 00:08, Florian Pritz wrote:
> On Wed, Sep 26, 2018 at 09:34:07AM +0300, Aki Tuomi
> wrote:
>> # before current passbd
>> passdb {
>> driver = passwd-file
>> args = username_format=%Lu /etc/dovecot/aliases
>> }
>>
>> # into /etc/dovecot/aliases
>> alias@user:::user=real_use
Larry Rosenman wrote:
>
> Larry Rosenman wrote:
> > I have my dovecot running with TLS, so the passwords are NOT
> transmitted in
> > the clear (starttls).
>
> The problem is not transmitting them in the clear but keeping them in
> the clear in a local file like muttrc, o
Hello everyone. I'm close to completing my first build of a mail server
- Postfix, Dovecot, Postgres (I know, sounds like overkill), Rspamd with
Redis and Unbound (please infer a mega lack of experience disclaimer).
The model is standalone internet with remoted sasl-authenticated
clients.
T
On Thu, 27 Sep 2018, Victor Sudakov wrote:
As others have written, you may see performance degradation as Dovecot
will have to rebuild indices, but if you have small mailboxes, this won't
be too bad. The only reason I use direct file access rather than IMAP
is that I'm too lazy to work out a pa
Two quick questions, if I may:
We've been asked to change an existing application (whose builtin S/MIME
capabilities are quite unclear) so that the e-mails it sends will be
S/MIME encrypted, if possible. I have some experience in getting an MTA
to encrypt e-mails in transit, but the trick is, of c
On Wed, Sep 26, 2018 at 09:34:07AM +0300, Aki Tuomi
wrote:
> # before current passbd
> passdb {
> driver = passwd-file
> args = username_format=%Lu /etc/dovecot/aliases
> }
>
> # into /etc/dovecot/aliases
> alias@user:::user=real_username noauthenticate
>
> This hopefully works.
This s
I am testing a special setup on one machine where I want to put some local
users that get mail locally to /home user directories via postfix
transport map local: for historical and practical reasons. Other users are
setup as virtual users.
The local users are *also* setup as virtual users for do
"Reliably" means what exactly?
- At progress of 66%?
- after e.g. 9611 Mails?
- whenever a specific Mail is touched?
Von unterwegs gesendet
> Am 27.09.2018 um 20:52 schrieb Evan Klitzke :
>
> I am using Dovecot 2.2.36 and I am trying to use doveadm backup to migrate
> email from Gmail to Do
I am using Dovecot 2.2.36 and I am trying to use doveadm backup to
migrate email from Gmail to Dovecot. When I run doveadm backup, it goes
for a while and then eventually hits an assertion error (I've tried this
a few times now and it happens reliably).
The assertion failure looks like this:
On 9/27/18, 10:57 AM, "Victor Sudakov" wrote:
Larry Rosenman wrote:
> I have my dovecot running with TLS, so the passwords are NOT transmitted
in
> the clear (starttls).
The problem is not transmitting them in the clear but keeping them in
the clear in a local file like
Larry Rosenman wrote:
> I have my dovecot running with TLS, so the passwords are NOT transmitted in
> the clear (starttls).
The problem is not transmitting them in the clear but keeping them in
the clear in a local file like muttrc, or entering the password each
time you launch mutt.
--
Victor
I have my dovecot running with TLS, so the passwords are NOT transmitted in
the clear (starttls).
On Thu, Sep 27, 2018 at 10:42 AM Victor Sudakov wrote:
> Joseph Tam wrote:
> >
> > > However, I often read and modify the mailboxes locally with mutt (e.g.
> > > append and delete mails).
> > >
> >
Larry Rosenman wrote:
> What I do is keep my passwords in a file encrypted by GPG and have mutt do:
> source "gpg -q --textmode -d ~/.neomutt/passwords.gpg |"
>
> that way they're not readable except by use of a passworded GPG key.
>
Very clever, I must admit.
--
Victor Sudakov, VAS4-RIP
Joseph Tam wrote:
>
> > However, I often read and modify the mailboxes locally with mutt (e.g.
> > append and delete mails).
> >
> > Should I expect any problems wit Dovecot indexes etc? What if I even
> > do "rm ~/Mail/some/mailbox", will Dovecot be mad at me?
>
> I do it all the time. Works fi
> On 27 Sep 2018, at 16.53, James wrote:
>
> On 27/09/2018 13:40, Stephan Bosch wrote:
>
>>> Address Line Code
>>> : DEBUG BLOCK: 3
>>> 0001: EXTENSIONS [1]:
>>> 0002: vacation
>>> 0004:2: VACATION
>>> 0007:4: seconds: NUM 5
>>> 000
What I do is keep my passwords in a file encrypted by GPG and have mutt do:
source "gpg -q --textmode -d ~/.neomutt/passwords.gpg |"
that way they're not readable except by use of a passworded GPG key.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640
Thomas Leuxner wrote:
>
> > > >> However, I often read and modify the mailboxes locally with Mutt (e.g.
> > > >> append and delete mails).
>
> Why not use Mutt's IMAP capabilities and keep the indexes nice and clean?
Maybe the only reason is that I don't want to bother with
authentication and do
Communigate Pro has a nice Migration/MoveIMAPMail utility. As
Communigate is free to use for up to five accounts, I think it is
legal to install it and use the MoveIMAPMail utility.
I have used it once to migrate mail from Communigate to dovecot.
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/
On 27/09/2018 13:40, Stephan Bosch wrote:
Address Line Code
: DEBUG BLOCK: 3
0001: EXTENSIONS [1]:
0002: vacation
0004:2: VACATION
0007:4: seconds: NUM 5
0009: Binary is corrupt.
The line numbers differs and 86400 is read as 5
On Thu, Sep 27, 2018 at 10:42:16 +0100, James wrote:
> On 25/09/2018 22:39, Stephan Bosch wrote:
>
> > Something mightily weird is going on at your end. It doesn't fail here
> > (see below). First of all, what is your configuration (output from
> > `dovecot -n`)?
>
> You have dovecot.conf but...
Op 27-9-2018 om 11:42 schreef James:
On 25/09/2018 22:39, Stephan Bosch wrote:
Something mightily weird is going on at your end. It doesn't fail here
(see below). First of all, what is your configuration (output from
`dovecot -n`)?
You have dovecot.conf but...
$ dovecot -c dovecot.conf -n
On 27.09.2018 13:30, Ángel L. Mateo wrote:
> El 27/09/18 a las 12:04, Aki Tuomi escribió:
>>
>> You can. In passdb, return userdb_your_own_variable=value, in userdb you
>> can omit the userdb_ prefix, except if you are using passwd-file.
>>
> I'm trying this. In the ldap configuration, I hav
As soon as I ask...
The field must be used as %{userdb:uuid}.
El 27/09/18 a las 12:30, Ángel L. Mateo escribió:
El 27/09/18 a las 12:04, Aki Tuomi escribió:
You can. In passdb, return userdb_your_own_variable=value, in userdb you
can omit the userdb_ prefix, except if you are
El 27/09/18 a las 12:04, Aki Tuomi escribió:
You can. In passdb, return userdb_your_own_variable=value, in userdb you
can omit the userdb_ prefix, except if you are using passwd-file.
I'm trying this. In the ldap configuration, I have:
pass_attrs =
=userdb_user=%{ldap:mail},=userdb_q
El 27/09/18 a las 12:04, Aki Tuomi escribió:
On 27.09.2018 13:01, Ángel L. Mateo wrote:
Hi,
I know that there are some variables (as user or username) I could
use inside dovecot. They are at https://wiki2.dovecot.org/Variables.
My question is if I can create my own variables from a
On 27.09.2018 13:01, Ángel L. Mateo wrote:
> Hi,
>
> I know that there are some variables (as user or username) I could
> use inside dovecot. They are at https://wiki2.dovecot.org/Variables.
>
> My question is if I can create my own variables from attributes at
> my pass/user db and then
Hi,
I know that there are some variables (as user or username) I could use
inside dovecot. They are at https://wiki2.dovecot.org/Variables.
My question is if I can create my own variables from attributes at my
pass/user db and then use it inside dovecot configuration.
--
Angel L. Mateo Ma
On 25/09/2018 22:39, Stephan Bosch wrote:
Something mightily weird is going on at your end. It doesn't fail here
(see below). First of all, what is your configuration (output from
`dovecot -n`)?
You have dovecot.conf but...
$ dovecot -c dovecot.conf -n
# 2.3.3.rc1 (14e4920d8): dovecot.conf
#
On 27.09.2018 10:45, Stanislav Humplík wrote:
> Hello,
>
> currently there is very handy post-login scripting already implemented
> but it naturally executes only when successful login happens. I would
> like to have another two script callbacks which runs:
>
> 1. immediately after client connec
Hello,
currently there is very handy post-login scripting already implemented
but it naturally executes only when successful login happens. I would
like to have another two script callbacks which runs:
1. immediately after client connects to server - dovecot should run
script with connection
31 matches
Mail list logo