Sponsored Content
Full Discussion: Electronic Mail Addressing
The Lounge What is on Your Mind? Electronic Mail Addressing Post 302433858 by Action on Wednesday 30th of June 2010 06:26:24 PM
Old 06-30-2010
Quote:
Originally Posted by bluescreen
When I was SA on 10 AT&T 3B2 systems, they used the BANG "!" in place of the AT "@". So a user's email address was: system!user

One caveat to this was there was no "DNS" back then and you had to know the route to the user's system. So when you sent an email, the "TO:" field looked something like this:

Code:
system4!system3!system2!system1!system!user

I know that form, it's UUCP, it was used with UNIX, and UNIX was property of AT&T. As fare as i can understand, it was time of Sendmail as the only MTA. Anyway, instead of always typing full routes email aliasing could be configured in system-wide alias file or user-own .mailrc file(s). System wide (/etc/aliases):
Code:
jimmi: host1!host2!host3!james

User-specific ($HOME/.mailrc):
Code:
alias jimmi host1!host2!host3!james

Mail forwarding could also be configured on central mail server, so that all the other hosts would be its clients in what has to do with email - all mail is submitted to the hub, and hub decides what mail goes to where and maintains all the aliases centrally. Of course, i don't know of your situation there, but that's how i imagine the solution of the problem with long routes.
The picture of 3B2-vme makes me recall of german MFA, it also had extension cards of such format.
 

4 More Discussions You Might Find Interesting

1. IP Networking

IP Addressing with Digital Unix

I'm trying to set up an IP address on a Digital Unix box. I would like to know the commands in order to do so. thanks (5 Replies)
Discussion started by: lavelyj
5 Replies

2. IP Networking

Dual IP addressing

I have a Unix application server with an internet IP address on it for a gateway and a Unix web server with the Internet IP as well configured for its gateway. Now the problem I have is this: due to these gateways, the application server can't communicate with our internal LAN. Therefore, it... (2 Replies)
Discussion started by: Ronny
2 Replies

3. Programming

Memory addressing question

Forgive me if this sounds like a newbie question. Any time you obtain a stack address from a pointer, what is this relative to by default? Is it the extra segment, the stack segment, what? How do you change change the relative positioning in memory? Thanks in advance (1 Reply)
Discussion started by: stevenswj
1 Replies

4. IP Networking

Addressing question

This is probably a stupid question but I am finding a tricky issue on my Solaris machines right now. I changed the hostname for my servers as requested by my superior. I had one server that lost it's entire network configuration when I rebooted. I reconfigured it with it's address and I can... (2 Replies)
Discussion started by: lnxjenn
2 Replies
Mail::SPF::Term(3)					User Contributed Perl Documentation					Mail::SPF::Term(3)

NAME
Mail::SPF::Term - SPF record term class DESCRIPTION
An object of class Mail::SPF::Term represents a term within an SPF record. Mail::SPF::Term cannot be instantiated directly. Create an instance of a concrete sub-class instead. Constructor The following constructor is provided: new(%options): returns Mail::SPF::Term Abstract. Creates a new SPF record term object. %options is a list of key/value pairs, however Mail::SPF::Term itself specifies no constructor options. new_from_string($text, %options): returns Mail::SPF::Term; throws Mail::SPF::ENothingToParse, Mail::SPF::EInvalidTerm Abstract. Creates a new SPF record term object by parsing the string and any options given. Class methods The following class methods are provided: name_pattern: returns Regexp Returns a regular expression that matches any legal name for an SPF record term. Instance methods The following instance methods are provided: text: returns string; throws Mail::SPF::ENoUnparsedText Returns the unparsed text of the term. Throws a Mail::SPF::ENoUnparsedText exception if the term was created synthetically instead of being parsed, and no text was provided. name: returns string Abstract. Returns the name of the term. SEE ALSO
Mail::SPF, Mail::SPF::Record, Mail::SPF::Mech, Mail::SPF::Mod <http://www.ietf.org/rfc/rfc4408.txt> For availability, support, and license information, see the README file included with Mail::SPF. AUTHORS
Julian Mehnle <julian@mehnle.net>, Shevek <cpan@anarres.org> perl v5.12.1 2010-07-05 Mail::SPF::Term(3)
All times are GMT -4. The time now is 01:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy