Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Email - Unsolicited Rate Limit Error Post 303042412 by baris35 on Tuesday 24th of December 2019 12:44:01 AM
Old 12-24-2019
Thank you Neo,
We will swap to paid gmail service.

Kind regards
Boris
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

rate of process

How can I determine if the data collection rate is 1 Hz on Solaris? (0 Replies)
Discussion started by: laila63
0 Replies

2. UNIX for Dummies Questions & Answers

Counting Files and send an email Notification if it exceeds a limit

Hi, I am trying to write a script to Count Files in a directory located on a remote server and send an email Notification if it exceeds a limit. The code given below doesnot check the condition and sends the mail everytime irrespective of the condition. I have put this script in the cron. Can... (10 Replies)
Discussion started by: amitsayshii
10 Replies

3. UNIX for Dummies Questions & Answers

Error, Login Limit Exceeded by 1 user

Would appreciate some help, system was displaying an error regarding the kernal when a "sar" was run, after a reboot we get "WARNING user login limit exceeded by 1 user". We have plenty of licences. any ideas? (1 Reply)
Discussion started by: nchrocc
1 Replies

4. UNIX and Linux Applications

Sendmail outgoing email rate

Does anyone know what's Sendmail outgoing email rate? e.g. 1000 outgoing email per minutes. If so, can we modify it? Thanks. :) (1 Reply)
Discussion started by: sunmagic2003
1 Replies

5. Shell Programming and Scripting

Check space of directories and send email if it has reached threshold limit

Hi, I need help in writing unix script for checking space of some directories on the system and also send an email when it reaches the threshold limit. I have written the followng code; #!/bin/ksh ADMIN="me@somewhere.com" # set alert level 80% is default THRESHOLD=80 df | grep -E... (5 Replies)
Discussion started by: jmathew99
5 Replies

6. AIX

Scan Rate

Hello, How can i tell ifthe ratio between fr and sr is ok? is fr/sr ratio of 0.9 acceptable? thanks. (1 Reply)
Discussion started by: LiorAmitai
1 Replies

7. Solaris

Limit: stacksize: Can't remove limit

Hi all, I'm using to Solaris machine. When I run a simple script this messenger come out:"limit: stacksize: Can't remove limit". Any one know the way to resolve this problem without reboot the machine? Thanks in advance. (3 Replies)
Discussion started by: Diabolist9
3 Replies

8. UNIX and Linux Applications

Autosys R11.3 : Error on log file size limit

Just had a migration from Autosys 4.5 to R11.3. After the migration to R11.3, Autosys jobs have been failing when the log file reaches a size of 800 MB. This did not happen before the migration, when Autosys 4.5 was used. Is there a way to configure the file size limit/cap in Autosys... (1 Reply)
Discussion started by: kimo222
1 Replies

9. Shell Programming and Scripting

How can I get the increased rate in MB?

Deal all, I have a directory called I want to know how many MBs are transferred to it every 2 hours. How can I do this? Any ideas? I have a simple idea but I can't translate it into shell script, the idea is: 1- get the size of the folder now, using 2- then get the size of the... (4 Replies)
Discussion started by: Mohannad
4 Replies

10. UNIX for Advanced & Expert Users

Limit transfer speed rate by iptables Rules

I have D-Link Router DSL-2730U that support busybox OS and iptables version 1.4.0 I managed successfully to block the host for being connect to the internet using the following command block by ip address iptables -I FORWARD -d 192.168.1.6 -j DROP Or By mac source iptables -I... (0 Replies)
Discussion started by: iLinux85
0 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 09:34 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy