Re: Dovecot Mail Server - Cloud Compatibility
> On 27/01/2021 23:48 Kristie Buller wrote: > > > I have a question regarding the Dovecot Server compatibility with Azure > Cloud, which our application is migrating to.We are currently usingDovecot > Mail Server v2.3.4. I need to verify that the software is compatible with > that type of environment or what we would need to continue using the software > once we migrate. > > Thank you, > > Kristie Buller Hi Kristie, community edition of dovecot mail server is not supported as per such, so feel free to run it anywhere you get it running. However, dovecot pro has object storage, which makes it more suitable for running in cloud environment. Aki
Re: [EXT] Re: Reminder Re: Dovecot Gmail OAuth2.0 Setting Question
Dear Mr. Tuomi
Do you have any idea how to solve this problem?
Best regards,
-
〒163-6017 東京都新宿区西新宿6-8-1 住友不動産新宿オークタワー
株式会社 ジャストシステム 技術企画室 情報システムグループ 福田泰葵
e-mail: taiki.fuk...@justsystems.com
内線: 5158
TEL: 03-5324-7900
mobile: 080-6198-7328
-
2021年1月26日(火) 18:51 福田泰葵 :
> Dear Mr. Tuomi
>
> Thank you for the instruction.
> I was able to output rawlogs.
> The following is the result.
>
> 20210126-184744.1.1.in：
>
> 1611654464.207331 HTTP/1.1 401 Unauthorized
> 1611654464.207331 Cache-Control: no-cache, no-store, max-age=0,
> must-revalidate
> 1611654464.207331 Pragma: no-cache
> 1611654464.207331 Expires: Mon, 01 Jan 1990 00:00:00 GMT
> 1611654464.207331 Date: Tue, 26 Jan 2021 09:47:44 GMT
> 1611654464.207331 Vary: X-Origin
> 1611654464.207331 Vary: Referer
> 1611654464.207331 Content-Type: application/json; charset=UTF-8
> 1611654464.207331 Server: ESF
> 1611654464.207331 X-XSS-Protection: 0
> 1611654464.207331 X-Frame-Options: SAMEORIGIN
> 1611654464.207331 X-Content-Type-Options: nosniff
> 1611654464.207331 Alt-Svc: h3-29=":443"; ma=2592000,h3-T051=":443";
> ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443";
> ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"
> 1611654464.207331 Accept-Ranges: none
> 1611654464.207331 Vary: Origin,Accept-Encoding
> 1611654464.207331 Transfer-Encoding: chunked
> 1611654464.207331
> 1611654464.207331 130
> 1611654464.207331 {
> 1611654464.207331 "error": {
> 1611654464.207331 "code": 401,
> 1611654464.207331 "message": "Request is missing required authentication
> credential. Expected OAuth 2 access token, login cookie or other valid
> authentication credential. See
> https://developers.google.com/identity/sign-in/web/devconsole-project.;,
> 1611654464.207331 "status": "UNAUTHENTICATED"
> 1611654464.207331 }
> 1611654464.207331 }
> 1611654464.207331
> 1611654464.207737 0
> 1611654464.207737
>
> 20210126-184744.1.1.out：
>
> 1611654464.165704 GET /oauth2/v2/userinfo HTTP/1.1
> 1611654464.165704 Host: www.googleapis.com
> 1611654464.165704 Date: Tue, 26 Jan 2021 09:47:44 GMT
> 1611654464.165704 User-Agent: dovecot-oauth2-passdb/2.3.13
> 1611654464.165704 Connection: Keep-Alive
> 1611654464.165727 Authorization: Bearer ??
> 1611654464.165730
>
> Best regards,
> --
>
> 〒163-6017 東京都新宿区西新宿6-8-1 住友不動産新宿オークタワー
> 株式会社 ジャストシステム 技術企画室 情報システムグループ 福田泰葵
> e-mail: taiki.fuk...@justsystems.com
> 内線: 5158
> TEL: 03-5324-7900
> mobile: 080-6198-7328
> --
>
> 2021年1月26日(火) 18:35 Aki Tuomi aki.tu...@open-xchange.com
> :
>
> No, the directory must exist. I'm sorry I wasn't clear enough when I
>> replied last time, but dovecot will not create the directory. You need to
>> create it and make it writable.
>>
>> Aki
>>
>> > On 26/01/2021 11:09 福田泰葵 wrote:
>> >
>> >
>> > Dear Mr. Tuomi
>> >
>> > Sorry, I have added the setting PrivateTmp=no to
>> /etc/systemd/system/dovecot.service.d/override.conf
>> > However, /tmp/oauth2 was not created.
>> >
>> > Best regards,
>> >
>> >
>> -
>> > 〒163-6017 東京都新宿区西新宿6-8-1 住友不動産新宿オークタワー
>> > 株式会社 ジャストシステム 技術企画室 情報システムグループ 福田泰葵
>> > e-mail: taiki.fuk...@justsystems.com
>> > 内線: 5158
>> > TEL: 03-5324-7900
>> > mobile: 080-6198-7328
>> >
>> -
>> >
>> >
>> >
>> > 2021年1月26日(火) 18:01 Aki Tuomi :
>> > > That is because you are using systemd, where the unit file, by
>> default, has PrivateTmp=yes.
>> > >
>> > > You can look under /tmp for dovecot private tmp directory and create
>> the directory there, or you can temporarily disable this security measure.
>> > >
>> > > systemctl edit dovecot
>> > >
>> > > [Service]
>> > > PrivateTmp=no
>> > >
>> > > systemctl daemon-reload
>> > > systemctl restart dovecot
>> > >
>> > > Aki
>> > >
>> > > > On 26/01/2021 10:57 福田泰葵 wrote:
>> > > >
>> > > >
>> > > > Dear Mr. Tuomi
>> > > >
>> > > > I have added the setting rawlog_dir = /tmp/oauth2 to
>> /etc/dovecot/dovecot-oauth2.conf.ext
>> > > > However, /tmp/oauth2 was not created.
>> > > >
>> > > > Best regards,
>> > > >
>> > > >
>> > > >
>> -
>> > > > 〒163-6017 東京都新宿区西新宿6-8-1 住友不動産新宿オークタワー
>> > > > 株式会社 ジャストシステム 技術企画室 情報システムグループ 福田泰葵
>> > > > e-mail: taiki.fuk...@justsystems.com
>> > > > 内線: 5158
>> > > > TEL: 03-5324-7900
>> > > > mobile: 080-6198-7328
>> > > >
>>
Dovecot Mail Server - Cloud Compatibility
I have a question regarding the Dovecot Server compatibility with Azure Cloud, which our application is migrating to. We are currently using Dovecot Mail Server v2.3.4. I need to verify that the software is compatible with that type of environment or what we would need to continue using the software once we migrate. Thank you, Kristie BullerIBM System Engineer - eSign & SMART ABS Sales & Contracting Delivery, AT Account 801 Chestnut - St. Louis, Mo Email: kristie.bul...@ibm.comphone: 618.660.6766
Re: Where is dovemon
> On 13. Jan 2021, at 13.30, li...@mlserv.org wrote: > > Hello, > > I found this link in the documentation: > > https://doc.dovecot.org/configuration_manual/dovemon/ > > But where can I find the program "dovemon"? I searched all over whithout > luck. In the source code, Google, nothing. It seems as only the web site > would exist. > > Can somebody help me please Dovemon is only part of the enterprise edition. It is not open source. Contact Open-Xchange sales for more information. Sami
Re: Dovecot and mutt
On 26/01/2021 18:18, Rupert Gallagher wrote: If someone needs to send a formatted text, then they can use a text editor on headed paper, export to PDF and send it as attachment. E-mail proper is the plain text body of the message. When people send fancy HTML and expect me to read it on my phone, then they have wasted their effort, because the message is too heavy to download, heavy to display, and because I ultimately read e-mails in plain text. And most of the times it is spam. And yet, ironically, this message you sent is in HTML. It does have a plain text part, but it's base64 encoded. Not a problem for any half-decent MUA, but for those read hardcore users that read their mail directly from ~/maildir (or something like that), it's an extra decoding step ;-) -- "Rembrandt's first name was Beauregard, which is why he never used it." -- Dave Barry Eduardo M KALINOWSKI edua...@kalinowski.com.br
Infinity loop when run "doveadm quota get -A" from Dovecot Director with 500 users
Hi all,
I have one Dovecot Director, two Dovecot Backends and one LDAP server with
about 500 users. I would like to run *doveadm quota get -A* from the
Director.
In each Backend, there is no problem when run the command:
# doveadm quota get -A
user1 User quota STORAGE 0 10485760
0
user1 User quota MESSAGE 0-
0
…
user500 User quota STORAGE 0 10485760
0
user500 User quota MESSAGE 0-
0
However, when I run from the Director, the command might stuck in an
infinity loop (I have to terminate to quit):
# doveadm quota get -A
user1 User quota STORAGE 0 10485760
0
user1 User quota MESSAGE 0-
0
…
user49User quota STORAGE 0 10485760 0
user49User quota MESSAGE 0- 0
user66User quota STORAGE 0 10485760 0
user66User quota MESSAGE 0- 0
^Cdoveadm(user86): Error: doveadm server failure
doveadm: Error: Failed to iterate through some users
doveadm: Error: backend2.local:24245: Command quota get failed for user53:
EOF
doveadm: Error: backend1.local:24245: Command quota get failed for user66:
EOF
doveadm: Error: Aborted
This problem occurs in both Dovecot 2.2.36 and Dovecot 2.3.11, 2.3.13 (I
build Dovecot from source). It's ok for me to get quota of one user from
the Director:
# doveadm quota get -u user1
Quota name TypeValueLimit%
User quota STORAGE 0 104857600
User quota MESSAGE 0-0
And if there's only one Backend, *doveadm quota get -A* from the Director
works well too.
After investigating, I found the infinity loop:
File src/doveadm/doveadm-mail-server.c:
static void doveadm_server_flush_one(struct doveadm_server *server)
{
unsigned int count = array_count(>queue);
do {
io_loop_run(current_ioloop);
} while (array_count(>queue) == count &&
doveadm_server_have_used_connections(server) &&
!DOVEADM_MAIL_SERVER_FAILED());
}
In case there're many Backends, I see only global variable *current_ioloop*
is used to notify in the callback function. Might this be a race condition?
I understand there's a workaround to do my work:
- Run *doveadm user '*'* to get all users
- Loop through all users and run *doveadm quota get -u xxx*
Thanks,
Anh Do
