- WLUG - wlug.mailman3.com

FW: Authentication on outgoing SMTP, how to set with postfix?

by Jim & Toni

Sorry if you get multiples, like it says, having trouble with outgoing. Thanks. -----Original Message----- From: Jim & Toni [mailto:jntdibb@bellatlantic.net] Sent: Monday, October 13, 2003 2:28 PM To: 'wlug(a)wlug.org' Subject: Authentication on outgoing SMTP, how to set with postfix? I've almost got postfix setup as a mail relay from my local linux box to 'outgoing.verizon.net'. But, the postfix howto doesn't specify how to provide login/password authentication for smtp servers that require it. The error was '554: Authentication required' Going to search more, but appreciate any help. Thanks.

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Gregory Avedissian

Andy Stewart wrote: > On Monday 13 October 2003 9:13 am, Gregory Avedissian wrote: > >>Same thing happens with any user, and the problem spans two consecutive >>installations on the same machine. The problem doesn't exist on my other >>machine, even though I intalled the same stuff. >> >>I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). >>Sax2 won't run on this machine - it goes to a black screen that won't >>respond to any keystrokes except the reset button. I had to setup XFree >>4.1 with the old sax, passing monitor and server parameters to it on the >>command line for it to run correctly (hsync, vsync, screen resolution >>and server). Sax2 doesn't seem to have the same switches. Is it bad to >>setup newer versions of X with sax instead of sax2? >> >>BTW, I had a lot of trouble setting up the older version of XFree from >>the CD's, too. >> >>Greg > > > HI Greg, > > I think sax2 has a command line switch to force it to run in a low res mode, > and I believe it is "-l" (minus ell). I've succeeded in using this with all > sorts of strange hardware. This switch is not the default. > > sax is designed for XFree86 3.x, while sax2 is designed for XFree86 4.x. SuSE > seems to be geared to more easily handle XFree86 4.x. > > See if you can get this graphics card to run in 640x480 8-bit color mode > first, and if you succeed, then get brave and attempt higher resolutions > afterwards. > > Later, > > Andy > > Andy, Lowres won't work. The problem is it sees the S3Virge chip on the vid card and wants to use the s3virge driver, when it should really be using the 3DLabs driver. In the old sax, it tries to run in lowres first, and it comes up very large and hanging way over the edge of my screen. What I've found to work is this - sax -h 30-70 -v 50-150 -a 1024x768 -s XF86_3DLabs I've read the help screen for sax2 a bunch of times, and I don't understand how to give it the same information. sax2 -m 0=vga sort of works. I get a 320x200 image that fills the bottom half of my screen and bleeds way off the right edge. sax2 -m 0=glint quits and gives me error messages (no device found - the card has a glint 500tx accelerator) sax2 -m 0=s3virge goes black and locks up, only reset button gets me out Can't figure out the proper syntax for the --xmode option to set the screen resolution or hsync, and setting vsync doesn't seem to be an option. If you know this secret, I'll buy you a beer. Greg

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Monday 13 October 2003 9:13 am, Gregory Avedissian wrote: > > Same thing happens with any user, and the problem spans two consecutive > installations on the same machine. The problem doesn't exist on my other > machine, even though I intalled the same stuff. > > I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). > Sax2 won't run on this machine - it goes to a black screen that won't > respond to any keystrokes except the reset button. I had to setup XFree > 4.1 with the old sax, passing monitor and server parameters to it on the > command line for it to run correctly (hsync, vsync, screen resolution > and server). Sax2 doesn't seem to have the same switches. Is it bad to > setup newer versions of X with sax instead of sax2? > > BTW, I had a lot of trouble setting up the older version of XFree from > the CD's, too. > > Greg HI Greg, I think sax2 has a command line switch to force it to run in a low res mode, and I believe it is "-l" (minus ell). I've succeeded in using this with all sorts of strange hardware. This switch is not the default. sax is designed for XFree86 3.x, while sax2 is designed for XFree86 4.x. SuSE seems to be geared to more easily handle XFree86 4.x. See if you can get this graphics card to run in 640x480 8-bit color mode first, and if you succeed, then get brave and attempt higher resolutions afterwards. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Gregory Avedissian

Andy Stewart wrote: > On Sunday 12 October 2003 2:25 pm, Gregory Avedissian wrote: > >>At the meeting last Thursday, I asked about a problem I'm having with >>KDE desktop, and Tim mentioned I should run 'tail -f /var/log/messages' >>in another terminal while loading KDE. > > > Hi Greg, > > What happens if you create a brand new user, and then log in as that user and > fire up KDE? I'm wondering if there is a system problem or if something is > fubar in one of your user specific KDE files. > > Later, > > Andy Hi Andy, Same thing happens with any user, and the problem spans two consecutive installations on the same machine. The problem doesn't exist on my other machine, even though I intalled the same stuff. I'm thinking it might have to do with my funky vid card (ELSA GLoria-L). Sax2 won't run on this machine - it goes to a black screen that won't respond to any keystrokes except the reset button. I had to setup XFree 4.1 with the old sax, passing monitor and server parameters to it on the command line for it to run correctly (hsync, vsync, screen resolution and server). Sax2 doesn't seem to have the same switches. Is it bad to setup newer versions of X with sax instead of sax2? BTW, I had a lot of trouble setting up the older version of XFree from the CD's, too. Greg

Oct. 13, 2003

Re: [Wlug] You can't get there from here...

by Andy Stewart

On Sunday 12 October 2003 2:25 pm, Gregory Avedissian wrote: > At the meeting last Thursday, I asked about a problem I'm having with > KDE desktop, and Tim mentioned I should run 'tail -f /var/log/messages' > in another terminal while loading KDE. Hi Greg, What happens if you create a brand new user, and then log in as that user and fire up KDE? I'm wondering if there is a system problem or if something is fubar in one of your user specific KDE files. Later, Andy -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA USA http://www.wlug.org

Oct. 13, 2003

You can't get there from here...

by Gregory Avedissian

At the meeting last Thursday, I asked about a problem I'm having with KDE desktop, and Tim mentioned I should run 'tail -f /var/log/messages' in another terminal while loading KDE. Description of problem: KDE starts to load, tells me it's checking peripherals, and then the screen goes black. Ctrl-alt-back kills the xserver and gets me out. In running the tail, I discovered that KDE really is runnning OK, but I have to switch to another virtual console (alt-F2) and then ctrl-alt-F7 will get me to the kde desktop. I get error messages from modprobe while kde is loading. It's looking for sound-slot-1, which I think is odd, because modules.conf doesn't say anything about a sound-slot-1. I only have one sound card, and it's at sound-slot-0. I tried turning off the sound server in the kde control center, and that didn't help. I also get gpm error messages when I go in an out of an x-session. Changing GPM_PARAMS in /etc/rc.config to the correct type of mouse helped get rid of flaky mouse behavior in console, but the error messages continue. Below are the messages. Any ideas or suggestions are appreciated. Thanks, Greg Oct 12 13:54:29 linux gpm[1601]: Error in protocol Oct 12 13:55:04 linux last message repeated 38 times Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-slot-1 Oct 12 13:55:05 linux modprobe: modprobe: Can't locate module sound-service-1-0

Oct. 12, 2003

Re: [Wlug] NIC settings -- how?

by David Goss

Hi all... hope someone can help... been away from the meetings for a while... ( like a year ) due to health reasons... then to boot my linux machine had a massive failure and i had to replace it... had it all set up the forward and masquerade a couple of windows boxes through my dsl connection... ( verizon ) have the pppoe all set up... but can't for the life of me remember how to set up the ipchains to handle the windows boxes for the wife and kids... and man they are getting hostile about not being able to get on the internet from home... i know it was not that hard to set up but for the life of me i can not find the docs i used in the first place... hoping to make some meetings soon... now that the health is getting back to "normal"... and buying beer for the helpful guy that can get my network back to normal as well... best regards to all dave goss

Oct. 11, 2003

Re: [Wlug] NIC settings -- how?

by Charles R. Anderson

On Thu, Oct 09, 2003 at 01:18:34PM -0400, Bill Mills-Curran wrote: > How can I view and alter NIC settings, like auto-negotiate, speed, > duplex on my Red Hat 8/9 boxes? mii-tool or ethtool, depending on the driver. -- Charles R. Anderson <cra(a)wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886

Oct. 9, 2003

NIC settings -- how?

by Bill Mills-Curran

How can I view and alter NIC settings, like auto-negotiate, speed, duplex on my Red Hat 8/9 boxes? Thanks, Bill

Oct. 9, 2003

Re: Old Hardware (Re: Re: Debian question)

by Bob George

"Chuck Homic" <chuck(a)vvisions.com> wrote: > [...] > Currently it is an excuse to own the domain underpowered.net. Hah, great name! > [...] > - How can I get on this list? That sounds cool. Info is at http://groups.yahoo.com/group/survpc/ . Be forewarned however: It's an often contentious place, with a few hard-core DOS holdouts. Not all that it could be, but success stories for using "old stuff" are always welcome. > - I chose Debian for three reasons. 1. familiarity, 2. laziness, 3. the > aforementioned 240M hard drive. Since Debian would install a working > base system in around 50M, I figured it could conserve well. That's why I wound up on Debian, although with a *bit* more disk space! > Currently > I'm running DNS, HTTP, FTP, & IMAP with ~100M free for data. I have to > erase the HTTP logs of virus attacks on a fairly regular basis to keep > that free space, though. ;) Great to hear that it keeps up with all that. A few folks on the list have asked about using various distributions on limited hardware, and I've generally recommended Debian as worth considering. I've installed it on 486en, but usually with 32M or more memory. I wasn't sure about less being practical (recogizing practical depends on the individual). > - In retrospect, it would be nice to have a package manager with more > modest RAM requirements. However, I'll decide this for real when I > install the second hard drive. With one HD just for swap, it might not > matter so much. Are you using dpkg or apt? > - I have no problem saturating my 10Mbit ethernet with a 486-25, so I'm > sure it would make a fine firewall/gateway if you don't use it for > anything else, and you might have to go easy on the firewall rules. Or > it might do fine with fancy firewall rules, who knows? Experience > running NAT (for a T1) on similar hardware indicates that that would be > no problem. I did notice that old NE2000 clone NICs caused my CPU utilization to spike, especially ISA versions. My 486-66 did fine with PCI cards, though that was a couple of kernels ago. > - Although installing packages is a pain (which would be fixed up for > $0.50 of RAM, I presume) it just hums along in the interim. I don't > know how much RAM the motherboard can take, and I wouldn't know who to > buy 30/72-pin SIMMs from. :) Although experience shows I wouldn't have > to buy them, they would be given to me if I express interest. (That's a > big bonus for old hardware! Hmm. If I didn't toss 'em before the big move, I might actually HAVE some 4M 30 pin SIMMs. I think I'm out of 72 pin though. I get sad thinking about what I had to toss in Phoenix due to no time prior to my move. I did give away a couple of trunkloads of old stuff. > [...] > - It's a good box just to have hooked up to a wire, but if you have such a > thing and you ever find yourself thinking about adding a second 486 to > boost resources, you've gone off the deep end. After the novelty value > subsides, you have to think about the energy cost. How many services > can you provide per watt? How would that compare to a 50W power supply > on an old P-100 thinkpad or something? Yeah, I finally started consolidating boxes. A real problem in Phoenix was heat, where my "den" easily ran 10 degrees hotter than the rest of the house. 'Course, here that's not quite the issue it was. Still, I don't like waste, and the quiet hum of my current systems is much nicer than the roar of fans I had (as well as the AC working overtime to keep up.) > (I'd often thought about using > aging laptops as servers, to simplify the UPS situation. I figure a > ~$40 car battery plugged into the AC jack could provide backup power for > quite a long time, but that's just insanity.) I wanted to do the same thing! Quiet, low power, and UPS built-in. Oh, and small too. Thanks for the info! - Bob

Oct. 9, 2003