steph> Up to now, I used PAM of each user in order to send and receive
steph> email. ( BTW, sending email, a use authentication was required
steph> and we used the login and passwd of the user on the system
So just to be clear, each user has a login on your mail server in
/etc/passwd? If so, I
Hi Zakaria
Thank you for your suggestion.
I don't think an out of date ca trust is the issue with me. I'm running Debian
Bullseye (i.e. latest Debian release) and its fully up to date with all patches.
I will look into your suggestion though.
Laura
‐‐‐ Original Message ‐‐‐
On
I'm having a frustrating problem trying to use "doveadm sync" to pull mails off
a server for migration purposes.
# 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.17.1 (a1a0b892)
# OS: Linux 5.10.0-11-amd64 x86_64 Debian 11.2
I have tried both explicit
Hi,
Up to now, I used PAM of each user in order to send and receive email. ( BTW,
sending email, a use authentication was required and we used the login and
passwd of the user on the system
Now, for dovecot, I start to use MD5 passwrd.. and that sounds to be OK
auth_mechanisms = plain
Hello Aki,
Thank you, that works. But it doesn't solve my main problem. Newer
versions of Outlook started to parse the "@domain" out of the
"user@domain" which yielded only "user". I found that by prepending a '\'
(backslash) it would yield "user@domain" correctly. But with GSSAPI, the
mikfum> thanks John for the reply
No problem! I'm not an expert by any stretch, but I've been using
dovecot for years and doing It for way too many years... LOL!
mikfum> what I would like to do is implement an autoarchive function
mikfum> at server level that, in the night while dovecot is
Hello
I try to test my sieve script, but found out that it is impossible to use a
sieve-filter tool with virtual mail users. It always uses a real user name
instead of passed via -u argument.
# sieve-filter -v -u postmas...@domain.tld ~/sieve/managesieve.sieve INBOX
sieve-filter(root): Fatal:
very nice!, you also made me find the wiki to look for answers to any other
trivial questions without boring you...
tx again
‐‐‐ Original Message ‐‐‐
Il lunedì 24 gennaio 2022 12:15 PM, Felix Zielcke ha scritto:
> Am Montag, dem 24.01.2022 um 10:18 + schrieb mikfum:
>
> > thanks
Am Montag, dem 24.01.2022 um 10:18 + schrieb mikfum:
> thanks John for the reply
> what I would like to do is implement an autoarchive function at
> server level that, in the night while dovecot is down, moves
> messages older than n days from the user inbox to a subfolder of the
> same user
ok, not a 'mass action' but I search about imap tools, thanks!
‐‐‐ Original Message ‐‐‐
Il lunedì 24 gennaio 2022 10:15 AM, Steven Varco ha
scritto:
> Hi Mik
>
> > I would like to ask if it is an acceptable practice to manage messages in
> > the maildir as a file (move them from
thanks
‐‐‐ Original Message ‐‐‐
Il lunedì 24 gennaio 2022 5:15 AM, Ted Hatfield ha scritto:
> I do this all the time on my server. From one user mailbox to another or
>
> from one maildir folder to another. On my platform I need to make certain
>
> owner/group of the moved messages
ok thanks
‐‐‐ Original Message ‐‐‐
Il lunedì 24 gennaio 2022 3:56 AM, ha scritto:
> I would like to ask if it is an acceptable practice to manage messages in the
> maildir as a file (move them from one folder to another) while dovecot is in
> stop state thinking that it will be
thanks John for the reply
what I would like to do is implement an autoarchive function at server level
that, in the night while dovecot is down, moves messages older than n days
from the user inbox to a subfolder of the same user (cur to cur)
tx
mik
‐‐‐ Original Message ‐‐‐
Il lunedì
Hi Mik
> I would like to ask if it is an acceptable practice to manage messages in the
> maildir as a file (move them from one folder to another) while dovecot is in
> stop state thinking that it will be rebuild to the next imap user login
Maildir is actually designed to do so, as the storage
14 matches
Mail list logo
