Sponsored Content
Operating Systems Solaris sendmail problem on Solaris 10 Post 302108394 by reborg on Monday 26th of February 2007 07:31:54 AM
Old 02-26-2007
The mailserver is configured not to relay from unknown senders (usually by domain).

ppi@localhost is not a known sender and is therefore not relayed,
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sendmail for Solaris 2.6

How do I configure send mail to send mail to internet mail accounts. The system is on a network which has an internet net router configured. (2 Replies)
Discussion started by: stuart.tootill
2 Replies

2. Solaris

Solaris 10 - Sendmail

Hello, I just installed Solaris 10 and my sendmail works. However, when I send an email the from heading appears as 'user@serverhostname.company.com'. Is there a way to remove the serverhostname so that the heading appears as 'user@company.com'. Thanks. (0 Replies)
Discussion started by: vitzit
0 Replies

3. Solaris

Problem starting Sendmail on Solaris 9

Hi, I am getting problem in starting up Sendmail on solaris. When I do /etc/init.d/sendmail start in Process list it shows sendmail process properly. But when I do portcheck by netstat it doesn't show Port 25/smtp. What could be the problem ? Thanks NeeleshG (6 Replies)
Discussion started by: neel.gurjar
6 Replies

4. Solaris

solaris 8/9 sendmail

Hi All, How do I make sure that sendmail outside the server is blocked? How do I make sure the port 25 is blocked on the firewall? How do I determine if port 25 is used or other ports? Thanks in advance for any commment you may add. (1 Reply)
Discussion started by: itik
1 Replies

5. Cybersecurity

How to configure sendmail in solaris 10

how to configure sendmail in solaris 10 ???? Anyone knows, pls share the documents. (1 Reply)
Discussion started by: vishwanathhcl
1 Replies

6. Solaris

sendmail solaris 10

My mail isbeing sent via server in format of : username@host.domain and from this fails as the domain does not exist. In solaris 9 we used DMdomain which cured the problem. this does not work in solaris 10 I have tried to rebuild sendmail.cf from a new version of the .mc file and tried... (7 Replies)
Discussion started by: smcart
7 Replies

7. Solaris

solaris 8/9 sendmail stop

Hi All, I need to stop sendmail from running on boot-up. How can I do this on Solaris 8 and 9 sparc? Please help and that you in advance. (2 Replies)
Discussion started by: itik
2 Replies

8. Solaris

Solaris sendmail issue

I am trying to send mail from a Solaris 10 machine to myself. The mail will be receive by a mail server. The problem is sendmail doesn't report any errors and there is nothing in mailq output. In the logs the stat=queued. I do not receive the mail in my mailbox. I could telnet to the... (7 Replies)
Discussion started by: sundar63
7 Replies

9. Solaris

Help to configure sendmail on Solaris 10

Hello, I need help to configure sendmail on Solaris 10. I have to configure sendmail to send mail on the Internet, now works only for sending mail for local users. I'm studying several tutorials ... When I try to send a mail to an external address (eg aaaa@gmail.com) the mail is placed... (3 Replies)
Discussion started by: arfry
3 Replies

10. Solaris

sendmail issue on solaris 9

We changed relay agent in sendmail.cf and submit.cf files, and restarted the send mail services from init.d, able to see the sendmail processes. But unable to send an email. Relay agent is telnetable with port 25. Please help us with the issue (2 Replies)
Discussion started by: sudhakar110
2 Replies
PPPOE-RELAY(8)						      System Manager's Manual						    PPPOE-RELAY(8)

NAME
pppoe-relay - user-space PPPoE relay agent. SYNOPSIS
pppoe-relay [options] DESCRIPTION
pppoe-relay is a user-space relay agent for PPPoE (Point-to-Point Protocol over Ethernet) for Linux. pppoe-relay works in concert with the pppoe client and pppoe-server server. See the OPERATION section later in this manual for details on how pppoe-relay works. OPTIONS
-S interface Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Only PPPoE servers may be connected to this interface. -C interface Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Only PPPoE clients may be connected to this interface. -B interface Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Both PPPoE clients and servers may be con- nected to this interface. -n num Allows at most num concurrent PPPoE sessions. If not specified, the default is 5000. num can range from 1 to 65534. -i timeout Specifies the session idle timeout. If both peers in a session are idle for more than timeout seconds, the session is terminated. If timeout is specified as zero, sessions will never be terminated because of idleness. Note that the idle-session expiry routine is never run more frequently than every 30 seconds, so the timeout is approximate. The default value for timeout is 600 seconds (10 minutes.) -F The -F option causes pppoe-relay not to fork into the background; instead, it remains in the foreground. -h The -h option prints a brief usage message and exits. OPERATION
pppoe-relay listens for incoming PPPoE PADI frames on all interfaces specified with -B or -C options. When a PADI frame appears, pppoe- relay adds a Relay-Session-ID tag and broadcasts the PADI on all interfaces specified with -B or -S options (except the interface on which the frame arrived.) Any PADO frames received are relayed back to the client which sent the PADI (assuming they contain valid Relay-Session-ID tags.) Likewise, PADR frames from clients are relayed back to the matching access concentrator. When a PADS frame is received, pppoe-relay enters the two peers' MAC addresses and session-ID's into a hash table. (The session-ID seen by the access concentrator may be different from that seen by the client; pppoe-relay must renumber sessions to avoid the possibility of duplicate session-ID's.) Whenever either peer sends a session frame, pppoe-relay looks up the session entry in the hash table and relays the frame to the correct peer. When a PADT frame is received, pppoe-relay relays it to the peer and deletes the session entry from its hash table. If a client and server crash (or frames are lost), PADT frames may never be sent, and pppoe-relay's hash table can fill up with stale ses- sions. Therefore, a session-cleaning routine runs periodically, and removes old sessions from the hash table. A session is considered "old" if no traffic has been seen within timeout seconds. When a session is deleted because of a timeout, a PADT frame is sent to each peer to make certain that they are aware the session has been killed. EXAMPLE INVOCATIONS
pppoe-relay -C eth0 -S eth1 The example above relays frames between PPPoE clients on the eth0 network and PPPoE servers on the eth1 network. pppoe-relay -B eth0 -B eth1 This example is a transparent relay -- frames are relayed between any mix of clients and servers on the eth0 and eth1 networks. pppoe-relay -S eth0 -C eth1 -C eth2 -C eth3 This example relays frames between servers on the eth0 network and clients on the eth1, eth2 and eth3 networks. AUTHORS
pppoe-relay was written by David F. Skoll <dfs@roaringpenguin.com>. The pppoe home page is http://www.roaringpenguin.com/pppoe/. SEE ALSO
pppd(8), pppoe(8), pppoe-sniff(8), pppoe-relay(8), /usr/share/doc/pppoe/README.Debian.gz 4th Berkeley Distribution 26 January 2001 PPPOE-RELAY(8)
All times are GMT -4. The time now is 03:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy