> I have rebuilt the entire project from scratch, using vanilla versions
> of Dovecot, Postfix, SOGO webmail etc and everything works as expected:
Hi, just wondering where do you find the vanilla version of only SOGO webmail?
I thought SOGO webmail was distributed as a whole server package...
‐‐‐ Original Message ‐‐‐
On Thursday, March 19, 2020 9:13 AM, Aki Tuomi
wrote:
> This is usually prevented by not configuring mail_home and mail_location to
> same directory:
>
> mail_home=/var/vmail/%Ld/%Lu/
> mail_location=maildir:~/mail
Thanks for the tip.
This means that if I now
iphone I see these "mail" folders but they are not really mail folders...
With Thunderbird as mail client it looks all good and I don't get this error.
Is this normal? if not, how can I prevent this issue?
Regards,
Mabi
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 3:57 PM, Sami Ketola wrote:
> Since you were migrating dovecot->dovecot I would have just used Dsync.
Thanks for the hint about dsync. It seems quite complex to setup and to use.
Isn't there an easier method? What about tar'ing the fil
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 3:26 PM, Sami Ketola wrote:
> So your rsync did not preserve mail object ctimes. Dovecot uses that for
> internal date if correct value is not in dovecot.index.cache.
Oh I see, so that's quite unfortunate that rsync does not preserve t
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 2:18 PM, Aki Tuomi
wrote:
> So doveadm fetch -u admin\\@domain.tld "mailbox date.saved" UID 130863
>
> Aki
This is the ouput:
mailbox: INBOX
date.saved: 2020-01-16 18:21:53
I think that might be the date where I have done the migrati
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 2:00 PM, Aki Tuomi
wrote:
> `sudo doveadm search -u admin\\@domain.tld HEADER MESSAGE-ID
> "sawh8n6hdrb...@mgw.subdom.domain.tld"`
Ah yes, I had to remove the "user" part of course... Thanks!
After running this command, the only outp
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 1:38 PM, Aki Tuomi
wrote:
> If you have message-id you can use
>
> `doveadm search -u user HEADER MESSAGE-ID "messageid"` to find out the UID.
I tried the following command:
sudo doveadm search -u user admin\@domain.tld HEADER MESSAGE
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 1:19 PM, Aki Tuomi
wrote:
> Can you try`doveadm fetch -u user date.saved UID mail-uid` To see if it
> matches this?
How can I find out the "mail-uid" of this specific message? Is that the
"Message-ID" header of that particular mail?
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 1:10 PM, mabi wrote:
> I have been using "rsync -av". As far as I know the "-a or --archive"
> parameter should preserve almost everything, at least the rsync man page says
> that.
If that is of any help
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 1:05 PM, Aki Tuomi
wrote:
> Did you add sufficient flags to rsync to retain file mtime and ctime? These
> are used to determine the mail saved date.
>
> Aki
I have been using "rsync -av". As far as I know the "-a or --archive" paramet
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 12:45 PM, Aki Tuomi
wrote:
> `doveadm search -u username@domain.com mailbox INBOX savedbefore 90`
>
> return any mails?
No it does not return any mails, although there are mails older than 90 days in
the INBOX.
> How did you do
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 11:46 AM, Aki Tuomi
wrote:
> Try`doveadm -Dv expunge -u username\\@domain.com mailbox INBOX savedbefore 90`
>
> It might give insight what goes wrong.
Here would be the output but I still can't see where the problem is:
Debug: Loading
savedbefore 90d
Unfortunately this does not work anymore. I also tried to run the command
manually as root which does not return any output or errors.
Any idea why this command does not work anymore?
Regards,
Mabi
o explicitly define again my postmaster_address parameter inside
protocol lmtp{} like this?
protocol lmtp {
postmaster_address = postmas...@mydomain.com
}
My very same question applies also for protocol lda {}...
Regards,
Mabi
‐‐‐ Original Message ‐‐‐
On Tuesday, January 28, 2020 10:17 AM, mabi wrote:
> > Your separator seems to be . instead of / so maybe inbox.*
>
> Thanks, that was it! Now let's see if I still get this panic...
Unfortunately even after a successful force-resync of all ma
‐‐‐ Original Message ‐‐‐
On Tuesday, January 28, 2020 10:12 AM, Sami Ketola
wrote:
> Your separator seems to be . instead of / so maybe inbox.*
Thanks, that was it! Now let's see if I still get this panic...
‐‐‐ Original Message ‐‐‐
On Tuesday, January 28, 2020 9:06 AM, Sami Ketola
wrote:
> doveadm does not travel over namespace boundaries. you need to run it
> separately for all namespaces you have with NAMESPACE/* as folder
I see, so with my following namespace config:
namespace inbox {
xes?
After the command I saw that the following file has been modified:
"Maildir/dovecot.index.log", that should be the case, right?
Best regards,
Mabi
race from core file it's hard to say.
>
> Aki
>
> On 27.1.2020 9.05, mabi wrote:
>
> > Hello,
> > Does anyone one have any idea? Aki maybe?
> > Regards,
> > Mabi
> > ‐‐‐ Original Message ‐‐‐
> > On Wednesday, January 22, 2020 11:37 AM, ma
Hello,
Does anyone one have any idea? Aki maybe?
Regards,
Mabi
‐‐‐ Original Message ‐‐‐
On Wednesday, January 22, 2020 11:37 AM, mabi wrote:
> Hello,
>
> Are there any chances that I could fix this issue by running a "doveadm
> force-rsync" (https://wiki2.dov
Hello,
Are there any chances that I could fix this issue by running a "doveadm
force-rsync" (https://wiki2.dovecot.org/Tools/Doveadm/ForceResync) on this
problematic mailbox?
Best regards,
Mabi
‐‐‐ Original Message ‐‐‐
On Tuesday, January 21, 2020 9:53 AM, mabi wrote:
>
Fatal:
imap(EMAIL_ADDRESS)<7741>: master:
service(imap): child 7741 killed with signal 6 (core dumps disabled -
https://dovecot.org/bugreport.html#coredumps)
Does anyone have any idea what could be going wrong here?
Maybe I need to run some kind of conversion or re-generate some indexes?
Best regards,
Mabi
‐‐‐ Original Message ‐‐‐
On Thursday, July 4, 2019 3:10 PM, Aki Tuomi wrote:
> > I am also not sure about sha512 hash because the Dovecot Variable wiki page
> > does not mention sha512 but only sha256. Is sha512 also available?
>
> Yes
Thank you Aki for confirming. I tried it out and it
‐‐‐ Original Message ‐‐‐
On Thursday, July 4, 2019 11:18 AM, Aki Tuomi via dovecot
wrote:
> It depends. You can use either one, seehttps://wiki2.dovecot.org/Variables
>
> I think the safest option would be setup LDAP so that the private
> password would be only readable by self, and have
‐‐‐ Original Message ‐‐‐
On Thursday, July 4, 2019 11:17 AM, @lbutlr via dovecot
wrote:
> > Is it possible to delete the inactive keypair? if yes how?
>
> Wouldn’t you then be unable to *unencrypt* previous emails?
That's also what I thought but based on my understand and on the documen
‐‐‐ Original Message ‐‐‐
On Tuesday, July 2, 2019 6:21 PM, Aki Tuomi wrote:
> Hi, you need to escape % with %%. We are aware of a bug affecting when %
> comes in from some field via userdb, and we are looking into how to fix this.
Aki, I was wondering, does this bug also affect the chan
used to encrypt new emails?
Is it possible to delete the inactive keypair? if yes how?
Regards,
Mabi
‐‐‐ Original Message ‐‐‐
On Tuesday, July 2, 2019 6:32 PM, Aki Tuomi via dovecot
wrote:
> I don't actually recommend using password directly from user as password for
> private keys, I recommend running them thru some hash / pkcs5 before that.
That's a great idea and makes things even
‐‐‐ Original Message ‐‐‐
On Tuesday, July 2, 2019 6:50 PM, Aki Tuomi via dovecot
wrote:
> Please reviewhttps://wiki.dovecot.org/NFS if you have not already done so.
I actually already went through this guide once but noticed now that I had the
mail_fsync parameter set to "optimized", s
‐‐‐ Original Message ‐‐‐
On Tuesday, July 2, 2019 6:39 PM, Aki Tuomi wrote:
> Are you by chance accessing mails using two different dovecot instances? This
> is not supported to be done concurrently, you need to use some sort of
> solution, such as dovecot director, to ensure user lands
‐‐‐ Original Message ‐‐‐
On Tuesday, July 2, 2019 6:21 PM, Aki Tuomi wrote:
> Hi, you need to escape % with %%. We are aware of a bug affecting when %
> comes in from some field via userdb, and we are looking into how to fix this.
Hi Aki,
Thank you very much for your very fast answer
rate -u em...@domain.tld -URf
doveadm(em...@domain.tld): Error: Failed to expand plugin setting
mail_crypt_private_password = 'SomethingWith%Percent': Unknown variable '%P'
Note here that the percent is escaped with a backslash "\%" in order for the
shell not to process it.
Regards,
Mabi
ng a Linux NFS server to store all the
mails mounted under /var/mail ?
Any hints what I can do to avoid these error messages?
Thank you in advance.
Best regards,
Mabi
‐‐‐ Original Message ‐‐‐
On Wednesday, May 29, 2019 8:01 AM, Aki Tuomi
wrote:
> We'll take this under consideration, but no promises.
Thank you very much Aki for consdering this. It would be really fair for all
the PostgreSQL users out there.
‐‐‐ Original Message ‐‐‐
On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot
wrote:
> there's no field name that is obviously the primary key. I've reworked the
> patch to use the postgres default primary key constraint name
> (tablename_pkey).
>
> The attached fix should work i
‐‐‐ Original Message ‐‐‐
On Saturday, May 25, 2019 12:18 AM, Sami Ketola via dovecot
wrote:
> just add:
>
> protocol lmtp {
> login_trusted_networks=
> }
Thank you so much Sami for the further details. I added the
login_trusted_networks specifically to the lmtp protocol and now I can s
‐‐‐ Original Message ‐‐‐
On Friday, May 24, 2019 11:23 AM, Aki Tuomi wrote:
> There is no maintainer for this package in OpenBSD?
Not really, well AFAIK packages for OpenBSD are updated every 6 months with the
new release of OpenBSD which is always around May and November. Exceptions ar
‐‐‐ Original Message ‐‐‐
On Friday, May 24, 2019 10:40 AM, Aki Tuomi via dovecot
wrote:
> Try setting login_trusted_networks=
Thank you Aki for your answer. Unfortunately on my Dovecot mailbox backend
servers I already have login_trusted_networks set to the IP of my Dovecot LMTP
proxy
be that Dovecot bug.
Cheers,
Mabi
‐‐‐ Original Message ‐‐‐
On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot
wrote:
> So looking into this with a postgresql databse to work with: the above query
> does not work. You have to specify either the column name or the constraint
> name that you expect to be violated
‐‐‐ Original Message ‐‐‐
On Sunday, May 19, 2019 10:45 PM, John Fawcett via dovecot
wrote:
> so basically if this works just as well:
>
> INSERT INTO last_logins (last_login,username,domain) VALUES
> (1558273000,'u...@domain.tld','domain.tld') ON CONFLICT DO UPDATE SET
> last_login=155
‐‐‐ Original Message ‐‐‐
On Sunday, May 19, 2019 7:36 PM, John Fawcett via dovecot
wrote:
> Attached is a tentative patch. I've verified no regression for mysql. There
> should be no regression for sqlite as the code path is identical.
>
> Are you able to test for pgsql? As mentioned by
‐‐‐ Original Message ‐‐‐
On Sunday, May 19, 2019 4:44 PM, John Fawcett via dovecot
wrote:
> I don't have PostgresSql, would you be able to verify if this syntax would
> work: INSERT INTO last_logins (last_login,username,domain) VALUES
> (1558273000,'u...@domain.tld','domain.tld') ON CO
‐‐‐ Original Message ‐‐‐
On Sunday, May 19, 2019 3:57 PM, Aki Tuomi wrote:
> It would be a feature request, also note that it's only available since
> version 9.5, so it really won't help anyone before that.
Would opening an issue as feature request on GitHub on the dovecot/core project
makes Dovecot's dictionary feature useless with PostgreSQL. Should
I open a bug for that? or is it more of a "feature request"?
Regards,
Mabi
xisting record in the table. Or am I missing something? or it does not work
with PostgreSQL? Which does not make much sense to me...
Regards,
Mabi
47 matches
Mail list logo
