Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Email - Unsolicited Rate Limit Error Post 303042411 by Neo on Tuesday 24th of December 2019 12:28:24 AM
Old 12-24-2019
Google limits mail forwarded though their relays to avoid and help manage spam.

Maybe you should "get off" gmail and build your own email servers since you have a lot of mail traffic.

That's my suggestion. Move to your own SMTP servers / infrastructure and "get off" gmail.
This User Gave Thanks to Neo For This Post:
 

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
CheckUser(3pm)						User Contributed Perl Documentation					    CheckUser(3pm)

NAME
Mail::CheckUser - check email addresses for validity SYNOPSIS
use Mail::CheckUser qw(check_email); my $ok = check_email($email_addr); use Mail::CheckUser qw(:constants check_email last_check) my $ok = check_email($email_addr); print "DNS timeout " if last_check()->{code} == CU_DNS_TIMEOUT; use Mail::CheckUser; my $res = Mail::CheckUser::check_email($email_addr); DESCRIPTION
This Perl module provides routines for checking validity of email address. It makes several checks: 1. It checks the syntax of an email address. 2. It checks if there any MX records or A records for the domain part of the email address. 3. It tries to connect to an email server directly via SMTP to check if mailbox is valid. Old versions of this module performed this check via the VRFY command. Now the module uses another check; it uses a combination of MAIL and RCPT commands which simulates sending an email. It can detect bad mailboxes in many cases. If is possible to turn off some or all networking checks (items 2 and 3). See "GLOBAL VARIABLES". This module was designed with CGIs (or any other dynamic Web content programmed with Perl) in mind. Usually it is required to quickly check e-mail addresses in forms. If the check can't be finished in reasonable time, the e-mail address should be treated as valid. This is the default policy. By default if a timeout happens the result of the check is treated as positive. This behavior can be overridden - see "GLOBAL VARIABLES". IMPORTANT WARNING
In many cases there is no way to detect the validity of email addresses with network checks. For example, non-monolithic mail servers (such as Postfix and qmail) often report that a user exists even if it is not so. This is because in cases where the work of the server is split among many components, the SMTP server may not know how to check for the existence of a particular user. Systems like these will reject mail to unknown users, but they do so after the SMTP conversation. In cases like these, the only absolutely sure way to determine whether or not a user exists is to actually send a mail and wait to see if a bounce messages comes back. Obviously, this is not a workable strategy for this module. Does it mean that the network checks in this module are useless? No. For one thing, just the DNS checks go a long way towards weeding out mistyped domain parts. Also, there are still many SMTP servers that will reject a bad address during the SMTP conversation. Because of this, it's still a useful part of checking for a valid email address. And this module was designed such that if there is exists possibility (however small) that the email address is valid, it will be treated as valid by this module. Another warning is about $Mail::CheckUser::Treat_Timeout_As_Fail global variable. Use it carefully - if it is set to true then some valid email addresses can be treated as bad simply because an SMTP or DNS server responds slowly. Another warning is about $Mail::CheckUser::Treat_Full_As_Fail global variable. Use it carefully - if it is set to true then some valid email addresses can be treated as bad simply because their mailbox happens to be temporarily full. EXAMPLE
This simple script checks if email address "blabla@foo.bar" is valid. use Mail::CheckUser qw(check_email last_check); my $email = 'blabla@foo.bar'; if(check_email($email)) { print "E-mail address <$email> is OK "; } else { print "E-mail address <$email> isn't valid: ", last_check()->{reason}, " "; } SUBROUTINES
$ok = check_email($email) Validates email address $email. Return true if email address is valid and false otherwise. $res = last_check() Returns detailed result of last check made with "check_email" as hash reference: { ok => OK, code => CODE, reason => REASON } OK True if last checked email address is valid. False otherwise. CODE A number which describes result of last check. See "CONSTANTS". REASON A string which describes result of last check. CONSTANTS
Constants used by "last_check" to describe result of last check can be exported with use Mail::CheckUser qw(:constants) List of all defined constants: CU_OK Check is successful. CU_BAD_SYNTAX Bad syntax of email address. CU_UNKNOWN_DOMAIN Mail domain mentioned in email address is unknown. CU_DNS_TIMEOUT Timeout has happen during DNS checks. CU_UNKNOWN_USER User is unknown on SMTP server. CU_SMTP_TIMEOUT Timeout has happen during SMTP checks. CU_SMTP_UNREACHABLE All SMTP servers for mail domain were found unreachable during SMTP checks. CU_MAILBOX_FULL Mailbox is temporarily full but probably a valid username. GLOBAL VARIABLES
It is possible to configure "check_email" using the global variables listed below. $Mail::CheckUser::Skip_Network_Checks If true then do only syntax checks. By default it is false. $Mail::CheckUser::Skip_SMTP_Checks If it is true then do not try to connect to mail server to check if a user exists. If this is true, and $Mail::CheckUser::Skip_Network_Checks is false, only syntax and DNS checks are performed. By default it is false. $Mail::CheckUser::Skip_SYN By default Net::Ping is used to determine remote reachability of SMTP servers before doing SMTP checks. Setting this to true skips this check. By default it is false. $Mail::CheckUser::Sender_Addr MAIL/RCPT check needs an email address to use as the 'From' address when performing its checks. The default value is "check@user.com". $Mail::CheckUser::Helo_Domain Sender domain used in HELO SMTP command. If undef Net::SMTP is allowed to use its default value. By default it is undef. Mail::CheckUser::Timeout Timeout in seconds for network checks. By default it is 60. $Mail::CheckUser::Treat_Timeout_As_Fail If it is true "Mail::CheckUser" treats checks that time out as failed. By default it is false. $Mail::CheckUser::Treat_Full_As_Fail If it is true "Mail::CheckUser" treats error "552 mailbox full" as an invalid email and sets CU_MAILBOX_FULL. By default it is false. $Mail::CheckUser::Net_DNS_Resolver Override with customized Net::DNS::Resolver object. This is used to lookup MX and A records for the email domain when network checks are enabled. If undef, Net::DNS::Resolver->new will be used. The default value is undef. $Mail::CheckUser::Debug If it is true then enable debug output on "STDERR". By default it is false. AUTHORS
Ilya Martynov ilya@martynov.org Rob Brown bbb@cpan.org Module maintained at Source Forge ( http://sourceforge.net/projects/mail-checkuser/ ). COPYRIGHT
Copyright (c) 1999-2003 by Ilya Martynov. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. $Id: CheckUser.pm,v 1.46 2003/09/18 23:51:36 hookbot Exp $ SEE ALSO
perl(1). perl v5.14.2 2012-03-10 CheckUser(3pm)
All times are GMT -4. The time now is 11:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy