This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Feature Request/BUGFIX: Quarantine report sent to unexisting mail addresses

Quarantine report sent to unexisting mail addresses.
All this mail will not be received by internal mail server and will be stuck in spool for a long time.

Should not the Astaro check recipient and discard bad addresses before trying to send Q. report?

Cheers,

Matan


This thread was automatically locked due to age.
Parents
  • Just verify recipients (with callout) when receiving your mails.
    So mails to non-existing recipients will be blocked at SMTP time.

    Regards,
    Tom
  • I just checked the Mail Manager for our own domain.  We use "With callout" and the Astaro still accepts email for non-existant recipients.

    I'll submit a support request.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • The good news is that 'Verify Recipient' "In Active Directory" works perfectly with Windows Server 2003.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Doh!  Like most mysteries, once we had the answer, it was obvious...

    The problem isn't that the Astaro is trying to send to non-existant email addresses, it's that it didn't reject those emails in the first place!  When using "In Active Directory," Astaro queries the AD.  When using "With callout," Astaro queries the email server.  If the mail server isn't configured to reject emails to unknown users, then the Astaro respects that and won't reject them either!

    I reinstalled our system from scratch onto a new server earlier this year.  I failed to tell Exchange to reject unknown recipients.  Here's what you need to do if you have Exchange 2003:
    [LIST=1]
    • On your Exchange 2003 server, start the 'Exchange System Manager'
    • Open the 'Global Settings' folder, right-click on 'Message Delivery' and select 'Properties'
    • On the 'Recipiet Filtering' tab, check the box for 'Filter recipients who are not in the Directory'
    • Click [OK] to save your change
    • Click [OK] to acknowledge the warning
    [/LIST]
    Cheers - Bob
    PS I opened a case with Astaro, and Tim_Astaro responded.  He pointed me in the right direction by suggesting that I telnet to my Exchange server to see how it responded to a RCPT TO to a bogus address.  Here's what happened:

    telnet  25
    220 OurDomain.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at  Fri, 24 Apr 2009 16:47:31 -0500

    HELO MyPC.OurDomain.local
    250 OurDomain.com Hello [10.x.x.64]
    MAIL FROM: me@OurDomain.com
    250 2.1.0 me@OurDomain.com....Sender OK
    RCPT TO: bogus@OurDomain.com
    250 2.1.5 bogus@OurDomain.com


    After I made the change above on my Exchange server, an email from my Gmail account to bogus@OurDomain.com was rejected as it should have been.

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Thank U!

    for verify recipient in AD, do I need to set up AD authentication, under users?
Reply Children
  • I think you're going to laugh at yourself when you look at the note beside the selection in WebAdmin...
    To use Active Directory, you must have an Active Directory Server specified in Users -> Authentication -> Active Directory. The Base DN setting here is optional.


    [;)] - Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA