On Mon, Apr 27, 2015 at 5:46 PM, yar <yardenack(a)gmail.com> wrote:
> I think I fixed the spam problem but we are still getting lots of
> deferred deliveries because of this. It may be an issue for a while,
> possibly even until we migrate the server.
Deferrals are still happening. Mailman is seeing the bounces and
starting to suspend gmail addresses. I had to confirm to stay
subscribed to Info.
Is anyone else getting these? Is it happening for other lists or just Info?
I'm going to try to start migration ASAP.
sudo room now automatically announces last BART departures.
It should announce last departures from MacArthur station for each of the
BART directions, SF, Richmond, Pittsburg and Fremont. It will announce each
last departure twice in the window 30 minutes to 10 minutes before
departure.
Here's how it works: I hooked up a usb audio adapter and some speakers to
the sudo server, wrote a little script that talks to the BART API and set
it up to run as a cronjob that speaks the results using espeak.
The code is here:
https://github.com/Juul/lastbart
It's all new and fragile so you probably shouldn't rely on it just yet.
--
marc/juul
On Sun, Apr 26, 2015 at 2:37 PM, yar <yardenack(a)gmail.com> wrote:
> Gmail seems to be rate-limiting our IP because we keep reflecting
> info(a)sudoroom.org spam. Incredibly, our postfix config lacked even
> basic spam protections. I've added a bunch of
> smtpd_recipient_restrictions which will hopefully help until we
> finally migrate to digitalocean.
I think I fixed the spam problem but we are still getting lots of
deferred deliveries because of this. It may be an issue for a while,
possibly even until we migrate the server.
Gmail seems to be rate-limiting our IP because we keep reflecting
info(a)sudoroom.org spam. Incredibly, our postfix config lacked even
basic spam protections. I've added a bunch of
smtpd_recipient_restrictions which will hopefully help until we
finally migrate to digitalocean.
---------- Forwarded message ----------
From: <mailman(a)lists.sudoroom.org>
Date: Sun, Apr 26, 2015 at 12:59 PM
Subject: Bounce action notification
To: info-owner(a)lists.sudoroom.org
This is a Mailman mailing list bounce action notice:
List: Info
Member: juul(a)labitat.dk
Action: Subscription disabled.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
mailman(a)lists.sudoroom.org.
---------- Forwarded message ----------
From: Mail Delivery System <MAILER-DAEMON(a)labitat.dk>
To: info-bounces(a)lists.sudoroom.org
Cc:
Date: Sun, 26 Apr 2015 21:46:39 +0200 (CEST)
Subject: Undelivered Mail Returned to Sender
This is the mail system at host labitat.dk.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<marcjc(a)gmail.com> (expanded from <juul(a)labitat.dk>): host
alt1.gmail-smtp-in.l.google.com[74.125.203.27] said: 421-4.7.0
[185.38.172.72 15] Our system has detected an unusual rate of
421-4.7.0 unsolicited mail originating from your IP address. To protect our
421-4.7.0 users from spam, mail sent from your IP address has been
temporarily 421-4.7.0 rate limited. Please visit 421-4.7.0
http://www.google.com/mail/help/bulk_mail.html to review our Bulk 421 4.7.0
Email Senders Guidelines. bz10si7534492pad.171 - gsmtp (in reply to end of
DATA command)
Final-Recipient: rfc822; marcjc(a)gmail.com
Original-Recipient: rfc822;juul(a)labitat.dk
Action: failed
Status: 4.7.0
Remote-MTA: dns; alt1.gmail-smtp-in.l.google.com
Diagnostic-Code: smtp; 421-4.7.0 [185.38.172.72 15] Our system has
detected an unusual rate of 421-4.7.0 unsolicited mail originating from
your IP address. To protect our 421-4.7.0 users from spam, mail sent from
your IP address has been temporarily 421-4.7.0 rate limited. Please visit
421-4.7.0 http://www.google.com/mail/help/bulk_mail.html to review our Bulk
421 4.7.0 Email Senders Guidelines. bz10si7534492pad.171 - gsmtp
---------- Forwarded message ----------
From: Ila Marcus <Weeks_Darrela1(a)comerciallabor.com>
To: Info <info(a)sudoroom.org>
Cc:
Date: Wed, 22 Apr 2015 02:26:42 +0600
Subject: [sudo-info] The erection you seek exists in the form of a pill
----38100116211850180
Content-Type: text/plain;
Content-Transfer-Encoding: 7Bit
These amazing medicines will bring you back to life
Your girlfriend will want nothing but your rock hard erection
We are the biggest shop in the net!
Get FREE tablets for every our customer!
http://zzb.bz/xwrDp
Experience true sexual Potential
----38100116211850180--
_______________________________________________
Info mailing list
Info(a)lists.sudoroom.org
https://lists.sudoroom.org/listinfo/info
FYI, sonic.net (our original ISP at sudo and the omni) charged our card
$150 because we did not send back the modem, which I wrote to the list
about one month ago. C'est la vie.
From: Sonic.net Billing <billing(a)sonic.net>
Date: Thu, Apr 16, 2015 at 2:01 AM
Subject: Sonic.net Invoice #7734422
<ooc(a)sonic.net>
4799 SHATTUCK AVE
OAKLAND, CA 94609-2032
_______________________________________________________________________
Description Unit Price Total
-----------------------------------------------------------------------
Charge overdue RMA for SRA06DD04 149.00 149.00
Total: 149.00
On Thu, Apr 2, 2015 at 4:24 PM, Matthew Senate <mattsenate(a)gmail.com> wrote:
> We had some issues getting Gratipay (our donation service provider at
> https://gratipay.com/sudoroom) to work with their payment processing
> Balanced Payments to make successful payouts (transactions) to our bank
> account with IAFCU, the Internet Archive Federal Credit Union, aka the
> Internet Credit Union.
>
> Now, the issues should be resolved. I am waiting to see the credit appear in
> our IAFCU account records, but I got confirmation that Gratipay successfully
> transacted the payout today via Balanced Payments.
Wow. THANK YOU SO MUCH for fixing this.
Hey all,
We had some issues getting Gratipay (our donation service provider at
https://gratipay.com/sudoroom) to work with their payment processing
Balanced Payments to make successful payouts (transactions) to our bank
account with IAFCU, the Internet Archive Federal Credit Union, aka the
Internet Credit Union.
Now, the issues should be resolved. I am waiting to see the credit appear
in our IAFCU account records, but I got confirmation that Gratipay
successfully transacted the payout today via Balanced Payments.
These were the primary issues, which took substantial digging to figure out:
1. There seem to be some federal regulations that required our credit
union to explicitly post payments to either our savings or our checking
account, without ambiguity. This is done by adding a suffix to our account
number for any given transaction, i.e. add "000" to correspond to our
savings account.
2. However, also, when this suffix is appended to our account number,
there must also be a matching value that corresponds to "savings" or
"checking" called a "TRANS code". Unfortunately, gratipay did not expose
this value option in their interface, despite it being supported by
Balanced Payments's API.
We should now have the correct suffix and the correct TRANS code that
matches to deposit gratipay payouts to our savings account at IAFCU.
Whew.
// Matt
On Thu, Mar 19, 2015 at 2:50 PM, Jenny Ryan <tunabananas(a)gmail.com> wrote:
> I believe the Wordpress was being maintained by Joe Maloney (probably a misspell there), and that the server was set up by DK.
Do you mean Joe Matheny? I'll email him and DK seperately.
We're preparing to migrate the sudoroom.org server sometime soon. The
BAPS wordpress is also sharing that server. It might be easiest - and
maybe even more appropriate - to move BAPS to the omni server ahead of
time and have it live there from now on?
I'd also like to get them an https cert while we're at it.
Who manages the BAPS wordpress? Who's the best person to contact and
coordinate with?
I'm happy to do all the legwork and logistics and will only need help
to reset their DNS at the right time. That and permission or blessings
from all people effected by it would be nice.
Thoughts? :)
On Wed, Mar 11, 2015 at 2:04 AM, Marc Juul <juul(a)labitat.dk> wrote:
> I had a hell of a time getting that to work.
Thank you Marc!!
Did you touch the phone at all? We had phone service with Sonic and
it's not clear whether we could still have a working phone. The old
number 510.858.7155 seems to no longer work.
Also, it looks like you used a personal email address for the account.
How would you feel about using accounts(a)lists.omnicommons.org?