RE: Ubuntu 16.04 dovecot-core requires deprecated ntpdate

> > When I select the dovecot-core package in Synaptic, it also wants to > install > > ntpdate. > Install packages at the command line using apt-get. It lets you better see > and understand what's going on. > dovecot-core /recommends/ ntpdate. This means you can install with apt-get >

RE: Ubuntu 16.04 dovecot-core requires deprecated ntpdate

> > So, this is obviously an Ubuntu packaging problem, so should be reported > there. I don't know where "there" is. Can you tell me where? Thanks, Michael

Ubuntu 16.04 dovecot-core requires deprecated ntpdate

I'm building a new Ubuntu 16.04 machine, including Dovecot. When I select the dovecot-core package in Synaptic, it also wants to install ntpdate. Problem: ntpdate has been replaced in Ubuntu with timedatectl. In fact, if ntpdate exists on the machine, ntpd will not work properly. See:

RE: Dovecot source code audit

Congratulations Timo and all. Michael > -Original Message- > From: dovecot [mailto:dovecot-boun...@dovecot.org] On Behalf Of Timo > Sirainen > Sent: Friday, January 13, 2017 9:17 AM > To: Dovecot Mailing List > Subject: Dovecot source code audit > > Mozilla

RE: expunging all mailboxes

> maybe the debug option '-D' gives a clue why it failes on your site? > > doveadm -D expunge -u user@domain mailbox '*' savedbefore 2d I don't see any errors in the debug output. And if there was an error, one would expect to see an error message when running the expunge command even without

RE: expunging all mailboxes

> Huh, it certainly did for me, although I used "all" instead of > "savedbefore 30d" since I just wanted to empty the trash. What > version of Dovecot? Mine is 2.2.27. Well, not for me. doveadm search -u user@domain ALL savedbefore 2d -- returns some messages doveadm expunge -u user@domain

RE: expunging all mailboxes

> doveadm expunge -u mailbox '*' savedbefore 30d That doesn't work for me either. The command is accepted, but the messages are not expunged. I guess my search/fetch will just have to return the mailbox name, in addition to other fields, and then I'll need to loop through the mailbox names and

RE: expunging all mailboxes

> > But is there a way tell it all mailboxes for a user? For example, > something > > like: > > > > doveadm expunge -u user@domain mailbox ALL savedbefore 30d > > try: > doveadm expunge -u user@domain ALL savedbefore 30d > > just like the example thats here: >

postlogin script - still confused

> You need to use executable = script-login -- /path/post-login.sh -a -r -g > note the double-dash. it tells getopt to stop processing arguments. > > Aki OK. Thanks. So let me make sure I have this right, since there is no syntax defined on the wiki - just an example which doesn't show the above

FW: postlogin script

No response seen yet. Trying again. Surely someone knows how the postlogin scripts work and can answer these questions easily... Anyone? Thanks, Michael -Original Message- From: dovecot [mailto:dovecot-boun...@dovecot.org] On Behalf Of Michael Fox Sent: Sunday, December 11, 2016 8

postlogin script

I'm using the postlogin service, following the examples in the wiki. But I can't find any documentation on the behavior (what's allowed/not allowed) of the script-login binary. So, some questions: Question 1: The examples show the following at the end of the post-login.sh script: exec "$@"

RE: shared/public mailbox application

> Basically we alias n...@domain.com to dove...@domain.com. doveadm@ has a > sieve-Script which files into the public folder. You could also configure > a postfix transport which does the job. Ah. OK. That may be more complexity than I need for my situation. So please bear with me as I try to

RE: shared/public mailbox application

ay, November 28, 2016 7:19 AM To: Michael Fox <n...@mefox.org> Cc: Dovecot Mailing List <dovecot@dovecot.org> Subject: Re: shared/public mailbox application Hi Michael, we migrated from Cyrus Shared Folders to Dovecot Public Folder. Our setup with Dovecot: * Publ

RE: shared/public mailbox application

> > Hi, > I did that in Linux (Ubuntu) by using symbolic links. > In the INBOX of users that you want to see shared emails place a symlink > to > the shared INBOX. > > | > | | ...INBOX > | | .Drafts (folder) > | | .Trash (folder > | | ... > | | ~.Shared AAA --> ../aaa > | |

FW: shared/public mailbox application

No answer. Trying again. Surely someone with experience with public mailboxes can offer some insight on whether the application below should be a public or shared namespace ... Thanks Michael -Original Message- From: dovecot [mailto:dovecot-boun...@dovecot.org] On Behalf Of Michael

shared/public mailbox application

I'm new to Dovecot and I need help configuring a shared or public mailbox - I'm not sure which is appropriate. I've read the wiki and Peer's book and neither appears to cover what I'd like to do. So I could use some specific help on how to configure a solution for the following: I'd like to

RE: autoexpunge clarification

Thanks Philon. In one of my situations, the potential for such old mail in accounts where the user is not receiving new mail or logging in is large. For example, one application is for an emergency auxiliary mail service. It can be heavily used during training, drills and, of course,

RE: autoexpunge clarification

On Behalf Of Philon > Sent: Wednesday, August 31, 2016 12:41 AM > To: Michael Fox <n...@mefox.org> > Cc: Dovecot Mailing List <dovecot@dovecot.org> > Subject: Re: autoexpunge clarification > > Hi Micheal, > > the article is fine if you continue reading it to the

autoexpunge clarification

I'm trying to understand autoexpunge, but the documentation is just not clear. Hopefully, someone can clear up a few questions. http://wiki.dovecot.org/MailboxSettings says the following: autoexpunge=: (v2.2.20+) Automatically at user deinitialization expunge all mails in this mailbox

RE: Dovecot book available again

Thanks Peer, I discovered it on Amazon a couple of days ago. Received it today. So far, it's exactly what I was hoping for. I'm already learning new things! Michael > -Original Message- > > after my publisher has to shut down his business at the end of last > year, it took several

RE: Save user passwords in clear text

> Is it possible to save user passwords as clear text through dovecot? I am > currently using MD5 passwords and I allow only "plain and login” > mechanisms but I want to switch my database to clear text as this will > give me the ability to use more mechanisms such as CRAM-MD5. Is this > possible?

RE: Dovecot password policy

> A lot of “bots” try very simple passwords say less than X > characters; over and over and over again before they give up. > > I realize Dovecot mitigates this by slowing them down; but always nice to > have another optional layer of defense to clip this kind of garbage closer > to the door.

RE: service-specific userdb affecting lmtp, quota-service

> On Wed, 3 Aug 2016, Steffen Kaiser wrote: > > >> Update: > >> > >> I was able to eliminate the /var/log/mail.err error messages (shown > below) > >> by creating a userdb.quota-status and userdb.lmtp passwd-file. > However, > >> since userdb.pop3 and userdb.imap will have different

RE: service-specific userdb affecting lmtp, quota-service

Update: I was able to eliminate the /var/log/mail.err error messages (shown below) by creating a userdb.quota-status and userdb.lmtp passwd-file. However, since userdb.pop3 and userdb.imap will have different extra-fields values for namespace (different namespace/xxx/inbox=yes values) I can't

service-specific userdb affecting lmtp, quota-service

The service specific passwd-file userdb is causing quota-status and lmtp to fail. Using: userdb { args = ... /etc/dovecot/auth.d/%d/userdb.%s } I'm getting the following in /var/log/mail.err when I try to send/receive mail: Aug 1 15:46:57 n6mef-gw dovecot: auth: Error:

passwd-file extra-fields: inbox=yes

I'd like to implement the virtual plugin so that POP3 users can see emails in their own inbox and a public namespace. As I understand it, I need to set "inbox=yes" separately, depending on which service the user is using. With passwd-file flat files, this means: userdb { args = ...

RE: POP3 & IMAP inbox setting for virtual

Thanks Steffen. I'll give that a try. > > > > I think you mean by %s. Correct? > > yes, %s = %{service} > > >> So, generate a passwd-file with namespace/inbox/inbox, make a script to > >> strip this settings from it and dump into another file. This script is > to > >> run each time, the main

RE: POP3 & IMAP inbox setting for virtual

Thanks Steffen. > you can select the passwd-file by %u , e.g. see the first example of > passdb's on http://wiki2.dovecot.org/AuthDatabase/PasswdFile I think you mean by %s. Correct? > So, generate a passwd-file with namespace/inbox/inbox, make a script to > strip this settings from it and

POP3 & IMAP inbox setting for virtual

Posted Monday 7/25. Haven't seen a response. Trying again: --- This is a noobie question, so bear with me if it's not worded correctly: Primary Requirements: 1) I'd like to have two namespaces - one private/per-user, and one public (visible by all logged-in users). The public

imap & pop3 using same mailbox with virtual plugin

This is a noobie question, so bear with me if it's not worded correctly: Primary Requirements: 1) I'd like to have two namespaces - one private/per-user, and one public (visible by all logged-in users). The public mailbox would be used to distribute information to all users. 2) I'd like both

doveconf -n display error for "remote"

Upon further testing, it seems that the issue below may only be a display bug in doveconf. In other words, the remote filter appears to work as configured, even though it is displayed with duplicate prefix length by doveconf. Is this sufficient information to report a bug or is there some other

RE: controlling STARTTLS by IP address

KSB: > Just curious, it is transferred in some RSxxx serial protocol? The expectation is that the unencrypted traffic will be used for clients on an Ethernet network behind a radio operating on amateur radio frequencies according to FCC Part 97 rules. The radio could be: -- 56+kbps UHF, such

RE: RE: controlling STARTTLS by IP address

> -Original Message- > From: dovecot [mailto:dovecot-boun...@dovecot.org] On Behalf Of Jochen > Bern > Sent: Friday, July 15, 2016 12:46 AM > To: dovecot@dovecot.org > Subject: Re: RE: controlling STARTTLS by IP address > > On 07/14/2016 11:52 PM, Michael Fox wro

RE: controlling STARTTLS by IP address

> I'm not a FCC lawyer, just a ham. Seems to me all you could do is "sign" > messages and not send them if the sign isn't correct.  The package itself > is in plain text. I'm not sure what the confusion or concern is. The intention is to use non-plaintext (but technically not encrypted)

RE: controlling STARTTLS by IP address

> > I just thought to remind people that with some firewalls, there's always > a way > > to perform "silent" redirections using the DNAT target in the PREROUTING > > table, i.e.,: > > > > -t nat -A PREROUTING -i ${EXTIF} -s ${NOTLSSOURCES} -p tcp --dport 110 \ > > --syn -j DNAT --to-destination

RE: controlling STARTTLS by IP address

> You could try > > remote x.x.x.x/y { >ssl = no > } > > Aki That works! Thanks SO much! Michael

RE: controlling STARTTLS by IP address

> > You could try > > remote x.x.x.x/y { >ssl = no > } > > Aki Wow. OK. But I can find no documentation on how to use that. Would it be used inside service pop3-login, or at the top level? And, does it apply the first match found? For example: # Disable SSL for radio clients

RE: controlling STARTTLS by IP address

> Are you 100% sure your interpretation of the FCC rules is correct? Yes > Do you really want passwords going out over RF unencrypted? No. I don't plan to use plaintext auth methods. > As far as I know, only ham bands are not allowed to use encryption. Even > baby monitors these days are DECT.

RE: controlling STARTTLS by IP address

> Seems like your firewall could redirect to a different port that doesn't > offer starttls. Yes, of course. But that would require multiple ports, making the client configuration cumbersome and error-prone. Michael

controlling STARTTLS by IP address

On my POP3 server, I need to be able to control the use of STARTTLS by client IP address. Specifically: * Clients on certain internal subnets (e.g., 192.168.1.0/24) must not have the option to use TLS. If the client tries to use STARTTLS, the option should be rejected. This is to satisfy US

RE: quota-status service

> > The way I understand it is, this Quota service was built specifically > for postfix. (I only have postfix, have not used any other MTA) > The "quota-status" executable is in you libexec directory. ( I compiled > my dovecot instance, hence is is not in "regular" directory) Thanks. I also

RE: FW: quota-status service

> No. But someone knew what to answer to them, you keep spamming the mailing > list with repeated '???' instead of waiting, which *is* impolite. Someone > WILL answer you when they have time to study your question and prepare an > answer. As I said, if you think you should be entitled to timely >

RE: FW: quota-status service

Aki: Over the last three days, I've watched many other questions being asked and answered. Were they also impolite to ask? Peter: What exactly was impolite about identifying missing information and listing the specific details that I'm looking for? Aki & Peter: Do either of you know the

FW: quota-status service

??? 3rd request -Original Message- From: dovecot [mailto:dovecot-boun...@dovecot.org] On Behalf Of Michael Fox Sent: Friday, July 1, 2016 5:56 PM To: Dovecot Mailing List <dovecot@dovecot.org> Subject: RE: quota-status service ??? From: Michael Fox [mailto:n...@mefox.org]

RE: quota-status service

??? From: Michael Fox [mailto:n...@mefox.org] Sent: Thursday, June 30, 2016 1:59 PM To: Dovecot Mailing List (dovecot@dovecot.org) <dovecot@dovecot.org> Subject: quota-status service I'm trying to understand the quota-status service, but I can't find complete documentation. The

quota-status service

I'm trying to understand the quota-status service, but I can't find complete documentation. The quota-status service is mentioned here: http://wiki.dovecot.org/Quota And an example configuration is shown: service quota-status { executable = quota-status -p postfix

RE: Postfix and Dovecot LDA vs. LMTP

> Actually we're one the way to get > the book back into the shop into the next few weeks. > > Peer That's great news! English version please! Michael

RE: Postfix and Dovecot LDA vs. LMTP

> imho wiki is the way to go to be up2date with information, else it would > make more sense to make more informative man pages in dovecot, that will > never be outdated I agree that the wiki is useful and important. It just doesn't have any depth regarding the "why" and "how" part of the

RE: Postfix and Dovecot LDA vs. LMTP

Thanks again Jan. I appear to have basic LMTP working now (messages are delivered to virtual mailboxes of valid recipients and non-existent recipients are rejected). Cool. Still lots more work to do. But I think I could really use the Dovecot book. I find the wiki to be lacking in explanation.

RE: Postfix and Dovecot LDA vs. LMTP

> The most crucial difference is that LDA is intended for delivering email > to a *real* user. > > Aki Thanks Aki. Pardon my ignorance, but why does it matter? In other words, what is it that makes LDA better for a *real* user and LMTP better for a virtual user? Thanks, Michael

RE: Postfix and Dovecot LDA vs. LMTP

Thanks Jan. I've been trying to obtain an English copy of the Dovecot book for months, prior to starting this project. So far, I just can't find a copy. It's too bad that the author/publisher won't do a second printing or, if they're not interested in making any more money, then release it to

Postfix and Dovecot LDA vs. LMTP

I'm new to Dovecot and will be using it with Postfix. I'm looking for recommendations regarding the use of Dovecot's LDA or LMTP for virtual mailbox delivery. Many of the simple examples on the wiki use LDA. So I've set that up initially. But apparently an advantage of LMTP is recipient

FW: error using default_fields in passwd-file

I didn't see a response. Sending again and adding doveconf -n output. I'm trying to put virtual user mail in: /var/vmail// I tried setting the home field in the userdb to /var/vmail/%d/%n But apparently variable expansion doesn't happen in the userdb because the Dovecot LDA

error using default_fields in passwd-file

I'm trying to put virtual user mail in: /var/vmail// I tried setting the home field in the userdb to /var/vmail/%d/%n But apparently variable expansion doesn't happen in the userdb because the Dovecot LDA created the literal directory /var/vmail/%d/%n/Maildir So then I tried to use

RE: newbie userdb lookup problem

> http://wiki.dovecot.org/LDA > > Section virtual users, with lookup has the answer. Thanks for the quick response Aki. I presume you're referring to this: service auth { unix_listener auth-userdb { mode = 0600 user = vmail # User running dovecot-lda #group = vmail # Or

newbie userdb lookup problem

I'm new to Dovecot and I'm having trouble getting basic, flat file userdb lookups to work. This must have been asked before, but if so, I can't find it. I'm following the basic setup here: http://wiki2.dovecot.org/HowTo/SimpleVirtualInstall with a few minor differences. Output of doveconf -n