Are you sure the majordomo 1.94.5 that you patched with restrict2domain
is the same majordomo that sendmail is using via the aliases file?
Dan Liston
Derivas, Eduardo V wrote:
> When I applied the restrict2domain patch to Majordomo, version 1.94.5, these line where added to majordomo.pl:
>
> if ($file =~ /\@/) { # Is the resticted string an email?
> $subdomain = $subscriber; # Is the resticted string a domain?
> $subdomain =~ s/^[^\@]+// if $file =~ /^\@/;
> if (&main'addr_match($subdomain, $file,
> (&main'cf_ck_bool($clean_list,"mungedomain") ? 2 : undef))) {
> $matches++;
> }
> return($matches);
> }
> These were the only lines that are different from the orgininal majordomo.pl.
>
> I am the owner of test-list and I sent email from my Exchange account account on my PC to the Majordomo test-list on the UNIX mail server. I get this message back from Majordomo:
> MAJORDOMO WARNING (mj_resend)!!
>
> Can't read /acct/majordom/majordomo-1.94.5/lists/@boeing.com: No such file or directory
>
> My test-list.config file has the following entry:
>
> restrict_post = @boeing.com
>
> If I use a file instead and list all the emails that can post to this lists it works fine.
>
> When I restrict_post to read:
> restrict_post = eduardo.v.derivas@boeing.com
>
> And I got this message after I sent mail to test-list from my PC:
>
> Can't read /acct/majordom/majordomo-1.94.5/lists/eduardo.v.derivas@boeing.com: No such file or directory
>
> When I change it to read:
> restrict_post = eduardo.v.derivas@boeing.com:evd6134@p16.iasl.ca.boeing
> and test it again, I get two messages:
> Can't read /acct/majordom/majordomo-1.94.5/lists/eduardo.v.derivas@boeing.com: No such file or directory
> ------
> Can't read /acct/majordom/majordomo-1.94.5/lists/evd6134@p16.iasl.ca.boeing.com: No such file or directory
>
> Thanks,
>
> Ed
> -----Original Message-----
> From: Deb [mailto:deb@tickleme.llnl.gov]
> Sent: Friday, June 13, 2003 2:01 PM
> To: Majordomo Users
> Subject: Re: taboo_headers problem..: restrict2domain
>
>
> Use it all the time. It would be helpful to see how you configured
> restrict_post. Can you copy/paste and send it to us?
>
> What did you do to test it?
>
> You can set restrict_post to eduardo.v.derivas@boeing.com, then see if you can
> post from a different address as well as your own.
>
> If you still have the same problem, how you applied the patch may need to be
> investigated. Also, the fellow who wrote the patch is on the list, so perhaps
> he has more helpful suggestions.
>
> deb
>
> Derivas, Eduardo V <eduardo.v.derivas@boeing.com> had this to say,
>> I applied this patch and did tried it, but it did not work for me. Majordomo was looking for a list called @companydomain.com. Has anyone had success with this patch?
>>
>> Ed
>>
>> -----Original Message-----
>> From: Daniel Liston [mailto:dliston@sonny.org]
>> Sent: Friday, June 13, 2003 12:14 PM
>> To: R Deepak
>> Cc: majordomo-users@greatcircle.com
>> Subject: Re: taboo_headers problem..: restrict2domain
>>
>>
>> The patch will allow you to use syntax such as;
>>
>> restrict_post = @lantana.tenet.res.in
>>
>> Anyone that attempts to write to your list from
>> any other domain will cause a bounce to the list
>> owner or moderator.
>>
>> I do not believe it allows for the same syntax
>> within a file defined on the restrict_post line.
>>
>> Dan Liston
>>
>> R Deepak wrote:
>> > - Check out this patch ...
>> > -
>> > - ftp://ftp.ccsf.org/majordomo-patches/1.94.5/restrict2domain.1
>> > -
>> >
>> > Doesn't seem to.
>> >
>> > After applying the patch, I set restrict_post to
>> >
>> > --
>> > restrict_post = all.restrict
>> > --
>> >
>> > all.restrict is a file in the lists directory.
>> >
>> > Contents of all.restrict
>> >
>> > ---
>> > @lantana.tenet.res.in
>> > ---
>> >
>> > It still bounces the message. I put in a \@lantana.tenet.res.in
>> > and checked too!
>> >
>> > Deepak
>>
>>
>
References:
|
|
