Afficher un message
Vieux 23/05/2007, 23h53   #13
Per Hedeland
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Invalid route address when using COMMA in aliases

In article <1179917531.110539.49910@p47g2000hsd.googlegroups. com>
gagnon.sylvain@gmail.com writes:
>On May 22, 5:35 pm, p...@hedeland.org (Per Hedeland) wrote:
>>
>> Is it google that deletes spaces adjacent to the word "sendmail" or is
>> it something you're doing? Just curious.:-)

>
>Don't know. If it's me, it's by mistake.


Weird. And it happened again - it's only in the quoted text in your
followups:

>> >Here's thesendmail.mc used to create the .cf file:


>> So you're doing alias lookups from the rulesets and simply using the
>> result (if any) - that won't work, with precisely the result you're
>> seeing. The ruleset processing is strictly one-address-at-a-time,
>> there's no way they can deal with the potential one-to-many mapping that
>> aliases provides.


>Is there something I can do? What we have sendmail doing is taking a
>employee_name@lacitec.on.ca and changing it to
>employee_name@email.lacitec.on.ca (employee name) and
>9999999@lacitec.on.ca (student number) and changing it to
>9999999@nims.lacitec.on.ca (that's why the rule for starting with a
>digit). The name is then checked against the alias file (but I believe
>it could be checked above instead with no harm done) and then against
>our ldap server to see if it's valid account before even sending it so
>our mail server need to do spam/virus for nothing.


If you're just doing an "existence check", you should use -m in the map
definitions, see doc/op/op.*.

--Per Hedeland
per@hedeland.org
  Réponse avec citation
 
Page generated in 0,05252 seconds with 9 queries