Re: File manager or browser for IMAP?

[Roger Klorese via dovecot]

On Tue, Sep 24, 2019 at 9:19 PM Steve Litt via dovecot 
wrote

>
> They only see some of the folders.



Are they subscribed?

>

Re: [Bug] Sieve vacation :addresses match only case-sensitive?

[Roger Klorese via dovecot]

>
> It is not recommended to rely on local-part case, but it is indeed
> case-sensitive.
>
> And this is to avoid such issues that postfix supports address
> cleanup/canonicalisation before forwarding mails to dovecot.
>
> --
> RFC 5321:
>
> "Local-part = Dot-string / Quoted-string ; MAY be case-sensitive
> […]
> While the above definition for Local-part is relatively permissive, for
> maximum interoperability, a host that expects to receive mail SHOULD avoid
> defining mailboxes where the Local-part requires (or uses) the
> Quoted-string form or where the Local-part is case-sensitive."
>
>



And therefore “receive liberally” policy that wants to assume
case-insensitivity should single-case the address IN THE COMPARISON.

>
>

Re: [Bug] Sieve vacation :addresses match only case-sensitive?

[Roger Klorese via dovecot]

On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot <
dovecot@dovecot.org>

> Further investigation showed me that it has to be a bug.
>
> I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole version 0.4.24
> (5a7e9e62):
>
> In this version the additional addresses in vacation :addresses
> ["t...@example.com"] are handled case-insensitive.
>
> In the new version: Dovecot 2.3.7.2 (3c910f64b), Pigeonhole version
> 0.5.7.2 (7372921a) installed via https://repo.dovecot.org/, (same sieve,
> same configuration) these addresses are handled case-sensitive.
>
> The case-sensitive matching of mail addresses, doesn't make any sense to
> me.
>
> Could someone confirm this behavior?
>
>
Isn’t RFC-compliant behavior to treat the local part as case-sensitive and
the domain-part as case-insensitive?

Re: Bug: subscriptions file

[Roger Klorese]

If John Doe dies and a new John Doe is born, they’re not the same person,
are they?
On Wed, May 23, 2018 at 10:37 PM Aki Tuomi <aki.tu...@dovecot.fi> wrote:

> That's rather difficult semantic question.
>
> Aki
>
> On 24.05.2018 08:35, Roger Klorese wrote:
>
> If something deletes and recreates the folder, it’s not really the folder
> to which you subscribed, is it?!
> On Wed, May 23, 2018 at 10:33 PM Aki Tuomi <aki.tu...@dovecot.fi> wrote:
>
>> I understand that reading that paragraph makes it sounds obscure and
>> outdated. But the problem is that if something deletes & recreates your
>> folder, while you were gone, you would lose the subscription. This includes
>> other MUAs that are in no way obligated to resubscribe to the folder if
>> they do this.
>>
>> Aki
>>
>> On 23.05.2018 23:13, Rupert Gallagher wrote:
>>
>> Sorry for top posting, my client is still broken.
>>
>> I have never seen the ghost of a "system-alerts" or similar "well-known"
>> mail folder in the past 30 years.
>>
>> Compliance with an RFC obscure feature is compellong us all to clear 
>> subscriptions
>> fol ders by hand.
>>
>> As we meet the problem over and over again, a non-RFC configuration
>> option could solve the problem, and it would be very much appreciated...
>>
>>
>> On Wed, May 23, 2018 at 11:57, Aki Tuomi <aki.tu...@dovecot.fi> wrote:
>>
>> > On 23.05.2018 12:31, Rupert Gallagher wrote:
>>
>> Dovecot does not clear the subscription file from non-existent folders.
>>
>>
>> Hi!
>>
>> Thank you for your bug report. Unfortunately this is not a BUG, but
>> mandated behavior by RFC3501, see last two paragraphs in the excerpt.
>>
>> Aki Tuomi
>>
>> 6.3.6.  SUBSCRIBE Command
>>
>>Arguments:  mailbox
>>
>>Responses:  no specific responses for this command
>>
>>Result: OK - subscribe completed
>>NO - subscribe failure: can't subscribe to that name
>>BAD - command unknown or arguments invalid
>>
>>   The SUBSCRIBE command adds the specified mailbox name to the
>>   server's set of "active" or "subscribed" mailboxes as returned by
>>   the LSUB command.  This command returns a tagged OK response only
>>   if the subscription is successful.
>>
>>   A server MAY validate the mailbox argument to SUBSCRIBE to verify
>>   that it exists.  However, it MUST NOT unilaterally remove an
>>   existing mailbox name from the subscription list even if a mailbox
>>   by that name no longer exists.
>>
>>Note: This requirement is because a server site can
>>choose to routinely remove a mailbox with a well-known
>>name (e.g., "system-alerts") after its contents expire,
>>with the intention of recreating it when new contents
>>are appropriate.
>>
>>
>>
>

Re: Bug: subscriptions file

[Roger Klorese]

If something deletes and recreates the folder, it’s not really the folder
to which you subscribed, is it?!
On Wed, May 23, 2018 at 10:33 PM Aki Tuomi  wrote:

> I understand that reading that paragraph makes it sounds obscure and
> outdated. But the problem is that if something deletes & recreates your
> folder, while you were gone, you would lose the subscription. This includes
> other MUAs that are in no way obligated to resubscribe to the folder if
> they do this.
>
> Aki
>
> On 23.05.2018 23:13, Rupert Gallagher wrote:
>
> Sorry for top posting, my client is still broken.
>
> I have never seen the ghost of a "system-alerts" or similar "well-known"
> mail folder in the past 30 years.
>
> Compliance with an RFC obscure feature is compellong us all to clear 
> subscriptions
> fol ders by hand.
>
> As we meet the problem over and over again, a non-RFC configuration option
> could solve the problem, and it would be very much appreciated...
>
>
> On Wed, May 23, 2018 at 11:57, Aki Tuomi  wrote:
>
> > On 23.05.2018 12:31, Rupert Gallagher wrote:
>
> Dovecot does not clear the subscription file from non-existent folders.
>
>
> Hi!
>
> Thank you for your bug report. Unfortunately this is not a BUG, but
> mandated behavior by RFC3501, see last two paragraphs in the excerpt.
>
> Aki Tuomi
>
> 6.3.6.  SUBSCRIBE Command
>
>Arguments:  mailbox
>
>Responses:  no specific responses for this command
>
>Result: OK - subscribe completed
>NO - subscribe failure: can't subscribe to that name
>BAD - command unknown or arguments invalid
>
>   The SUBSCRIBE command adds the specified mailbox name to the
>   server's set of "active" or "subscribed" mailboxes as returned by
>   the LSUB command.  This command returns a tagged OK response only
>   if the subscription is successful.
>
>   A server MAY validate the mailbox argument to SUBSCRIBE to verify
>   that it exists.  However, it MUST NOT unilaterally remove an
>   existing mailbox name from the subscription list even if a mailbox
>   by that name no longer exists.
>
>Note: This requirement is because a server site can
>choose to routinely remove a mailbox with a well-known
>name (e.g., "system-alerts") after its contents expire,
>with the intention of recreating it when new contents
>are appropriate.
>
>
>

Re: Permissions on /var/log/dovecot

[Roger Klorese]

So is yours.

Why not say what SHOULD be done? Since we were discussing logging,
including only the lines about logging seem to be a reasonable response to
the original open-ended question. “Please include the complete output of
‘dovecot -n’” would get your point across instead of just letting you be a
snarky ass.
On Mon, Mar 19, 2018 at 1:14 PM Odhiambo Washington 
wrote:

>
>
> On 19 March 2018 at 22:45, @lbutlr  wrote:
>
>> On 2018-03-19 (13:19 MDT), Odhiambo Washington 
>> wrote:
>> >
>> > What does your doveconf -n have?
>>
>> imap_id_log = *
>> log_path = /var/log/dovecot
>>
>
> This is a very useless response!
>
>
>
> --
> Best regards,
> Odhiambo WASHINGTON,
> Nairobi,KE
> +254 7 3200 0004/+254 7 2274 3223
> "Oh, the cruft."
>

Re: How to make dovecot access a MySQL database with a certain domain?

[Roger Klorese]

Replace 127.0.0.1 with the domain name.
On Tue, Nov 28, 2017 at 10:08 AM Spike98  wrote:

> I am trying to make a mail server with Postfix using the Dovecot software.
> At the time of wanting to access my server from a mail client, it does not
> let me access and see the logs of my server with the command:
>
> $ service dovecot status
> with the following error:
>
> dovecot: auth-worker(2769): Error: mysql(127.0.0.1): Connect failed to
> database (postfix): Access denied for user 'postfix'@'localhost' (using
> password: YES) - waiting for 125 seconds before retry
>
> From what I understand of this error is that it is trying to enter
> 'postfix' @ 'localhost' instead of the domain that I specify when I made
> the database that is mydomain.com
>
> How can you make dovecot go to MySQL with post...@mydomain.com instead of
> localhost
>
> This is my Dovecot configuration
>
> /etc/dovecot/dovecot-sql.conf.ext
>
> driver=mysql
>
> default_pass_scheme=PLAIN-MD5
>
> connect=host=127.0.0.1 dbname=postfix user=postfix password=postfix
>
> password_query=SELECT username,domain,password FROM usuarios WHERE
> username='%n' AND domain='%d'
>
> user_query=SELECT 1007 as uid, 1007 as gid,
> concat("maildir:/var/vmail",domain,'/',username,'/') as mail FROM usuarios
> WHERE username='%n' AND domain='%d'
>
> iterate_query=SELECT username,domain FROM usuarios

Re: Dovecot - Postfix Calender Synchronisation

[Roger Klorese]

On Thu, Aug 24, 2017 at 11:28 PM Rupert Gallagher <r...@protonmail.com>
wrote:

> On Thu, Aug 24, 2017 at 10:55 PM, Roger Klorese <rogerklor...@gmail.com>
> wrote:
>
> > "Webmail? We use dovecot." And how exactly do you read and write mail
> using dovecot?
>
> With a MUA.
>

And you’re suggesting that webmail is somehow more of a risk than lots of
users each running their own MUA. I see.

>
>

Re: Dovecot - Postfix Calender Synchronisation

[Roger Klorese]

“Webmail? We use dovecot.” And how exactly do you read and write mail using
dovecot?
On Thu, Aug 24, 2017 at 10:56 AM Gregory Sloop  wrote:

>
>
> RG> Re: portable formats and their mime type
>
> RG> https://en.m.wikipedia.org/wiki/ICalendar
> RG> https://en.m.wikipedia.org/wiki/VCard
>
> RG> Re: dependencies
>
> RG> - db: why? just use the ical and vcard files! They are files,
> RG> they are in a directory, they can be used like dovecot uses eml
> RG> files! No need for postgresql or mysql.
>
> RG> - webmail: why? We use dovecot!!!
>
> RG> - apache web: why? we use nginx.
>
> RG> - linux: why? we use other unix systems.
>
> RG> - python: why? it takes 140MB all by itself, it is an interpreter
> RG> (slow), it is a security hazard, we would have to install it on
> RG> purpose and sanbox it in a virtual machine! So we have to install a vm
> manager.
>
> RG> Bloody hell...
>
> This is a little tongue-in-cheek, but...
> Do you also yell "Get offa my lawn you dirty punk kids!" regularly?
>
> I thought I had the curmudgeonly-old-man schtick down, but you're like Obi
> Wan.
> :)
>

Re: passwd-file, getting invalid uid 0

[Roger Klorese]

Did you miss the part about 0 also being hardcoded?

On Tue, Jul 18, 2017 at 1:34 PM Larry Rosenman  wrote:

> On Tue, Jul 18, 2017 at 3:31 PM, Larry Rosenman 
> wrote:
>
> > That didn't change it :(
> > Jul 18 15:28:14 thebighonker dovecot: auth-worker(77908): Error:
> > passwd-file /etc/passwd: User root has invalid UID '0'
> > Jul 18 15:28:14 thebighonker dovecot: auth-worker(77908): Error:
> > passwd-file /etc/passwd: User toor has invalid UID '0'
> >
> > doveconf -n:
> > lrosenman:~ lrosenman$ ssh tbh.lerctr.org doveconf -n
> > # 2.2.31 (65cde28): /usr/local/etc/dovecot/dovecot.conf
> > # Pigeonhole version 0.4.19 (e5c7051)
> > # OS: FreeBSD 11.1-PRERELEASE amd64
> > auth_mechanisms = plain login
> > auth_realms = lerctr.org thebighonker.lerctr.org tbh.lerctr.org
> > thejonesonair.com thejonesonair.net
> > default_vsz_limit = 1 G
> > deliver_log_format = msgid=%m: %$ (subject=%s from=%f size=%w)
> > doveadm_password =  # hidden, use -P to show it
> > first_valid_gid = 0
> > first_valid_uid = 0
> > lda_mailbox_autocreate = yes
> > listen = 192.147.25.65, ::
> > lmtp_save_to_detail_mailbox = yes
> > login_access_sockets = tcpwrap
> > mail_attribute_dict = file:%h/mail/.imap/dovecot-mail-attributes
> > mail_location = mbox:~/mail:INBOX=~/mail/INBOX
> > mail_log_prefix = "%s(%u/%p): "
> > mail_plugins = " fts fts_solr notify stats virtual"
> > mail_privileged_group = mail
> > mail_server_admin = mailto:l...@lerctr.org
> > mail_server_comment = LERCTR Mail Server
> > mailbox_list_index = yes
> > managesieve_notify_capability = mailto
> > managesieve_sieve_capability = fileinto reject envelope encoded-character
> > vacation subaddress comparator-i;ascii-numeric relational regex
> imap4flags
> > copy include variables body enotify environment mailbox date index ihave
> > duplicate mime foreverypart extracttext vacation-seconds editheader
> > mboxmetadata servermetadata imapsieve vnd.dovecot.imapsieve
> > namespace archive {
> >   hidden = no
> >   list = no
> >   location = mbox:~/MAIL-ARCHIVE
> >   prefix = ARCHIVE/
> >   separator = /
> > }
> > namespace inbox {
> >   inbox = yes
> >   location =
> >   mailbox Drafts {
> > special_use = \Drafts
> >   }
> >   mailbox INBOX {
> > auto = create
> >   }
> >   mailbox SENT {
> > special_use = \Sent
> >   }
> >   mailbox SPAM {
> > special_use = \Junk
> >   }
> >   mailbox "Sent Messages" {
> > special_use = \Sent
> >   }
> >   mailbox Trash {
> > special_use = \Trash
> >   }
> >   mailbox virtual/Flagged {
> > special_use = \Flagged
> >   }
> >   mailbox virtual/all {
> > special_use = \All
> >   }
> >   prefix =
> > }
> > namespace virtual {
> >   hidden = no
> >   list = yes
> >   location = virtual:~/MAIL-VIRTUAL:INDEX=MEMORY
> >   prefix = Virtual/
> >   separator = /
> > }
> > passdb {
> >   args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
> >   driver = sql
> > }
> > passdb {
> >   args = user=%Ln noauthenticate
> >   driver = static
> >   skip = authenticated
> > }
> > passdb {
> >   args = failure_show_msg=yes session=yes max_requests=20
> >   driver = pam
> >   skip = authenticated
> > }
> > plugin {
> >   fts = solr
> >   fts_autoindex = yes
> >   fts_solr = url=http://thebighonker.lerctr.org:8983/solr/dovecot/
> >   fts_tika = http://localhost:9998/tika/
> >   imapsieve_mailbox1_before = file:/usr/local/share/dovecot-
> > pigeonhole/sieve/report-spam.sieve
> >   imapsieve_mailbox1_causes = COPY
> >   imapsieve_mailbox1_name = SPAM
> >   imapsieve_mailbox2_before = file:/usr/local/share/dovecot-
> > pigeonhole/sieve/report-ham.sieve
> >   imapsieve_mailbox2_causes = COPY
> >   imapsieve_mailbox2_from = SPAM
> >   imapsieve_mailbox2_name = *
> >   imapsieve_url = sieve://thebighonker.lerctr.org
> >   mail_log_events = delete undelete expunge copy mailbox_delete
> > mailbox_rename flag_change append
> >   mail_log_fields = uid box msgid size from subject vsize flags
> >   recipient_delimiter = +
> >   sieve = ~/.dovecot.sieve
> >   sieve_dir = ~/sieve
> >   sieve_execute_bin_dir = /usr/local/share/dovecot-pigeonhole/sieve
> >   sieve_extensions = +editheader +vacation-seconds +mboxmetadata
> > +servermetadata
> >   sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute
> >   sieve_pipe_bin_dir = /usr/local/share/dovecot-pigeonhole/sieve
> >   sieve_plugins = sieve_imapsieve sieve_extprograms
> >   stats_command_min_time = 1 mins
> >   stats_domain_min_time = 12 hours
> >   stats_ip_min_time = 12 hours
> >   stats_memory_limit = 16 M
> >   stats_refresh = 5s
> >   stats_session_min_time = 15 mins
> >   stats_track_cmds = yes
> >   stats_user_min_time = 1 hours
> > }
> > protocols = imap pop3 lmtp sieve
> > service auth {
> >   unix_listener auth-client {
> > mode = 0666
> >   }
> >   unix_listener auth-master {
> > mode = 0666
> >   }
> > }
> > service doveadm {
> >   inet_listener http {
> > port = 8080
> > ssl = yes
> >   }
> > }
> > service 

Re: STARTTLS issue with sieve

[Roger Klorese]

But if it won’t trust that copy, that invalidates the chain, right?

On Sun, Jul 9, 2017 at 9:48 AM Heiko Schlittermann 
wrote:

> Alexander Dalloz  (So 09 Jul 2017 13:14:56 CEST):
> …
> > It is wrong to send the root CA along with the intermediate and server
> > certificates. The root CA cert must be in the CA trust bundle of the
> client.
>
> I wouldn't say it is wrong. But it should be useless, as the client
> wont trust the root CA it received. The client should trust only its
> copy of the root CA.
>
> Best regards from Dresden/Germany
> Viele Grüße aus Dresden
> Heiko Schlittermann
> --
>  SCHLITTERMANN.de  internet & unix support -
>  Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
>  gnupg encrypted messages are welcome --- key ID: F69376CE -
>  ! key id 7CBF764A and 972EAC9F are revoked since 2015-01  -
>

Moving from CentOS to GF RPMs

[Roger Klorese]

Does anyone have fool-proof documentation for this fool on how to configure
repos and what operations to perform to move from the distro RPMs to the GF
ones without breaking stuff?

Re: Clamping down on mailbox sizes...

[Roger Klorese]

I'd take the opposite approach and tell them no new mail will be received
until they are under quota.
On Tue, Jan 24, 2017 at 4:52 PM SH Development 
wrote:

> I don’t want to do this for all users….but…
>
> I have a few users who insist that they use their mailboxes regularly and
> don’t want it cancelled.  Fine.  But they won’t clean them out either.
>
> What steps would you all recommend for setting quotas on some users but
> not others?
>
> Specifically starting out with identifying WHICH accounts have excessive
> amounts of crap in them, by age, then sending them a notice stating they
> are going to get limited, then deleting mail older than x number of days if
> they don’t do it themselves by a certain time frame...
>
> Thoughts?
>
> Jeff

Re: Relative home path not allowed - but how is this relative?

[Roger Klorese]

Never mind - query was a little screwed up...!

Got it now. Thanks.

On Sat, Jan 21, 2017 at 5:33 PM, Roger Klorese <rogerklor...@gmail.com>
wrote:

> I just set up my server with MySQL support for
> authentication/authorization compatible with Postfix Admin.
>
> Initially, I was getting the "Relative home directory paths not supported"
> message, and it's easy to see why - Postfix Admin stores the maildir as
> "$domain/$userpart@$domain".
>
> But the directories in 10-mail.conf are set as
>
> mail_location = maildir:/home/mailboxes/%d/%u
> mail_home = maildir:/home/mailboxes/%d/%u
>
> ...and the user_query has been revised to:
>
> user_query = SELECT concat('/home/mailboxes/', maildir) as full_maildir
> FROM mailbox WHERE username = '%u';
>
> ...so how are any of these relative paths?
>

Relative home path not allowed - but how is this relative?

[Roger Klorese]

I just set up my server with MySQL support for authentication/authorization
compatible with Postfix Admin.

Initially, I was getting the "Relative home directory paths not supported"
message, and it's easy to see why - Postfix Admin stores the maildir as
"$domain/$userpart@$domain".

But the directories in 10-mail.conf are set as

mail_location = maildir:/home/mailboxes/%d/%u
mail_home = maildir:/home/mailboxes/%d/%u

...and the user_query has been revised to:

user_query = SELECT concat('/home/mailboxes/', maildir) as full_maildir
FROM mailbox WHERE username = '%u';

...so how are any of these relative paths?