Results 1 to 16 of 16
  1. #1
    Join Date
    Mar 2001
    Posts
    1,434

    AOL blocking all "apache" like return-paths

    Just an FYI: AOL mail servers are now rejecting all emails with a return path of anything like nobody@, httpd@, apache@, sender@, www@, root@, etc... This is their new system to cut down on spam. Of course if you have any web based scripts that send email (ecommerce receipts, forms, etc...) then they will be rejected.

    Seems like a dumb move to me, but AOL thinks it is best for their members. Check your mail logs if you send a lot of email to AOL from web based scripts.

    - John C.

  2. #2
    Join Date
    Jul 2002
    Posts
    1,441
    Where did you find this info at?
    Synergy Blue LLC
    SonataWeb.net | SynergyBlue.com
    USA should so something about: http://www.brillig.com/debt_clock/

  3. #3
    Join Date
    Mar 2001
    Posts
    1,434
    AOL postmaster support center. We realized emails to AOL that orignated from web scripts were being blocked, so we inquired, and that is what they told us. We confirmed it as emailing directly to AOL from the server was fine, but a script on the server such as a form would be rejected.

    I can't believe they took such a drastic action, and I'm surprised more people haven't noticed or complained yet...

    - John C.

  4. #4
    Join Date
    Jul 2002
    Posts
    1,441
    They are just digging a hole for themselves
    Synergy Blue LLC
    SonataWeb.net | SynergyBlue.com
    USA should so something about: http://www.brillig.com/debt_clock/

  5. #5
    Join Date
    Mar 2003
    Location
    Canada
    Posts
    8,909
    Thanks for the headsup.

    I never get spam from any of those names@ though....
    Patrick William | RACK911 Labs | Software Security Auditing
    400+ Vulnerabilities Found - Quote @ https://www.RACK911Labs.com

    www.HostingSecList.com - Security notices for the hosting community.

  6. #6
    Join Date
    Mar 2001
    Posts
    1,434
    It's not the from: address, but the return-path in the envelope matching those names that triggers the block. This will affect most webservers that send out email from scripts that run as the webserver.

    - John C.

  7. #7
    Join Date
    Jul 2003
    Location
    Nothing but, net
    Posts
    2,062
    At least give us a link to the postmaster.aol.com address that this info is provided on.

  8. #8
    Join Date
    Mar 2001
    Posts
    1,434
    And there's the kicker. AOL has not disclosed this information yet on their site. If you are whitelisted already, you can get to a higher support level that will explain this... Gotta love AOL.

    Right now, you just get the DYN:T1 dynamic block message, that links to:
    http://postmaster.info.aol.com/errors/421dynt1.html

    - John C.

  9. #9
    Join Date
    Oct 2000
    Location
    Midwest
    Posts
    159
    Looks like we are having the same or similar issue with AOL. Mail sent from Outlook through our server is delivered to AOL just fine. Our notification email generated by Perl scripts on our server are sitting in the queue for the last 6 days. When trying to send we see a ttp://postmaster.info.aol.com/errors/421rlycs4.html error. I have an open ticket with AOL, but if I can not resolve it I may suggest all 50,000 members of my site that use AOL contact their support folks...
    "Windows has detected the mouse has moved, Please restart your system
    for changes to take effect."

  10. #10
    That's what they offer in their latest final attempt to save the company?
    Looks like they want to go bankrupt to me.

  11. #11
    Join Date
    Oct 2000
    Location
    Midwest
    Posts
    159
    as a test I wrote a quick one line script to change

    nobody 99 99
    <[email protected]>

    to

    nobody 99 99
    <[email protected]>

    on all the messages in the mail queue

    Mail is flying out of the server like lightning..

    I guess this is proof that AOL is rejecting mail based on the term Nobody
    "Windows has detected the mouse has moved, Please restart your system
    for changes to take effect."

  12. #12
    Join Date
    Oct 2000
    Location
    Midwest
    Posts
    159

  13. #13
    Anybody know if subscribers@ or no-reply@ would fall into this category of
    generic reply-to? I just started seeing a lot of 421rlycs4 errors in my maillogs.

    Thanks a ton..

  14. #14
    Join Date
    Oct 2000
    Location
    Midwest
    Posts
    159

  15. #15
    Join Date
    Sep 2002
    Location
    Top Secret
    Posts
    11,686
    This doesn't surprise me, and adds to the "don't use AOL" reasoning.
    Can this be worked around? You bet. Use smart software that actually uses an smtp server connection, such as vb, or phpbb (I think). They're just digging their own hole here, but I see the reasoning for it. A LOT of spam comes from those "webmail" forms and, sadly, individuals just won't fix those, or take them off the 'net, even tho they're highly exploitable.
    WHMCS Guru - WHMCS addons, management, support and more.
    WHMCS Notifications Extended - Add slack, hipchat, SMS, pushover to WHMCS !!
    Always looking for Linux, WHMCS, Support Desk work. PM for details

  16. #16
    Join Date
    Jul 2004
    Posts
    246
    Looks like a thread started at cpanel too;

    http://forums.cpanel.net/showthread.php?t=47711

    Installing phpsuexec may take care of it, but you will need to tweak settings and files if your scripts break.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •