<div><div dir="auto">It may not be particularly helpful but in my work with AWS I tend to avoid doing anything that can’t be done with an API to one of their services. They’re simply not great at working any other way.</div></div><div dir="auto"><br></div><div dir="auto">Can you use their SES service?</div><div dir="auto"><br></div><div dir="auto">Where I work we have 18,000 ec2 instances but run our mail relays on Rackspace. I don’t know if this is because of RDNS, or just for “legacy reasons”.</div><div dir="auto"><br></div><div dir="auto">Good luck with the Vogons...</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 30, 2019 at 12:21 PM Joshua Judson Rosen <<a href="mailto:rozzin@hackerposse.com">rozzin@hackerposse.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Anyone familiar with this?<br>
<br>
I've got at work VPS hosted with Amazon right now, and am trying to get<br>
Amazon to drop their constrictions on outbound SMTP traffic so that I can get logcheck<br>
reports etc. out of the server. Ideally I'd also like to get them to fix the<br>
PTR record in DNS so that it points back to the server's actual FQDN rather than<br>
some goofy "<a href="http://ec2-xx-xx-xx-xx.compute-1.amazonaws.com" rel="noreferrer" target="_blank">ec2-xx-xx-xx-xx.compute-1.amazonaws.com</a>" name.<br>
<br>
Amazon considers both of those things to be the same issue for some reason,<br>
and AFAICT has only a single form to fill out that combines them.<br>
I had the administrator on the account fill out the form, and got back<br>
this response 3 days later:<br>
<br>
We've received your request to add a RDNS entry.<br>
<br>
In order to make sure we process your request as quickly as possible,<br>
please use the form provided below to resubmit the request using<br>
the email address and information connected to the account in question:<br>
<br>
<a href="https://aws.amazon.com/forms/ec2-email-limit-rdns-request" rel="noreferrer" target="_blank">https://aws.amazon.com/forms/ec2-email-limit-rdns-request</a><br>
<br>
<br>
Not even any mention of whether they have removed the throttling on traffic outbound to SMTP ports<br>
(through testing, I can verify that they haven't--I still can just barely trickle mail out).<br>
<br>
The URL that they're directing us to is the same URL as for the form that we already filed,<br>
and we've verified that the e-mail address that we gave when we originally filed it<br>
was the e-mail address listed as the admin contact.<br>
<br>
AND we know we were logged in with the the relevant admin privileges when we filed the form...,<br>
because filing it from outside the admin login isn't even possible--attempting to do so just<br>
results in an error-message: "Root Account Required: We're sorry. This form requires a root account".<br>
<br>
What am I misunderstanding about this process?<br>
<br>
Do they really just want the request *filed twice*? Or does this indicate that there's<br>
actually some mismatch somewhere that we're overlooking?<br>
<br>
(and, yeah--I know, there are services that both cost less *and* are less of<br>
a hassle to deal with; for the time being I'd really like to figure out<br>
how to get Amazon to actually at on this...).<br>
<br>
-- <br>
Connect with me on the GNU social network! <<a href="https://status.hackerposse.com/rozzin" rel="noreferrer" target="_blank">https://status.hackerposse.com/rozzin</a>><br>
Not on the network? Ask me for more info!<br>
_______________________________________________<br>
gnhlug-discuss mailing list<br>
<a href="mailto:gnhlug-discuss@mail.gnhlug.org" target="_blank">gnhlug-discuss@mail.gnhlug.org</a><br>
<a href="http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/" rel="noreferrer" target="_blank">http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Kyle Smith<br><br></div>