11-14-2006
Sendmail Config - Open Relay
Puzzled; I have two Solaris systems, both running Solaris 5.8 and Sendmail version 8.11.7p1. One of the machines will not allow relaying (via anonymous connection to port 25). The other will allow relaying from anywhere to anywhere with impunity.
I can not find any fundemental difference in the configuration; /etc/mail/relay-domains doesn't exist on either box. I was under the impression that Sendmail after 8.9 didn't allow relaying by default.
Anybody have any idea what I ought to check to figure out why one host is relaying, and disable (or at least restrict) this functionality ?
Thanks.
10 More Discussions You Might Find Interesting
1. Cybersecurity
I'm trying to get my Solaris 7 sendmail server to allow external clients to send to external recipients. I know this has to do with relaying, but I'm not sure how unsafe I have to get to allow this. I simply need for users to login from any domain and be allowed to send mail via SMTP to any... (4 Replies)
Discussion started by: Solaris
4 Replies
2. UNIX for Dummies Questions & Answers
All
I am having a bit of a problem with my sendmail smtp server. The environment:
Redhat Linux 8
sendmail-8.12.8-9.80.
The mailserver is used by our application to send mail notifications to users on the system. The application is hosted on 2 different servers (separate domains)... (2 Replies)
Discussion started by: skotapal
2 Replies
3. Solaris
I have a sendmail issue
When I try to send a mail message using mailx I get a "connection refused by mail14.messagelabs.com" error.
relay=mail14.messagelabs.com., dsn=4.0.0, stat=Deferred: Connection refused by mail14.messagelabs.com
However, mail14.messagelabs.com doesn't exist. The... (4 Replies)
Discussion started by: soliberus
4 Replies
4. Solaris
When I try to send mail, sendmail delays a lot. After monitoring syslog, I noticed that sendmail starts with this first message... waits a minute and gives the second message... waits another minute and then sends off the email. How do I correct this in sendmail or completly disable it. I'm sending... (0 Replies)
Discussion started by: adelsin
0 Replies
5. Red Hat
Hi,
I notice that my relay on sendmail.cf is just "DS" and no ip. So I guess, it's using the local DNS to relay my mail which sometimes being spammed. I would like to add a new relay ip "DSxxx.xxx.xxx.xxx" on sendmail.cf.
What do I need to edit sendmail.cf? Do I just use vi or m4?
... (4 Replies)
Discussion started by: itik
4 Replies
6. Red Hat
Hi Guys,
I want to setup sendmail using my username and password on my ISP to be able to send out messages.
I'm using Linux. So far, what I've done is modified the sendmail.mc with the following changes:
define(`SMART_HOST',`myispsmtpoutgoingserver')
FEATURE(authinfo)dnl
In my... (0 Replies)
Discussion started by: adshocker
0 Replies
7. UNIX for Advanced & Expert Users
Hello there,
First of all I tell you that this is my first postfix installation so please be patient...
I have following scenario:
fetchmail --> postfix --> amavis-new --> postfix --> exchange 2010.
Everything -except exchange ;-)- runs on an opensuse 12.1 box.
Now, I have a list of... (0 Replies)
Discussion started by: lpacor
0 Replies
8. UNIX and Linux Applications
Hello there,
First of all I tell you that this is my first postfix installation so please be patient...
I have following scenario:
fetchmail --> postfix --> amavis-new --> postfix --> exchange 2010.
Everything -except exchange ;-)- runs on an opensuse 12.1 box.
Now, I have a list of... (0 Replies)
Discussion started by: lpacor
0 Replies
9. UNIX for Dummies Questions & Answers
Hello there,
First of all I tell you that this is my first postfix installation so please be patient...
I have following scenario:
fetchmail --> postfix --> amavis-new --> postfix --> exchange 2010.
Everything -except exchange ;-)- runs on an opensuse 12.1 box.
Now, I have a list of... (2 Replies)
Discussion started by: lpacor
2 Replies
10. Solaris
Hi Techies
Bit new to sendmail thingy.
I have a Solaris 10 box. There is a request generated by customer that they want Solaris 10 box to use as relay an external smtp server.
the smtp server is updated in hosts file and it is pingable.
I have updated by "vi" /etc/mail/sendmail.cf
# ...... (0 Replies)
Discussion started by: khaniqshahid
0 Replies
LEARN ABOUT DEBIAN
prelude-manager
prelude-manager(1) General Commands Manual prelude-manager(1)
NAME
prelude-manager - Collects and normalize events.
SYNOPSIS
prelude-manager [options]
DESCRIPTION
Prelude Manager is a high-availability server which can collect, filter, relay, reverse-relay, normalize and store events. Events can come
from registered analyzers and/or managers. The common usage is to store nomalized events into a database, thus this can be extended to
store informations in plain text or xml files.
OPTIONS
Some prelude-manager option are contextual, they have to be prefixed by another.
--prelude Prelude generic options
--profile=<name> Profile to use for this analyzer
--heartbeat-interval=<interval> Number of seconds between two heartbeat
--server-addr=<address> Address where this sensor should report to (addr:port)
--analyzer-name=<name> Name for this analyzer
--db=<INAME>
Options for the libpreludedb plugin
-t, --type=<type> Type of database (mysql/pgsql/sqlite3)
-l, --log=<file name> Log all queries in a file, should be only used for debugging purpose
-h, --host=<address> The host where the database server is running (in case of client/server database)
-f, --file=<file name> The file where the database is stored (in case of file based database)
-p, --port=<port number> The port where the database server is listening (in case of client/server database)
-d, --name=<name> The name of the database where the alerts will be stored
-u, --user=<user> User of the database (in case of client/server database)
-P, --pass=<password> Password for the user (in case of client/server database)
--debug=<INAME>
Option for the debug plugin
-o, --object=<name> Name of IDMEF object to print (no object provided will print the entire message)
-l, --logfile=<file name> Specify output file to use (default to stdout)
--relaying=<INAME>
Relaying plugin option
-p, --parent-managers=<address> List of managers address:port pair where messages should be sent to
--textmod=<INAME>
Option for the textmod plugin
-l, --logfile=<file name> Specify logfile to use
--xmlmod=<INAME>
Option for the xmlmod plugin
-l, --logfile=<file name> Specify output file to use
-v, --validate=<xml> Validate IDMEF XML output against DTD
-f, --format=<format> Format XML output so that it is readable
-d, --disable-buffering=<boolean> Disable output file buffering to prevent truncated tags
--idmef-criteria-filter=<INAME> Filter message based on IDMEF criteria
-r, --rule=<rule> Filter rule, or filename containing rule
--hook=<value> Where the filter should be hooked (reporting|reverse-relaying|plugin name)
--config=<file name>
Configuration file to use
-v, --version
Print version number
-D, --debug-level=<level>
Run in debug mode
-d, --daemon
Run in daemon mode
-P, --pidfile=<file name>
Write Prelude PID to pidfile
-c, --child-managers=<address>
List of managers address:port pair where messages should be gathered from
-l, --listen=<address>
Address the sensors server should listen on (addr:port)
-f, --failover=<boolean>
Enable failover for specified report plugin
-h, --help
Print help
FILES
/etc/prelude/prelude-manager.conf - the configuration file
BUGS
This man page hadn't been proof-read yet.
SEE ALSO
prelude-adduser(1)
prelude-manager(1)