is there a plugin or anyway I can modifie any email content ?
I would like to change body text, headers, attachments
I know it is forbidden by protocol, but anyway ?
Hello there,
is there a way to make the mailcrypt plugin use the user's password or at least
store it in a hashed value?
I'm using a passwd file for authentication.
I feel uncomfortable saving the private password in plaintext in that file.
Regards
> On 3 Sep 2019, at 19.08, R.N.S. via dovecot wrote:
>
> I tried this, but I have done something wrong probably.
>
> I added this to 20-imap 20-pop 20-managesieve and 20-submission. Always in
> the protocol sections. I also disabled the passdb section from the
> auth-ldap.conf.ext in
On 4.9.2019 8.48, Benny Pedersen via dovecot wrote:
> Matthew Brown via dovecot skrev den 2019-09-04 07:12:
>> is there a plugin or anyway I can modifie any email content ?
>
> not apricated to do
>
>> I would like to change body text, headers, attachments
>
> use roundcube
>
> i already hate
On 4.9.2019 9.21, Dustin Schoenwolf via dovecot wrote:
> Hello there,
>
> is there a way to make the mailcrypt plugin use the user's password or
> at least store it in a hashed value?
>
> I'm using a passwd file for authentication.
>
> I feel uncomfortable saving the private password in plaintext
Do I have to replace the "password" part with the actual password or can I just
copy it like that?
Will dovecot create the keypair automatically or do I have to use doveadm?
4. Sep. 2019, 08:33 von aki.tu...@open-xchange.com:
>
>
>
> On 4.9.2019 9.21, Dustin Schoenwolf via dovecot wrote:
It should pick up the password used by the user, there is a caveat here
though. The keypair is created on first use, so password will be
initialized to empty string going thru pkcs5. This is slightly inconvenient.
To avoid this, you should probably have
protocol imap {
passdb {
Is any of the password schemes supported or is there a reason you chose pkcs5?
4. Sep. 2019, 08:45 von aki.tu...@open-xchange.com:
>
> It should pick up the password used by the user, there is a caveat here
> though. The keypair is created on first use, so password will be
>
PKCS5 is a password based key derivation function. The linked
documentation has information what you can use here.
Aki
On 4.9.2019 10.06, i...@unkn0wn3d.com wrote:
> Is any of the password schemes supported or is there a reason you
> chose pkcs5?
>
>
>
> 4. Sep. 2019, 08:45 von
> Am 04.09.2019 um 16:58 schrieb Sami Ketola via dovecot :
>
>
>
>> On 4 Sep 2019, at 16.38, R.N.S. via dovecot wrote:
>>>
>>> passdb {
>>> args = /etc/dovecot/master-users
>>> driver = passwd-file
>>> master = yes
>>> pass = yes
>>> }
>>> passdb {
>>> args =
> Am 03.09.2019 um 10:01 schrieb R.N.S. via dovecot :
>
> Hi,
>
> Can global ACLs for public folders be stored in SQL or LDAP instead of a
> dovecot-acl file?
>
> I could only find something for shared folders, but not for public folders?
Is there somebody who does have some ideas?
Thanks
> Le 4 sept. 2019 à 19:37, Roger Klorese via dovecot a
> écrit :
>
>
>
> On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot
> mailto:dovecot@dovecot.org>>
> Further investigation showed me that it has to be a bug.
>
> I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole
On 1 Sep 2019, at 15:53, Michael Hallager wrote:
> On 2019-09-02 06:24, Alexander Dalloz via dovecot wrote:
>> Am 01.09.2019 um 14:41 schrieb Aleksandr Mette via dovecot:
>>> 4. Forward e-mail
>> Don't do that nor let your users auto-forward their mail received on
>> your MX. Else you will end up
> On 4 Sep 2019, at 16.38, R.N.S. via dovecot wrote:
>>
>> passdb {
>> args = /etc/dovecot/master-users
>> driver = passwd-file
>> master = yes
>> pass = yes
>> }
>> passdb {
>> args = /etc/dovecot/dovecot-ldap.conf.ext
>> driver = ldap
>> }
>>
...
>> protocol sieve {
>> passdb {
>> args
On 04/09/2019 15:26, @lbutlr via dovecot wrote:
> A lot of mail that is not spam when it arrives WILL be spam when it is
> forwarded as it will fail SPF, Fail DKIM, and any header checks will flag the
> mail as suspicious.
>
> The only way to safely forward mail is to enclose it as an
Hi,
Have anyone else experienced problems using Dovecot with the mail app in beta
releases of iOS/iPadOS 13?
TLS is failing for my, it have worked fine for years and I am on the latest
Dovecot version now, it works fine with older clients but not with the ones
upgraded:
Sep 04 19:49:16
On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot <
dovecot@dovecot.org>
> Further investigation showed me that it has to be a bug.
>
> I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole version 0.4.24
> (5a7e9e62):
>
> In this version the additional addresses in vacation
> Am 04.09.2019 um 18:32 schrieb R.N.S. via dovecot :
>
>
>
>> Am 04.09.2019 um 16:58 schrieb Sami Ketola via dovecot :
>>
>>
>>
>>> On 4 Sep 2019, at 16.38, R.N.S. via dovecot wrote:
passdb {
args = /etc/dovecot/master-users
driver = passwd-file
master = yes
> Since local users open a security hole into your mail server, I would
argue that virtual users
Can you elaborate on that? I would argue exactly the oposite. Having
your virtual users in a
3rd party environment, adds only security exploits of that 3rd party
environment.
I guess most run
On 4 Sep 2019, at 07:26, @lbutlr wrote:
> with IMAP logging and local rules.
IMAP logins.
--
"640K ought to be enough RAM for anybody." - Bill Gates, 1981
On 3 Sep 2019, at 00:32, d.gent...@m4ever.de wrote:
> This is a question about the imap protocol, since I am having a hard time
> finding these things out, so I hope you guys can help me. We are using
> Dovecot to receive mails and having an issue with Thunderbird. ⌘
You and most everyone who
On 2 Sep 2019, at 02:08, Alexander Dalloz wrote:
> Unless you run a big install with lots of accounts where it can be handy to
> use some sort of meta tool (modoboa, postfixadmin, ...) there is zero need
> for an SQL backend.
It is much easier to manage users, even a few users, via a database
So... I've done some testing.
One method which seemed to work - at least for primitive cases - was to:
* Mount the ALT storage on the destination.
* Run "doveadm force-resync \*" on the destination.
(putting all the mails in ALT storage into the dovecot.map.index)
* Run dsync from source to
> Am 04.09.2019 um 08:24 schrieb Sami Ketola via dovecot :
>
>
>
>> On 3 Sep 2019, at 19.08, R.N.S. via dovecot wrote:
>>
>> I tried this, but I have done something wrong probably.
>>
>> I added this to 20-imap 20-pop 20-managesieve and 20-submission. Always in
>> the protocol sections.
> Am 04.09.2019 um 15:31 schrieb R.N.S. via dovecot :
>
>
>
>> Am 04.09.2019 um 08:24 schrieb Sami Ketola via dovecot :
>>
>>
>>
>>> On 3 Sep 2019, at 19.08, R.N.S. via dovecot wrote:
>>>
>>> I tried this, but I have done something wrong probably.
>>>
>>> I added this to 20-imap 20-pop
Am 02.09.19 um 15:05 schrieb Philipp Faeustlin via dovecot:
The recipients in the vacation :addresses String list are matched
case-sensitive.
If the recipient gets a mail with wrong case, the message is discarded
with:
"discarding vacation response for implicitly delivered message; no known
> Le 4 sept. 2019 à 20:11, Henrik Johansson via dovecot a
> écrit :
>
> Hi,
>
> Have anyone else experienced problems using Dovecot with the mail app in beta
> releases of iOS/iPadOS 13?
>
> TLS is failing for my, it have worked fine for years and I am on the latest
> Dovecot version now,
>
> It is not recommended to rely on local-part case, but it is indeed
> case-sensitive.
>
> And this is to avoid such issues that postfix supports address
> cleanup/canonicalisation before forwarding mails to dovecot.
>
> --
> RFC 5321:
>
> "Local-part = Dot-string / Quoted-string ;
> On 4 Sep 2019, at 21:35, Jean-Daniel wrote:
>
> Just a wild guess as I didn’t try to configure Mail on Catalina yet, but it
> looks like your server only supports ‘DHE-RSA…’ ciphers.
> I think that modern systems prefers using ECDHE key exchange and would not be
> surprise if iOS requires
On 5.9.2019 5.29, Michael Fincham via dovecot wrote:
> Hi Dovecot folks,
>
> I recently reported this bug in Debian
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939442) after a stretch ->
> buster upgrade, however since I can reproduce it using the latest 2.4 from
> git I thought
Hi Dovecot folks,
I recently reported this bug in Debian
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939442) after a stretch ->
buster upgrade, however since I can reproduce it using the latest 2.4 from git
I thought perhaps I ought to take it straight upstream.
Here's the text I
> Le 4 sept. 2019 à 21:35, Jean-Daniel via dovecot a
> écrit :
>
>>
>> Le 4 sept. 2019 à 20:11, Henrik Johansson via dovecot
>> a écrit :
>>
>> Hi,
>>
>> Have anyone else experienced problems using Dovecot with the mail app in
>> beta releases of iOS/iPadOS 13?
>>
>> TLS is failing for
32 matches
Mail list logo
