From: Xavier Parizet <xav@gentooist.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Catch all mailbox
Date: Wed, 09 Sep 2009 16:56:28 +0200 [thread overview]
Message-ID: <4AA7C21C.3020905@gentooist.com> (raw)
In-Reply-To: <200909091650.21773.joost@antarean.org>
[-- Attachment #1: Type: text/plain, Size: 2413 bytes --]
J. Roeleveld a écrit :
> On Wednesday 09 September 2009 14:49:37 Xavier Parizet wrote:
>> J. Roeleveld a écrit :
>>> On Wednesday 09 September 2009 14:19:45 Xavier Parizet wrote:
>>>> J. Roeleveld a écrit :
>>>>> Hi All,
>>>>>
>>>>> I know this is probably off-topic, but I'm hopefull someone on this
>>>>> list knows how to do this.
>>>>>
>>>>> My current situation:
>>>>> Postfix gets an email delivered for user X
>>>>> Postfix passes this to cyrus (lmtp-transport)
>>>>> if user X does not exist within cyrus, the email gets bounced.
>>>>>
>>>>> I would like this bounced email to be delivered to a seperate cyrus
>>>>> email folder.
>>>>>
>>>>> I tried to find the answer on google, but all the solutions I found
>>>>> either only work with the postfix local delivery agent (eg. not
>>>>> compatible with cyrus) or requires a list to be maintained using all
>>>>> the known email-boxes.
>>>>>
>>>>> I prefer a fall-back solution where an email directed at a user not
>>>>> listed in either the alias table (stored in ldap) or not known to cyrus
>>>>> is redirected to a specific cyrus mailbox.
>>>> A solution could be doing a catch-all alias (see [1]) :
>>>> if your domain is example.com, then add an alias mapping @example.com to
>>>> oneaddress@example.com either using virtual alias or
>>>> /etc/postfix/aliases .
>>>>
>>>> HTH.
>>>>
>>>> [1] http://www.postfix.org/VIRTUAL_README.html
>>> I did notice this option, but it would require me to duplicate the alias
>>> table into a alias file. I tried setting a "@<domain>" entry in my
>>> ldap-tree, but this did not work.
>> If you use LDAP as a virtual backend, then [1] will then be a better place
>> to look. Setting mailacceptinggeneralid ldap attribute to @<domain> seems
>> to be the solution (if you use "standard" LDAP scheme).
>>
>> HTH.
>>
>> [1] http://www.postfix.org/LDAP_README.html#example_virtual
>
> I tried this, but when looking at the ldap logs, I notice that the 'domain'
> part does not exist in the search string.
> Eg. '%s' only shows the user, '%d' is empty, eg. query is ignored
>
> Does anyone know how I can force postfix to add the domain to the search query?
Is mydomain parameter set in /etc/postfix/main.cf ?
> Thanks,
>
> Joost
>
--
Xavier Parizet
YaGB : http://gentooist.com
GPG : C7DC B10E FC21 63BE
B453 D239 F6E6 DF65 1569 91BF
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2009-09-09 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 11:54 [gentoo-user] Catch all mailbox J. Roeleveld
2009-09-09 12:19 ` Xavier Parizet
2009-09-09 12:40 ` J. Roeleveld
2009-09-09 12:49 ` Xavier Parizet
2009-09-09 14:50 ` J. Roeleveld
2009-09-09 14:56 ` Xavier Parizet [this message]
2009-09-09 15:00 ` J. Roeleveld
2009-09-09 18:06 ` Xavier Parizet
2009-09-09 19:23 ` Stroller
2009-09-09 20:02 ` Xavier Parizet
2009-09-10 6:26 ` J. Roeleveld
2009-09-09 12:26 ` Neil Bothwick
2009-09-09 12:36 ` J. Roeleveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AA7C21C.3020905@gentooist.com \
--to=xav@gentooist.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox