Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Mail2News Gateway at m2n.mixmin.net

68 views
Skip to first unread message

Fritz Wuehler

unread,
Nov 5, 2012, 1:17:07 AM11/5/12
to
As its name suggests, a Mail2News Gateway provides a means to
send a standard Email and have it posted to a newsgroup. The
Gateway receives incoming Emails, modifies them slightly to a
News format and then posts them.

The simplest way to use the Gateway is to just send an Email
using a format like this:
To: mail...@m2n.mixmin.net
Subject: Anything you like
From: Your Name/Email
Newsgroups:alt.test

Other headers can be included at your discretion, a common
example being:
X-No-Archive: Yes
This instructs news archives not to store the message.


Alternate Usage
In some instances it may not be possible to insert a Newsgroups
header into a message. This may be because the client
application doesn't support custom headers or perhaps that the
user doesn't know how to edit them. In these instance the
following method may provide an alternative.
To: mail2news-yyyy...@m2n.mixmin.net

Where:
yyyymmdd is today's date, such as 20120318 for 18th March 2012.
news.group is the Usenet group that the message is destined for.

Example
To send a message to a group called alt.test on the date given
above:
To: mail2news-201...@m2n.mixmin.net
Multiple groups can be specified up to a maximum of three by
seperating them with a equals sign:
To: mail2news-20120318-
alt.test=alt.testi...@m2n.mixmin.net
Date Validation

The purpose of the date component is to prevent serious abuse of
Usenet by means of automated spamming. As the date only remains
valid for a period of 24 hours, by the time spammers harvest it,
it is no longer accepted by the Gateway.
Email Address Obfuscation

One issue with the above message format is the resulting spam
that's likely to be directed at your Email address. This is
caused by spammers using applications called Harvesters to
collect Email addresses from Usenet. To overcome this problem,
the Mail2News Gateway provides a means to munge the Email
address of the sender.:

To: mail2new...@m2n.mixmin.net
To: mail2news_nospam-y...@m2n.mixmin.net

This will completely remove the senders address from the From
header and will instead put it in a new header using the
following format:
Author-Supplied-Address: user <at> domain <dot> com
This has the benefit of protecting the real address from
harvesters, but the downside that it relies on some knowledge on
the behalf of the recipient to discover the real address in the
message headers if they want to reply to it.


Outbound News Server
By default the Mail2News Gateway relies on an operator
configured list of news servers to feed each message to. In rare
instances a poster may prefer to elect a specific server in
order to override the default. This can be done by adding the
following header:
X-Newsserver: news.server.address
Only a single server can be specified in this manner and the
message will be delivered using a 'post' method rather than
'ihave'.


Crossposting
Crossposting is limited on this server to a maximum of three
groups.

Anonymous

unread,
Nov 5, 2012, 8:34:57 AM11/5/12
to
<snip>

> Other headers can be included at your discretion, a common example being:
> X-No-Archive: Yes
> This instructs news archives not to store the message.

DON'T use 'X-No-Archive: Yes'. There is no reason for using this
option in news groups and it only serves to frustrate people who
are trying to read articles in the future.

<snip>

> Crossposting
> Crossposting is limited on this server to a maximum of three groups.

I have always heard the limit is 5.

user

unread,
Nov 5, 2012, 10:21:54 AM11/5/12
to
Anonymous wrote:
> <snip>
>
>> Other headers can be included at your discretion, a common example being:
>> X-No-Archive: Yes
>> This instructs news archives not to store the message.
>
> DON'T use 'X-No-Archive: Yes'. There is no reason for using this
> option in news groups and it only serves to frustrate people who
> are trying to read articles in the future.
>
Sometimes it is desirable to prevent anyone from reading it in the future.

Dave U. Random

unread,
Nov 5, 2012, 4:35:34 PM11/5/12
to
The NSA has already grabbed it for perpetuity!

Curmudgeon

unread,
Nov 7, 2012, 5:38:47 AM11/7/12
to
On: Mon, 05 Nov 2012 09:21:54 -0600, user <us...@nowhere.net> wrote:
>Anonymous wrote:
>> <snip>
>>
>>> Other headers can be included at your discretion, a common example being:
>>> X-No-Archive: Yes
>>> This instructs news archives not to store the message.
>>
>> DON'T use 'X-No-Archive: Yes'. There is no reason for using this
>> option in news groups and it only serves to frustrate people who
>> are trying to read articles in the future.
>>
>Sometimes it is desirable to prevent anyone from reading it in the future.

... which X-No-Archive does not accomplish.

Privacy is like virginity, you don't get it back.

There is no way to prevent the retention of digital data by anyone who
has it. When you make that data public by publishing it, you give it
to anyone who downloads it. You would be foolish and naive to believe
otherwise.

The X-No-Archive request is a flag to anyone who wants to easily
identify the juicy stuff to archive. You should assume that if
someone in the future wants to retrieve your post, there will be an
archive somewhere which has it, and you will only have made it easier
to find. You appear to believe that if you direct someone not to save
your message, then some force of nature will compel them to do that.
As I say, this is foolish and naive.

Crusty Old Curmudgeon

Anonymous

unread,
Nov 7, 2012, 7:56:43 AM11/7/12
to
And again, why would someone post a public message and then not
want it to be read in the future? I have come across messages that
had answers that I need to lok at again, but they were gone. Don't
even bother to post if you intend to use 'X-No-Archive: Yes'.

Anonymous

unread,
Nov 7, 2012, 12:35:39 PM11/7/12
to
In article <1216789d6f4d4431...@msgid.frell.theremailer.net>
Curmudgeon <fr...@spamexpire-201211.rodent.frell.theremailer.net> wrote:
>
> On: Mon, 05 Nov 2012 09:21:54 -0600, user <us...@nowhere.net> wrote:
> >Anonymous wrote:
> >> <snip>
> >>
> >>> Other headers can be included at your discretion, a common example being:
> >>> X-No-Archive: Yes
> >>> This instructs news archives not to store the message.
> >>
> >> DON'T use 'X-No-Archive: Yes'. There is no reason for using this
> >> option in news groups and it only serves to frustrate people who
> >> are trying to read articles in the future.
> >>
> >Sometimes it is desirable to prevent anyone from reading it in the future.
>
> .... which X-No-Archive does not accomplish.
>
> Privacy is like virginity, you don't get it back.
>
> There is no way to prevent the retention of digital data by anyone who
> has it. When you make that data public by publishing it, you give it
> to anyone who downloads it. You would be foolish and naive to believe
> otherwise.
>
> The X-No-Archive request is a flag to anyone who wants to easily
> identify the juicy stuff to archive. You should assume that if
> someone in the future wants to retrieve your post, there will be an
> archive somewhere which has it, and you will only have made it easier
> to find. You appear to believe that if you direct someone not to save
> your message, then some force of nature will compel them to do that.
> As I say, this is foolish and naive.
>
> Crusty Old Curmudgeon

What he likely meant, which you may not have picked up due to his
choice of words, was this:

"Sometimes it is desirable to prevent [someone] from reading it in
the future".

This is easier to grasp for one with a crusty "old" mind and
attitude, perhaps? :) We too often post in haste without adequate
care for our words.

Anonymous

unread,
Nov 8, 2012, 1:11:17 AM11/8/12
to
In article <a10992128f2805ef...@foto.ro1.torservers.net>
So, duh! I guess this header functioned to serve its purpose on you
at least? Hey, Beaver. o/

Curmudgeon

unread,
Nov 18, 2012, 6:15:00 AM11/18/12
to
It is indeed desireable to post with deliberation rather than haste,
and to be carefull in one's choice of words. This is readily evident
from reading everyone else's posts, and all too often less evident when
composing one's own.

So I will try again, and this time omit the use of the F-word and
N-word, which may have upset some readers.

Misunderstanding how much privacy one actually has is widespread and
may, and has, caused great problems for those who misunderstood. An
example in the news currently revolves around the astounding fact that
the Directory of Central Intelligence did not understand that
everything that passes through gmail is archived forever, even if
Google claims otherwise. Similarly, anything that is posted on usenet
is archived forever, and if some posting contails material that you
don't want archived, the only reliable course that you have is to not
post it. Using the no-archive directive solely for the possibility
that someone might be inconvenienced seems perverse. Hoping that, by
chance, someone whom you don't want to see your post will not find it,
is dicey at best. For Petraeus, that roll of the dice has not turned
out well.

It is bad practice to rely on something that you know is unreliable.

Crusty Old Curmudgeon

0 new messages