PPP clients couldn't get e-mail - PPP

This is a discussion on PPP clients couldn't get e-mail - PPP ; Dear Experts, I have a problem: remote PPP clients (Mdaemon Server) couldn't get their e-mails from PPP dial-in server and I don't know why. When I tailed the log file (tail -f /var/log/mgetty.log.ttyS1 and tail -f /var/log/messages) I found no ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: PPP clients couldn't get e-mail

  1. PPP clients couldn't get e-mail

    Dear Experts,

    I have a problem: remote PPP clients (Mdaemon Server) couldn't get
    their e-mails from PPP dial-in server and I don't know why. When I
    tailed the log file (tail -f /var/log/mgetty.log.ttyS1 and tail -f
    /var/log/messages) I found no any noticable errors, just said:

    Jul 31 08:50:32 mail mgetty[12219]: data dev=ttyS1, pid=12219,
    caller:'none', conn='33600/ARQ/LAPM/V42BIS', name='',
    cmd='/usr/sbin/pppd', user='/AutoPPP/'
    Jul 31 08:50:32 mail pppd[12219]: pppd 2.4.0 started by a_ppp, uid 0
    Jul 31 08:50:32 mail pppd[12219]: Using interface ppp0
    Jul 31 08:50:32 mail pppd[12219]: Connect: ppp0 <--> /dev/ttyS1
    Jul 31 08:50:34 mail pppd(pam_unix)[12219]: session opened for user
    province by a_ppp(uid=0)
    Jul 31 08:50:32 mail pppd[12219]: user province logged in
    Jul 31 08:50:35 mail pppd[12219]: local IP address 192.168.100.17
    Jul 31 08:50:35 mail pppd[12219]: remote IP address 192.168.100.254
    Jul 31 08:50:35 mail pppd[12219]: LCP terminated by peer
    (|'^WM-^S^@ Jul 31 08:50:35 mail pppd[12219]: Hangup (SIGHUP)
    Jul 31 08:50:35 mail pppd[12219]: Modem hangup
    Jul 31 08:50:35 mail ppp(pam_unix)[12219]: session closed for user
    province
    Jul 31 08:50:35 mail pppd[12219]: Connection terminated.
    Jul 31 08:50:35 mail pppd[12219]: Connect time 4.3 minutes.
    Jul 31 08:50:35 mail pppd[12219]: Sent 9827 bytes, received 15359
    bytes.
    Jul 31 08:50:35 mail pppd[12219]: Exit.

    The province client (Mdaemon) could sent all the messages from remote
    queue outbox but after that they came back in. As a result, the client
    could not get e-mails from the server mail box and could not send its
    mails into the box.

    Please help me!

    Thanks so much.

  2. Re: PPP clients couldn't get e-mail

    vadavid@cmac.org.kh (Va David) writes:
    > Jul 31 08:50:35 mail pppd[12219]: local IP address 192.168.100.17
    > Jul 31 08:50:35 mail pppd[12219]: remote IP address 192.168.100.254
    > Jul 31 08:50:35 mail pppd[12219]: LCP terminated by peer
    > (|'^WM-^S^@

    The peer terminated the connection immediately (less than a second)
    after it came up. There's no indication here why it might have done
    this. At a guess, though, the peer is upset about the nature of the
    connection.

    You might get more clues by using the 'debug' option in pppd (and make
    sure that you have daemon.debug directed to a file in
    /etc/syslog.conf), but I doubt it.

    The real debug information is on the peer's side. You need to find
    out why the peer decided to drop the link.

    > The province client (Mdaemon) could sent all the messages from remote
    > queue outbox but after that they came back in. As a result, the client
    > could not get e-mails from the server mail box and could not send its
    > mails into the box.


    I don't think I quite understand that. The peer doesn't have an IP
    link at all. How does email come into the picture ... ?

    --
    James Carlson, Solaris Networking
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  3. Re: PPP clients couldn't get e-mail

    Va David wrote:

    > I have a problem: remote PPP clients (Mdaemon Server) couldn't get
    > their e-mails from PPP dial-in server and I don't know why. When I
    > tailed the log file (tail -f /var/log/mgetty.log.ttyS1 and tail -f
    > /var/log/messages) I found no any noticable errors, just said:


    > Jul 31 08:50:32 mail mgetty[12219]: data dev=ttyS1, pid=12219,
    > caller:'none', conn='33600/ARQ/LAPM/V42BIS', name='',
    > cmd='/usr/sbin/pppd', user='/AutoPPP/'
    > Jul 31 08:50:32 mail pppd[12219]: pppd 2.4.0 started by a_ppp, uid 0

    ^^^^^^^^
    Pppd starts.

    > Jul 31 08:50:32 mail pppd[12219]: Using interface ppp0
    > Jul 31 08:50:32 mail pppd[12219]: Connect: ppp0 <--> /dev/ttyS1
    > Jul 31 08:50:34 mail pppd(pam_unix)[12219]: session opened for user
    > province by a_ppp(uid=0)
    > Jul 31 08:50:32 mail pppd[12219]: user province logged in
    > Jul 31 08:50:35 mail pppd[12219]: local IP address 192.168.100.17
    > Jul 31 08:50:35 mail pppd[12219]: remote IP address 192.168.100.254
    > Jul 31 08:50:35 mail pppd[12219]: LCP terminated by peer
    > (|'^WM-^S^@ > Jul 31 08:50:35 mail pppd[12219]: Hangup (SIGHUP)
    > Jul 31 08:50:35 mail pppd[12219]: Modem hangup
    > Jul 31 08:50:35 mail ppp(pam_unix)[12219]: session closed for user
    > province
    > Jul 31 08:50:35 mail pppd[12219]: Connection terminated.
    > Jul 31 08:50:35 mail pppd[12219]: Connect time 4.3 minutes.


    The PPP connection lasted for 4.3 minutes.

    > Jul 31 08:50:35 mail pppd[12219]: Sent 9827 bytes, received 15359
    > bytes.
    > Jul 31 08:50:35 mail pppd[12219]: Exit.

    ^^^^^^^^
    Pppd exits.

    The 4.3 minute connect time contradicts the 3 seconds that elapsed
    between the time pppd started running and the time it exited. Why?

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* Better is the enemy of good enough. */