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
Email::Address(3)					User Contributed Perl Documentation					 Email::Address(3)

NAME
Email::Address - RFC 2822 Address Parsing and Creation SYNOPSIS
use Email::Address; my @addresses = Email::Address->parse($line); my $address = Email::Address->new(Casey => 'casey@localhost'); print $address->format; VERSION
version 1.898 DESCRIPTION
This class implements a regex-based RFC 2822 parser that locates email addresses in strings and returns a list of "Email::Address" objects found. Alternatively you may construct objects manually. The goal of this software is to be correct, and very very fast. Package Variables ACHTUNG! Email isn't easy (if even possible) to parse with a regex, at least if you're on a "perl" prior to 5.10.0. Providing regular expressions for use by other programs isn't a great idea, because it makes it hard to improve the parser without breaking the "it's a regex" feature. Using these regular expressions is not encouraged, and methods like "Email::Address->is_addr_spec" should be provided in the future. Several regular expressions used in this package are useful to others. For convenience, these variables are declared as package variables that you may access from your program. These regular expressions conform to the rules specified in RFC 2822. You can access these variables using the full namespace. If you want short names, define them yourself. my $addr_spec = $Email::Address::addr_spec; $Email::Address::addr_spec This regular expression defined what an email address is allowed to look like. $Email::Address::angle_addr This regular expression defines an $addr_spec wrapped in angle brackets. $Email::Address::name_addr This regular expression defines what an email address can look like with an optional preceding display name, also known as the "phrase". $Email::Address::mailbox This is the complete regular expression defining an RFC 2822 emial address with an optional preceding display name and optional following comment. Class Methods parse my @addrs = Email::Address->parse( q[me@local, Casey <me@local>, "Casey" <me@local> (West)] ); This method returns a list of "Email::Address" objects it finds in the input string. The specification for an email address allows for infinitley nestable comments. That's nice in theory, but a little over done. By default this module allows for two (2) levels of nested comments. If you think you need more, modify the $Email::Address::COMMENT_NEST_LEVEL package variable to allow more. $Email::Address::COMMENT_NEST_LEVEL = 10; # I'm deep The reason for this hardly-limiting limitation is simple: efficiency. Long strings of whitespace can be problematic for this module to parse, a bug which has not yet been adequately addressed. The default behavior is now to collapse multiple spaces into a single space, which avoids this problem. To prevent this behavior, set $Email::Address::COLLAPSE_SPACES to zero. This variable will go away when the bug is resolved properly. In accordance with RFC 822 and its descendants, this module demands that email addresses be ASCII only. Any non-ASCII content in the parsed addresses will cause the parser to return no results. new my $address = Email::Address->new(undef, 'casey@local'); my $address = Email::Address->new('Casey West', 'casey@local'); my $address = Email::Address->new(undef, 'casey@local', '(Casey)'); Constructs and returns a new "Email::Address" object. Takes four positional arguments: phrase, email, and comment, and original string. The original string should only really be set using "parse". purge_cache Email::Address->purge_cache; One way this module stays fast is with internal caches. Caches live in memory and there is the remote possibility that you will have a memory problem. On the off chance that you think you're one of those people, this class method will empty those caches. I've loaded over 12000 objects and not encountered a memory problem. disable_cache enable_cache Email::Address->disable_cache if memory_low(); If you'd rather not cache address parses at all, you can disable (and re-enable) the Email::Address cache with these methods. The cache is enabled by default. Instance Methods phrase my $phrase = $address->phrase; $address->phrase( "Me oh my" ); Accessor and mutator for the phrase portion of an address. address my $addr = $address->address; $addr->address( "me@PROTECTED.com" ); Accessor and mutator for the address portion of an address. comment my $comment = $address->comment; $address->comment( "(Work address)" ); Accessor and mutator for the comment portion of an address. original my $orig = $address->original; Accessor for the original address found when parsing, or passed to "new". host my $host = $address->host; Accessor for the host portion of an address's address. user my $user = $address->user; Accessor for the user portion of an address's address. format my $printable = $address->format; Returns a properly formatted RFC 2822 address representing the object. name my $name = $address->name; This method tries very hard to determine the name belonging to the address. First the "phrase" is checked. If that doesn't work out the "comment" is looked into. If that still doesn't work out, the "user" portion of the "address" is returned. This method does not try to massage any name it identifies and instead leaves that up to someone else. Who is it to decide if someone wants their name capitalized, or if they're Irish? Overloaded Operators stringify print "I have your email address, $address."; Objects stringify to "format" by default. It's possible that you don't like that idea. Okay, then, you can change it by modifying $Email:Address::STRINGIFY. Please consider modifying this package variable using "local". You might step on someone else's toes if you don't. { local $Email::Address::STRINGIFY = 'host'; print "I have your address, $address."; # geeknest.com } print "I have your address, $address."; # "Casey West" <casey@geeknest.com> Modifying this package variable is now deprecated. Subclassing is now the recommended approach. Did I Mention Fast? On his 1.8GHz Apple MacBook, rjbs gets these results: $ perl -Ilib bench/ea-vs-ma.pl bench/corpus.txt 5 Rate Mail::Address Email::Address Mail::Address 2.59/s -- -44% Email::Address 4.59/s 77% -- $ perl -Ilib bench/ea-vs-ma.pl bench/corpus.txt 25 Rate Mail::Address Email::Address Mail::Address 2.58/s -- -67% Email::Address 7.84/s 204% -- $ perl -Ilib bench/ea-vs-ma.pl bench/corpus.txt 50 Rate Mail::Address Email::Address Mail::Address 2.57/s -- -70% Email::Address 8.53/s 232% -- ...unfortunately, a known bug causes a loss of speed the string to parse has certain known characteristics, and disabling cache will also degrade performance. SEE ALSO
Email::Simple, perl. AUTHOR
Originally by Casey West, <casey@geeknest.com>. Maintained, 2006-2007, Ricardo SIGNES <rjbs@cpan.org>. ACKNOWLEDGEMENTS
Thanks to Kevin Riggle and Tatsuhiko Miyagawa for tests for annoying phrase-quoting bugs! COPYRIGHT
Copyright (c) 2004 Casey West. All rights reserved. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.16.3 2013-02-07 Email::Address(3)
All times are GMT -4. The time now is 05:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy