Sieve daemon errors? (Part 1 of 2, Pt 2 to follow when Pt 1 resolved)
dovecot at steve.wattlink.net
dovecot at steve.wattlink.net
Sat May 1 23:05:51 EEST 2021
P.S. the .BAK file shows sieve present, but the line is still commented out.
--
Steve Watt KD6GGD PP-ASEL-IA factories.words.yappy
Don't let your schooling get in the way of your education.
From: Steve Watt <steve at watt.com>
Sent: Saturday, May 1, 2021 13:04
To: 'Dan Egli' <dan at newideatest.site>; 'dovecot at dovecot.org' <dovecot at dovecot.org>
Subject: RE: Sieve daemon errors? (Part 1 of 2, Pt 2 to follow when Pt 1 resolved)
For some reason, your 20-managesieve.conf protocols line is not what is included in the examples.
The examples show:
> ##
> ## ManageSieve specific settings
> ##
>
> # Uncomment to enable managesieve protocol:
> #protocols = $protocols sieve
>
> # Service definitions
Note the protocols line.
Your configuration is showing:
> # Uncomment to enable managesieve protocol:
> #protocols = $protocols
>
> # Service definitions
Where did the “sieve” go at the end of that protocols line? Anyhow, it should be added, and the line uncommented.
However, I’m concerned that there are so many odd things going on in the configuration so far; it’s possible some of it was during debugging, but you may want to start fresh and retry.
Steve
--
Steve Watt KD6GGD PP-ASEL-IA factories.words.yappy
Don't let your schooling get in the way of your education.
From: Dan Egli <dan at newideatest.site <mailto:dan at newideatest.site> >
Sent: Saturday, May 1, 2021 08:10
To: steve at watt.com <mailto:steve at watt.com> ; dovecot at dovecot.org <mailto:dovecot at dovecot.org>
Subject: Re: Sieve daemon errors? (Part 1 of 2, Pt 2 to follow when Pt 1 resolved)
Still haven't heard back on why 4190 isn't being listened to. I put the entire /etc/dovecot/conf.d directory into https://www.newideatest.site/dovecot, so feel free to look at the configs and see if you can figure out why the sieve listener isn't running.
On 5/1/2021 1:14 AM, Dan Egli wrote:
So I see. THAT part is fixed. But now when I restart dovecot, NOTHING is listening on 4190. So how to I tell dovecot to listen on 4190 with the sieve daemon?
On 5/1/2021 12:53 AM, dovecot at steve.wattlink.net <mailto:dovecot at steve.wattlink.net> wrote:
Exactly as I suspected:
> service lmtp {
> inet_listener lmtp {
> address = 127.0.0.1
> port = 4190
> }
> }
As for why it looks that way? Dunno. Check conf.d/20-lmtp.conf. That doesn’t make sense.
--
Steve Watt KD6GGD PP-ASEL-IA factories.words.yappy
Don't let your schooling get in the way of your education.
From: Dan Egli <mailto:dan at newideatest.site> <dan at newideatest.site>
Sent: Friday, April 30, 2021 23:50
To: steve at watt.com <mailto:steve at watt.com> ; dovecot at dovecot.org <mailto:dovecot at dovecot.org>
Subject: Re: Sieve daemon errors? (Part 1 of 2, Pt 2 to follow when Pt 1 resolved)
Ask and ye shall receive: # dovecot -n
# 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.13 (cdd19fe3)
# OS: Linux 5.11.16-gentoo-x86_64 x86_64 Gentoo Base System release 2.7 xfs
# Hostname: jupiter.newideatest.site
auth_debug = yes
auth_mechanisms = plain login
auth_socket_path = /run/dovecot/auth-userdb
auth_verbose = yes
debug_log_path = /var/log/dovecot/debug.log
default_vsz_limit = 1 G
disable_plaintext_auth = no
first_valid_uid = 114
hostname = jupiter.newideatest.site
info_log_path = /var/log/dovecot/info.log
log_path = /var/log/dovecot/error.log
mail_debug = yes
mail_gid = exim4u
mail_location = maildir:/var/mail/%d/%n/Maildir:INDEX=/var/mail/indexes/%d/%1n/% n
mail_plugins = fts
mail_privileged_group = mail
mail_server_admin = <redacted>
mail_uid = exim4u
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character vacati on subaddress comparator-i;ascii-numeric relational regex imap4flags copy includ e variables body enotify environment mailbox date index ihave duplicate mime for everypart extracttext imapsieve vnd.dovecot.imapsieve
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
passdb {
args = /etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
plugin {
fts_autoindex = yes
fts_autoindex_exclude = \Junk
fts_autoindex_exclude2 = \Trash
fts_autoindex_exclude3 = \Drafts
fts_autoindex_exclude4 = \Spam
fts_enforced = yes
imapsieve_mailbox1_before = file:/var/lib/dovecot/sieve/report-spam.sieve <file://var/lib/dovecot/sieve/report-spam.sieve>
imapsieve_mailbox1_causes = COPY
imapsieve_mailbox1_name = Spam
imapsieve_mailbox2_before = file:/var/lib/dovecot/sieve/report-ham.sieve <file://var/lib/dovecot/sieve/report-ham.sieve>
imapsieve_mailbox2_causes = COPY
imapsieve_mailbox2_from = Spam
imapsieve_mailbox2_name = *
plugin = fts managesieve sieve
sieve = file:%h/sieve;active=%h/.dovecot.sieve <file://%25h/sieve;active=%25h/.dovecot.sieve>
sieve_Dir = ~/sieve
sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute
sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter
sieve_global_dir = /var/lib/dovecot/sieve/
sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment
sieve_global_path = /var/lib/dovecot/sieve/default.sieve
sieve_pipe_bin_dir = /var/lib/dovecot/sieve
sieve_plugins = sieve_imapsieve sieve_extprograms
}
postmaster_address = postmaster at newideatest.site <mailto:postmaster at newideatest.site>
service auth {
unix_listener auth-client {
mode = 0600
user = exim4u
}
unix_listener auth-userdb {
group = exim4u
mode = 0777
user = exim4u
}
}
service lmtp {
inet_listener lmtp {
address = 127.0.0.1
port = 4190
}
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
process_min_avail = 0
service_count = 1
vsz_limit = 64 M
}
service managesieve {
process_limit = 1024
}
service stats {
unix_listener stats-reader {
mode = 0777
user = exim4u
}
unix_listener stats-writer {
mode = 0777
user = exim4u
}
}
service submission-login {
inet_listener submission {
port = 2587
}
}
ssl_cert = </etc/letsencrypt/live/newideatest.site/fullchain.pem
ssl_client_ca_dir = /etc/pki/tls/exim_tls/
ssl_dh = # hidden, use -P to show it
ssl_key = # hidden, use -P to show it
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
userdb {
args = uid=exim4u gid=exim4u home=/var/mail/%Ld/%Ln
driver = static
}
verbose_ssl = yes
protocol lmtp {
info_log_path = /var/log/dovecot/lmtp.log
log_path = /var/log/dovecot/lmtp-errors.log
mail_plugins = fts sieve sieve
postmaster_address = postmaster at newideatest.site <mailto:postmaster at newideatest.site>
}
protocol lda {
info_log_path = /var/log/dovecot/lda.log
log_path = /var/log/dovecot/lda-errors.log
mail_plugins = fts sieve sieve
}
protocol imap {
mail_plugins = fts imap_sieve
}
protocol sieve {
info_log_path = /var/log/dovecot/sieve.log
log_path = /var/log/dovecot/sieve-errors.log
managesieve_implementation_string = Dovecot
managesieve_max_compile_errors = 5
managesieve_max_line_length = 64 k
}
j
On 5/1/2021 12:44 AM, Steve Watt wrote:
>From a little bit of poking around in the source, I wonder if you somehow have the LMTP listener running on the sieve port.
The output of doveconf -n will help more than just the 90-sieve.conf. Also check the dovecot log; I found it helpful (once I figured out how to configure it) with debugging.
[ Apologies for top post; brain-damaged MUA in use. ]
--
Steve Watt KD6GGD PP-ASEL-IA factories.words.yappy
Don't let your schooling get in the way of your education.
From: dovecot <mailto:dovecot-bounces at dovecot.org> <dovecot-bounces at dovecot.org> On Behalf Of Dan Egli
Sent: Friday, April 30, 2021 23:13
To: dovecot at dovecot.org <mailto:dovecot at dovecot.org>
Subject: Sieve daemon errors? (Part 1 of 2, Pt 2 to follow when Pt 1 resolved)
Folks, I am still trying to get help here. Let me re-state what is going on. I have a webmail program (SOGo) that connects to the Dovecot sieve system to handle things like mail filters and what not. That way dovecot's lda program can move things where they belong. So I went through the config files, and found the places where I need to enable sieve (this is in Gentoo Linux, by the way). Now, when dovecot starts I do see a listener on the sieve port on localhost:
#netstat -tl | grep sieve
tcp 0 0 localhost:sieve 0.0.0.0:* LISTEN
And when I telnet to the port, it does connect. But it doesn't say much.
telnet localhost sieve
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 jupiter.newideatest.site Dovecot ready.
Yet every example I see online is showing a HECK of a lot more than this. So what's up? Anyone got any idea what I did wrong? I've put the 90-sieve.conf file on my web server at www.newideatest.site/90-sieve.conf <http://www.newideatest.site/90-sieve.conf> for those who want to see it. If any other config files are wanted/needed to help figure this out, let me know what they are and I'll take care of it. Here's an example of what other websites I've looked at say I SHOULD see:
Trying 162.243.12.140...
Connected to test3.rtcamp.com.
Escape character is '^]'.
"IMPLEMENTATION" "Dovecot Pigeonhole"
"SIEVE" "fileinto reject envelope encoded-character vacation subaddress
comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave"
"NOTIFY" "mailto"
"SASL" "PLAIN LOGIN"
"STARTTLS"
"VERSION" "1.0"
OK "Dovecot ready."
so why am I not getting all this?
--
Dan Egli
>From my Test Server
--
Dan Egli
>From my Test Server
--
Dan Egli
>From my Test Server
--
Dan Egli
>From my Test Server
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dovecot.org/pipermail/dovecot/attachments/20210501/d31cc4f5/attachment-0001.html>
More information about the dovecot
mailing list