Re: VIM
Charl Matthee wrote: > > On Tue Sep 18 2001 at 10:38:57AM +0200 'Craig' <[EMAIL PROTECTED]> wrote: > > > Need to do an extended find and replace with VIM, anyone > > know the syntax for me ? I have a really long named.conf > > file I need to modify ... > > :%s/thing_to_find/thing_to_replace/gc > > g: global > c: check with operator before substituting > > If you need to find and replace over multiple lines I suggest you rather > use a little perl script. maybe if you want to script, you can use the -s option of vim cat < EOF > cmd.file :1,$s/thing_to_find/thing_to_replace/ :wq EOF vim -s cmd.file named.conf regards hugh > > Ciao > > Charl > __ > >Making reality real since 1974. > __ > > [ Charl Matthee ] [ +27-11-721-3800 ] > [ Reality Manufacturing ] [ +27-11-405-6508 ] > __ > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SMTP commands
Maybe you can find some usefull information in the RFC1425 and RFC1854 http://www.faqs.org/rfcs/rfc1425.html http://www.faqs.org/rfcs/rfc1854.html regards H Paul Casey wrote: > > Hi there, > I am looking for a website or some kind of reference site where i can find > the commands used while > Telneted into a SMTP port. > Mail RCPT > Data > etc > etc > > if someone could help me i would appreciate it. > > thanks > Paul > > > Paul Casey (QBE, AFLA, BYU, MCP, A+) > Technical Adminstrator > T-Sol (Pty) Ltd. > [EMAIL PROTECTED] > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Routing problem.
Hello, For your problem you maybe can solve it with a arp publication on box2 ? eg: ARP -i fxp0 -Ds 213.219.39.198 fxp1 pub Friedrich Clausen wrote: > > Greetings all, > > I will try and make myself as clear as possible so please excuse my poor ascii > picture but it seems to help explanations better. I hope this question is > appropriate for the list but I dont know where else to ask. First I will give > some info : > > Internet >| > Router >| >| > --- > | tl0|- --- > | Box2||Hub|--|eth0 Box3| > | fxp1fxp0|- --- > --- | > / | | > / | | >/ --- > / > / >- >|Hub|--- >- | > | | > | | > | | >-- >|eth0 Box1 eth1| >-- > > Networks Involved : 192.168.1.0/24 > 213.219.39.192/29 > 213.219.39.196/29 > 213.219.39.200/28 > > Router - 213.219.39.193 > > Box1 - Debian Linux workstation > eth0 : 192.168.1.92 > > Box2 - OpenBSD gateway > fxp0 : 192.168.1.50 > fxp1 : 213.219.39.204 > alias : 213.219.39.197 > tl0 : 213.219.39.194 > > Box3 - Debian Linux Server > eth0 : 213.219.39.202 > eth1 : 213.219.39.198 > > The problem is I cannot ping 213.219.39.198 from anywhere other than Box2 or > Box1. However I can ping 213.219.39.202 from anywhere. At first I thought that > it was because eth1 did not have a default route but I discovered that default > routes are assigned per computer not per interface. I put up a virtual > interface (213.219.39.197) on box2 so it can talk to 213.219.39.198 on box1. > > The weird thing is that if I ping 213.219.39.198 from box3 then it recieves > the echo request, here is "tcpdump -i eth1 icmp" on box1 : > > 14:08:27.201192 192.168.1.92 > 213.219.39.198: icmp: echo request (DF) > 14:08:28.197807 192.168.1.92 > 213.219.39.198: icmp: echo request (DF) > > But it just never replies and I cannot figure out why. However if I ping from > box2 or box1 then it works : > > 14:10:50.909501 213.219.39.197 > 213.219.39.198: icmp: echo request > 14:10:50.910048 213.219.39.198 > 213.219.39.197: icmp: echo reply (DF) > > It appears that the eth1 interface does not know how to send a reply to the > host that pings it so that is why I tried to assign a default gateway to it > but that just stopped everything from working. So the question is, how can > I make eth1 on box1 reachable from everywhere. Thank you very much for your > time and I hope I have made my problem clear. > > Regards, Friedrich. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Routing problem.
Hello, For your problem you maybe can solve it with a arp publication on box2 ? eg: ARP -i fxp0 -Ds 213.219.39.198 fxp1 pub Friedrich Clausen wrote: > > Greetings all, > > I will try and make myself as clear as possible so please excuse my poor ascii > picture but it seems to help explanations better. I hope this question is > appropriate for the list but I dont know where else to ask. First I will give > some info : > > Internet >| > Router >| >| > --- > | tl0|- --- > | Box2||Hub|--|eth0 Box3| > | fxp1fxp0|- --- > --- | > / | | > / | | >/ --- > / > / >- >|Hub|--- >- | > | | > | | > | | >-- >|eth0 Box1 eth1| >-- > > Networks Involved : 192.168.1.0/24 > 213.219.39.192/29 > 213.219.39.196/29 > 213.219.39.200/28 > > Router - 213.219.39.193 > > Box1 - Debian Linux workstation > eth0 : 192.168.1.92 > > Box2 - OpenBSD gateway > fxp0 : 192.168.1.50 > fxp1 : 213.219.39.204 > alias : 213.219.39.197 > tl0 : 213.219.39.194 > > Box3 - Debian Linux Server > eth0 : 213.219.39.202 > eth1 : 213.219.39.198 > > The problem is I cannot ping 213.219.39.198 from anywhere other than Box2 or > Box1. However I can ping 213.219.39.202 from anywhere. At first I thought that > it was because eth1 did not have a default route but I discovered that default > routes are assigned per computer not per interface. I put up a virtual > interface (213.219.39.197) on box2 so it can talk to 213.219.39.198 on box1. > > The weird thing is that if I ping 213.219.39.198 from box3 then it recieves > the echo request, here is "tcpdump -i eth1 icmp" on box1 : > > 14:08:27.201192 192.168.1.92 > 213.219.39.198: icmp: echo request (DF) > 14:08:28.197807 192.168.1.92 > 213.219.39.198: icmp: echo request (DF) > > But it just never replies and I cannot figure out why. However if I ping from > box2 or box1 then it works : > > 14:10:50.909501 213.219.39.197 > 213.219.39.198: icmp: echo request > 14:10:50.910048 213.219.39.198 > 213.219.39.197: icmp: echo reply (DF) > > It appears that the eth1 interface does not know how to send a reply to the > host that pings it so that is why I tried to assign a default gateway to it > but that just stopped everything from working. So the question is, how can > I make eth1 on box1 reachable from everywhere. Thank you very much for your > time and I hope I have made my problem clear. > > Regards, Friedrich. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: An LDAP authentication howto for Debian?
[EMAIL PROTECTED] wrote: > > On Sun, May 06, 2001 at 11:22:09AM +0200, Russell Coker wrote: > > On Saturday 05 May 2001 06:48, [EMAIL PROTECTED] wrote: > > > Since we're on the subject of LDAP, one thing I hate about LDAP, and it > > > may be just my ignorance, is this: I'm use to using PH for mail routing. > > > Within PH, for the user record, you can add many aliases for them, > > > which sendmail happily uses. I can't figure out how to do this with > > > LDAP! Does anyone have an eyedeer? > > > > When using LDAP for email aliases you have multi-valued attributes for both > > the incoming address and the delivery address. This allows you to have one > > user with multiple email addresses, an alias expansion to multiple users, or > > a multi-user alias with multiple addresses. > > I think I tried all that. What attributes? All the ones I tried are being > limitted to a single value. > > Tim > Well, you may try MailAlternateAddress, this attribute is multi-valued. for example here's the ldapsource i use for a postfix configuration: ldapsource_server_host = $myhostname ldapsource_server_port = 389 ldapsource_search_base = dc=test,dc=org ldapsource_timeout = 5 ldapsource_query_filter = (&(objectclass=mailrecipient)(mailalternateaddress=%s)) ldapsource_result_attribute = mail well you have to put it on virtual_maps = ldap:ldapsource alias_maps = ldap:ldapsource It was pretty simple with postfix as usual :) I dont know if you can set a query_filter with sendmail but this is not an ldap problem, that's why you dont have to hate LDAP for that ! Hugh
Re: An LDAP authentication howto for Debian?
[EMAIL PROTECTED] wrote: > > On Sun, May 06, 2001 at 11:22:09AM +0200, Russell Coker wrote: > > On Saturday 05 May 2001 06:48, [EMAIL PROTECTED] wrote: > > > Since we're on the subject of LDAP, one thing I hate about LDAP, and it > > > may be just my ignorance, is this: I'm use to using PH for mail routing. > > > Within PH, for the user record, you can add many aliases for them, > > > which sendmail happily uses. I can't figure out how to do this with > > > LDAP! Does anyone have an eyedeer? > > > > When using LDAP for email aliases you have multi-valued attributes for both > > the incoming address and the delivery address. This allows you to have one > > user with multiple email addresses, an alias expansion to multiple users, or > > a multi-user alias with multiple addresses. > > I think I tried all that. What attributes? All the ones I tried are being > limitted to a single value. > > Tim > Well, you may try MailAlternateAddress, this attribute is multi-valued. for example here's the ldapsource i use for a postfix configuration: ldapsource_server_host = $myhostname ldapsource_server_port = 389 ldapsource_search_base = dc=test,dc=org ldapsource_timeout = 5 ldapsource_query_filter = (&(objectclass=mailrecipient)(mailalternateaddress=%s)) ldapsource_result_attribute = mail well you have to put it on virtual_maps = ldap:ldapsource alias_maps = ldap:ldapsource It was pretty simple with postfix as usual :) I dont know if you can set a query_filter with sendmail but this is not an ldap problem, that's why you dont have to hate LDAP for that ! Hugh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
