Re: [ADM] Fortsat fejlmeldinger
- From: "Torben Taustrup" <ttau@xxxxxxxxxx>
- To: <astrolist@xxxxxxxxxxxxx>
- Date: Fri, 10 Dec 2010 19:09:28 +0100
Hej Frank og I andre
Tak for oplysningerne og jeres input i forbindelse med denne
sag. Nu er problemet heldigvis ikke så stort, at folk bliver
smidt af Astrolist, men jeg synes, at det er vigtigt, at den
slags oplysninger tilflyder listens medlemmer, så de har den
nødvendige information og måske efterfølgende træffe deres
valg.
Verden er indviklet - vi har lige flyttet vores
mobiltelefoner fra Telmore til TDC. Vi er så i mellemtiden
blevet opmærksomme på, at TDC ejer Telmore. Nu forstår jeg
bedre, at Telmore bl.a. skriver, at man er velkommen tilbage
;)
mvh
Torben
[ADM]
----- Original Message -----
From: "Frank Larsen" <frank@xxxxxxxxxx>
To: <astrolist@xxxxxxxxxxxxx>
Sent: Friday, December 10, 2010 9:20 AM
Subject: Re: [ADM] Fortsat fejlmeldinger
> Hej Torben (og Andre)
> Jeg har gravet lidt i fejlkoden.(som Flemming gjorde
> tidligere)
>
> Det handler om at modtagernes mailserver (i dette tilfælde
> TDC) afviser
> en mail fordi den ikke lever op til mailformaterings
> standarden angivet
> i RFC2822 section 2.2.
> Det handler om at alle datalinier i mailbody i SMTP
> kommunikation skal
> afsluttes med "CRLF" som er to ASCII tegn.
> ER de ikke det kan det KAN mailserveren retteligt afvise
> den.
>
> Jeg ser at fejlen er hidrørende den 6/11 og der gik der
> helt klart noget
> galt med et indlæg. Jeg skrev et kort indlæg "SV: NGC891 -
> ny version"
> kl 21.25 og da jeg selv modtog den astrolist fra var den
> bare ren
> volapyk -- ellere rettere tilfældige ASCII tegn. HVIS der
> i mailteksten
> har været et eller flere "CR" eller "LF" ville det
> fremprovokere fejlen.
> Det kan også være der er gået kuk i SMTP kommunikationen
> så headeren til
> mailen ikke er korrekt termineret.
>
> Men den burde være blevet afvist af astrolist's server i
> første omgang
>
> http://www.experts-exchange.com/Networking/Protocols/Application_Protoco
> ls/Email/SMTP/Q_25139390.html
>
> Denne angiver et lignende problem OGSÅ vedrørende mails
> til TDC kunder
> (mail.dk)
> http://www.webwiz.co.uk/forums/lone-cr-in-signature_topic28666.html
>
> kravet om sammenhørende CR/LF skyldes et sikkerhul i SMTP
> standarden som
> blev lukket for 5-6 år siden. Dengang betød det at op mod
> 1 ud 10 mails
> blev afvist da de færreste systemer sendte RFC2822 gyldige
> mails.
>
> Frank Larsen
>
>
>
> On 08/12/2010 23:09 "Torben Taustrup" <ttau@xxxxxxxxxx>
> <ttau@xxxxxxxxxx> wrote:
>
>> Hej folkens
>>
>> Som jeg tidligere har informeret om, så modtager jeg
>> fejlmeldinger på en del mailadresser.
>> Jeg er ikke i stand til at gøre noget ved dette problem,
>> så
>> hvis en eller flere af nedenstående ejere af
>> fejlbehæftede
>> mailadresser vil kontakte sin udbyder og informere om
>> fejlmeldingen, så er der måske en chance for, at
>> problemet
>> kan blive rettet.
>> Det lader til at være et TDC-relateret problem.
>>
>> mvh
>> Torben
>>
>>
>> These users have returned errors and are being watched
>> for
>> the list astrolist.
>>
>> Action Trans Fatal Error span User
>> ----------------------------------------------------------------------
>> Expired 0 1 Nov 06 - Nov 06
>> <Reib@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <bogk@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <bwinkler@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> NotSub 0 1 Nov 06 - Nov 06
>> <j-kartin@xxxxxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <lars_spatzek@xxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <fam.herbst@xxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <hans.slotsbo@xxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <jocl@xxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <spatzek@xxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <snf@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <loevenholt@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <oeng@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <skaar@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <svaneeng@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <carfra@xxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <luh@xxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <novot@xxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <otlastro@xxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <sorenvh@xxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <aldrich@xxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <gemini@xxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <gunnar.tyrsted@xxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <oz2jb@xxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <bozz@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <hmkilde@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <cilla@xxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <mcma@xxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <vernols@xxxxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <friis@xxxxxxxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <bjaras@xxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <astro.soren@xxxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <senedergaard@xxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <fohbr@xxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <thorsbro@xxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <andersfb.holm@xxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <hrjo@xxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <ib_jansen@xxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <jtoft@xxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <krja@xxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <a.e.petersen@xxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <hansleth@xxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <jacobfriis@xxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <lwras@xxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <m.simonsen@xxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <pedermose@xxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <sap@xxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <vagnl@xxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <wega@xxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <kursch@xxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <lemon@xxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 jgp@xxxx
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 morten.brix@xxxx
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <vgydesen@xxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <frank123@xxxxxxxxxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <preben@xxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <tandplejen@xxxxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <hugo@xxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <hieracium@xxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <cujla@xxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <hauge.pedersen@xxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06 <hjfo@xxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> Expired 0 1 Nov 06 - Nov 06
>> <wibniels@xxxxxxxxxxx>
>> 550 5.6.0 Lone CR or LF in body (see RFC2822
>> section
>> None 1 0 Nov 26 - Nov 26 <ca.str@xxxxxxxx>
>> conversation with
>> ----------------------------------------------------------------------
>>
>> Key to actions:
>> None - No action taken, user left in watchfile.
>> Vacation - User's VACATION flag was set.
>> User reached 7 transient errors.
>> NOTE: This list is configured so users who
>> would
>> be set VACATION will be Unsub'd instead.
>> Unsub - User was unsubscribed.
>> User reached 2 fatal errors.
>> Expired - User has not had a bounce for 30 days,
>> watch has been expired.
>> Admin - User is administrator, no action taken.
>> Protect - User is flagged PROTECTED, no action taken.
>> Manual - There was no default action taken, handle
>> manually.
>> NotSub - Bounce message received for user not
>> subscribed
>> to this list. This is caused when someone
>> is
>> forwarding to another address and their
>> mailserver
>> reports the wrong one, or if someone has
>> been
>> unsubscribed from the list but not expired
>> from
>> the watches yet.
>>
>>
>> Torben Taustrup
>> TOC Observatory homepage
>> <http://tocobs.org>
>> "Just do it"
>>
>
Other related posts:
