janooo 's Profile

Now imagine what happens when Postfix receives an email for 'john@example.com'.
Postfix will first check if there are any aliases in the virtual_alias_maps
table. It finds the catchall entry as above and since there is no more specific
alias the catchall account matches and the email is redirected to
'kerstin@gmail.com'. This is probably not what you wanted. So you would need to
make the table rather look like this:

More specific aliases have precedence over general catchall aliases. Postfix
will find an entry for 'john@example.com' first and find that email should be
"forwarded" to 'john@example.com' - the same email address. This trickery may
sound weird but it is needed if you plan to use catchall accounts. So the
virtual_alias_maps mapping must obey both the "view_aliases" view and this
"john-to-himself" mapping. Create a cf file
/etc/postfix/mysql-email2email.cf for the latter mapping:

user = mailuser
password = mailuser2007
hosts = 127.0.0.1
dbname = mailserver
query = SELECT email FROM view_users WHERE email='%s'

Did the trick

How the comparison services make their money could have a bearing on the user experience. The sites receive upfront fees or retainers from the insurers they list, but they will also earn commission for sales or even just "clicks".

"Some comparison websites are paid by insurers according to the number of clicks they receive, regardless of whether a sale is made," says James Harrison, chief executive of comparison site Insurancewide. The distinction is important, he adds, because if a site is paid per click, there is less pressure to match consumers with the right deal for them.

Semantic meaning and sharing fields between content types

One of the primary goals of CCK is that the fields have semantic meaning. What does this mean? It means that a field called "Age", while being in principle identical in nature to a field called "Number of toes you have", is intended to convey a different meaning. Both fields store data as an integer. Both should be configured to only allow positive numbers. Age, however, should always be understood to refer to the length of time something has existed and the number of toes you have, while still a number, should be understood to have a totally different meaning.

Furthermore, it is often the case that a particular field with a particular semantic meaning needs to be used for more than one content type. For example, a content type called "Person" may have an Age field, and a content type called "Animal" may also have an Age field. Semantically, these fields should have the same meaning. CCK solves this problem by letting you use existing fields with any number of content types

Making arguments be passed by reference

By default, function arguments are passed by value (so that if
the value of the argument within the function is changed, it does
not get changed outside of the function). To allow a function to modify its
arguments, they must be passed by reference.

To have an argument to a function always passed by reference, prepend an
ampersand (&) to the argument name in the function definition:

• Hi,

  
  

  I may be looking at this in the wrong way, so please correct me if I am, but this seems like it should be very simple to me:

  
  

  I would create a new content type, called University Degree. Then I would add the 4 required fields (Year, Type, Degree & School) as standard CCK fields, using whatever combination of select boxes or text boxes you require. There is no reason to use taxonomy for any of this data.

  
  

  Then, each user can create an unlimited number of University Degree’s (in practice this will obviously only be 1 or 2 each).

  
  

  Using Views, you could very easily create a list of each user’s degrees or any other list based on any of the 4 fields.

  
  

  I’m sorry if I’ve mis-understood your requirements, but this type of approach has always worked for me.

  
  

  Ian

  
  
  
  
  
•