Chat / support@radicenter.eu

Maildelivery error / Rämpsposti listid / SPAM jms…

1. Mail delivery error
2. Mail delivery error – SPF viga
3. Rämpsposti listid / filtrid

Mail delivery error

Kui olete saanud sarnase veateate:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

XXXXXX.XXXX@XXXXX.XX
SMTP error from remote mail server after RCPT TO:<XXXXXX.XXXX@XXXXX.XX>:
host mail.XXXXXXX.XX [XXX.XXX.XXX.XXX]: …

Tasub kontrollida, mis serverid on veateates mainitud ning milline veateade täpsemalt on.
Levinumad veateated ja nende inglisepärased vasted (vastavalt nendele saab määrata edasised toimingud):

550 – Requested actions not taken as the mailbox is unavailable.
550 is always a problem external to your own mail server.
Usually it is at the recipient’s end, but it could also originate from inside your own “walls” through being caused, for example, by an appliance which scans your outgoing emails once they’ve left your server.
(also called SMTP Error 5.5.0)

SMTP Error 550 will be returned by many servers If the recipient email address simply does not exist on the remote side (you will often get “550 Invalid recipient” or “550 User account is unavailable” or “ does not like recipient – 550 Address rejected” or “550 No such user here” or “550 Not our Customer” or “550 Account not available” or “Remote host said : 550 – Barack.Obama@ThisCompany.com, this THISCOMPANY.COM Mailbox Does Not Exist – Giving up”). In this case the sender of the email needs to contact the recipient verbally to get the correct email address.

————–

SMTP Error 550 will sometimes also be returned by the recipient’s anti-spam firewall if, for example, the anti-spam firewall does not like the sender (typically because the sender needs to be whitelisted). A typical example of an SMTP Error 550 return message by an anti-spam firewall might be :

240.240.240.240 does not like recipient.
Remote host said: 550-Verification failed for
John.Doe@YourDomain.com
550-Previous (cached) callout verification failure
550 Sender verify failed
Giving up on 240.240.240.240.

————–

SMTP Error 550 can also be returned by your own mail and web filtering appliance where the message leaves your mail server and is intercepted by your web and mail filtering appliance, before it leaves your premises, and for whatever configuration reasons it thinks your email is spam or dangerous for the recipient (in other words it tries to protect your company from accidentally sending viruses and accidental spam emails – through a PC being infected with a bot – to your customers). Here is a typical example of such a response :

The attached file had the following undeliverable recipient(s):
John.Doe@comcast.net

Transcript of session follows:
Command: Data…
Response: 550 Cyberoam Anti Spam Engine has identified
this email as a spam. Ref-
id:str=0001.0A0B0206.4BA7422C.01F5,ss=1,vtr=str,vl=0,p t =
————–

SMTP Error 550 will also be returned if the user’s mailbox is not local and Mail Relay is not enabled, or the sending address is invalid (the latter is a way, by the remote server, to control spam).

————–

Other situations of SMTP Error 550 include sending mail to recipients outside of your domain where this is not allowed.

————–

SMTP Error 550 is also returned when you are attempting to send through a server which requires SMTP authentication and you have not supplied credentials (ie. your mail server, or email program, is attempting to send without SMTP authentication)

————–

Yet another set of circumstances where an SMTP error 550 might be issued include an incorrect From address when used with an ISP where you can send mail only if the From address is from a domain that they host for you (at the time of writing, September 2008, and still at time of this update, Septemer 2012, British Telecom in the UK is such an ISP – you have to notify them through a lengthy, ridiculous, and almost soul destroying procedure, involving proving that you own the domain, for them to allow you to send emails from a domain name that they do not host for you).

————–

Another case of SMTP Error 550 is when the recipient’s server is down (or cannot receive mail at this time) and the ISP’s servers will retry periodically for a limited amount of time (this is often accompanied by a return mail from your ISP informing the sender of the email of just that situation).

————–

Another case of SMTP Error 550 is when the recipient’s server requires you to make a change to the To part of your email to achieve successful delivery of the email (some organizations configure their receiving mail servers in this way when they have changed their domain name and want to force the senders to update his address books – for example, My-Great-Company.com has changed its domain to MyGreatCompany.com and you are still using the old domain name).

————–

Yet another set of circumstances when the SMTP Error 550 is received is when the recipient’s mailbox has
been suspended. For instance, the QMAIL SMTP mail program has an endearing way of telling you about a mailbox that has been suspended : “I’m afraid I wasn’t able to deliver your message to the following addresses. This is a permanent error; I’ve given up. Sorry it didn’t work out. : does not like recipient. Remote host said: 550 [SUSPEND] Mailbox currently suspended – Please contact correspondent directly.”.

————–

Another circumstance of an SMTP Error 550 is when the recipient’s mailbox has been disabled. The typical reasons for this are the mailbox being full (the user needs to delete messages before new ones will be accepted) or the user not having paid a bill. An example of the reply you will receive is : “550 mailbox temporarily disabled”

————–

SMTP Error 550 can also occur when either your DNS or your ISP’s DNS is not configured correctly for the recipient’s mailserver details, or the recipient’s MX record is configured incorrectly. A typical error message for this type of error might be : “550-Verification failed for my@exchangeserver.com – 550-Unrouteable address – 550 Sender verify failed (in reply to RCPT TO command) “.

————–

”Mailbox is inactive”. Another instance of error 550 is when there is a temporary system-wide problem at the ISP. The error takes two forms, the one just quoted, or :
“5.1.0 – Unknown address error 550-‘Mailbox is inactive’”.

This error is almost always a problem at the hosting ISP which hosts the POP box(es) of the recipient’s email address or domain. You need to inform the recipient that there is a problem with their hosting company. So, for example, if you are sending an email to John.Doe@clara.net and you get the “Mailbox is inactive” error, then you need to tell John Doe that his hosting ISP, ClaraNET, are having problems with incoming emails and that he should talk to them.

Mail delivery error – SPF viga

Osa kliente on raporteerinud veateadetest, kus tuleb saatjal tagasiside:

SMTP error from remote mail server after RCPT TO::
host MAILISAAJA_HOST [HOSTI_IP]: 550 5.7.1 :
Recipient address rejected: Message rejected due to:
SPF fail – not authorized. Please see http://www.openspf.net/Why?s=mfrom;id=SAATJA_MAIL;ip=RADICENTERI_VAHESERVERI_IP;r=SAJJA_MAIL

Antud teade tähendab et olete:
1. saatnud maili kasutajale, kes on suunanud oma maili muule aadressile ja viimase mailiserver keeldub maili vastu võtmast kuna teie enda domeeni SPF on erinev vaheserveri SPF’ist
2. saatnud maili serverile, kuhu teil ei ole lubatud maili saata.

Meie mailiserverid toetavad SRS lahendust (kuid vaikimisi juhul, kui on suunatud reaalne eksisteeriv mailboks, mitte virtuaalne e-maili aadress)

Soovitus Radicenteri klientidele:
Kui olete oma maili suunanud kuhugi välisele serverile, kontrollige, kas antud server kontrollib SPF olemasolu või mitte. Kui kontrollib, soovitan suunamise maha võtta ning lisada hoopis meiepoolne mailbox üle IMAP ühenduse! (Antud lahendus välistab erinevad võimalikud probleemid kirjade saatmisel/vastuvõtmisel)

Rämpsposti listid / filtrid

Rahvusvahelised rämpsposti filtrid ehk “mustad nimekirjad” on andmebaasid mis sisaldavad spämmerite andmeid, et serverid saaks seal olevaid kirjeid vältida. Server filtreerib kirju nende nimekirjade baasil ning eemaldab / blokeerib reeglina kõik nö. spämmikirjad mis on kuidagi sattunud antud andmebaasidesse.

Radicenter jälgib ka ise oma hallatavaid mailiservereid
ning kui juhtub et mõne meie kliendi toimel on mõni serveritest sattunud musta nimekirja, üritame selle sealt esimesel võimalusel eemaldada (Tavaliselt võib aega minna peale eemaldustaotluse saatmist olenevalt listist 1 – 48h).
Kui “mõistlikus ajaraamis” (nädalavahetustel max kuni 24h – tööpäevadel max kuni 12h) ei ole võimalik meie hostitavat serverit rämpsposti listist eemaldada, võtame kasutusele “muud vahendid” e-mailide tõrgeteta tööks.
Kui mõne meie kliendi süül on põhjustatud listi sattumine ning see toob kaasa ka rahalisi nõudeid, vastutab antud nõuete eest konkreetne klient isiklikult (vt. Radicenteri kasutajatingimused).

Osad kliendid on soovinud ka et me ei kasutaks näiteks listi a või b – NB! Alltoodud listid on kasutusel globaalselt kõikidel meie serveritel ning neid ei eemaldata! Kui kellegi (mitte meie kliendi) e-mail on sattunud mõnda nendest listidest, lasub temal (Või tema ISP’l) kohustus probleemi likvideerimisel antud mail ka sealt listist eemaldada. Radicenter “enda poolt mitte hostitud” / “mitte meie klientide” e-maile filtritest eemaldada ei aita/ei eemalda! Igal listil on võimalik e-maili ja/või mailiserverit eemaldada vastava soovi alusel – selleks külastage antud listi kodulehte.

Meie serverid kasutavad järgmisi rämpsposti filtreid:
– cbl.abuseat.org
– bl.spamcop.net
– combined.rbl.msrbl.net
– b.barracudacentral.org
– zen.spamhaus.org
– hostkarma.junkemailfilter.com

NB! Alates 05.2015 – rakendasime klientide tungival soovil oma serveritel ka whitelistid, kuhu lisati suuremad eestis asuvad mailiteenuse pakkujad.
Antud teenusepakkujatelt tulevaid maile rahvusvaheliste listide poolt meie serveritel ei blokeerita.

Küsimused / Vastused:

K: Hei, aga mul on oma mailiserver smtp.xxxxxxx.xx – palun lisage ka see whitelisti.
V: Kui olete ise oma mailiserveri admin/haldaja – kuulub rahvusvahelistest rämpsposti listidest antud serveri eemaldamine Teie pädevusse. Kahjuks väiksemaid teenusepakkujaid/servereid eraldi listi ei lisata! Samuti ei lisata listi VPS või jagatud hostinguga lehti – viimaste probleemide puhul palun pöörduge oma teenusepakkuja/haldaja poole!

K: Ma ei soovi et te kasutaksite blocklisti N. Palun eemaldage see otsekohe, kuna see ei võimalda mul korrektselt töötada.
V: Antud blocklistid (sh. rämpsposti list N) on lisatud mailiserveritele turvalisuse kaalutlustel. Rahvusvahelistesse listidesse sattumiseks peab olema olnud ebakorrapäraline käitumine vastavalt mailiserverilt. Antud listidesse niisama ei satuta! Kui Teil on probleem oma mailiserveriga, pöörduge palun oma teenusepakkuja poole! Kasutatavaid rahvusvahelisi rämpsposti liste ei eemaldata nimekirjast!

Comments are currently closed.

See veebileht kasutab küpsiseid, mis aitavad teha lehe külastamise mugavamaks. Meie veebilehte külastades nõustute meiepoolse küpsiste kasutamisega.
Sain aru.