Mailing List Archive

On Tue, Oct 20, 1998 at 03:04:28AM +0200, [Eazy|E] wrote:
> I wonder if new upcoming version will handle those chars or if there are
> any patches released for as called "funky" chars.

Actually, the one I want to see is allowing +'s in the email address
portion, since 'bem+something' is how I flag some addresses.

I think it's just a bit paranoid sanity checking on the input to make
sure people don't claim to be '^C^C^C^[HELPSTOP' and such.

--
Brian Moore | "The Zen nature of a spammer resembles
Sysadmin, C/Perl Hacker | a cockroach, except that the cockroach
Usenet Vandal | is higher up on the evolutionary chain."
Netscum, Bane of Elves. Peter Olson, Delphi Postmaster

"Eazy|E\"" <sniper@kibla.org> writes:

> I wonder if new upcoming version will handle those chars or if there are
> any patches released for as called "funky" chars.

No I don't see a reason to allow such characters in a real name, I
think you can use these characters in the comment field.

If you really don't like it go and change it
(g10/keygen.c:ask_user_id) - It is free sofware and you are allowed
to change it - see COPYING :-)


Werner

brian moore <bem@cmc.net> writes:

> Actually, the one I want to see is allowing +'s in the email address
> portion, since 'bem+something' is how I flag some addresses.

If + is a valid character in a mailbox name, it should be allowed.
Anyone has the RFC handy?

> I think it's just a bit paranoid sanity checking on the input to make

The reason why I did this is to ease parsing of user IDs; we might
need this in the future.


Werner

On Tue, 20 Oct 1998, Werner Koch wrote:

> brian moore <bem@cmc.net> writes:
>
> > Actually, the one I want to see is allowing +'s in the email address
> > portion, since 'bem+something' is how I flag some addresses.
>
> If + is a valid character in a mailbox name, it should be allowed.
> Anyone has the RFC handy?

Yes it's valid. One MTA in fact (qmail) uses + and - characters to
designate alternate delivery mailboxes. I.e. I am subscribed to this list
through the address caskey-lists-g10 and that is passed through my list
subscription filters for special handling.

C=)

--------------------------------------------------------------------------
Heuer's Law: Any feature is a bug unless it can be turned off.
--------------------------------------------------------------------------
Caskey <caskey*technocage.com> /// pager.818.698.2306
TechnoCage Inc. ///| gpg: aiiieeeeeee!!!
--------------------------------------------------------------------------
Early bird gets the worm, but the second mouse gets the cheese.

"Caskey L. Dickson" <caskey@technocage.com> writes:

> Yes it's valid. One MTA in fact (qmail) uses + and - characters to

Okay, I changed this and allowed ´+´ in the mailboxname.

Is it new, that qmail allows ´+´ as separator or is there a special
meaning for this?


Werner

On Tue, Oct 20, 1998 at 08:57:53AM +0200, Werner Koch wrote:

> The reason why I did this is to ease parsing of user IDs; we might
> need this in the future.

What about throwing an rfc822 address parser at the user IDs and
checking if it returns a reasonable result?

tlr
--
Thomas Roessler · 74a353cc0b19 · dg1ktr · http://home.pages.de/~roessler/
2048/CE6AC6C1 · 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1

> > If + is a valid character in a mailbox name, it should be allowed.
> > Anyone has the RFC handy?

It's perfectly valid character, and it's in very common usage, hence
it should be allowed. BTW, according to RFC821 and RFC822 any of the
128 ASCII characters can occur in the local part of an e-mail address
if quoted properly, although I've _never_ seen an e-mail address
containing control characters (such a thing would be outright silly,
even though perfectly legal - I'm sure you can break a lot of e-mail
software by using an e-mail address which contains backslash-NUL).
Another note: Even though 8-bit-characters are illegal, they _do_
occur in e-mail addresses.

> Yes it's valid. One MTA in fact (qmail) uses + and - characters to
> designate alternate delivery mailboxes.

Actually it is sendmail (and compatibles) which uses '+' for this.
qmail uses '-'.

Greetings, Norbert.

P.S. Here's the quote from RFC821. The specification in RFC822 goes
along similar lines.


<domain> ::= <element> | <element> "." <domain>

<element> ::= <name> | "#" <number> | "[" <dotnum> "]"

<mailbox> ::= <local-part> "@" <domain>

<local-part> ::= <dot-string> | <quoted-string>

<name> ::= <a> <ldh-str> <let-dig>

<ldh-str> ::= <let-dig-hyp> | <let-dig-hyp> <ldh-str>

<let-dig> ::= <a> | <d>

<let-dig-hyp> ::= <a> | <d> | "-"

<dot-string> ::= <string> | <string> "." <dot-string>

<string> ::= <char> | <char> <string>

<quoted-string> ::= """ <qtext> """

<qtext> ::= "\" <x> | "\" <x> <qtext> | <q> | <q> <qtext>

<char> ::= <c> | "\" <x>

<dotnum> ::= <snum> "." <snum> "." <snum> "." <snum>

<number> ::= <d> | <d> <number>

<CRLF> ::= <CR> <LF>

<CR> ::= the carriage return character (ASCII code 13)

<LF> ::= the line feed character (ASCII code 10)

<SP> ::= the space character (ASCII code 32)

<snum> ::= one, two, or three digits representing a decimal
integer value in the range 0 through 255

<a> ::= any one of the 52 alphabetic characters A through Z
in upper case and a through z in lower case

<c> ::= any one of the 128 ASCII characters, but not any
<special> or <SP>

<d> ::= any one of the ten digits 0 through 9

<q> ::= any one of the 128 ASCII characters except <CR>,
<LF>, quote ("), or backslash (\)

<x> ::= any one of the 128 ASCII characters (no exceptions)

<special> ::= "<" | ">" | "(" | ")" | "[" | "]" | "\" | "."
| "," | ";" | ":" | "@" """ | the control
characters (ASCII codes 0 through 31 inclusive and
127)

Note that the backslash, "\", is a quote character, which is
used to indicate that the next character is to be used
literally (instead of its normal interpretation). For example,
"Joe\,Smith" could be used to indicate a single nine character
user field with comma being the fourth character of the field.

On Tue, 20 Oct 1998, Werner Koch wrote:

> "Caskey L. Dickson" <caskey@technocage.com> writes:
>
> > Yes it's valid. One MTA in fact (qmail) uses + and - characters to
>
> Okay, I changed this and allowed ´+´ in the mailboxname.
>
> Is it new, that qmail allows ´+´ as separator or is there a special
> meaning for this?

New for qmail? I don't think so. I think it's just another preference.
I know some people use it for virtual domains as a way of 'encoding' the
'@'. I.e. caskey@sample.com gets re-mailed to
caskey+sample.com@technocage.com

Some list operators use it to munge the headers so that bounces go to
g10-bounce+caskey=sample.com@net.lut.ac.uk. Not that ours does it, mind
you.

Off topic personal note:

I use the '-' mechanism for organizing my incoming list mail and to create
throwaway email addresses. I.e. if you must give an email address to
download a piece of software, caskey-junkmail-pgp@technocage.com. I then
filter everything through my .qmail-junkmail-default to the bit bucket
unless I'm expecting something interesting. Hmm... spam as a source of
entropy? Could work...

C=)

--------------------------------------------------------------------------
Heuer's Law: Any feature is a bug unless it can be turned off.
--------------------------------------------------------------------------
Caskey <caskey*technocage.com> /// pager.818.698.2306
TechnoCage Inc. ///| gpg: aiiieeeeeee!!!
--------------------------------------------------------------------------
Early bird gets the worm, but the second mouse gets the cheese.

At 3:43 AM 10/20/98, Caskey L. Dickson wrote:
>Hmm... spam as a source of entropy? Could work...

SPAM is far too repetitive to be a reliable source of entropy. :-)

-- "TANSTAAFL" Rich lynch@cognitivearts.com webmaster@ and www. all of:
R&B/jazz/blues/rock - jademaze.com music industry org - chatmusic.com
acoustic/funk/world-beat - astrakelly.com sculptures - olivierledoux.com
my own company - l-i-e.com uncommon ground - uncommonground.com