Re: more info about deleting users
> On May 2, 2016 at 9:56 AM Tom Sommer wrote: > > > > On 2016-04-29 16:25, Matteo Gaito Test Account wrote: > > > i've search a lot in order to find a way to delete account by dovecot > > but i > > found only this way > > > > http://dovecot.org/list/dovecot/2011-November/079273.html > > > > It's possible today delete a maildir remotely with doveadm or with > > dovecot api? > > Would love this as well > > // Tom You could try using fs commands that are available in doveadm HTTP API. --- Aki Tuomi
Cannot connect to Dovecot IMAP or POP
Hello all. Thank you for your service.
Easy when you know how, but presently I do not. After literally months of
research and experimentation we simply cannot log into our PAM / apache2 /
postfix / dovecot pop3/imap STARTTLS email server with an ordinary email
client, e.g., Evolution or Thunderbird.
We can connect to the host server in a host of different ways (no pun
intended)—http, https, ssh, vnc, telnet, openssl -sclient
Similarly we can connect to postfix and dovecot in yet another number of
ways—telnet, openssl -sclient—but cannot log in to the email server with a
normal email client (either Evolution or Thunderbird) by either pop3 or imap.
SSL certificates are in place, verified, and tested.
Part of the problem is the many changes in all the involved operating systems
and protocols (e.g., imaps and pop3s are deprecated, openSUSE has migrated to
LEAP, etc.) so many of the docs from Google are no longer valid. Additionally,
there simply are bugs: Leap 42.1 YAST does not work when it comes to setting up
websites. Documented. But I digress.
I'm sure it's something really simple, but it evades me. Research details
below. Any help would be more than appreciated.
Thanks in advance, Andy
=== Configuration testing details ===
System is:
Linux openSUSE Leap 42.1
Dovecot --version 2.2.18,
Postfix Version: 2.11.6-3.1
Apache2 Version: 2.4.16-9.1
Connections
1. Evolution or Thunderbird to pop3 or imap reports:
The reported error was "Could not connect to
mail.privustech.com: Connection refused".
Both connect successfully to googlemail.com with the same
protocol:
Port 993 SSL on a dedicated port
I have also tried
Port 143 STARTTLS after connecting
without success
2. openssl s_client -connect mail.privustech.com:xxx
a. xxx=25, 110, 143 all return
error:140770FC
b. xxx=993, 995 return
socket: Connection refused
connect:errno=111
3.telnet to
a. smtp works.
b. pop3
andy@tm2t:~> telnet 70.186.159.22 110
...
+OK POP3 2007e.104 server ready
<48fa.572a0...@privustech.com>
...
user andy
-ERR Unknown AUTHORIZATION state command
c. imap connects but does not allow login, and should not.
http://marc.info/?l=imap&m=118775891829506&w=2
The most simple answer is "you
cannot TELNET to a modern, correctly-configured,
IMAP server and log in to it."
andy@tm2t:~> telnet 70.186.159.22 143
...
* OK [...] privustech.com IMAP4rev1 2007e.404 at Wed, 4
May 2016 10:26:28
-0400 (EDT)
... A NO Invalid login credentials
Modules
• Apache2 works just fine. The server is up and answering. ping works
just fine. We have http and https to all vhost sites (privustech,
mailprivustech, nptbeyond, gvhl, truthcourage, and their www. subsites).
• Postfix reports no errors. We can log in on localhost, send a message
to ourselves and see the message.
• Dovecot:
a. Logging is enabled in 10-logging.conf to
/var/log/dovecot.conf but no logging has occurred there.
b. doveconf -n throws no errors.
Checks and tests completed
1. /etc/hosts is just fine.
2. Firewall is open for telnet, postfix, dovecot.
3. Added andy to dovecot, postfix groups, in addition to mail, reset
password to ANDYbbs14@.
4. We tried enabling imaps, pop3s, but this command returns errors
about these protocols being obsolete.
https://tools.ietf.org/html/rfc2595
Use of these ports is discouraged in favor of the
STARTTLS or STLS
commands.
5. Reviewed doveconf -n:
a. Note, there are no Dovecot users established other than
user postfix
group postfix
service auth {
unix_listener auth-userdb {
group = postfix
user = postfix
}
}
i. postfi
Re: Cannot connect to Dovecot IMAP or POP
Re-read the following:
1st
http://wiki2.dovecot.org/PasswordDatabase
2nd
http://wiki2.dovecot.org/Authentication/Mechanisms
then edit /etc/dovecot/conf.d/10-auth.conf
auth_mechanisms = plain login
On 05/04/16 19:00, C. Andrews Lavarre wrote:
Hello all. Thank you for your service.
Easy when you know how, but presently I do not. After literally months of
research and experimentation we simply cannot log into our PAM / apache2 /
postfix / dovecot pop3/imap STARTTLS email server with an ordinary email
client, e.g., Evolution or Thunderbird.
We can connect to the host server in a host of different ways (no pun
intended)—http, https, ssh, vnc, telnet, openssl -sclient
Similarly we can connect to postfix and dovecot in yet another number of
ways—telnet, openssl -sclient—but cannot log in to the email server with a
normal email client (either Evolution or Thunderbird) by either pop3 or imap.
SSL certificates are in place, verified, and tested.
Part of the problem is the many changes in all the involved operating systems
and protocols (e.g., imaps and pop3s are deprecated, openSUSE has migrated to
LEAP, etc.) so many of the docs from Google are no longer valid. Additionally,
there simply are bugs: Leap 42.1 YAST does not work when it comes to setting up
websites. Documented. But I digress.
I'm sure it's something really simple, but it evades me. Research details
below. Any help would be more than appreciated.
Thanks in advance, Andy
=== Configuration testing details ===
System is:
Linux openSUSE Leap 42.1
Dovecot --version 2.2.18,
Postfix Version: 2.11.6-3.1
Apache2 Version: 2.4.16-9.1
Connections
1. Evolution or Thunderbird to pop3 or imap reports:
The reported error was "Could not connect to mail.privustech.com:
Connection refused".
Both connect successfully to googlemail.com with the same
protocol:
Port 993 SSL on a dedicated port
I have also tried
Port 143 STARTTLS after connecting
without success
2. openssl s_client -connect mail.privustech.com:xxx
a. xxx=25, 110, 143 all return
error:140770FC
b. xxx=993, 995 return
socket: Connection refused
connect:errno=111
3.telnet to
a. smtp works.
b. pop3
andy@tm2t:~> telnet 70.186.159.22 110
...
+OK POP3 2007e.104 server ready
<48fa.572a0...@privustech.com>
...
user andy
-ERR Unknown AUTHORIZATION state command
c. imap connects but does not allow login, and should not.
http://marc.info/?l=imap&m=118775891829506&w=2
The most simple answer is "you
cannot TELNET to a modern, correctly-configured,
IMAP server and log in to it."
andy@tm2t:~> telnet 70.186.159.22 143
...
* OK [...] privustech.com IMAP4rev1 2007e.404 at Wed, 4
May 2016 10:26:28
-0400 (EDT)
... A NO Invalid login credentials
Modules
• Apache2 works just fine. The server is up and answering. ping works just fine. We have http and https to all vhost sites (privustech, mailprivustech, nptbeyond, gvhl, truthcourage, and their www. subsites).
• Postfix reports no errors. We can log in on localhost, send a message
to ourselves and see the message.
• Dovecot:
a. Logging is enabled in 10-logging.conf to
/var/log/dovecot.conf but no logging has occurred there.
b. doveconf -n throws no errors.
Checks and tests completed
1. /etc/hosts is just fine.
2. Firewall is open for telnet, postfix, dovecot.
3. Added andy to dovecot, postfix groups, in addition to mail, reset
password to ANDYbbs14@.
4. We tried enabling imaps, pop3s, but this command returns errors
about these protocols being obsolete.
https://tools.ietf.org/html/rfc2595
Use of these ports is discouraged in favor of the
STARTTLS or STLS
commands.
5. Reviewed doveconf -n:
a. Note, there are no Dovecot users established other than
user postfix
group postfix
service auth {
unix_listener auth-userdb {
Re: Cannot connect to Dovecot IMAP or POP
2. openssl s_client -connect mail.privustech.com:xxx a. xxx=25, 110, 143 all return error:140770FC You need to add the "-starttls protocol" parameter, otherwise "openssl s_client" thinks your using SSL, not STARTTLS i.e. openssl s_client -starttls pop3 -connect mail.privustech.com:110 openssl s_client -starttls imap -connect mail.privustech.com:143 But even if you do that, you get the same error because it can't start the TLS session: $ nc mail.privustech.com 143 * OK [CAPABILITY IMAP4REV1 I18NLEVEL=1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS LOGINDISABLED AUTH=CRAM-MD5] privustech.com IMAP4rev1 2007e.404 at Wed, 4 May 2016 22:26:36 -0400 (EDT) x STARTTLS x NO Server certificate not installed So there you go, dovecot can't get at your server certificate. You can start the search of your problem from there. The configuration verbose_ssl = yes will help to log the problem. ssl_dh_parameters_length = 2048 Probably not related to your problem, but this will cause wildly variable dovecot initialization times, as temp key generation of this length can result in a lot of candidate primailty testing. Joseph Tam
Is there a way to override Sieve's "not sending notification for auto-submitted message" behavior?
Goal: 1) Setup a Google Calendar entry for a biweekly task 2) Configure the email notification schedule 3) When the email notification from Google arrives have Sieve send a notification to an alias I have setup for my cell provider's email to text messaging gateway 4) Receive text message I know there are other products which likely handle this better, but I'm specifically attempting to replicate old behavior by getting text message reminders when a specific Google Calendar event occurs. The problem I'm having is that Sieve is attempting to help by NOT sending a notification for emails that it finds are automatically generated. I didn't found a lot of information when I searched for additional details, but I didn't find an earlier message thread on this list that led me to believe that the default behavior is likely chosen as some sort of safety net to prevent common issues from occurring. What I would like to do is override this behavior at some level (per rule, per user, system-wide, whatever) to allow for Sieve notifications when emails matching a specific pattern are detected regardless of whether they are auto-generated or not. I already found mention in the documentation[1] that the editheader extension refuses to remove the Auto-Submitted header, so setting up a per user or global rule to do just that wouldn't help. I also haven't come upon a way to simply modify the value for the Auto-Submitted header, so that doesn't look to work in this situation either. Does anyone know of a way to accomplish this? Thanks in advance for your help! [1] http://wiki2.dovecot.org/Pigeonhole/Sieve/Extensions/Editheader
