Email help needed :)

[Ulquiorra]

So lately a person has been getting this bouncing mail when trying to send me an email:

What does it mean and how can I fix it?

"This is a delivery failure notification message indicating that
an email you addressed to email address :
-- blah@blah.com

could not be delivered. The problem appears to be :
-- Recipient email server rejected the message

Additional information follows :
-- Verification failed for <blahblah@blahlol.com>
Unrouteable address
Sender verify failed

This condition occurred after 1 attempt(s) to deliver over
a period of 0 hour(s).

If you sent the email to multiple recipients, you will receive one
of these messages for each one which failed delivery, otherwise
they have been sent."


Thanks for any info !

 

[skeptic_SA]

Might be your email address? Blah@blah.com sounds more like a website name and doesn't appear to have the correct suffix that an email address would have?

 

[Ho3n3r]

Might be your email address? Blah@blah.com sounds more like a website name and doesn't appear to have the correct suffix that an email address would have?

I'm guessing that is not the real address...

 

[CamiKaze]

I'm guessing that is not the real address...

He was being sarcastic... or...

 

[skeptic_SA]

I'm guessing that is not the real address...

"This is a delivery failure notification message indicating that
a reply you addressed to:
--skeptic_SA
could not be delivered. The problem appears to be :
-- Recipient rejected the message"

 

[Ho3n3r]

He was being sarcastic... or...

Forgot the comic sans then. I really struggle sensing tone in text messages.

 

[Grimis]

the bounce is largely incomplete rather post it its entirety but replace address'

is it being generating from the senders servers or your internal servers?
Unrouteable address - is vague
Sender verify failed - the sender domain could be blacklisted and your filter is blocking

 

[Ulquiorra]

-----Original Message-----
From: Domain postMaster address [mailtoostmaster@lamarinafoods.co.za]
Sent: 03 November 2016 03:24 PM
To: meh.
Subject: [Postmaster] Email Delivery Failure

This is a delivery failure notification message indicating that
an email you addressed to email address :
-- recipient's email address replaced

could not be delivered. The problem appears to be :
-- Recipient email server rejected the message

Additional information follows :
-- Verification failed for <sender's email address replaced>
Unrouteable address
Sender verify failed

This condition occurred after 1 attempt(s) to deliver over
a period of 0 hour(s).

If you sent the email to multiple recipients, you will receive one
of these messages for each one which failed delivery, otherwise
they have been sent.


Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more Click Here.


It is generated by the senders server, but she's giving my email the blame, which is working however >.<" I don't have any problem receiving sending to anyone else, and i can send her emails.

 

[Grimis]

you appear to be @lamarinafoods.co.za behind Mimecast servers, best to log a ticket with support@mimecast.co.za

cant see sender domain
use mxtoolbox.com, do a blacklist:*senderdomain* to see if they are listed anywhere, if not best to contact mimecast.

gluck

 

[sajunky]

You have to be more specific regarding your setup as remedy is different.

1. SMTP server belongs to your ISP network. In such case you are already authenticated, but SMTP server you use is blacklisted on Internet. It happens on public ISP servers.

2. SMTP server belongs to your Email provider which is different to your ISP. In such case you should use authenticate option, usually the same login/password as for your incoming mail server. I think it is your case, as server tries to authenticate you by IP address and fails on that.

 

[WAslayer]

by the looks of it, your mail server aka the recipient mail server in the bounceback, is attempting to verify that the senders email address does indeed exist and is unable to do so, hence the error.. so the sender may be sending from an alias or another address unknown to the rest of the internet which is why the error is being received.. but contact your email provider, explain the issue to them.. if they are worth their salt, they should be able to diagnose the issue in minutes and send you logs which you can send to the sender which the sender can send to their email provider if needed to resolve the issue..

 

[Ivork]

That error is symptomatic of your organization's / ISP MTA using an anti-spoofing technique called "callout" or "callback". Google it.

Essentially your email server first checks to see if the sender does infact exist before accepting their message.
If your buddy @lamarinafoods.co.za (mimecast server) is blocking such lookups, or she is sending out from an incorrect address etc they will get such a message back. If Mimecast finds that YOUR server is blacklisted it will refuse to talk to it as well (before the 250 OK or recipient OK which your callback server is looking for), resulting in your server not been able to verify the address and therefore not accepting it, and therefore your buddy's MTA sending her that failure message back.

So she receive mail from you.
You can send to yourbuddy@lamarinafoods.co.za but she can't send to you@YourDomain.com.

So you probably relaying via another server other than your receiving MTA - that is fine and why it works.
Remember it is your receiving server (what your MX records point to) that will be doing the callback check.

It is generated by the senders server, but she's giving my email the blame, which is working however >.<" I don't have any problem receiving sending to anyone else, and i can send her emails.

That you are aware of......sending no prob.
Messages not received how would you know unless they foned you?

So she is correct! - it is your MX MTA's fault that they can't send you email.
Find out why and fix it or disable the callout feature.

We don't have ip's and at the very least would need your domain before we can help further.