Re: Getting email together with dman Newbie #61
on Sat, Dec 15, 2001 at 06:19:56AM +0200, Ian Balchin ([EMAIL PROTECTED]) wrote: > Hi, > Hello, brenda et al, > > Deja vu, but cannot find it so must start again. > > I solved the first part of the error message from wvdial's > invocation of pppd by noting that it did not occure if I was super > user. System utilities (including things like networking and dialup) often expect to be run as root _OR_ as a set of users defined as having privileges to use the facility. I'm not familiar with wvdial particularly. > But, of course, the ppp daemon still died. I put in a path in > wvdial.conf and that problem has gone now. > > Have been reading /usr/share/doc/ppp/FAQ.gz - particularly the > third question that is about 15% of the way through (reading with > mc). This line was not in syslog.conf so have added them. > > *.err;kern.debug;auth.notice;mail.crit;daemon.info/dev/console > daemon,local2.debug /etc/ppp/log > > in fact the second line and accompanying explanation was not clear > and I modified the last part to > > /var/log/ppp.log > > figuring that (a) all the log files were in /var/log and (b) the > log file should be named not just log. I created a file ppp.log > with a one line entry for recognition with > > cat ppp.log > > I sent the HUP signal > > kill -HUP 'cat /var/run/syslog.pid' > > which with no output I was satisfied had run OK (these things > _are_ picky with which inverted commas can be used!) Note the distinction between "'" (a quote) and "`" (a backquote or "backtick"). The latter resolves output of a command and uses it as the argument for other commands. Better, substitute the "$( expression )" form: $ cat /var/run/syslog.pid $ ps up $( cat /var/run/syslog.pid ) Incidentally, the latter is a way to check to see if a process has truly died. Peace. -- Karsten M. Self http://kmself.home.netcom.com/ What part of "Gestalt" don't you understand? Home of the brave http://gestalt-system.sourceforge.net/Land of the free We freed Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org Geek for Hire http://kmself.home.netcom.com/resume.html pgpARWoIIFk1s.pgp Description: PGP signature
Re: Getting email together with dman Newbie #61
On Thu, Dec 13, 2001 at 08:17:18AM +0200, Ian Balchin wrote: > Brenda et al, > > a few points overlooked. > > 1. I was running wvdial manually on its own, $ wvdial, so expected > that it would connect and relinquish control back to the prompt. It > does no have its own prompt to accept input, and all the iinfo was > on- screen. Heh, well after all that hand-waving about using wvdial, it seems I don't actually use it on a day-to-day basis. I use the scripts pon and poff (supplied in ppp package). I have attached them to menu items that are presented in X-Windows. In any case, wvdial still works, I tried it at the command line and here is the output: == wvdial output == seal:/etc/ppp/peers# wvdial --> WvDial: Internet dialer version 1.41 --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 OK --> Modem initialized. --> Sending: ATDT my-isps-phone-number-here --> Waiting for carrier. ATDT my-isps-phone-number-here CONNECT 19200/ARQ/V34/LAPM/V42BIS --> Carrier detected. Waiting for prompt. User Access Verification Username: Username: --> Looks like a login prompt. --> Sending: bjb bjb Password: --> Looks like a password prompt. --> Sending: (password) ottawa4> --> Hmm... a prompt. Sending "ppp". ppp Entering PPP mode. Async interface address is unnumbered (Ethernet0) Your IP address is ww.xx.yy.zz. MTU is 1500 bytes Header compression will match your system. --> Looks like a welcome message. --> Starting pppd at Thu Dec 13 22:06:01 2001 == wvdial output == I am running as root. Now I see why I probably gave up on wvdial, it is running at 19.4Kb and the modem is capable of 33.8. I think I failed to configure it better and gave up on it. Also I wanted regular users to be able to dial up. To hang up, I typed ctl-C into the xterm where wvdial was running: = more wvdial output Caught signal #2! Attempting to exit gracefully... --> Disconnecting at Thu Dec 13 22:10:55 2001 seal:/etc/ppp/peers# = more wvdial output -- [EMAIL PROTECTED] Welcome to the GNU age! http://www.gnu.org
Re: Getting email together with dman Newbie #61
Thus spake Ian Balchin: > 4. I am perhaps confusing a nameserver address with an ISP address. > I read it that the name server can be remote from the ISP (unless > he runs one himself) to provide a numerical address for > [EMAIL PROTECTED] so that the email can be then sent to > that address. If I am using my ISP as a smarthost I do not need > this. Still, I will call them today and check this out. Correct > 5. I have looked carefully through Muttrc and can find no unneeded > lines with reference to POP or my ISP except for the one commented > out re latter when I gave it an unsuccessful try previously It occurs to me - do you see this error when you try to fetch mail from within mutt? That may be the source of it - no POP servers listed in .muttrc, and so it can't get to them. Fetchmail will handle this end, one it's up and running. Then you can just read your mail locally. HTH, Steve -- Happiness is a positive cash flow. pgpAqOfCQ5jeZ.pgp Description: PGP signature
Re: Getting email together with dman Newbie #61
Ian Balchin wrote: >3 if i run $ ifconfig ppp it generates > >ppp: error fetching interface information: device not found The device ppp is created dynamically. And usually it creates an instantiation named ppp0. __ www.edsamail.com
Re: Getting email together with dman Newbie #61
On Mon, Dec 10, 2001 at 08:29:52PM +0200, Ian Balchin wrote:
> EXIM
>
> I ran eximconfig again, correctly, and am sure there is no problem
> there.
>
>
> > The "visible" mail name of your system should be the same as "echo
> > $HOST". Don't worry about it too much, just don't pick the name
> > of your ISP (or some other real server).
>
> looking at set i have no $HOST so gave hephaestus which is the
> machine name (I have $HOSTNAME which is perhaps what you meant?)
good.
>
> > When you get to the question
> > Which machine will act as the smarthost and handle outgoing mail?
> > this is where you enter in the name of your ISP's SMTP server.
> > ("imail.imaginet.co.za" according to what you wrote farther down)
>
> OK, in Windows Pegasus this is entered as both my SMTP and POP3 host
> so sounds OK
I have an exim.conf that was modified by hand (using advice
from this list, a while ago). I tried just now to create an
exim.conf using eximconfig, and it produced something
different.
So
looking at exim.conf in my emacs editor:
qualify_domain = achilles.net # my isp's domain
qualify_recipient = localhost
#local_domains = not defined (see the comment delimiter at beg. of line)
local_domains_include_host = true
local_domains_include_host_literals = true
#relay_domains =
Stuff after this didn't change much, until the section
ROUTERS CONFIGURATION
There is a new stanza before all the others:
lookuphost:
driver = lookuphost
transport = remote_smtp
Well that'll do for starters. I don't know what it all means,
but try defining your keywords (or commenting them out) as
above using values appropriate to your situation.
I am not using my isp as a smarthost. For outgoing mail,
my exim has to connect with the MTA of the recipient.
I should really fix this so that my outgoing email all gets
dumped onto my isp, for later delivery (that's what a smarthost
does). Then I wouldn't have to stay connected until all my
outgoing emails have been sent to the respective remote
MTA's (which sometimes takes hours, if the recipient has
a stupid isp). My isp's mail service is excellent,
and I'd be able to hang up virtually right away and
my isp (who is connected to the internet 24/7 anyway)
would worry about delivering to the stupid isps when
they can receive mail.
Anyway the point is that the configuration above won't
give you smarthost capability. Doing that is On My
List of Stuff To Do (but fiddling with eximconfig today
is certainly pointing me in the right direction).
> FETCHMAIL
>
>
> > First you need to tell mutt which host. Edit ~/.muttrc for that.
> > Instead I use fetchmail for retrieving the mail.
>
> OK, then that will be good enough for me, fetchmail seems to be the standard
> anyway.
>
>
> I wrote the .fetchmailrc file. Then I wondered where to put it.
> The /usr/share/doc/fetchmail/sample.rc file states
>
>
> 1. put in your home directory (ie. /home/ian)
> 2. permissions should not be greater than -rw--- (0600)
>
>
> this is what i have done, but as I wrote it from root, I have done a
> chown to change it to my ownership as there was a complaint that i
> did not own it.
Excellent.
>
>
> Now, when I run fetchmail from user ian i get
>
>
> POP# connection to imail.imaginet.co.za failed: temporary name
> server error fetchmail: Query status=2 (SOCKET)
Ah, name resolution errors. A whole other topic.
Files that will be interesting at this stage are:
/etc/resolv.conf see resolv.conf(5)
/etc/nsswitch.conf see nsswitch.conf(5)
/etc/host.conf you guessed it: host.conf(5)
My /etc/resolv.conf says: (these are _my_ isp's nameservers)
nameserver 209.151.0.10
nameserver 209.151.0.12
My /etc/host.conf says:
order hosts,bind
multi on
My /etc/nsswitch.conf is the default one, except maybe
the line "hosts" has files and dns reversed:
hosts: files dns
Or maybe its not reversed and this _is_ the default, I don't
remember. Anyway as a dialup user you want "files" first.
See the networking howtos: /usr/share/doc/HOWTO/
NET-3-HOWTO.txt.gz
NET3-4-HOWTO.txt.gz
Net-HOWTO.txt.gz
Networking-Overview-HOWTO.txt.gz
Unix-and-Internet-Fundamentals-HOWTO.txt.gz
To view:
zless NET3-4-HOWTO.txt.gz
I got the above list of files with:
locate HOWTO
to remember where the HOWTO files are
ls -la /usr/share/doc/HOWTO/en-txt/*[nN][eE][tT]*
So, the above is the list of all files with net in the name
(with any capitalisation of "net") in the directory
/usr/share/doc/HOWTO
This misses the stuff in the subdirectory mini:
ls -lad /usr/share/doc/HOWTO/en-txt/* | grep "^d"
Looking for lines that start with d (directory lines in
long-format listings start with d, eg:
drwxr-xr-x2 root root 3072 Nov 14 2000 ../mini
Then same ls -la command as above in this directory. Turns
up files:
Home-Network-mini-HOWTO.txt.gz
IP-Subnetworking.txt.gz
Netrom-Node.txt.gz
Netstation.txt.gz
Anyway, get name reso
