Home Forums OS X Server and Client Discussion Mail Postfix and netinfo == recipient_delimiter won’t work?

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #358954
    Pascal
    Participant

    I tried to make use of Mail Address Extensions and set (as per default) the recipient delimiter to ‘+’:

    postconf recipient_delimiter
    recipient_delimiter = +

    Unfortunately this does not make things work 🙁

    I suspect this is because of the combination of postfix and netinfo — but just a guess…

    Has anybody had more success with this?

    Pascal

    #359311
    Pascal
    Participant

    BTW: It is indeed *not* Postfix, as it will forward mail with recipient delimiters to Mailman without problems. Which is very handy if you intend to upgrade Mailman from 2.1.2 to 2.1.5.

    #359317
    Pascal
    Participant

    In another attempt — and because I thought it could be a deliver-related problem — I set:

    mailbox_transport = lmtp:unix:/var/imap/socket/lmtp

    Postfix seems to talk directly to Cyrus via LMTP now, bypassing the deliver program. Though this does work as usual, it does not enable address extensions in Cyrus either… 🙁

    Anyone has any other ideas?

    #362216
    dmkash
    Participant

    I did finally find the answer. In our case it was Postfix that was rejecting the e-mail because it didn’t recognize the user “postuser+info” or whatever.

    To solve this, I created a file in /etc/postfix named local_recipients_regexp with this regular expression: /^[email protected]/i OK and added this file to the local_recipient_maps in Postfix. See below:

    postconf local_recipient_maps
    local_recipient_maps = proxy:unix:passwd.byname regexp:/etc/postfix/local_recipients_regexp $alias_maps

    This tells postfix that addresses with a + in them can be accepted. Once Postfix accepted the e-mails, they were delivered to the shared folders correctly. Note that I had to also set postuser in /etc/imapd.conf.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.

Comments are closed