[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Emails being tagged as spam -- NMH solution???

From: Ralph Corderoy
Subject: Re: [Nmh-workers] Emails being tagged as spam -- NMH solution???
Date: Mon, 23 Feb 2015 11:19:06 +0000

Hi Andy,

> > You  guess  wrong.  It  is  useful. I'm  declaring  what's  valid  and
> > interested parties  can use it, and  I've seen they do,  to help judge
> > what they've received.
> By the way,  my apologies for using  your domain as an  example.

I don't mind;  lots of spammers use it anyway.  And it's your IP address
if any backlist feedback is occurring.  :-)  I found the number of
automatic "bounce" emails, "still undelivered after N hours", that kind
of thing, dropped off very quickly when I put SPF in place.

> I was so
> surprised to  actually find a domain  that used -all that  I immediately
> put on my ``for science'' hat and proceeded to test.

twitter.com and amazon.com are two others with `-all' IIRC.

> > Did Hotmail accept  the message over SMTP, or also  deliver it to your
> > inbox? What  was the  detail of  their spam  judgement, e.g.  based on
> > its  headers? (Using  Hotmail  as  an arbiter  of  quality!? Would  be
> > interesting to hear what Gmail does.)
> Yes,  Hotmail accepted  the message  over  SMTP from  a non-approved  IP
> address and delivered it the Spam folder.

OK, so SPF may well have encouraged it to place it in +spam.

> Interesting observation.  I've always  found it to  be the  opposite and
> you're actually the first to have mentioned  it. At least for me, I find
> that  having  the  text  wrapped  at  odd  places,  or  not  wrapped  at
> all  depending on  the  terminal/software displaying  it,  is much  more
> difficult.

I'm on the GNU groff mailing list, and there's the odd correspondent
there that runs their emails through nroff.  :-)  It also fully
justifies on a TTY, e.g.

    tr -dc 0-4a-c </dev/urandom | tr -s a-z \\n | sed 100q |
    nroff | grep .

Thankfully, man(1) has --nj that can be put into $MANOPT.  :-)

A larger space indicates to me a significant break, e.g. end of
sentence.  Lack of hyphenation means many spaces are becoming two in
your formatting, creating ugly rivers of whitespace.  These are a
problem in typesetting of proportional fonts fully justified;
fixed-width doesn't have a chance.  Subjective, I agree.

It also breaks vim's formatting of the `> ' quotes lines above, i.e. it
preserves the multiple spaces thinking they're significant.

Cheers, Ralph.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]