===
From: Steve Hadachek via dovecot
Sent: Thursday, April 11, 2024 10:03:22 AM
To: dovecot@dovecot.org
Subject: Message Age Deletion Query
Hello. Using Mochahost and want to delete mailbox items older than 1 month
(approx) from receipt . Reading
Hello. Using Mochahost and want to delete mailbox items older than 1 month
(approx) from receipt . Reading DoveCot documentation, not finding age query.
Can you please specify this for me and provide an example?
Thank you and Kind Regards,
-Steve Hadachek
Hello,
I am hoping that you can help me.
I am running this command on my main email server, one way backup/sync to the
backup server.
sudo doveadm sync -1 -A remote:root@x.x.x.x
x.x.x.x is my remote server.
I will add a new email on the main, run the command and it shows up on the
backup. -
it wasn’t isolated to a
single network.
> On Jan 22, 2024, at 6:15 PM, Michael Grant wrote:
>
> On Mon, Jan 22, 2024 at 04:28:09PM -0500, Steve Dondley via dovecot wrote:
>> OK, I was chasing log ghosts. What was actually going on was fail2ban was
>> kicking on for users an
problem.
On Jan 22, 2024, at 10:41 AM, Steve Dondley via dovecot
wrote:
Based on your email I went back and took a closer took at the logs.
The client reported this happened at 11:58 of the 19th. I went back
and took a
closer look and around 11:56 I found
ce of the error some users have been seeing, not the
errors I originally posted here to the mailing list.
On Jan 21, 2024, at 8:34 PM, Benny Pedersen wrote:
Steve Dondley via dovecot skrev den 2024-01-22 02:18:
I have a mail server using dovecot that has been running
> there is no user in the above line
>
>> Some characteristics of the problem that may offer a clue:
>> * happening with multiple users, not just the same one
>> * happens from different IP addresses.
>
> bots detected
The problem is happening to real users on real devices who are reporting
I have a mail server using dovecot that has been running without issue for
quite a couple of years now. It serves email for about 30 individuals.
But since Jan 14th, users have been reporting spurious errors in MS Outlook:
316 Jan 21 00:38:12 ip-172-30-0-131 dovecot: pop3-login: Disconnected
Hi,
I have recently moved a dovecot installation from 2.2.36 on RHEL7.9 onto 2.3.20
on Amazon Linux 2023 and I'm now seeing the error message in the title relating
to /usr/bin/checkpassword (which doesn't exist on either). This is a project
that I've inherited, and I've never used dovecot
emote server, as long as your data is encrypted.
Now if your vendor does what so many vendors do, and screws up, you're
still the master of your own data.
SteveT
Steve Litt
Autumn 2023 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
__
Bernardo Reino said on Sun, 19 Nov 2023 09:04:15 +0100 (CET)
>On Sun, 19 Nov 2023, Steve Litt wrote:
>
>> Michael Orlitzky said on Sat, 18 Nov 2023 17:31:49 -0500
>>
>>> On Sat, 2023-11-18 at 16:54 -0500, Steve Litt wrote:
>>>>
>>>> I forgo
Bernardo Reino said on Sun, 19 Nov 2023 09:04:15 +0100 (CET)
>On Sun, 19 Nov 2023, Steve Litt wrote:
>
>> Michael Orlitzky said on Sat, 18 Nov 2023 17:31:49 -0500
>>
>>> On Sat, 2023-11-18 at 16:54 -0500, Steve Litt wrote:
>>>>
>>>> I forgo
Michael Orlitzky said on Sat, 18 Nov 2023 17:31:49 -0500
>On Sat, 2023-11-18 at 16:54 -0500, Steve Litt wrote:
>>
>> I forgot to say: I'm using Dovecot 2.3.21 on an up to date 64 bit
>> x86_64 Void Linux computer using runit for its init system. I
>> populate Dove
Steve Litt said on Sat, 18 Nov 2023 16:42:42 -0500
>Hi all,
>
>Ten years after the fact I learned about POODLE (Padding Oracle On
>Downgraded Legacy Encryption) vulnerabilities, which enable a poorly
>configured server to force my client to downgrade to vulnerable
>encrypt
Hi all,
Ten years after the fact I learned about POODLE (Padding Oracle On
Downgraded Legacy Encryption) vulnerabilities, which enable a poorly
configured server to force my client to downgrade to vulnerable
encryption.
My current conf.d/10-ssl.conf contains the following line:
ssl_cipher_list
Hello,
I'm working on an implementation of a dict server. I've looked through
all your documentation but can't seem to find how I can create the
proper URI to direct the quota plugin to use a TCP socket instead of a
UNIX socket. I'd appreciate any insight you can provide.
Steve
to me like nothing there applies
to my Dovecot setup. I'll be checking it from time to time.
Thanks,
SteveT
Steve Litt
Summer 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm
arts
>that have a replacement in elsewhere of the code.
Is there a document on the deprecations and their replacements? I'd
like to read it.
>
>The mail server functionality is going to remain 100% open source and
>free.
The preceding sentence is a huge relief for me. Thanks!
SteveT
Steve Litt
t/core/tree/release-2.3
>
>> - For how long will Dovecot version 2.3 still be supported (security
>> fixes, bug fixes)? Is there any EOL plan?
>
>This will be informed later, but as general rule, once we make a new
>major release, 2.3 will go into maintenance
On Tue, 2022-10-18 at 16:48 +0200, Bernardo Reino wrote:
> On 18/10/2022 12:17, Michael wrote:
> >
> > [...]
> > so, raid is mandatory, which is already the case, but what about backup?
> > how can i achieve a backup/snapshot of both, the mdbox (nfs share) and
> > the index files (local raid)
On Sat, 2022-08-13 at 18:36 +0200, lutz.niede...@gmx.net wrote:
>
> The real problem is that we must not use the running, old dovecot
> installation.
> So we are not able to connect to the old server, pull all folders and mails
> and
> create a new maildir structure. Currently, we can't do
key=str.lower):
print("{}: {} unread.".format(key, newboxes[key]))
if __name__ == '__main__':
main()
===
My 20 minutes of testing indicate this is not always accurate and must
not be relied on without backup methods, but I'm going to be using it
until I find something better.
Thanks,
Steve
On Tue, 2022-07-19 at 16:33 +1200, Peter wrote:
> On 19/07/22 3:18 pm, Steve Litt wrote:
> > Is there any way I could use
> > doveadm or other tools to create a report that shows all my folders
> > in a
> > hierarchy?
>
> See doveadm(1) and doveadm-mailbox(1), sp
On Tue, 2022-07-19 at 09:19 +0300, Aki Tuomi wrote:
>
> > On 19/07/2022 06:18 EEST Steve Litt
> > wrote:
> >
> >
> > Hi all,
> >
> > I use a Dovecot IMAP server on my Linux desktop computer, and I'm
> > pretty good at writing shellscripts
uot;. So I'm not sure what "free into the new folder" means.
> but I do not know what config you have check tre
>command and see if that does some of what you want.
Thanks,
SteveT
>
>> Il giorno 18 lug 2022, alle ore 20:20, Steve Litt
>> ha scritto:
>>
>&
Steve Litt
Summer 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm
there are one or more
Dovecot provided tools to do this kind of admin. What are the names of
those tools?
Thanks,
SteveT
Steve Litt
Summer 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm
I have a small client whose insurance company insists they have MFA for their
email to be covered under some kind of data protection policy. Currently I have
the client set up on a Debian box for the email server coupled with roundcube
for webmail. Most the users just use roundcube but some
mail IMAP
will turn into pumpkins because of insistence on OAuth2. Do I need to
do anything to Dovecot to get ready for this Mass Extinction Event?
Do you think I'll need to dump fetchmail for something else?
Thanks,
SteveT
Steve Litt
March 2022 featured book: Making Mental Models: Advanced Edi
On 2021-09-17 08:13 AM, Steve Dondley wrote:
The bug I patched also threw a similar kind of error:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970692
I don't know if this is another debian issue or a misconfiguration on
my end. I'm not sure where to begin to look. Can someone please
The bug I patched also threw a similar kind of error:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970692
I don't know if this is another debian issue or a misconfiguration on
my end. I'm not sure where to begin to look. Can someone please point
me in the right direction?
I think
I'm running debian bullseye. I've had issues running solr on debian due
to some kind of bug I was able to patch by upgrading the os.
After the upgrade, everything seems to work perfectly fine and the
search feature in my client using solr now works. However, I get
hundreds of these pairs of
So share your solution! Just because you found a solution, doesn't
mean others won't run into the same problem... *hint* *hint*
My solution had nothing to do with dovecot. The solution involved
hacking the php code of an ancient cms so that your could reply directly
to the person who
On 2021-09-07 01:25 PM, Amol Kulkarni wrote:
Hello,
After I replaced my certificate with a new one yesterday, I'm seeing
some ssl related errors. There are successful pop/imap logins using SSL
also. So I think the certificate in itself is fine. No user has
complained as yet, so I don't know
Since most people will want fts_autoindex, the wiki page should
include it in its example configuration that goes into 90-plugin.conf.
Possibly better ... maybe it should default to "yes".
It's probably a safe bet the developers, who are experts on these
systems, probably have good reason
On 2021-09-03 12:43 PM, Shawn Heisey wrote:
I have Solr FTS on my dovecot install. I followed the instructions on
the dovecot wiki.
How long a delay should I expect to see between new mail being
delivered with the dovecot LDA and an indexing request sent to Solr?
Because I get a LOT of email
On 2021-09-04 05:50 PM, Marc wrote:
You do not want to do that because that can create loops.
Yeah, right after I posted this I did some more googling and someone
else was saying the same thing.
I found another way around the problem I was trying to solve, though. So
I'm good. Thanks for
I don't want dovecot to wait X days before sending out another vacation
response. However, setting the :days to "0" doesn't work.
RFC https://www.rfc-editor.org/rfc/rfc5230.html#section-4.1 says:
4.1. Days Parameter
The ":days" argument is used to specify the period in which addresses
On 2021-08-24 08:53 PM, Steve Dondley wrote:
MY SETUP: I have apache solr full text search enabled with dovecot. I
have an inbox with about 40 subfolders. I'm using the roundcube
web-based mail client. The find command is showing 15823 email files
and apache solr reports the same number. I'm
On 2021-08-25 04:32 PM, Shawn Heisey wrote:
On 8/25/2021 2:10 PM, Steve Dondley wrote:
And it looks like I'm running into a major bug in the slightly dated
version of dovecot debian uses:
https://www.mail-archive.com/dovecot@dovecot.org/msg78825.html
Recently I did a fairly major upgrade
I think this will be nailed once I figure out this issue.
And it looks like I'm running into a major bug in the slightly dated
version of dovecot debian uses:
https://www.mail-archive.com/dovecot@dovecot.org/msg78825.html
And this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970692
On 2021-08-25 04:05 PM, Steve Dondley wrote:
The search time was no better with it on than off.
So I'm thinking I got something misconfigured somewhere. It seems IMAP
may not be using solr to fetch results. But this would be odd since I
definitely do see a big improvements in times with fts
The search time was no better with it on than off.
So I'm thinking I got something misconfigured somewhere. It seems IMAP
may not be using solr to fetch results. But this would be odd since I
definitely do see a big improvements in times with fts plugins turned
on when using roundcube.
OK,
I'm inclined to believe the problem is not that high up the food
chain. Because when I query IMAP on a single folder over telnet
following the instructions found here:
https://doc.dovecot.org/configuration_manual/fts/solr/, imap reports
that it's taking 3 to 4 seconds to return results:
a
Random guess... Buffering?
Whatever is sending to the browser isn't sending enough bytes to flush
the buffer so the data is left in limbo until enough time goes by the
buffer gets flushed anyways. Maybe a apache/nginx thing, php thing or
browser thing. Remember its solr > dovecot > php > web
On 2021-08-25 02:05 PM, Steve Dondley wrote:
Try this in on the commandline of the Solr server:
time curl
"http://localhost:YYY/solr/dovecot/select?q=maynez=edismax=body+to+subject+cc+from;
OK I had to modify the query path slightly to get it to work with my
core to:
time curl
That query should search ALL emails that dovecot has indexed to Solr.
There is no restriction for mailbox or folder.
OK.
Try replacing "maynez" with something else that you know will be in the
index.
Did a search on "the". Still nothing. Very, very weird. What would
explain why my
Try this in on the commandline of the Solr server:
time curl
"http://localhost:YYY/solr/dovecot/select?q=maynez=edismax=body+to+subject+cc+from;
OK I had to modify the query path slightly to get it to work with my
core to:
time curl
This is a search for "a" which I had run several times, so Solr was
serving it from its cache, and this time it only took 6 milliseconds.
It also shows what a facet can do. The longest time I got for the "a"
search was 15 milliseconds, before the query was in the cache.
I think they
One other data point from my experimenting that might shed some light on
the problem:
If I limit a search to a single folder instead of across all folders, it
still takes 5 or 6 seconds for the results to appear. So that kind of
destroys my theory that the problem might be caused by having
THE PROBLEM: When I do a full text search through all my inbox and all
subfolders on a single word, search results are returned in about 10
to 15 seconds. This is better than the 40 seconds or so I'm getting
when I turn off the fts and fts_solr plugins but still a little
disappointing.
I did
MY SETUP: I have apache solr full text search enabled with dovecot. I
have an inbox with about 40 subfolders. I'm using the roundcube
web-based mail client. The find command is showing 15823 email files and
apache solr reports the same number. I'm running a dedicated mail server
with a 1 GB of
In 10-auth.conf, I have "disable_plaintext_auth = yes"
For port 143, I'd like to do something like this to override that
setting:
service imap-login {
inet_listener imap {
port = 143
disable_plain_text_auth = no
}
}
Based on https://wiki.dovecot.org/LoginProcess and
On 2021-04-29 09:40 AM, Steve Dondley wrote:
I am using Outlook without any problems what so ever.
It sounds to me like you are setting up Outlook to use port 465. In
the
setup screen, set the port to either "25" or "587". I am using "587"
with "starttls&quo
I am using Outlook without any problems what so ever.
It sounds to me like you are setting up Outlook to use port 465. In the
setup screen, set the port to either "25" or "587". I am using "587"
with "starttls" Your "incoming mail port" will depend on how you have
Dovecot configured. I use
On 2021-04-29 01:45 AM, @lbutlr wrote:
On 28 Apr 2021, at 12:49, Steve Dondley wrote:
I repeatedly have a hell of a time getting clients' Outlook software
working well with Dovecot. It's hard for me to test myself since I
don't have Outlook and it would be impossible to keep up with all
I think my problem might be here. Instead of %Ln, maybe I should have
%L%n?
Nope: https://wiki.dovecot.org/DomainLost
On 2021-04-28 02:49 PM, Steve Dondley wrote:
I repeatedly have a hell of a time getting clients' Outlook software
working well with Dovecot. It's hard for me to test myself since I
don't have Outlook and it would be impossible to keep up with all the
different versions anyway.
I've got
Your best bet to make Outlook behave better as an IMAP client is to
configure a mail "profile" via
Control Pannel --> User Accounts --> Mail, and set all the particulars
there. Recent versions of Outlook have a stripped down configuration
interface that offers no flexibility. For example, from
I repeatedly have a hell of a time getting clients' Outlook software
working well with Dovecot. It's hard for me to test myself since I don't
have Outlook and it would be impossible to keep up with all the
different versions anyway.
I've got the following settings, currently:
I'm looking at config documentation for solr on dovecot:
https://doc.dovecot.org/configuration_manual/fts/solr/
In the suggested solrconfig.xml file
(https://raw.githubusercontent.com/dovecot/core/master/doc/solr-config-7.7.0.xml),
it has the following line:
7.7.0
I'm running solr version
le,
because it's a very complicated, very ever-scope-expanding moving
target.
I don't even call the above described method as a workaround, because I
consider systemd the root cause.
SteveT
Steve Litt
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques
So where are you calling Spamassassin for each email? Hmm... maybe
you need to have -d ${recipient} in your spamassassin call?
Or better yet, call the 'deliver' program from dovecot like I showed
isntead.
spamass-dovecot_destination_recipient_limit = 1
virtual_alias_maps =
When I send an email to a single user on a server, it is received by the
user without a problem. But when sending to multiple users, the emails
disappear into a black hole. The logs contain no errors and indicate the
emails were sent:
Apr 5 13:10:29 email postfix/pipe[31703]: F3A912027D:
Ah, yes, it is there. I had a typo in my "find" command. Thanks!
On 2021-04-05 11:04 AM, Felix Zielcke wrote:
Am Montag, dem 05.04.2021 um 10:57 -0400 schrieb Steve Dondley:
I'm looking at the documentation at
https://doc.dovecot.org/settings/plugin/fts-plugin/#fts-decoder
It
I'm looking at the documentation at
https://doc.dovecot.org/settings/plugin/fts-plugin/#fts-decoder
It says "See the decode2text.sh script included in Dovecot for how to
use this."
I don't have this script installed and can't find it anywhere on my
Debian Buster server. I'm running dovecot
On 2021-04-05 07:49 AM, Steve Dondley wrote:
OK, I got solr working on a new virtual machine with a healthier 4 GB
of ram. Initially, I experienced the same slowness as before as on the
1 GB machine. I went back and reviewed the documentation at
https://wiki.dovecot.org/Plugins/FTS/Solr
I am brand new to solr and I'm interested in using sharing it between
several dovecot machines I'm running. I'm looking for some big picture
guidance on what I need to do to configure solr to work with the
different dovecot machines. So far, I managed to set up a single
"dovecot" core on the
configuring solr with the proper xml config files.
After doing this, the search time is well below one second now.
On 2021-04-05 06:12 AM, Steve Dondley wrote:
Does you server have enough ram?
I think this may be the issue. I only have 1 GB of ram on the machine
and I was just reading a blog post
Does you server have enough ram?
I think this may be the issue. I only have 1 GB of ram on the machine
and I was just reading a blog post recommending at least 4 GB. I think
what I'll do is set up a separate instance for solr and use that instead
of running it on the same machine as
I'm experimenting with Apache Solr and Dovecot. As far as I can tell, I
have dovecot working with Apache Solr as demonstrated by this output:
a search text "cash"
* SEARCH 4 8 26 35 45 52 54 55 63
a OK Search completed (0.356 + 0.001 + 0.068 secs).
However, when using the roundcube search bar
issing something obvious.
plugin {
imapsieve_url = sieve://127.0.0.1:4190
}
Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<47541>:
Debug: imapsieve: mailbox INBOX: Mailbox attribute /shared/imapsieve/script
not found
Mar 19 16:21:48 mhv3 dovecot[47532]: imap(steve)<
I googled around for a quite bit but surprisingly came up empty for an
answer to this question which I'm sure has been broached before.
I've got a linux box running dovecot/postfix using maildir format. I
was surprised to learn that a client that had many GBs of email was
running POP3, not IMAP.
.
By the way, when I do:
openssl s_client -connect 192.168.0.2:993 \
-cert/etc/ssl/dovecot_certs/private/dovecot.pem
openssl asks me for the passphrase and upon receiving it gives me the
information. This does not happen if I give it the location of the
public key.
Thanks,
SteveT
Steve Litt
-in tests.
Also, I continue to not be able to find where all the testing is turned on/off
at once? I'm sure it will be obvious when someone tells me but
please tell me, because I'm pulling my hair out.
Steve
This is the source RPM I'm using
https://repo.dovecot.org/ce-2.3.13/centos/8/SRPMS/2.3.13-2_ce/
Steve
>
>> On 08/01/2021 04:34 st...@keptprivate.com wrote:
>>
>>
>>
>> I tried to post this in a more nuanced way, but the fact is the latest
>>
This is the source RPM I'm using
https://repo.dovecot.org/ce-2.3.13/centos/8/SRPMS/2.3.13-2_ce/
Steve
>
>> On 08/01/2021 04:34 st...@keptprivate.com wrote:
>>
>>
>>
>> I tried to post this in a more nuanced way, but the fact is the latest
>>
, and it there).
It seems like some untested changes have crept into the source rpm build.
Steve
> Il 08/01/21 03:34, st...@keptprivate.com ha scritto:
>>
>> I tried to post this in a more nuanced way, but the fact is the latest
>> source RPM does not build on the latest Centos 8.
>>
>>
ed through the spec file and I don't really see where to turn that back on.
Sorry if any of this is stupid, but I'm new to building directly from the
dovecot repo.
Steve
Error seen - sorry for this!!
> On 6 Jan 2021, at 14:24, Steve Akerman wrote:
>
> Hi,
>
> Dovecot 2.3.13 builds successfully on this old OS X, but pigeonhole
> v0.5.13fails as below:
>
> gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include/dovecot-I../..
>
Hi,
Dovecot 2.3.13 builds successfully on this old OS X, but pigeonhole
v0.5.13fails as below:
gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include/dovecot-I../..
-I../../src/lib-managesieve -fPIE -DPIE -std=gnu99 -g -O2 -Wall -W
-Wmissing-prototypes -Wmissing-declarations
it in
order to help others in the future?
Thanks
Steve
> On 10 Dec 2020, at 14:58, Steve Akerman wrote:
>
> Good afternoon
>
> I have been using Dovecot with great success for several months now with one
> problem:
>
> I have received several messages (3 to date out
MIME
I have attached an extract from the log which shows the above sequence
Finally, I have kept one such message from the sendmail queue (df and qf)
should this be useful, but prefer not to post here as not sanitised
Any help in correcting my configuration would be appreciated.
Thanks
Steve
I have an operational need to disable TLSv1.3 due to inadequate support to
exclude certain ciphers.
There is no need to disable TLSv1.3 and attempts to do so will be flagged as
“downgrade attacks”.
Let us ignore TLSv1.2 as a downgrade option. And focus on TLSv1.3 for
its entirety of this
I cannot even reorder the server-side TLSv1.3 such that CHACHA20 has
first-order before AES.
https://github.com/openssl/openssl/issues/7562
Also, more testimony to the same problem (by others) is posted over at
ServerFault (StackOverflow):
https://serverfault.com/questions/975871/forcing-dovecot-2-3-4-1-to-use-tlsv1-2
On 5/8/20 11:50 AM, Steve Egbert wrote:
I have an operational need to disable TLSv1.3 due to inadequate support
have adjusted it to 3 (TLSv1.2) and it works when Dovecot is set to
TLSv1.2.
(Details of Thunderbird security.tls.version.fallback-limit is given in
http://kb.mozillazine.org/Security.tls.version.* )
Steve
have adjusted it to 3 (TLSv1.2) and it works when Dovecot is set to
TLSv1.2.
(Details of Thunderbird security.tls.version.fallback-limit is given in
http://kb.mozillazine.org/Security.tls.version.* )
Steve
On Wed, 18 Mar 2020 17:37:31 +0200 (EET)
Aki Tuomi wrote:
> One of the various mail clients I use sends HTML only mails in some
> situations.
So you're taking your problem and making it our problem?
SteveT
Steve Litt
March 2020 featured book: Troubleshooting: Why Bother
When attempting to perform autoupdate after my 'autogen.sh' broke, it
says that there is missing a file called:
dovecot/core/doc/wiki/Makefile.am
But in the Github repository, there is a misnamed file named
"Makefile.am.in".
I think this file is misnamed and should be renamed to
re-downloading all mail.
Steve Newcomb
s...@coolheads.com
(Unable to edit the wiki page... Mysterious question stood in the way, something like,
"How do you prevent spam?" Evidently I don't know the correct answer.
ellscript that subscribed
them one by one.
Thanks,
SteveT
Steve Litt
December 2019 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
not subscribed.
Thanks,
SteveT
Steve Litt
December 2019 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
That's already in conf.d/10-auth.conf.
On 10/24/2019 1:31 AM, Aki Tuomi via dovecot wrote:
On 24.10.2019 6.18, Steve Matzura via dovecot wrote:
Got all the Postfix errors fixed but maybe one, so I don't think
that's involved in this mix any more.
I had a domain definition problem, got
Got all the Postfix errors fixed but maybe one, so I don't think that's
involved in this mix any more.
I had a domain definition problem, got that sorted.
The accounts' logins are correct. I tried several from the shell, and
they let me in.
Here's the minus-n output, not very different
*** dovecot.conf ***
## Dovecot configuration file
# If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration
# "doveconf -n" command gives a clean output of the changed settings. Use it
# instead of copy files when posting to the Dovecot mailing list.
# '#' character and
It's really pretty empty; would you rather see some of the 10-*.conf files?
## Dovecot configuration file
# If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration
# "doveconf -n" command gives a clean output of the changed settings. Use it
# instead of copy files when posting
It was the three passdb blocks you sent me.
On 10/22/2019 4:43 AM, Aki Tuomi via dovecot wrote:
Can you show what you ended up pasting?
Aki
On 22.10.2019 11.34, Steve Matzura via dovecot wrote:
I pasted that block at the end of dovecot.conf, restarted, and got the
following in syslog:
Oct
exited, code=exited, status=89/n/a
Oct 22 08:24:32 tgvprod systemd[1]: dovecot.service: Failed with result
'exit-code'.
On 10/22/2019 4:00 AM, Aki Tuomi via dovecot wrote:
block quote
On 22.10.2019 10.33, Steve Matzura via dovecot wrote:
block quote
Sorry for having lost the original chain
:SMTPAUTH: with ESMTPSA
id MnpFiaSdxUnHgMnpFiYE6m; Mon, 21 Oct 2019 23:39:25 -0700
To:
r...@theglobalvoice.info
From: Steve Matzura
Subject: Testing again
Message-ID:
<61b4f0c2-89fa-c4de-8288-871a8708f...@noisynotes.com>
Date: Tue, 22 Oct 2019 02:39:26 -0400
User-Agent: Mozilla/5.0 (Wi
1 - 100 of 350 matches
Mail list logo
