En bouncebesked er information fra en e-mailserver om, at en e-mailadresse ikke fungerer. Det kan være den e-mailserver, der står for at sende e-mailen ud i verden (altså Ubivox) eller den, der tager imod.
Det er vigtigt at få fjernet e-mailadresser, der bouncer flere gange, da det kan have negativ indflydelse på din og vores leveringssikkerhed, hvis det ikke gøres.
Ubivox håndterer automatisk alle bouncebeskeder vi modtager, og du skal altså som kunde intet gøre for at fjerne modtagerne.
Typer af bounces – soft og hard
Der findes to typer bounces – soft bounces og hard bounces. Soft bounces er midlertidige fejl, f.eks. en fyldt indbakke, der gør at e-mailen ikke kan gemmes hos modtageren. Hard bounces er permanente fejl, f.eks. at en e-mailadresse ikke længere findes hos et firma, fordi den ansatte ikke længere er ansat.
Vi fjerner hard bounces første gang vi støder på dem, og vi fjerner soft bounces efter gentagne fejlbeskeder. Eftersom Ubivox forsøger at levere e-mails i op til 48 timer efter de er sendt ud i verden, kan der gå et stykke tid før en bouncebesked bliver sendt til os og bliver behandlet.
Liste over fejlkoder
Der findes mange forskellige typer bounces, og vores system prøver at kategorisere dem ud fra type og indhold. Her følger en ikke-komplet liste over de typiske fejlbeskeder vi tager imod:
|
10 – Bad email address
hard |
This is a hard bounce where we were able to positively identify that delivery attempts to this email address should no longer be attempted. This usually indicates that the requested mailbox does not exist. |
|
20 – Temp failure – General
soft |
This is a soft bounce which indicates a possibly temporary failure in delivery of the message. The email address itself may or may not be invalid. This is often the result of ambiguous messages such as a mailbox being “inactive” or “unavailable”. |
|
21 – Temp failure – DNS Failure
soft |
This is a soft bounce caused by a failed DNS lookup. This can be caused by failures in DNS lookup either by Ubivox itself or subsequent relay servers. |
|
22 – Temp failure – Mailbox full
soft |
This is a soft bounce caused by the recipient’s mailbox or quota being full. |
|
23 – Temp failure – Message size too large
other |
This is an other bounce caused by the destination email server rejecting the message due to its size. |
|
24 – Temp failure – Missing MX record
soft |
No MX records were found for this recipient. |
|
29 – Temp failure – Unable to connect
soft |
This is a soft bounce where we were unable to connect to the remote server. |
|
40 – General bounce
other |
This is an other bounce that could not otherwise be categorized. Ubivox positively identified that this is a bounce message, but was unable to determine a more specific category. |
|
50 – Mail block – General
other |
This is an other bounce caused by the remote server rejecting the message for reasons that are not otherwise covered by a more specific “Mail block” category. |
|
52 – Mail block – Spam detected
other |
This is an other bounce caused by the remote server rejecting the individual message content as spam. |
|
53 – Mail block – Attachment detected
other |
This is an other bounce caused by the remote server rejecting the individual message due to its inclusion of one or more attachments. |
|
54 – Mail block – Relay denied
other |
This is an other bounce caused by the remote server refusing to serve as a relay for delivery of the message. |
|
55 – Mail block – SPF/DKIM/DMARC
other |
This is an other bounce caused by the remote server refusing delivery of the message due to SPF, DKIM, or DMARC policies. Resolving the specific complaint in the bounce message can often improve deliverability. |
|
59 – Mail block – Unable to connect
other |
This is an other bounce where we were unable to connect to the remote server (much
like code |
|
60 – Auto-reply
other |
These are messages received by the bounce processor that were generated by an auto-reply system such as a vacation autoresponder. These are not actual bounces. |
|
70 – Transient bounce
other |
This is an other bounce caused by a temporary delay in message transmission. The remote server will usually continue trying to deliver the message for a limited period of time. |
|
90 – Unsubscribe request
hard |
This is a hard bounce caused by a request to unsubscribe from the mailing list. |
|
200 – Spam Complaint
n/a |
Fejl i bounces
I ganske få tilfælde kategoriseres en bouncebesked forkert, hvilket medfører at en kontakt fjernes fra listen. Sker det kan vores support hjælpe med at genaktiver kontakten på listen.
Hvis du mangler information eller hjælp, som du ikke finder her på guide sitet, er du altid velkommen til at kontakte vores support!
support@ubivox.com / tlf. 70 70 13 37