This has been done. Don -- expect future messages into emacsbugs to come
from lists.gnu.org
-jag
> [EMAIL PROTECTED] - Tue May 13 13:06:56 2008]:
>
> On Tue, 13 May 2008, Joshua Ginsberg via RT wrote:
> > Don had expressed to me that he didn't wish for the gnu.org spam
>
Hi Stefan --
Don had expressed to me that he didn't wish for the gnu.org spam
filtration to occur, but if you all generally feel it would be a good
idea, we can do that -- by spam filtration do you mean our envelope
checks? SpamAssassin? TMDA?
-jag
> [EMAIL PROTECTED] - Mon May 12 15:11:34 2008]
The router is in place, and a test message behaved as expected. I'm
marking this issue resolved. Thanks!
-jag
> [jag - Mon May 05 11:18:23 2008]:
>
> Alright, so in conclusion, the router would only permit a posting to
> [EMAIL PROTECTED] if the posting has the envelope MAIL FROM of
> [EMAIL PRO
Alright, so in conclusion, the router would only permit a posting to
[EMAIL PROTECTED] if the posting has the envelope MAIL FROM of
[EMAIL PROTECTED] -- otherwise, the message would
be redirected to [EMAIL PROTECTED] -- Don, I'll hang out
in #debian on oftc to coordinate this changeover in real-tim
Howdy --
Thank you -- by "envelope from" I mean the value submitted during the
SMTP exchange for the MAIL command, e.g. MAIL FROM:
<[EMAIL PROTECTED]> -- if this is correct, I can
set up the router based on that, but I'd like to also restrict the
router's action by client, that is, "What host will
Sorry for the delay in response -- we're trying to tie up loose ends
before baughj resigns his post in a week.
Yes, this is most certainly possible. Do you want to coordinate the
changeover? Or would you like me to simply take care of it whenever?
-jag
> [beuc - Mon Mar 31 17:02:59 2008]:
>
> H
Howdy --
I apologize for the delay in response, but I can certainly help you move
forward with this.
Rather than muck with an already creaky and hack-laden Mailman instance,
I'd prefer to do this on the MTA side -- I can create a router to
conditionally reroute traffic for bug-gnu-emacs elsewhere
use only valid regular expressions, and I
imagine everything should work. All of the messages for epix-users were
shunted, however we vacuum the shunt queue rather regularly because of
so many poorly encoded messages ending up there. I'm not sure we can
recover them.
-jag
> [EMAIL PROTECTED] - F
My first thought in looking at it is to question your spam filters. Try
emptying them or setting them to "Hold" here:
http://lists.nongnu.org/mailman/admin/epix-users/?VARHELP=privacy/spam/header_filter_rules
... and let me know if that fixes the issue. Some of them are rather
general and probabl
> [beuc - Tue Jan 01 04:47:07 2008]:
>
> Hi sysadmins,
>
> Can you tell us about the mail system status?
Since it was reported that the T-1 was fixed, there have been no further
issues with mail service.
> This user has trouble with his mailing lists.
I'll need more specific trouble about wha
> Do we recommend the use of that list anywhere (on gnu.org or savannah)?
A by no means exhaustive search turned up the following URL's and their
respective translations:
www.gnu.org/software/libtool/
www.gnu.org/server/standards/README.html
www.gnu.org/server/standards/README.savannah.html
>
Howdy!
Not sure what happened -- there were no outages and nobody else was
reporting any difficulty. Sometimes routes shift and take a little while
to settle out. If this happens again, please do a traceroute and enclose
that along with a timestamp. That would be most helpful.
-jag
> [EMAIL PROT
The error message suggests you had a line or a header in your changelog
that exceeded 131071 bytes. Now given this particular changelog is 1.1
MB large, it wasn't included in the bounce. Do you see anything like
that in the actual CVS changelog?
-jag
> [EMAIL PROTECTED] - Thu Aug 16 20:26:42 2007
> It is possible for you to recover /var/mailman/lists/bug-gnucomm from
> the latest backup?
Done.
-jag
--
Joshua "jag" Ginsberg -- [EMAIL PROTECTED]
Senior Systems Administrator -- Free Software Foundation
Thanks for the $0.02 -- Savannah's SCSI cabling is set up the same as it
has been for three years. The three disks that failed were on separate
SCSI buses. When we brought it in for servicing, we redid all of the
cabling and reseated the SCSI controller. It was after this point that
the fourth disk
The credit for the fix goes to baughj.
For the record, we've added additional monitoring to the mailing list
system. The sysadmins will receive pages whenever the queues on either
the MTA or the mailing list manager exceed normal operating levels. I
apologize for you having to bring this to our at
Sylvain --
While I appreciate your permitting us the chance to chime in here, you
already know the answer to this. No, there's no kludge to put in place
right now. Yes, we know there's a problem with spam. Yes, it's our top
priority right now. Yes, a new system is in the works. Yes, it will be
ava
Sorry -- let me be more explicit...
The problem regarding 199.232.75.2 has been resolved.
The failure of sender verify is temporarily cached, yes. By this point,
it should have been wiped from cache.
-jag
> [beuc - Fri Dec 16 14:21:20 2005]:
>
> Hi,
>
> Mark Garey seems to be blacklisted by l
This was a temporary problem that was resolved as of Wednesday.
-jag
> [beuc - Fri Dec 16 14:21:20 2005]:
>
> Hi,
>
> Mark Garey seems to be blacklisted by lists.gnu.org.
>
> Can you have a look at it?
> Tell me if I can be of any help.
>
>
> The original Savannah support request can be foun
Hi Sylvain --
Helpful information would include:
1) Dates/times of post attempts
2) Hostnames/IP's that the posts were being relayed through
3) Information from his mail administrator about what the relay host's
logs say is happening to the messages
-jag
> [beuc - Tue Dec 06 07:12:09 2005]:
>
20 matches
Mail list logo
