• Email

    Author
    Topic
    #376461

    Using 2000 Exchange mail server. Bellsouth is our DSL provider. We have a customer who can not receive email we send. No problem with sending email to any one else. And they have no problem “receiving” email from any one else. We can receive email from this customer, but when we try to “reply” we get an notification from our server stating the following: The recipient could not be reached: You do not have permission to send to this recipient. For assistance, contact your system administrator and it has a number of #5.7.1. AND, their email address has changed by adding +AEA- in the middle of “their” address. However, if we type in the email address to send a “new” email, we still get the same error messages but the email address stays the same without adding the +AEA-.

    So my questions is….has any one else had this problem and if so, is there a way to correct the problem? And where is the problem? Is it our end, even though we have no other problems with sending email to any one else. Or is it our customers problem, even though they can receive email from others? And last but not least, how can we correct the problem?

    please PLEASE HELP!!! confused

    Viewing 1 reply thread
    Author
    Replies
    • #616660

      I’ve seen this problem but have never had time to really look into it. A quick search on Google Groups turned up a few hits. Hopefully one of these will steer you in the right direction:

      http://groups.google.com/groups?num=30&amp…this+recipient”%5B/url%5D

    • #616693

      You might want to double-check that you are not on any of the “black hole” lists that some ISPs use to bounce spam mail. Any company whose message travels through an open relay can get on the list.

      If you post or private mail me your SMTP server address, I can try to bounce a message through it to see if it’s relaying for strangers.

      • #619925

        I want to thank you and CMUNRO for your help in the right direction. This has been a hair pulling experience. Therefore, I wanted to post the out come to help others that may run across this problem in the future. (and maybe spare you the hair loss hairout)

        At our company we do not have a static IP address from our provider, therefore it changes periodically. It appears all “non” static address ranges on our providers network is on a list to prevent someone from using one of their addresses to spam people. Only end users that subscribed to this blocking service failed to receive our mail. To work around this, you must either obtain a static IP address or change the configuration on your exchange mail server. You need to configure your outgoing mail to go directly to your provider and the provider forwards the email to the recipient. Instead of the mail going directly from you or your server to the recipient which is how ours “was” set up. Now when we send an email it shows it is delivered from (imf15dis.provider.net) with the providers static IP address instead of our (server.name.local) at whatever current non static IP address our providers has us on at that time. For more information there is a web site that will explain in more detail. It is http://www.mail-abuse.org.

        • #619930

          Julie,

          Thanks for following up! Valuable information.

    Viewing 1 reply thread
    Reply To: Email

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: