similar to: recipient_delimiter

On 15/03/2020 21:26, GMX Account wrote: > have a look at this: > > http://www.postfix.org/postconf.5.html#recipient_delimiter > > [...]When the recipient_delimiter [1] set contains multiple characters > (Postfix 2.11 and later), a user name or .forward file name is > separated from its extension by the first character that matches the > recipient_delimiter [1] set.[...]

On 15/03/2020 20:26, Peter wrote: > Poorly documented, imo, but you want lmtp_save_to_detail_mailbox = yes: Thanks, tried it, but no, that's not what I want and it doesn't help in my case. To recap: If I set recipient_delimiter to "+-" (or "-" alone), having a user named "foo-bar" won't work anymore, because Dovecot always tries to deliver to user

I see no documents in the Dovecot documents wiki on how Dovecot features can be used in the fight against spam. One hit came up in a search, and it was about how to fight spam in the MoinMoin Wiki itself (e.g. TextCHAs and such). I already asked in another thread about removing message files at the search from a designated "learn-spam" folder. My next question would be how to

I'm setting up a Postfix and Dovecot combination. What I want to do is have a user database that (1) is not running from some engine (so not LDAP or SQL or such) ... and (2) is completely disassociated from system users (e.g. most email users are not in /etc/passwd and most /etc/passwd users are not email users). Ideal would be a one-file solution, which can be managed by text editing or

I'm looking for an IMAP testing tool, suitable to use with Dovecot IMAP. It needs to support TLS, STARTTLS, and login/authentication. It needs to be able run from command line, shell scripts, and even do so under cron jobs (e.g. a way to supply the password to use w/o a terminal prompt). Typical interactive mail clients just don't cut it (even the text mode ones). One reason is I need

I have this in dovecot-postfix.conf: mail_location = maildir:/home/mail/dnamesum=%12MLd/dname=%Ld/unamesum=%12MLn/uname=%Ln/mail Yes, it is excessive, but that's just for testing. The pattern I really want is less clear for debugging. In postfix/main.cf I have: mailbox_command = /usr/lib/dovecot/deliver -c /etc/dovecot/dovecot-postfix.conf -a "${RECIPIENT}" I verified through

On 22-11-19 22:48, Ralph Seichter via dovecot wrote: > * Robert via dovecot: > >> We use a simple system for routing emails to different email users by >> postfixing the addresses with the actual user: xxxJohn at domain; >> yyyJohn at domain etc all will be delivered to user John. >> (This way John can invent a new email address on-the-fly and that will >> be

I suspect this is a user agent issue, given that Evolution is flaky in so many areas. When I deliver mail to a subfolder/subbox (e.g. the -m option in the deliver command), and Evolution doesn't know of it, yet, creating it fails, and Evolution still can't get to it. Doing things the other way around (create it in Evolution first, then deliver to it) works fine. Seems to be silliness to

Hi, I have some trouble to use dovecot as MDA. I followed the instructions in http://wiki.dovecot.org/LDA and http://wiki.dovecot.org/LDA/Postfix I have multiple virtual users, stored in a LDAP server, and it look like postfix is still delivering the mails directly to the maildirs. Dovecot version : 1.2.15 (using the 1:1.2.15-4 squeeze packets) postfix version : 2.7.1 (using the 2.7.1-1

Can I enable $recipient_delimiter = ?+? for only the virtual sql users? $ doveconf -n # 2.2.5: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.1-RELEASE i386 auth_mechanisms = PLAIN LOGIN disable_plaintext_auth = no first_valid_uid = 89 login_log_format_elements = user=<%u> %r %m %c mail_location = maildir:~/Maildir mail_max_userip_connections = 90 managesieve_notify_capability =

Is there a tool equivalent to the system "passwd" command (or maybe "adduser" or "useradd") that can support a passwd-file by setting a password, encrypting it with the salted MD5 scheme? The system "passwd" command doesn't have an option to "do it to this alternate file instead of /etc/shadow".

Hi, It would be nice if the recipient_delimiter configuration option supported multiple recipient delimiters as Postfix now does. e.g. now if I set: recipient_delimiter = +- in Postfix, then test-extension at sample.com and test+extension at sample.com are both recognized. But if I set: recipient_delimiter = +- in Dovecot, neither of the above are recognized and instead test+-extension at

I'm getting this message, which looks like Postfix is the one logging it, but I don't know where it comes from or which configuration it needs to be placed in. Anyone know what this means? May 26 13:13:28 eth0 postfix/pipe[13821]: warning: pipe flag `D' requires dovecot_destination_recipient_limit = 1

Am 2019-09-20 12:06, schrieb Randal, Phil: > When I migrated our mx boxes from CentOS 5 to 7 I made the leap to > postfix. > > I built a test server with postfix etc on it and threw everything I > could think of at it before going live. > > The key is, like in learning a new language, to start thinking in > postfix terms instead of thinking in sendmail terms. Exactly, I

Hello, does the recipient_delimiter option accepts multiple delimiter by now? -- Regards J?rg Backschues

Hi, we're using thunderbird as our client, it has the functionality to sort spamassassin tagged mails in a folder called 'Junk'. I have this folder on my dovecot server and i'd like to use the recipient_delimiter feature to get my spam/junk mails directly to this folder. what i have done yet: dovecot.conf: plugin { recipient_delimiter = + } postfix: master.cf dovecot

Ave Maria! I have Dovecot and Postifx setup with MySQL - emails seem to go through the server but for some reason the pipe into the wrong Virtual Domain any ideas? Also I notice If you need any other configurations please let me know... mail.info logs: Apr 12 13:30:14 Server1 postfix/smtpd[21411]: connect from mail-qe0-f48.google.com[209.85.128.48] Apr 12 13:30:14 Server1

Hi, have a look at this: http://www.postfix.org/postconf.5.html#recipient_delimiter [...]When the recipient_delimiter [1] set contains multiple characters (Postfix 2.11 and later), a user name or .forward file name is separated from its extension by the first character that matches the recipient_delimiter [1] set.[...] --- Original Nachricht --- Betreff:?Re: lmtp and recipient_delimiter

On Sonntag, 15. M?rz 2020 21:43:08 CET Juri Haberland wrote: > On 15/03/2020 21:26, GMX Account wrote: > > have a look at this: > > > > http://www.postfix.org/postconf.5.html#recipient_delimiter > > > > [...]When the recipient_delimiter [1] set contains multiple characters > > (Postfix 2.11 and later), a user name or .forward file name is > >

I'm currently running postfix + dovecot, with virtual users In postfix I have set recipient_delimiter = + so that postfix accepts mail for user at example.com, user+foo at example.com, and user+spam at example.com all deliver to inbox. what I would like is to have email directed to user+foo at example.com delivered to the IMAP folder foo (and, in the context of amavisd, have amavis