Dear exim & dovecot users,
posting on both mailing lists as I am not sure who has the ultimate
responsability for this field.
I am trying to set up a mail server for multiple domains in my VPS. So I
managed to set up the authentication through a dovecot authenticator,
which relies to a sqlit
On 08/22/2016 02:00 PM, Aki Tuomi wrote:
Seems you accidentically replied to me only.
Yup, whoops.
Postfix uses the filename you provide as name for the db file, so
running it against symlinks does follow the symlink, but it uses the
symlink name as what it uses to create the .db file.
You
"Scott W. Sander" writes:
Received: from mail.domain.test
by appserver4.domain.com (Dovecot) with LMTP id z7RGLzH4uldlPAAAxdv4Dw
for ; Mon, 22 Aug 2016 09:03:45 -0400
---
I want the part that says "by appserver4.domain.com (Dovecot)" to say "by
mail.domain.test (Dovecot)". I don't wa
+1
I opened a ticket (a while ago) to add manual selection of the curves.
On Mon, Aug 22, 2016 at 6:59 PM, Aki Tuomi <'aki.tu...@dovecot.fi'> wrote:
On 22.08.2016 16:21, İhsan Doğan wrote:
> Hi,
>
> I've noticed that Dovecot is using per default the elliptic curve
> sect571r1. Because not all cl
On 22.08.2016 21:53, Michael Starks wrote:
On 08/22/2016 01:29 AM, Aki Tuomi wrote:
It seems your postfix is misbehaving. Did you forget to run postmap?
Aki Tuomi
Dovecot oy
Thanks for the response, Aki. I dug a little deeper and found this:
lrwxrwxrwx. 1 root root20 Jul 24 01:37 virtua
Hi Andreas,
On 19/08/2016 10:11 PM, Andreas Meyer wrote:
> Hello!
>
> Certificates from letsencrypt are renewed every three months.
>
> Does that mean a MUA has to accept the renewed certificates manually
> everytime it is renewed?
No, if the certificate is not a self-signed one, and if the MUA
> I noticed you are using mbox format. Maybe the mbox file itself is
> corrupted. The command you were supposed to run, by the way, was
Possibly. Though I guess that should bring the bug along to the copy of
a mbox?
> doveadm index -u username INBOX
Yes, that's what I was running, I just mistyp
On 22.08.2016 16:50, Ladislav Laska wrote:
Well, good news and bad news.
I backed up the indexes (presumably the ~/.mbox/.imap/*) and started
tinkering:
dovecotadm -u username INBOX
did nothing, it didn't event produce a message in the log, and the
indexes were not updated. I deleted the ind
On 22.08.2016 16:21, İhsan Doğan wrote:
Hi,
I've noticed that Dovecot is using per default the elliptic curve
sect571r1. Because not all clients might support sect571r1, I would like
to set the elliptic curve manually. Is that possible?
-Ihsan
Hi!
If your openssl does not support automa
On 19/08/16 17:35, b...@indietorrent.org wrote:
So, I'm back to where I was with this problem two years ago.
Maybe this will help you.
I've been using antispam plugin in the same way you intend to do it for
years now. (script modification date Feb 2014).
All the Maildirs on my system are und
Removing the headers entirely was discussed:
http://dovecot.markmail.org/search/?q=received#query:received+page:1+mid:t4utsjcionjcfwce+state:results
Don't know if it was forgotten for 2.3, but hope not :)
---
Tom
On 2016-08-22 15:14, Scott W. Sander wrote:
Here are some example headers from an
On 2016-08-22 13:21, Peter Mogensen wrote:
===
protocol lda {
# passdb {
#driver = static
# }
userdb {
args = /etc/dovecot/dovecot-dict-auth.conf.ext
driver = dict
result_success = continue-ok
result_
Well, good news and bad news.
I backed up the indexes (presumably the ~/.mbox/.imap/*) and started
tinkering:
dovecotadm -u username INBOX
did nothing, it didn't event produce a message in the log, and the
indexes were not updated. I deleted the indexes, and let dovecot rebuild
them. This fixed
Hi,
I've noticed that Dovecot is using per default the elliptic curve
sect571r1. Because not all clients might support sect571r1, I would like
to set the elliptic curve manually. Is that possible?
-Ihsan
--
ih...@dogan.chhttp://blog.dogan.ch/
On 22.08.2016 15:10, Ladislav Laska wrote:
> Not really. I tried copying the inbox and wanted to delete half the
> messages to filter out the problematic one, but opening the copy works
> fine.
>
> What could be the culprit? Does dovecot keep some index that might be
> corrupted?
>
> On Mon, Aug
Here are some example headers from an email sent from an internal Exchange
account to an account on Dovecot (u...@domain.test):
---
Received: from mail.domain.test
by appserver4.domain.com (Dovecot) with LMTP id z7RGLzH4uldlPAAAxdv4Dw
for ; Mon, 22 Aug 2016 09:03:45 -0400
Received: fr
Hi there,
Quoting RFC 3501 sec. 7.4.2 “FETCH Response” (data item BODYSTRUCTURE):
“A body type of type MESSAGE and subtype RFC822 contains,
immediately after the basic fields, the envelope structure, body
structure, and size in text lines of the encapsulated message.”
According the
Not really. I tried copying the inbox and wanted to delete half the
messages to filter out the problematic one, but opening the copy works
fine.
What could be the culprit? Does dovecot keep some index that might be
corrupted?
On Mon, Aug 22, 2016 at 02:43:01PM +0300, Aki Tuomi wrote:
> On 21.08.2
On 21.08.2016 13:59, Ladislav Laska wrote:
> Hi!
>
> dovecot -n and backtrace are both attached in my original email, due to their
> size. Did the attachments not arrive?
>
> The relevant log does not contain much more than the trace, but here it is:
>
Any chance to get the offending email someho
Sorry... I meant LDA - not LMTP.
More specifically ... the delivery happening during an LMTP session.
I'm trying something like this:
===
protocol !lda {
passdb {
driver = passwd-file
args = /etc/dovecot/accounts
}
Hi,
I can see dovecot is doing a passdb query when handling the LMTP RCPT
command.
That's kinda unexpected for me. I would have thought it only did a
userdb lookup.
I have disabled lmtp_proxy to be sure it didn't do a passdb lookup to
check the proxy field.
Is this expected? Doesn't the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 19 Aug 2016, b...@indietorrent.org wrote:
On 2016-08-19 12:17, b...@indietorrent.org wrote:
Aha! Clearly, the vmail user cannot read from nor write to /tmp. (Why
that is, I have no idea, as the /tmp directory's permissions certainly
Do you
22 matches
Mail list logo
