1 |
On Wednesday 09 September 2009 16:56:28 Xavier Parizet wrote: |
2 |
> J. Roeleveld a écrit : |
3 |
> > On Wednesday 09 September 2009 14:49:37 Xavier Parizet wrote: |
4 |
> >> J. Roeleveld a écrit : |
5 |
> >>> On Wednesday 09 September 2009 14:19:45 Xavier Parizet wrote: |
6 |
> >>>> J. Roeleveld a écrit : |
7 |
> >>>>> Hi All, |
8 |
> >>>>> |
9 |
> >>>>> I know this is probably off-topic, but I'm hopefull someone on this |
10 |
> >>>>> list knows how to do this. |
11 |
> >>>>> |
12 |
> >>>>> My current situation: |
13 |
> >>>>> Postfix gets an email delivered for user X |
14 |
> >>>>> Postfix passes this to cyrus (lmtp-transport) |
15 |
> >>>>> if user X does not exist within cyrus, the email gets bounced. |
16 |
> >>>>> |
17 |
> >>>>> I would like this bounced email to be delivered to a seperate cyrus |
18 |
> >>>>> email folder. |
19 |
> >>>>> |
20 |
> >>>>> I tried to find the answer on google, but all the solutions I found |
21 |
> >>>>> either only work with the postfix local delivery agent (eg. not |
22 |
> >>>>> compatible with cyrus) or requires a list to be maintained using all |
23 |
> >>>>> the known email-boxes. |
24 |
> >>>>> |
25 |
> >>>>> I prefer a fall-back solution where an email directed at a user not |
26 |
> >>>>> listed in either the alias table (stored in ldap) or not known to |
27 |
> >>>>> cyrus is redirected to a specific cyrus mailbox. |
28 |
> >>>> |
29 |
> >>>> A solution could be doing a catch-all alias (see [1]) : |
30 |
> >>>> if your domain is example.com, then add an alias mapping @example.com |
31 |
> >>>> to oneaddress@×××××××.com either using virtual alias or |
32 |
> >>>> /etc/postfix/aliases . |
33 |
> >>>> |
34 |
> >>>> HTH. |
35 |
> >>>> |
36 |
> >>>> [1] http://www.postfix.org/VIRTUAL_README.html |
37 |
> >>> |
38 |
> >>> I did notice this option, but it would require me to duplicate the |
39 |
> >>> alias table into a alias file. I tried setting a "@<domain>" entry in |
40 |
> >>> my ldap-tree, but this did not work. |
41 |
> >> |
42 |
> >> If you use LDAP as a virtual backend, then [1] will then be a better |
43 |
> >> place to look. Setting mailacceptinggeneralid ldap attribute to |
44 |
> >> @<domain> seems to be the solution (if you use "standard" LDAP scheme). |
45 |
> >> |
46 |
> >> HTH. |
47 |
> >> |
48 |
> >> [1] http://www.postfix.org/LDAP_README.html#example_virtual |
49 |
> > |
50 |
> > I tried this, but when looking at the ldap logs, I notice that the |
51 |
> > 'domain' part does not exist in the search string. |
52 |
> > Eg. '%s' only shows the user, '%d' is empty, eg. query is ignored |
53 |
> > |
54 |
> > Does anyone know how I can force postfix to add the domain to the search |
55 |
> > query? |
56 |
> |
57 |
> Is mydomain parameter set in /etc/postfix/main.cf ? |
58 |
|
59 |
Yes, I believe this is necessary for postfix to actually accept emails? |
60 |
|
61 |
Or how else do I get this configured? |
62 |
|
63 |
Thanks, |
64 |
|
65 |
Joost |