Address `questions‌@panoramio.com' might be bogus. Continue? (y or n)

Address `questions‌@panoramio.com' might be bogus. Continue? (y or n)

[jidanni]

Address `questions‌@panoramio.com' might be bogus.  Continue? (y or n)  y

Better have the message say why: Silly user name? Invisible character in
the address? Etc.

Re: Address `questions‌@panoramio.com' might be bogus. Continue? (y or n)

[jidanni]

> Address `questions‌@panoramio.com' might be bogus.  Continue? (y or n)  y

> Better have the message say why: Silly user name? Invisible character in
> the address? Etc.

And indeed, it turned out to be an invisible character.

<=?utf-8?Q?questions=E2=80=8C?=@panoramio.com>: host
    aspmx.l.google.com[74.125.155.27] said: 550-5.1.1 The email account that
    you tried to reach does not exist. Please try 550-5.1.1 double-checking the

        character: ‌ (8204, #o20014, #x200c)
preferred charset: unicode (Unicode (ISO10646))
       code point: 0x200C
           syntax: . 	which means: punctuation
      buffer code: #xE2 #x80 #x8C
        file code: #xE2 #x80 #x8C (encoded by coding system utf-8)
          display: by this font (glyph code)
    xft:-unknown-FreeSans-normal-normal-normal-*-16-*-*-*-*-0-iso10646-1 (#x8EF)

OK, well it looked fine to me. Gnus should "warn me of the dangers",
saying next time:

Address `questions‌@panoramio.com' (questions=E2=80=8C@...) might be bogus.  Continue? (y or n)

Re: Address `questions‌@panoramio.com' might be bogus. Continue? (y or n)

[Tommy Kelly]

jidanni@jidanni.org writes:

> Address `questions‌@panoramio.com' might be bogus.  Continue? (y or n)  y
>
> Better have the message say why: Silly user name? Invisible character in
> the address? Etc.

I agree. I just (for the first time) saw the same message and had no
idea what it was telling me.

Tommy

Re: Address `questions‌@panoramio.com' might be bogus. Continue? (y or n)

[Reiner Steib]

On Fri, Jan 14 2011, Tommy Kelly wrote:

> jidanni@jidanni.org writes:
>
>> Address `questions‌@panoramio.com' might be bogus.  Continue? (y or n)  y
>>
>> Better have the message say why: Silly user name? Invisible character in
>> the address? Etc.

The check includes several expressions that are potentially invalid or
bogus addresses:

,----[ M-x customize-variable RET message-bogus-addresses RET ]
| message-bogus-addresses: Hide Value Value Menu List:
| Set:
| [X] noreply
| [X] nospam
| [X] invalid
| [X] duplicate @
| [X] non-ascii local part
| [X] whitespace
| Other:
| INS
|    State: STANDARD.
| 
| List of regexps of potentially bogus mail addresses. Hide Rest
| See `message-check-recipients' how to setup checking.
| 
| This list should make it possible to catch typos or warn about
| spam-trap addresses.  It doesn't aim to verify strict RFC
| conformance.
`----

> I agree. I just (for the first time) saw the same message and had no
> idea what it was telling me.

Feel free to suggest a better wording.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: Address `questions‌@panoramio.com' might be bogus. Continue? (y or n)

[Tommy Kelly]

Reiner Steib <reinersteib+gmane@imap.cc> writes:
> Feel free to suggest a better wording.

There's nothing wrong with the wording. It's just that it would be more
informative if it described which of the bogosity tests had
tripped. Perhaps that's not possible given the way the tests are executed.

Tommy

Re: Address `questions‌@panoramio.com' might be bogus. Continue? (y or n)

[Rupert Swarbrick]

[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Fri, Jan 14 2011, Tommy Kelly wrote:
>
>> jidanni@jidanni.org writes:
>>
>>> Address `questions‌@panoramio.com' might be bogus.  Continue? (y or n)  y
>>>
>>> Better have the message say why: Silly user name? Invisible character in
>>> the address? Etc.
>
> The check includes several expressions that are potentially invalid or
> bogus addresses:
>
> ,----[ M-x customize-variable RET message-bogus-addresses RET ]
> | message-bogus-addresses: Hide Value Value Menu List:
> | Set:
> | [X] noreply
> | [X] nospam
> | [X] invalid
> | [X] duplicate @
> | [X] non-ascii local part
> | [X] whitespace
> | Other:
> | INS
> |    State: STANDARD.
> | 
> | List of regexps of potentially bogus mail addresses. Hide Rest
> | See `message-check-recipients' how to setup checking.
> | 
> | This list should make it possible to catch typos or warn about
> | spam-trap addresses.  It doesn't aim to verify strict RFC
> | conformance.
> `----
>
>> I agree. I just (for the first time) saw the same message and had no
>> idea what it was telling me.
>
> Feel free to suggest a better wording.
>
> Bye, Reiner.

Couldn't you allow message-bogus-addresses to have (cons "string" "msg")
as possible entries. Then message-bogus-recipient-p could return "msg"
(if there is one) or T otherwise. Then message-check-recipients could
add "msg" to the format call.

Rupert

[-- Attachment #2: Type: application/pgp-signature, Size: 315 bytes --]

Re: Address `questions‌@panoramio.com' might be bogus. Continue? (y or n)

[jidanni]

By the way, Reiner, your messages incur high SpamAssassin penalties:
X-Spam-Report: 
	*  0.0 FREEMAIL_FROM Sender email is freemail
	*      (reinersteib+gmane[at]imap.cc)
	*  2.8 FREEMAIL_REPLYTO Reply-To/From or Reply-To/body contain different
	*      freemails

Re: Address `questions‌@panoramio.com' might be bogus. Continue? (y or n)

[Ted Zlatanov]

On Sat, 15 Jan 2011 21:15:29 +0100 Reiner Steib <reinersteib+gmane@imap.cc> wrote: 

RS> On Fri, Jan 14 2011, Tommy Kelly wrote:
>> jidanni@jidanni.org writes:
>> 
>>> Address `questions‌@panoramio.com' might be bogus.  Continue? (y or n)  y
>>> 
>>> Better have the message say why: Silly user name? Invisible character in
>>> the address? Etc.

RS> The check includes several expressions that are potentially invalid or
RS> bogus addresses:

RS> ,----[ M-x customize-variable RET message-bogus-addresses RET ]
RS> | message-bogus-addresses: Hide Value Value Menu List:
RS> | Set:
RS> | [X] noreply
RS> | [X] nospam
RS> | [X] invalid
RS> | [X] duplicate @
RS> | [X] non-ascii local part
RS> | [X] whitespace
RS> | Other:
RS> | INS
RS> |    State: STANDARD.
RS> | 
RS> | List of regexps of potentially bogus mail addresses. Hide Rest
RS> | See `message-check-recipients' how to setup checking.
RS> | 
RS> | This list should make it possible to catch typos or warn about
RS> | spam-trap addresses.  It doesn't aim to verify strict RFC
RS> | conformance.
RS> `----

"Address `x' might be invalid (noreply, nospam, whitespace).  Continue? (y/n/h) "

Where `h' can pop up a buffer with an explanation of each of those and a
link to Customize for `message-bogus-addresses'.

Ted

Re: Address `questions‌@panoramio.com' might be bogus. Continue? (y or n)

[Lars Ingebrigtsen]

Ted Zlatanov <tzz@lifelogs.com> writes:

> "Address `x' might be invalid (noreply, nospam, whitespace).  Continue? (y/n/h) "

Well, I think the only really interesting case here is the invisible
characters.  I'll amend the message to be what jidanni suggested.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen