slashcode-general — This is the general discussion list. Install questions welcome.

Re: [Slashcode-general] per-section templates?

[Nathan V. <na...@th...>]

For *blocks*, the old method still applies in slash 2-- so if you want an
"older stuff" block in your debian section, you have to make a block named
debian_more (that's why by default there are blocks like features_more and
articles_more).  Also, if you have a block named "debian" it will show up
on all the pages in the debian section (index and articles).

And in case anyone's confused, the semicolon notation is used when you
dump the templates using template-tool, and in the comments.  Using the
template editor in backSlash, you have to use the section field.  You may
need to make a new "debian" section in it (using the new template form).

Speaking of sections, it is important to note that the "default", "light",
and "admin" sections used for templates are NOT the same as the other
sections.  Regular sections (like "features", "articles" or "debian") are
paradigmatically kind of like sections of a newspaper, but these special
ones are just for templates.  If the user is an author, slash looks for a
given template in the admin section first, then the default section.
Same with light view, or with one of the site sections.

So Barry, you could make multiple SectionIndex templates , and if you set
their section field differently they will be different, and if one doesn't
exist the default one would be used.

Alex, you silly newbie, what is "documentation"?  Actually, it would be
great if you could collect the wisdom on this topic and submit it to
slashcode.com or something...

-n
-- 
Nathan Vonnahme             na...@th...
senior web developer        third sector technologies
http://enteuxis.org/nathan  http://thethirdsector.com

Re: [Slashcode-general] per-section templates?

[<al...@ya...>]

 --- as...@en... wrote:
 > > Uhmm, I remeber that you change the section template in the template
> > name, as I put in other answer.
> > 
> > For example, to have a index tempate for the debian section:
> > 
> > index;index;debian ... ¿isn't this correct?
> 
> Oops I got my Slash1 and Slash2 mixed up. The underscore method is Slash1. In Slash2, Alvaro's
> semicolons are correct.
> 
> Adam 

At the risk of sounding like a newbie - is this sort of thing in some documentation
somewhere?

Alex


=====
Alex McLintock        al...@OW...    Open Source Consultancy in London
OpenWeb Analysts Ltd, http://www.OWAL.co.uk/ 
DR WHO COMPETITION: http://www.diversebooks.com/cgi-bin/caption/captions.cgi?date=200104
Get Your XML T-Shirt <t-shirt/> at http://www.inversity.co.uk/

____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie

Re: [Slashcode-general] per-section templates?

[Alvaro d. C. <ac...@ba...>]

El 12 Jul 2001 03:26:45 -0500, as...@en... escribió:
> > Uhmm, I remeber that you change the section template in the template
> > name, as I put in other answer.
> > 
> > For example, to have a index tempate for the debian section:
> > 
> > index;index;debian ... isn't this correct?
> 
> Oops I got my Slash1 and Slash2 mixed up. The underscore method is Slash1. In Slash2, Alvaro's semicolons are correct.

guau, ¿this works in Slash1? I don't know. It's a pity doesn't play with
it :-(

Cheers

-- Alvaro

> 

Re: [Slashcode-general] per-section templates?

[<as...@en...>]

> Uhmm, I remeber that you change the section template in the template
> name, as I put in other answer.
>=20
> For example, to have a index tempate for the debian section:
>=20
> index;index;debian ... =BFisn't this correct?

Oops I got my Slash1 and Slash2 mixed up. The underscore method is Slash1=
. In Slash2, Alvaro's semicolons are correct.

Adam

Re: [Slashcode-general] per-section templates?

[Alvaro d. C. <ac...@ba...>]

El 12 Jul 2001 00:04:30 -0500, as...@en... escribió:
> Barry,
> 
> What you are trying to do with sections is one of the main reasons they exist. All you have to do is add the section name as a prefix to your template followed by underscore, ie, sectionname_header for the header.

Uhmm, I remeber that you change the section template in the template
name, as I put in other answer.

For example, to have a index tempate for the debian section:

index;index;debian ... ¿isn't this correct?

Cheers

-- Alvaro

> 
> Keep in mind though that this may not be the best way to go unless your sections all look radically different. Rather, if they are variations on a theme, then stick with the one header template but populate it with elements that can vary depending on which section you're in (template-toolkit is part of Slash just for this).
> 
> Good luck -- you're at the point where the tedium of installing Slash starts to pay off!
> 
> Adam K
> 
> Barry Caplan <bc...@i1...> wrote ..
> > Hi....
> > 
> > I am working to get deeper into the details of completely changing the look 
> > and feel of a slash site. I think I still near the beginning.....
> > 
> > I have made a new template, called "mainSectionIndex", which is now 
> > included in "header" This works fine.
> > 
> > I would like to have a "xSectionIndex" template for each section, which 
> > would be included each time the section page is displayed.
> > 
> > My first thought was to modify each section's slashhead.inc, but that seems 
> > to be generated by slashd every hour.
> > 
> > It looks like one way to go would be to modify the header template further, 
> > so there was a kind of if then thing, looking roughly like this:
> > 
> > if section =a then include aSectionIndex
> > else section =b then include bSectionIndex
> > ....
> > else include mainSectionIndex #default
> > 
> > 
> > Does that seem reasonable,or is there a better way?
> > 
> > If it is reasonable, then what would the code look like? I have not found a 
> > listing of what variables and hashes are available to the header template 
> > (OK, I didn't look that hard because I am not sure this is the best 
> > approach yet....),
> > 
> > Just as a quick test, I tried adding in the "header" template this line: 
> > "Section = [% section %] zzzzzz".  I did not get anything in the variable 
> > part, even though I stopped and started both slashd and apache to force the 
> > updates.
> > 
> > Also, it is not 100% clear to me how the variables end up in the template 
> > form the source code.
> > 
> > Has anyone done something similar they would like to share?
> > 
> > 
> > Thanks,
> > 
> > 
> > Barry
> > 
> > 
> > _______________________________________________
> > Slashcode-general mailing list
> > Sla...@li...

Re: [Slashcode-general] per-section templates?

[Alvaro d. C. <ac...@ba...>]

Hi!

The slashcode 2.0 version try to use fisrt a template with the section
name and if it doesn't find it, then uses the general.  An example:

index;index;default
index;index;debian

If you have a section called debian, the system will use
index;index;debian for it. For the main page an the other sections, it
will use the default template.

Cheers

-- Alvaro


El 11 Jul 2001 17:55:33 -0700, Barry Caplan escribió:
> Hi....
> 
> I am working to get deeper into the details of completely changing the look 
> and feel of a slash site. I think I still near the beginning.....
> 
> I have made a new template, called "mainSectionIndex", which is now 
> included in "header" This works fine.
> 
> I would like to have a "xSectionIndex" template for each section, which 
> would be included each time the section page is displayed.
> 
> My first thought was to modify each section's slashhead.inc, but that seems 
> to be generated by slashd every hour.
> 
> It looks like one way to go would be to modify the header template further, 
> so there was a kind of if then thing, looking roughly like this:
> 
> if section =a then include aSectionIndex
> else section =b then include bSectionIndex
> ....
> else include mainSectionIndex #default
> 
> 
> Does that seem reasonable,or is there a better way?
> 
> If it is reasonable, then what would the code look like? I have not found a 
> listing of what variables and hashes are available to the header template 
> (OK, I didn't look that hard because I am not sure this is the best 
> approach yet....),
> 
> Just as a quick test, I tried adding in the "header" template this line: 
> "Section = [% section %] zzzzzz".  I did not get anything in the variable 
> part, even though I stopped and started both slashd and apache to force the 
> updates.
> 
> Also, it is not 100% clear to me how the variables end up in the template 
> form the source code.
> 
> Has anyone done something similar they would like to share?
> 
> 
> Thanks,
> 
> 
> Barry
> 
> 
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-general
> 

Re: [Slashcode-general] per-section templates?

[<as...@en...>]

Barry,

What you are trying to do with sections is one of the main reasons they exist. All you have to do is add the section name as a prefix to your template followed by underscore, ie, sectionname_header for the header.

Keep in mind though that this may not be the best way to go unless your sections all look radically different. Rather, if they are variations on a theme, then stick with the one header template but populate it with elements that can vary depending on which section you're in (template-toolkit is part of Slash just for this).

Good luck -- you're at the point where the tedium of installing Slash starts to pay off!

Adam K

Barry Caplan <bc...@i1...> wrote ..
> Hi....
> 
> I am working to get deeper into the details of completely changing the look 
> and feel of a slash site. I think I still near the beginning.....
> 
> I have made a new template, called "mainSectionIndex", which is now 
> included in "header" This works fine.
> 
> I would like to have a "xSectionIndex" template for each section, which 
> would be included each time the section page is displayed.
> 
> My first thought was to modify each section's slashhead.inc, but that seems 
> to be generated by slashd every hour.
> 
> It looks like one way to go would be to modify the header template further, 
> so there was a kind of if then thing, looking roughly like this:
> 
> if section =a then include aSectionIndex
> else section =b then include bSectionIndex
> ....
> else include mainSectionIndex #default
> 
> 
> Does that seem reasonable,or is there a better way?
> 
> If it is reasonable, then what would the code look like? I have not found a 
> listing of what variables and hashes are available to the header template 
> (OK, I didn't look that hard because I am not sure this is the best 
> approach yet....),
> 
> Just as a quick test, I tried adding in the "header" template this line: 
> "Section = [% section %] zzzzzz".  I did not get anything in the variable 
> part, even though I stopped and started both slashd and apache to force the 
> updates.
> 
> Also, it is not 100% clear to me how the variables end up in the template 
> form the source code.
> 
> Has anyone done something similar they would like to share?
> 
> 
> Thanks,
> 
> 
> Barry
> 
> 
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-general

[Slashcode-general] Viewing (perl?) problem

[Antonides, L. (utm) <Lod...@or...>]

Hi,

I installed slashcode under redhat 7.1 and everything works when I look at
the pages by using localhost (127.0.0.1). When I type the ip address of my
webserver it shows the directory contents.
httpd.conf is located under /usr/local/conf
slash is located under/usr/local/slash/
I included in httpd.conf slash.conf
It looks to me that perl scripts aren't processed. 
Can anybody help me out? I would really appreciate it.

Lodewijk

[Slashcode-general] Undefined subroutine?

[Brent M. <br...@me...>]

slashd.log...

Thu Jul 12 02:32:16 2001        Running Moderatord
Undefined subroutine &Slash::DB::Static::MySQL::moderatordLog called at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Slash/DB/Static/MySQL.pm line 497.


Any Ideas??

[Slashcode-general] per-section templates?

[barry <sla...@i1...>]

Hi....

I am working to get deeper into the details of completely changing the look 
and feel of a slash site. I think I still near the beginning.....

I have made a new template, called "mainSectionIndex", which is now 
included in "header" This works fine.

I would like to have a "xSectionIndex" template for each section, which 
would be included each time the section page is displayed.

My first thought was to modify each section's slashhead.inc, but that seems 
to be generated by slashd every hour.

It looks like one way to go would be to modify the header template further, 
so there was a kind of if then thing, looking roughly like this:

if section =a then include aSectionIndex
else section =b then include bSectionIndex
....
else include mainSectionIndex #default


Does that seem reasonable,or is there a better way?

If it is reasonable, then what would the code look like? I have not found a 
listing of what variables and hashes are available to the header template 
(OK, I didn't look that hard because I am not sure this is the best 
approach yet....),

Just as a quick test, I tried adding in the "header" template this line: 
"Section = [% section %] zzzzzz".  I did not get anything in the variable 
part, even though I stopped and started both slashd and apache to force the 
updates.

Also, it is not 100% clear to me how the variables end up in the template 
form the source code.

Has anyone done something similar they would like to share?


Thanks,


Barry

[Slashcode-general] per-section templates?

[Barry C. <bc...@i1...>]

Hi....

I am working to get deeper into the details of completely changing the look 
and feel of a slash site. I think I still near the beginning.....

I have made a new template, called "mainSectionIndex", which is now 
included in "header" This works fine.

I would like to have a "xSectionIndex" template for each section, which 
would be included each time the section page is displayed.

My first thought was to modify each section's slashhead.inc, but that seems 
to be generated by slashd every hour.

It looks like one way to go would be to modify the header template further, 
so there was a kind of if then thing, looking roughly like this:

if section =a then include aSectionIndex
else section =b then include bSectionIndex
....
else include mainSectionIndex #default


Does that seem reasonable,or is there a better way?

If it is reasonable, then what would the code look like? I have not found a 
listing of what variables and hashes are available to the header template 
(OK, I didn't look that hard because I am not sure this is the best 
approach yet....),

Just as a quick test, I tried adding in the "header" template this line: 
"Section = [% section %] zzzzzz".  I did not get anything in the variable 
part, even though I stopped and started both slashd and apache to force the 
updates.

Also, it is not 100% clear to me how the variables end up in the template 
form the source code.

Has anyone done something similar they would like to share?


Thanks,


Barry

Re: [Slashcode-general] small problem viewing the site

[Micah Y. <yo...@ho...>]

> I installed slashcode on my computer running redhat 7.1.
> Everything went fine except for the last part. It looks like index.pl is
> not processed.
> When I use localhost in my browser I see the correct page, but when I use
> my IP address it only shows the content of the directory.
> I put "Include /usr/local/slash/httpd/slash.conf" in my httpd.conf which is
> located in /usr/share/conf/
>
> Does anyone have a clue what i did wrong?

You might want to look at your slash site's config file, in 
/usr/local/slash/site/*/*.conf.  Maybe even post it here.

My guess is that it's trying to do a virtual domain on the localhost.  What I 
did on my local computer is comment out the <VirtualHost> and </VirtualHost> 
lines and comment out some things in the main Apache httpd.conf that 
conflicted with it.

-- 
Like to travel?                        http://TravTalk.org
Micah Yoder Internet Development       http://yoderdev.com

[Slashcode-general] small problem viewing the site

[Antonides, L. (utm) <Lod...@or...>]

Hi,

I installed slashcode on my computer running redhat 7.1.
Everything went fine except for the last part. It looks like index.pl is not
processed.
When I use localhost in my browser I see the correct page, but when I use my
IP address it only shows the content of the directory.
I put "Include /usr/local/slash/httpd/slash.conf" in my httpd.conf which is
located in /usr/share/conf/

Does anyone have a clue what i did wrong?

[Slashcode-general] Apache Advanced Extranet Server (mod_perl proxied)

[Brent M. <br...@me...>]

I'm running Mandrake 8 with Apache Advanced Extranet Server where mod_perl
is proxied on it's own apache processes (port 8200) to increase speed and
performance.  Has anyone been able to get slashcode to run this way?  It's
driving me nuts.

--Brent

Re: [Slashcode-general] Slash::Search and portald boxes

[Nathan V. <na...@th...>]

On Sat, 7 Jul 2001, Ross Beyer wrote:

> The problem I'm having is actually quite simple.  When I try to use
> search.pl on my site, I get an Apache error that reads:
>
> [Sat Jul  7 22:12:49 2001] [error] Can't locate Slash/Search.pm in @INC (@INC contains: /usr/perl5/5.00503/sun4-solaris /usr/perl5/5.00503 /usr/perl5/site_perl/5.005/sun4-solaris /usr/perl5/site_perl/5.005 .  /usr/local/apache/ /usr/local/apache/lib/perl) at /usr/local/slash/site/news.lpl.arizona.edu/htdocs/search.pl line 10.
> BEGIN failed--compilation aborted at /usr/local/slash/site/news.lpl.arizona.edu/htdocs/search.pl line 10.
>

I had similar issues and I finally figured out that I had a different,
old, bad version of search.pl.  One of the alpha releases, I think, had a
search.pl in the slashcode theme and if you didn't install the search
plugin right it would leave the old one there, and if you chose the
symlink option it would sometimes link to the old one and then the plugin
wouldn't install over it, or something like that, I don't remember.
Anyway, make sure you don't have different search.pl's running around.
And I think that this is fixed in the current release, if you start from
scratch...

-n

-- 
Nathan Vonnahme             na...@th...
senior web developer        third sector technologies
http://enteuxis.org/nathan  http://thethirdsector.com

[Slashcode-general] Slash::Search and portald boxes

[Ross B. <rb...@lp...>]

Hello,
	I actually have two questions.  
	
1.) I've just recently gotten a slash-2.0.0 site running on a Solaris 
box.  I'm having a problem with the search.pl page/function, and I 
couldn't find anything quite like my problem in either the mailing list 
archives or in the Patches or Bug Reports on SourceForge.

The problem I'm having is actually quite simple.  When I try to use
search.pl on my site, I get an Apache error that reads:

[Sat Jul  7 22:12:49 2001] [error] Can't locate Slash/Search.pm in @INC (@INC contains: /usr/perl5/5.00503/sun4-solaris /usr/perl5/5.00503 /usr/perl5/site_perl/5.005/sun4-solaris /usr/perl5/site_perl/5.005 .  /usr/local/apache/ /usr/local/apache/lib/perl) at /usr/local/slash/site/news.lpl.arizona.edu/htdocs/search.pl line 10.
BEGIN failed--compilation aborted at /usr/local/slash/site/news.lpl.arizona.edu/htdocs/search.pl line 10.

Line 10 of search.pl reads "use Slash::Search;" which I believe requires a 
Slash/Search.pm file in my PERL distribution, which (as the error
message says) I clearly don't have.  Furthermore, I can't actually find
any documentation about the Slash::Search routine, whereas there is
such info for Slash::Utility and Slash::Display (for example).  
I've tried reinstalling the Slash::Bundle via the CPAN prompt, 
but I think that the Slash PERL modules are actually installed when
you "make install" from the slash-2.0.0 source directory, and I can't
find any trace of a Search in there.

Any help would be greatly appreciated.  Thanks.

2.) My other question is that I notice that Slashdot has a huge list
of (what I assume are) portald blocks that users can add to their 
personal preferences.  This list is much greater than that distributed
with slash-2.0.0 .  Is there some kind of master list of portald 
blocks (with their associated URL and RDF info for other Slash site 
administrators)?

-- 
                                        Ross

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[ben h k. <ja...@mo...>]

> Seems like the hardest part is what to do with all your installed modules.  
> You pretty much have to do the complete install of all the packages again, if 
> I'm not mistaken...

Well, yes, but that is what autobundle is for.  To make a Bundle consisting of every module you have already installed.

.b

-- 
"Mir's outstanding success is that it has survived."
			Dr. David Whitehouse
			BBC News Online science editor

Re: [Slashcode-general] index.shtml or index.pl

[Alvaro d. C. <ac...@ba...>]

El 07 Jul 2001 01:19:45 -0500, Leoncini Xavier escribió:
> I have a question regarding the change in the new config.
> It seems that the new slash starts first with the index.pl,
> which kind of make my computer choke for while before answering.
> I wonder why this change has been made, or is this wait period just due
> because I just chose
> to not recompile apache and just used the deb apache and mod_perl.
> I know I could just try and compare ut If someone has a similar experience
> and solved it
> I woulld appreciate.

For access index.shtml you can enable this line commented out in the
apache conf for a virtual site:

    # this directive will redirect non-logged-in users to
    # index.shtml if they request the home page; turn it
    # on to help increase performance
    #PerlTransHandler Slash::Apache::IndexHandler

Good luck!

-- Alvaro


> Thanks
> Xavier
> 
> --
>                         Xavier Leoncini
> xa...@ny...
> http://www.nycircus.com
> NYCircus.com: NYC Lifestyles
> 
> 

[Slashcode-general] index.shtml or index.pl

[Leoncini X. <xa...@ny...>]

I have a question regarding the change in the new config.
It seems that the new slash starts first with the index.pl,
which kind of make my computer choke for while before answering.
I wonder why this change has been made, or is this wait period just due
because I just chose
to not recompile apache and just used the deb apache and mod_perl.
I know I could just try and compare ut If someone has a similar experience
and solved it
I woulld appreciate.
Thanks
Xavier

--
                        Xavier Leoncini
xa...@ny...
http://www.nycircus.com
NYCircus.com: NYC Lifestyles

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Micah Y. <yo...@ho...>]

> But I've never thought perl was that hard to install or upgrade.
> "./Configure -des && make install"

Seems like the hardest part is what to do with all your installed modules.  
You pretty much have to do the complete install of all the packages again, if 
I'm not mistaken...

-- 
Like to travel?                        http://TravTalk.org
Micah Yoder Internet Development       http://yoderdev.com

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Chris N. <pu...@po...>]

At 10:18 -0400 2001.07.06, Jamie McCarthy wrote:
>pu...@po... (Chris Nandor) writes:
>
>> Recommending perl 5.6.1 is good.  Requiring it is bad.
>
>I agree, and I'm actively taking out 5.6-isms when I see them
>(apparently three-argument open() is new to 5.6, which I didn't know
>when I put that code into a couple of places).

Yeah.  perl 5.6 has some really nice syntax changes (like autovivifying
filehandle references!), but nothing we need.

>But I've never thought perl was that hard to install or upgrade.
>"./Configure -des && make install"
>
>Of course, now that I say that, I'm reminded how perl5.6 failed
>about 3 of its tests on my new debian/reiser system, leaving me
>skeptical about installing it.  Heh.  Never mind.

Exactly.  Now, it is not as bad as if we still supported 5.004 (which we do
not), because perl 5.6 can be built with binary compatability to perl
5.005, so you don't need to rebuild shared libraries, etc.  But there are
still little problems here and there that many people can, do, and will run
into, such so that it is not worth the trouble.

A strong recommendation for 5.6.1 is warranted, but that's where I'd stop it.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-general] Can't locate DBIx/Password.pm in @INC

[Jamie M. <ja...@mc...>]

pu...@po... (Chris Nandor) writes:

> Recommending perl 5.6.1 is good.  Requiring it is bad.

I agree, and I'm actively taking out 5.6-isms when I see them
(apparently three-argument open() is new to 5.6, which I didn't know
when I put that code into a couple of places).

But I've never thought perl was that hard to install or upgrade.
"./Configure -des && make install"

Of course, now that I say that, I'm reminded how perl5.6 failed
about 3 of its tests on my new debian/reiser system, leaving me
skeptical about installing it.  Heh.  Never mind.
--
 Jamie McCarthy
 ja...@mc...

Re: [Slashcode-general] Small Issues with a Slashcode Install

[Chris N. <pu...@po...>]

At 10:33 -0800 2001.07.03, Nathan Vonnahme wrote:
>Somebody had this problem before and I think it was because of a repeated
>line in the httpd.conf -- make sure you're not doing something twice
>there, especially one of the PerlHandler thingies.

Specifically, read your httpd/slash.conf.  The first two directives
probably need to be commented out.  Here is what it says:

	# this is all the mod perl specific stuff that makes
	# slash the root handler for the site
	# ... you might want to check to make sure these are not already
	# defined in your main httpd.conf, if you have trouble
	AddHandler perl-script .pl
	PerlHandler Apache::Registry

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-general] Site not sending mail

[Chris N. <pu...@po...>]

At 03:02 -0400 2001.07.03, Micah Yoder wrote:
>OK, this is weird.  I just installed a second Slash site on my box.  AFAIK it
>has the EXACT same configuration as the other one, which works fine.  But the
>second one simply won't send any mail.  This is in the error_log:
>
>----------
>Error sending to <mi...@yo...> (550-5.7.1 reject sending to address
>'<mi...@yo...>'.)
>[Tue Jul  3 09:53:38 2001] [error]
>/users.pl:Apache::ROOTjesusgeeks_2enet::users_2epl:/usr/local/slash/site/jesusgeeks.net/htdocs/users.pl:243:Can't
>
>send mail 'JesusGeeks user password for yoderdev' to mi...@yo...:
>Error sending to <mi...@yo...> (550-5.7.1 reject sending to address
>'<mi...@yo...>'.)
>
>
>[Tue Jul  3 09:53:38 2001] [error] Which was called
>by:Apache::ROOTjesusgeeks_2enet::users_2epl:/usr/local/slash/site/jesusgeeks.net/htdocs/users.pl:208:Can't
>
>send mail 'JesusGeeks user password for yoderdev' to mi...@yo...:
>Error sending to <mi...@yo...> (550-5.7.1 reject sending to address
>'<mi...@yo...>'.)
>------
>
>a bit of funny notation in there about where the error is.  Apparently, a
>period is replaced with "_2e".
>
>I diff'd users.pl on both sites, they're the same.  A look at
>/var/log/maillog is showing that NOTHING is getting there -- there are no
>messages related to this transaction.  So aparently postfix (sendmail
>replacement) isn't even running.
>
>When I set up my first site, I also had problems sending mail, but it turned
>out to be a Postfix config error and failure messages DID show up in
>/var/log/maillog.
>
>Any ideas what could be causing this?

My guess would be your smtp_server entry in the vars table.  If you have
the same SMTP server set, look into the specific error you are getting.
Here is some info from sendmail about it.

	http://www.sendmail.org/~ca/email/relayingdenied.html

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/

Re: [Slashcode-general] Re: Fry

[Chris N. <pu...@po...>]

At 18:07 -0400 2001.07.05, Micah Yoder wrote:
>On Thursday 05 July 2001 21:00, you wrote:
>
>> Target date of getting it installed on slashdot in early August. But
>
>hmm.  I'd expect a release BEFORE running Slashdot on it.  Oh well.

Well, our dilemma is that we are using all our resources to get Slashdot
running the new code.  This means that installation procedures,
documentation, and cleaning up for general use are being neglected while
working code is being emphasized.  It is more a time issue than anything
else.  We'd love to get it all out as a release first, but there just isn't
time to get those "little" things ready.

-- 
Chris Nandor                      pu...@po...    http://pudge.net/
Open Source Development Network    pu...@os...     http://osdn.com/