On Fri, 17 Jul 2009, alan wrote:
Since everyone is shooting down my v3 ideas with "here's how you could
do it in v1", let me shoot yours down. :-) All(!) you have to do is
have your MTAs encode the sender in the helo name it uses when
transmitting the email. For instance, assign an ID number to every
recipient in your "braindead" list. Use BDnnnnnnnn.smtp.example.com
as the HELO name in your MTA, where nnnnnnnn is the ID assigned to the
braindead recipient.
A I'm hoping its a joke
Yes, it's a joke.
"Doable" often means "too painfully ugly to actually implement".
B the helo is invariant it should not change from one connection to the next
and if it does the machine often triggers anti-bot detection systems
The HELO would always be the same for a given recipient domain, so it won't
trigger the anti-bot systems.
C most MTA's have no method to change the helo without restart
So don't use one of those inflexible MTAs. :-)
In the case of sendmail, just use a Socketmap for the %j macro (or
copy a Socketmap macro to %j on each connection for efficiency).
D then you have the headache of maintaining the A records for all thes helo's
and the spf records for all these helo's {+CSV or any other record types that
get used to validate HELO in the future}
Just use a wild card in DNS.
*.smtp.example.com IN A 1.2.3.4
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
Archives: https://www.listbox.com/member/archive/735/=now
RSS Feed: https://www.listbox.com/member/archive/rss/735/
Powered by Listbox: http://www.listbox.com