similar to: Bug with latest GCC 9

On 1/25/19 8:24 PM, Stephan Bosch wrote: > > > Op 25/01/2019 om 10:59 schreef Martin Li?ka: >> Hi. >> >> As mentioned here: >> https://bugzilla.opensuse.org/show_bug.cgi?id=1123136 >> >> there's a new issue with GCC 9, it's related to: >> https://gcc.gnu.org/gcc-9/porting_to.html#complit >> >> in: >> /* Not const! Never

Op 25/01/2019 om 10:59 schreef Martin Li?ka: > Hi. > > As mentioned here: > https://bugzilla.opensuse.org/show_bug.cgi?id=1123136 > > there's a new issue with GCC 9, it's related to: > https://gcc.gnu.org/gcc-9/porting_to.html#complit > > in: > /* Not const! Never return this as a result directly! */ > #define SMTP_ADDRESS_LITERAL(localpart, domain) \ >

On 25/04/2019 12:52, Martin Li?ka via dovecot wrote: > On 1/25/19 8:24 PM, Stephan Bosch wrote: >> >> Op 25/01/2019 om 10:59 schreef Martin Li?ka: >>> Hi. >>> >>> As mentioned here: >>> https://bugzilla.opensuse.org/show_bug.cgi?id=1123136 >>> >>> there's a new issue with GCC 9, it's related to: >>>

Hello! I'm having crashes with LMTP delivery when user is over quota on the latest CentOS 7.4 with the latest Dovecot 2.3.0.1 from Dovecot repo. I see the issue has been fixed on January 17, but it doesn't seem to have made it into 2.3.0.1 (I compared with the source from https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz).

Hi, These warnings are included by default with -Wall in GCC 4.6 [1], and LLVM should support them instead of throwing -Wunknown-warning-option. [1]: http://gcc.gnu.org/gcc-4.6/porting_to.html Thanks.

Using gcc 4.9 to build the llvm 3.4 branch fails with the following error: llvm[1]: Compiling APFloat.cpp for Release build [...] /usr/lib64/gcc/x86_64-unknown-linux-gnu/4.9.0/../../../../include/c++/4.9.0/cstddef:51:11: error: no member named 'max_align_t' in the global namespace using ::max_align_t; ~~^ gcc 4.8.2's caused no such issue, so it must be a change in

I would like to define some constants that I can use across models and views and I cannot figure out how to do that. Googling hasn''t turned up anything useful and I''m looking at the PickAxe book, and I get the impression that a constant must belong to a class. If I just want a constant like... CompanyPhoneNo = "(602) 999-9999" and be able to use it in any view

Hi, I have another sieve question, this time about setting variables. I join a lot of mailing lists at ietf.org. I thought it'd be handy to filter these all into a common folder and then into individual folders, without having to configure each mailing list independently. So wrote this (this is just a part, obviously): require ["envelope", "variables",

I have read through http://wiki.dovecot.org/Quota/Dict, which suggests a database schema for using quota. For 1.2, this includes a username, bytes and messages. Is there any way to modify the queries used to split out username into localpart and domain? This would enable me to put the current quota information in my main mailbox table and display it to users in my admin interface. Or

I use recipient_delimiter addresseses quiet a bit, and I want to put several of them into a mailbox if anyof (header :contains ["to"] [ ?FOO", ?foo", ?bar", ?florin"]) { fileinto :create ?later"; stop; } When I get an email addressed to me+FOO at example.com or me_florin at example.com, the messages end up in my inbox (Yes, I have both + and _

First of all, you can probably go online before you convert all passwords. You can modify your query in dovecot-sql.conf.ext to something like the following: SELECT IF(crypt_pass IS NULL OR crypt_pass='', CONCAT('{PLAIN}',plain_pass), crypt_pass) as password FROM mailuser .. This is assuming that: * for incoming users, you have a plain_pass column containing just the plaintext

Hi, I've set up 2 servers with dovecot 2.2.9 using maildir using structure: /var/maildir/domain/localpart Server A: mx1.xxx.de Server B: mx2.xxx.de Mails are delivered to dovecot only on server A by exim4/dovecot deliver replication to Server B works immediatelly: mark mail as read on server A, mail is marked as read on server B. BUT: when i mark a mail as read on Server B, noting

( previous thread at http://www.syslinux.org/archives/2015-January/023050.html ) > > <info from="web interface mailman" extra_from="backend mailinglist software"> > dmarc_moderation_action Option > dmarc_moderation_action (privacy): Action to take when anyone posts > to the list from a domain with a DMARC Reject/Quarantine Policy. > >

Hi, I have an OpenSMTPD / Dovecot installation on an OpenBSD server. I recently came across an issue where Dovecot LMTP would reject a message sent to a local user from an address which contains a single apostrophe (e.g. firstname.o'lastname at example.com). Apparently apostrophe, as well as a number of other special characters, are valid characters in the local part of the email address

I have a rule that sends all mail from root to a mailbox, but I want it to NOT send mail from mailing-lists there. if allof (address :contains :localpart "From" "root", not anyof(exists ["List-Id","List-ID","Mailing-List", "X-List-Name","List-Post"])) { fileinto "root-mail"; stop; }

Hi all, a dsync failed due a corrupted mdbox file. Force-resync throws the same error. (Dovecot 2.3.9.2) Is there any change to fix/repair the file? dsync-local(LOCALPART at DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning: fscking index file /var/mail/12/DOMAIN.TLD/242/LOCALPART/mdbox/storage/dovecot.map.index dsync-local(LOCALPART at DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning:

Hi, we are using dovecot IMAP in a complex virtual setup with almost 4000 accounts; postfix hands over to deliver for local delivery into a home directory as stored in the SQL database. That's /srv/vmail/$DOMAIN/$LOCALPART for most of them, but I'd rather not hardcode this scheme anywhere as it's in SQL. By a policy change, we need to insert a filter in this chain and the filter must

Hello > GCC versions listed here are known to not work. If you are using one of > these versions, please try to upgrade your GCC to something more recent. > If you run into a problem with a version of GCC not listed here, please > let us know. Please use the "gcc -v" command to find out which version > of GCC you are using. This is not true. GCC is not broken. 1. You

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.2. You will need this release for Dovecot v2.3.2, because the previous v0.5.1 release will not work. No changes were performed since the release candidate. Much like version 0.4.24 for Dovecot v2.2, this release consists mostly of fixes that accumulated over the last few months. Beyond that, this release

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.2. You will need this release for Dovecot v2.3.2, because the previous v0.5.1 release will not work. No changes were performed since the release candidate. Much like version 0.4.24 for Dovecot v2.2, this release consists mostly of fixes that accumulated over the last few months. Beyond that, this release