The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Domain Exceeded Max Emails Per Hour via Script only

Discussion in 'E-mail Discussions' started by acenetryan, Dec 4, 2007.

  1. acenetryan

    acenetryan Well-Known Member
    PartnerNOC

    Joined:
    Aug 21, 2005
    Messages:
    197
    Likes Received:
    1
    Trophy Points:
    18
    We have a user who is unable to send emails via a script.

    It works fine when you send using any email account. Only when sending email via a script does the user receive the message:

    domain.tld has exceeded the max emails per hour

    I've checked his smtp bytes log and the last recorded email was well beyond an hour ago. He has definitely not exceeded the max emails per hour.

    I was unable to determine exactly why he is getting this, but I did find that when I cleared:

    /var/cpanel/maxemailstracker/domain.tld

    he was able to send again. This file appears to be a cached representation of how many emails he's sent in the last hour. What script updates these files?

    Does anyone know what the "timestamps" present in these files represent? e.g.:

    0.1.0.70=<NUMBER OF EMAILS SENT IN LAST HOUR (not really)>

    I've reset Exim to defaults, updated exim, and updated cPanel. No love.

    As I mentioned, it's corrected now that I've cleared out that file, but I have the distinct feeling it's coming back as soon as he sends another 200 emails (200 is our imposed sending limit).
     
  2. silversurfer

    silversurfer Well-Known Member

    Joined:
    Dec 29, 2002
    Messages:
    274
    Likes Received:
    0
    Trophy Points:
    18
    Yup. Seeing this issue as well. The email count appears not to be reset and absolutely no idea how this is reset. Any ideas?
     
  3. silversurfer

    silversurfer Well-Known Member

    Joined:
    Dec 29, 2002
    Messages:
    274
    Likes Received:
    0
    Trophy Points:
    18
  4. kernow

    kernow Well-Known Member

    Joined:
    Jul 23, 2004
    Messages:
    865
    Likes Received:
    9
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    You could allow that user to bypass the default max email per hour by editing ( or create if it doesn't exist ) the file /var/cpanel/maxemails . So if 200 is your hourly limit but you want domain.com to send 500 then edit to read:
    Code:
    domain.com=500
    Note If you put domain.com=0 then that domain will be excluded from any hourly limit.
     
  5. Metro2

    Metro2 Well-Known Member

    Joined:
    May 24, 2006
    Messages:
    376
    Likes Received:
    10
    Trophy Points:
    18
    Location:
    USA
    cPanel Access Level:
    Root Administrator
    Is it only resolved for Edge and Current? Because I'm running Release WHM 11.11.0 cPanel 11.15.0-R18264 and even after upcp --force the problem still exists for me.

    maxemailtracker is still not resetting hourly
     
  6. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Note that 18264 (what you're running) is less than 18284 (the build where this was fixed) :).
     
  7. Metro2

    Metro2 Well-Known Member

    Joined:
    May 24, 2006
    Messages:
    376
    Likes Received:
    10
    Trophy Points:
    18
    Location:
    USA
    cPanel Access Level:
    Root Administrator
    Note that I have used WHM > Cpanel > Upgrade to Latest Version and also run /scripts/upcp --force and that is the version I still get - 18264 - which is why I asked the question - if the resolution was only for Current and/or Edge.

    Just trying to find out of there's something wrong on my server and thought I'd ask here before submitting a ticket. Excuse me for not being smart enough to know that by simply seeing a version number in a bugzilla ticket that says "issue is resolved in 18284" without stating whether that is Release or not.

    Sorry, but after the crap I've been through with cPanel in the last two weeks, I don't have much of a sense of humor.
     
  8. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Note changelog.cpanel.net shows the latest build numbers for the various builds as follows (meaning, if you were to run upcp, this would be the highest build number you could get at the moment):

    EDGE: 18335
    CURRENT: 18335
    RELEASE: 18264
    STABLE: 18033

    As with any bug fix or enhancement, it will propagate through the builds being in EDGE first and STABLE last. Once the build number for RELEASE goes beyond 18284 then you will have this particular fix. If you do not want to wait for the fix to propagate to RELEASE, then you may want to run CURRENT. However, remember that CURRENT is not as thoroughly tested as RELEASE and does not adhere to the same quality standards as RELEASE as a result.
     
  9. Metro2

    Metro2 Well-Known Member

    Joined:
    May 24, 2006
    Messages:
    376
    Likes Received:
    10
    Trophy Points:
    18
    Location:
    USA
    cPanel Access Level:
    Root Administrator
  10. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Because not every build the developers make is pushed out to the 4 main builds, hence statements such as the one in the bugzilla entry: >18284, meaning the next released build with a number bigger than 18284,
     
  11. Metro2

    Metro2 Well-Known Member

    Joined:
    May 24, 2006
    Messages:
    376
    Likes Received:
    10
    Trophy Points:
    18
    Location:
    USA
    cPanel Access Level:
    Root Administrator
    Thanks for answering both questions, one before I even asked it :)
     
    #11 Metro2, Dec 5, 2007
    Last edited: Dec 5, 2007
  12. heavypredator

    heavypredator Well-Known Member

    Joined:
    May 2, 2003
    Messages:
    93
    Likes Received:
    1
    Trophy Points:
    8
    This is stupid - its critical issue if scripts cant send emails - it should be propagated in all builds asap
     
    Metro2 likes this.
  13. 4u123

    4u123 Well-Known Member
    PartnerNOC

    Joined:
    Jan 2, 2006
    Messages:
    765
    Likes Received:
    1
    Trophy Points:
    18
    Bump!!

    Any ideas when this fix might reach release ?
     
  14. 4u123

    4u123 Well-Known Member
    PartnerNOC

    Joined:
    Jan 2, 2006
    Messages:
    765
    Likes Received:
    1
    Trophy Points:
    18
    We are now getting lots of complaints from customers and this is becoming a critical issue.

    We have too many servers to keep resetting the limits every few hours and I'm not prepared to increase the limits because im concerned about the security of my servers.

    This is a major blunder guys - please put this fix into todays update!
     
    Metro2 likes this.
  15. Metro2

    Metro2 Well-Known Member

    Joined:
    May 24, 2006
    Messages:
    376
    Likes Received:
    10
    Trophy Points:
    18
    Location:
    USA
    cPanel Access Level:
    Root Administrator
    Any estimate on when we might expect 18284 for Release which was built (according to bugzilla) back on December 3rd and doesn't have this issue?
     
  16. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,458
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Release 18373 was released last night.
     
  17. Metro2

    Metro2 Well-Known Member

    Joined:
    May 24, 2006
    Messages:
    376
    Likes Received:
    10
    Trophy Points:
    18
    Location:
    USA
    cPanel Access Level:
    Root Administrator

    Thanks. I was just going by http://changelog.cpanel.net/ which still shows 18264 as the latest version of Release.
     
  18. cPanelKenneth

    cPanelKenneth cPanel Development
    Staff Member

    Joined:
    Apr 7, 2006
    Messages:
    4,458
    Likes Received:
    22
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    The change log will always lag the actual build, due to various reasons. Checking layer1.cpanel.net will show you the latest build numbers.
     
  19. Metro2

    Metro2 Well-Known Member

    Joined:
    May 24, 2006
    Messages:
    376
    Likes Received:
    10
    Trophy Points:
    18
    Location:
    USA
    cPanel Access Level:
    Root Administrator
    We appear to still be having this issue after upgrading to 18373.

    Anyone else?
     
  20. Metro2

    Metro2 Well-Known Member

    Joined:
    May 24, 2006
    Messages:
    376
    Likes Received:
    10
    Trophy Points:
    18
    Location:
    USA
    cPanel Access Level:
    Root Administrator
    Up to cPanel 11.16.0-R18450 and this problem still exists - once a script on a user's account reaches the max email per hour they can send (300 on my settings), the file /var/cpanel/maxemailstracker/theirdomain.com gets "stuck" and will not reset back to 0. So for example, if I have a customer who has a script (such as a forum or newsletter) that sends out 301 emails, they can't send any more unless I manually delete the file /var/cpanel/maxemailstracker/theirdomain.com

    This was a confirmed bug in cpanel that was supposedly fixed a couple releases ago, so my data center can't help me with it. I have submitted a direct ticket to cpanel regarding the issue in hopes to an answer / resolve, but just in case I'm overlooking something I thought to re-visit this thread as well.

    Anyone else still have this issue?
     
Loading...

Share This Page