Sponsored Content
Full Discussion: Sendmail Issue.
Operating Systems Linux Red Hat Sendmail Issue. Post 302443425 by Hari_Ganesh on Sunday 8th of August 2010 11:35:30 PM
Old 08-09-2010
Gurus

I have neither of these configured(Reverse DNS and SMART_HOST)...Infact the machine i am working on is a standalone server not in any domain.

Suppose that i configure both,will smtp-gmail start accepting my mails? If so what is the security that smtp-gmail server has against spammers.How exactly are the smtp servers protected against spammers if all it requires is a SMART_HOST and reverse DNS lookup.

Am asking this to understand the E-Mail setup. I read in howstuffworks.com and got a little understanding...But this thing perplexes me..


Thanks
HG
 

10 More Discussions You Might Find Interesting

1. Linux

Sendmail issue

Hi gurus! I need help to make sendmail to accept unknown user mail. That is if the user does not exist sendmail keep on processing the mail and store it in a some mailbox ... Thanks for any idea! (5 Replies)
Discussion started by: andryk
5 Replies

2. Solaris

sendmail issue

Hi, yesterday I had issues, sendmail was not responding quickly while sending email and users did not receive any email, This happened with sendmail on solaris 10 and also with sendmail on a linux box. Found it is something to do with DNS blacklists, following lists did not work for me,... (2 Replies)
Discussion started by: upengan78
2 Replies

3. UNIX for Dummies Questions & Answers

Issue with sendmail

Hi Team, I have a script written to sendmail along with attachment in html format. The code is export MAILFROM="abc@abc.com" export MAILTO="abc@abc.com" export CONTENT="./GRP_SPI_ERR.html" export SUBJECT="TEST EMAIL: TESTING HTML" { print - "From: $MAILFROM" print - "To: ${MAILTO}"... (3 Replies)
Discussion started by: Vinaykumar1
3 Replies

4. Solaris

Sendmail Issue

Hi, Guru i had configure in my two server to send out the email. One of the server able to send in the reasonable timing. but another not, it delay almost one day or two days but mostly not send at all. below is the syslog when i try to send out the mail. GOOD Server Dec 28 11:29:39... (5 Replies)
Discussion started by: SmartAntz
5 Replies

5. Solaris

Sendmail issue

Hi all, we are using solaris 10. we need to increase every users mail boxes size as all users mail boxes got filled..Please help..its urgent.. Thanks in advance.. (1 Reply)
Discussion started by: bpsunadm
1 Replies

6. AIX

Sendmail issue

My aix boxes have the port 25 listening and I want to bock that. But before that I want to check the recent logs of the sendmail activity and any open sockets using the port. Please advise. (1 Reply)
Discussion started by: ranasarkar
1 Replies

7. Red Hat

Sendmail issue

Hi Every One, one of our server configuration on sendmail config we are using SMAR_HOST ### define(`SMART_HOST', 'mail.xxx.com') and /etc/sysconfig/sednmail DAEMON is setted to NO so let me know why sendmail is not working for this server any this else u need please do let me know (0 Replies)
Discussion started by: venikathir
0 Replies

8. UNIX for Advanced & Expert Users

Sendmail issue

One of the applications sends mail to the users on daily basis. It sends mail within (internal users) the firewall (e.g., username@companyname.com) and not sending mail outside (external users) the firewall (e.g., username@yyyy.com). When we contacted the admin people they informed us to register... (5 Replies)
Discussion started by: abuibi
5 Replies

9. Emergency UNIX and Linux Support

Sendmail issue

Hi, I'm using sendmail version 8.13.8-8.1.el5_7. I'm pretty new to it. The servera are running RHEL 5.8. My question basically is that I would want to know is there a way to change the from address. I would be able to change it using the return address in mailx command. However I would like to... (3 Replies)
Discussion started by: maverick_here
3 Replies

10. Red Hat

Sendmail issue

Dear All , I have some problem in Sendmail , where it was sending mails perfectly fine with the Ip address of the client machine. But suddenly there was an issue , the SMTP takes the IP of the bond1 interface. So the IP could not get validated in the relay server. So how should i send... (1 Reply)
Discussion started by: jegaraman
1 Replies
smtp(n) 							    smtp client 							   smtp(n)

__________________________________________________________________________________________________________________________________________________

NAME
smtp - Client-side tcl implementation of the smtp protocol SYNOPSIS
package require Tcl package require mime ?1.5.4? package require smtp ?1.4.5? ::smtp::sendmessage token option... _________________________________________________________________ DESCRIPTION
The smtp library package provides the client side of the Simple Mail Transfer Protocol (SMTP) (1) (2). ::smtp::sendmessage token option... This command sends the MIME part (see package mime) represented by token to an SMTP server. options is a list of options and their associated values. The recognized options are: -servers A list of SMTP servers. The default is localhost. -ports A list of SMTP ports. The default is 25. -client The name to use as our hostname when connecting to the server. By default this is either localhost if one of the servers is localhost, or is set to the string returned by info hostname. -queue Indicates that the SMTP server should be asked to queue the message for later processing. A boolean value. -atleastone Indicates that the SMTP server must find at least one recipient acceptable for the message to be sent. A boolean value. -originator A string containing an 822-style address specification. If present the header isn't examined for an originator address. -recipients A string containing one or more 822-style address specifications. If present the header isn't examined for recipient addresses). If the string contains more than one address they will be separated by commas. -header A list containing two elements, an smtp header and its associated value (the -header option may occur zero or more times). -usetls This package supports the RFC 3207 TLS extension (3) by default provided the tls package is available. You can turn this off with this boolean option. -tlspolicy This option lets you specify a command to be called if an error occurs during TLS setup. The command is called with the SMTP code and diagnostic message appended. The command should return 'secure' or 'insecure' where insecure will cause the package to continue on the unencrypted channel. Returning 'secure' will cause the socket to be closed and the next server in the -servers list to be tried. -username -password If your SMTP server requires authentication (RFC 2554 (4)) before accepting mail you can use -username and -password to pro- vide your authentication details to the server. Currently this package supports DIGEST-MD5, CRAM-MD5, LOGIN and PLAIN authen- tication methods. The most secure method will be tried first and each method tried in turn until we are either authorized or we run out of methods. Note that if the server permits a TLS connection, then the authorization will occur after we begin using the secure channel. If the -originator option is not present, the originator address is taken from From (or Resent-From); similarly, if the -recipients option is not present, recipient addresses are taken from To, cc, and Bcc (or Resent-To, and so on). Note that the header key/values supplied by the -header option (not those present in the MIME part) are consulted. Regardless, header key/values are added to the outgoing message as necessary to ensure that a valid 822-style message is sent. The command returns a list indicating which recipients were unacceptable to the SMTP server. Each element of the list is another list, con- taining the address, an SMTP error code, and a textual diagnostic. Depending on the -atleastone option and the intended recipients, a non- empty list may still indicate that the message was accepted by the server. EXAMPLE
proc send_simple_message {recipient email_server subject body} { package require smtp package require mime set token [mime::initialize -canonical text/plain \ -string $body] mime::setheader $token Subject $subject smtp::sendmessage $token \ -recipients $recipient -servers $email_server mime::finalize $token } send_simple_message someone@somewhere.com localhost \ "This is the subject." "This is the message." REFERENCES
[1] Jonathan B. Postel, "SIMPLE MAIL TRANSFER PROTOCOL", RFC 821, August 1982. (http://www.rfc-editor.org/rfc/rfc821.txt) [2] J. Klensin, "Simple Mail Transfer Protocol", RFC 2821, April 2001. (http://www.rfc-editor.org/rfc/rfc2821.txt) [3] P. Hoffman, "SMTP Service Extension for Secure SMTP over Transport Layer Security", RFC 3207, February 2002. (http://www.rfc-edi- tor.org/rfc/rfc3207.txt) [4] J. Myers, "SMTP Service Extension for Authentication", RFC 2554, March 1999. (http://www.rfc-editor.org/rfc/rfc2554.txt) BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category smtp of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. SEE ALSO
ftp, http, mime, pop3 KEYWORDS
email, internet, mail, mime, net, rfc 2554, rfc 2821, rfc 3207, rfc 821, rfc 822, smtp, tls CATEGORY
Networking COPYRIGHT
Copyright (c) 1999-2000 Marshall T. Rose and others mime 1.4.5 smtp(n)
All times are GMT -4. The time now is 11:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy