MUA 'new email' User-Agent email header field - suggestions and questions
I know, I know, this is wildly off topic for this list, but I dare to ask: Dear Dolly, I note that many punky punks round these parts use their MUA du journk, yet happily advertise (of course falsely) their MUA User-Agent name and version (due to the default header config which does as much). Of course everyone round these parts is perfectly aware of such matters and has long ago manually modified such string to discretely lead any would be infiltrator astray. Such significant information so many people give away, "presently company excluded" of course... :) So, can anyone tell me of known spam filters or "outright rejection" filters in any known mail server configurations/ setups, which would reject an email header such as: User-Agent: Could be mutt but fucked if I'm telling you. Is it better to simply not include such a header? Or is it better to do the sly "make it look genuine but it's not" number? Better is a purely objective assessment of course with no rune for alternative threat models or other subjective quasi quagmires... Confused, Z P.S. Thank you my gracious and all knowing lords of the crypto best practices paddfock. May we romp in freedom with daisies to save the world, as I've heard love and light is all powerful and will save us all.
Personally I believe in obfuscation... The less the spooks know the better including knowing of your evasion by taunting them (/depends on what your trying to accomplish I guess/). For browsers like firefox there's IPFuck and a user-agent string changer that allows one to spoof another browser or create a "/Could be mutt but fucked if I'm telling you/" string. Must be some tool like that for mail user-agents. https://addons.mozilla.org/en-US/firefox/addon/blend-in/ Also see: https://sourceforge.net/projects/emspoofer/ Rr On 06/08/2016 04:02 AM, Zenaan Harkness wrote:
I know, I know, this is wildly off topic for this list, but I dare to ask:
Dear Dolly, I note that many punky punks round these parts use their MUA du journk, yet happily advertise (of course falsely) their MUA User-Agent name and version (due to the default header config which does as much).
Of course everyone round these parts is perfectly aware of such matters and has long ago manually modified such string to discretely lead any would be infiltrator astray. Such significant information so many people give away, "presently company excluded" of course... :)
So, can anyone tell me of known spam filters or "outright rejection" filters in any known mail server configurations/ setups, which would reject an email header such as:
User-Agent: Could be mutt but fucked if I'm telling you.
Is it better to simply not include such a header?
Or is it better to do the sly "make it look genuine but it's not" number?
Better is a purely objective assessment of course with no rune for alternative threat models or other subjective quasi quagmires...
Confused, Z
P.S. Thank you my gracious and all knowing lords of the crypto best practices paddfock. May we romp in freedom with daisies to save the world, as I've heard love and light is all powerful and will save us all.
On 06/08/16 21:02 +1000, Zenaan Harkness wrote:
So, can anyone tell me of known spam filters or "outright rejection" filters in any known mail server configurations/ setups, which would reject an email header such as:
User-Agent: Could be mutt but fucked if I'm telling you.
Choose some phrase that does not include both mutt and fucked and you're probably fine, with regards to the commercial email space. Otherwise avoid non-ascii. User-agent strings have importance in direct client to server protocols, like http and imap. -- Dan White
On 6/8/16, Dan White <dwhite@olp.net> wrote:
User-agent strings have importance in [...] imap
Link to RFC please. Just pick the most popular thing out there and clone it. Else read the TBB ua string rehashes on tor-talk. Or use no string at all. https://user-agents.me/
On 06/08/16 23:57 -0400, grarpamp wrote:
On 6/8/16, Dan White <dwhite@olp.net> wrote:
User-agent strings have importance in [...] imap
Link to RFC please.
https://www.ietf.org/rfc/rfc2971.txt -- Dan White
On 6/9/16, Dan White <dwhite@olp.net> wrote:
Its an optional extension, and a privacy violating one, with a long list of MUST NOTs, in deference to actual CAPABILITYs, thus ignored this pointless rfc from list of standard rfc's. I'll submit my own bugs and pass on stats.
participants (4)
-
Dan White
-
grarpamp
-
Rayzer
-
Zenaan Harkness