Re: [mailop] Filter out emoji from email adresses

>>So it still contains only ASCII, until displayed. Exactly, but when the mail client tries to display the crap in the name field, it causes it to crash. Guess it tries to render Emoji in a field that is not designed to accept Emoji, thus it just silentcrash into desktop. So people can't access

[mailop] Filter out emoji from email adresses

Anyone that have a general algoritm to filter out emoji from sender addresses? How I do in regexp to identify emoji? (its such a stupid thing).. A guy sent a email containing emoji in the name part of a email sender address in MIME FROM (like: Name [EMOJI] ). This caused a few email clients to

Re: [mailop] Is forwarding to Gmail basically dead?

>>Do they also allow you to search for the original sender? No not via sender search, as the encapsulated email is part of the BODY of the container email. So usually you have to search via body search. >>And, again, what is the overall benefit to the end user from this scheme? Benefit is

Re: [mailop] Is forwarding to Gmail basically dead?

>> An "anonymous" proxy, configured specifically to hide the original poster No, all proxies are per definition anonymous unless they specifically add the header X-Forwaded-For. Otherwise, the IP becomes “automatically” hidden, if it passes communication unmodified. That’s why they have become

Re: [mailop] Is forwarding to Gmail basically dead?

>> it basically makes it impossible to respond to the original email sender Nope, you just open the encapsulated email (open the .EML attachment), and respond to that. Some mail clients show the encapsulated email in a “frame” which has its own reply buttons. Best regards, Sebastian

Re: [mailop] Is forwarding to Gmail basically dead?

>>Many antispam filters will right away classify such an email as spam. No, that’s not true, UNLESS the antispam filter resides as a local software in the client's software as a plugin to the email client, which would of course detect the "attached file" even its not technically an attached

Re: [mailop] Is forwarding to Gmail basically dead?

používateľ Sebastian Nielsen via mailop napísal:>>>On my site, users can use only own address/aliases, but i can use any (including any domain)...>>Of course since you are administrator. Nothing strange with that.It was not meant as self-presentation, but as particular examplethat o

Re: [mailop] Is forwarding to Gmail basically dead?

>>And how you can know if site enforces that? And i don't mean guess, nor >>believe, but really **know** with particular message? Since you on your domain are in control of SPF, you of course choose a provider you **know** enforces that. So you simply choose a provider who you trust enforces

Re: [mailop] Is forwarding to Gmail basically dead?

>> because SPF is too easy to forge.) Wrong. When a shared space is used, its up to that particular space, to enforce so customers cannot use other customer’s email addresses. In the same way you cannot, and should not be able to use someu...@hotmail.com

Re: [mailop] Why is mail forwarding such a mess?

>>To me this seems "fairer" than wrapping the message alone, because the >>forwarding server now takes on the burden of the reputation hit for that >>message. >>Eventually, enough viagra messages will be forwarded that the >>forwarder can't get any mail delivered anywhere. That’s on the

Re: [mailop] Why is mail forwarding such a mess?

This would require some sort of trust. Like with certificates, but where you apply that you are not a spam sender. The tricky part is that the original sender, cannot know (and should not know) where a mail is forwarded. So a handshake between the original sender and final recipient isn't gonna

Re: [mailop] Is forwarding to Gmail basically dead?

Från: John Levine via mailop Skickat: den 10 februari 2024 04:35 Till: mailop@mailop.org Kopia: sebast...@sebbe.eu Ämne: Re: [mailop] Is forwarding to Gmail basically dead? It appears that Sebastian Nielsen via mailop said: >Or people could stop forwarding emails in idiotic ways, because when

Re: [mailop] Is forwarding to Gmail basically dead?

>>just because SPF and DMARC are so badly designed that they can't handle it >>doesnt make it "forging" anything. It isn't badly designed. Forwarding a email, is the equvalient of, when you receive a signed envelope from me containing a letter, you forge my signature on the new envelope. That

Re: [mailop] Is forwarding to Gmail basically dead?

Or people could stop forwarding emails in idiotic ways, because when you forward an email, you are actually forging the original sender. Ergo, if you forward a email from genuineu...@genuineserver.com to myacco...@gmail.com via an account called exam...@example.org .. Technically, you

Re: [mailop] Samsung and SIZE

>> I was thinking about not advertising SIZE myself, because our limits are >> already very high so people can send large attachments internally. I would still suggest setting a sensible limit, like 100 MB or similar, to avoid the problem that certain MUAs tend to timeout, crash or stall while

Re: [mailop] Samsung and SIZE

2024 08:56 Till: mailop Ämne: Re: [mailop] Samsung and SIZE Am 15.01.24 um 07:54 schrieb Sebastian Nielsen via mailop: That header is supposed to be attached by the originating MUA, and I don't *think* transit MTAs are permitted to rewrite it... Problem is, that when MUA or first MTA has

Re: [mailop] Displaying logos

>>I do think it would be better to use a common key that could be used to >>verify multiple signed user images, this way only one DNS record would need >>to be published and the user's eMail address could be used as part of the >>verification, sort of like how OpenVPN does this (I'm sketchy on

Re: [mailop] Samsung and SIZE

>> That header is supposed to be attached by the originating MUA, and I don't >> *think* transit MTAs are permitted to rewrite it... Problem is, that when MUA or first MTA has a incorrect date set, the email comes like last in inbox... have seen emails set with 1970-01-01 00:00:00 Or, even

Re: [mailop] Displaying logos

I envision this being a system for individual domains, ergo non-corporate domain owners. For domains with a few users, then it would require a DNS record per user yes. For domains with many users, then it would be a corporation owning it, and thus it would bear the logo for the corporation.

Re: [mailop] Displaying logos

I have sent this to Digicert and Entrust in a hope of creating a simple certification BIMI process for individuals. If this process becomes standardized, it could gain the same traction as Lets Encrypt and eventually become free. Remember how StartSSL had cheap code signing and SSL wildcard

Re: [mailop] Samsung and SIZE

Then you need to reconfigure server to ignore said parameters. Originalmeddelande Från: ml+mailop--- via mailop Datum: 2024-01-13 19:58 (GMT+01:00) Till: mailop@mailop.org Kopia: ml+mai...@esmtp.org Ämne: Re: [mailop] Samsung and SIZE On Sat, Jan 13, 2024, Sebastian Nielsen

Re: [mailop] Samsung and SIZE

Why is it a problem? The server ignores commands that it don't have capability for anyways. Only wonkiness of Samsung Mail (same in Microsoft Outlook), I have noticed, is that new email happens to arrive in the middle of the inbox if the sending server has its date incorrectly set. (EXTREMELY

Re: [mailop] ClientID - was Re: Microsoft lays hands on login data: Beware of the new Outlook

Yeah, with lockdown to webmail cookie, you could require 2FA or mobile auth via webmail... then you get a cookie and can then login using the regular email client. Like, if you don't supply a cookie clientid, it will respond: "Please login to webmail once to authorize this client".But this

Re: [mailop] Abuse AUTH from Microsoft outlook IP space

ng proxied, yes. But if it was due to not liking the features (which I'm quite certain has not changed on our end) wouldn't it be more logical to quit after HELO/EHLO rather than AUTH? On 2023-08-14 11:08, Sebastian Nielsen via mailop wrote: > Could it also be their outlook for mobile conne

Re: [mailop] Abuse AUTH from Microsoft outlook IP space

Could it also be their outlook for mobile connections, where the connection fails for some other reason, like the server don't like the features supported? It seems to use some sort of proxy, where outlook's server connects to the server in question instead of a direct connection from the phone

Re: [mailop] Delivery Reports, requested by Microsoft Outlook customer, reported as Spam by same Mic

Another thing to consider, is that the "Spam" button in some MUAs and some web mail providers, is lookalike the delete button, so newbie users may make it wrong.I have even seen providers making "Spam" the default action, so you have to push an arrow and select "delete" in an dropdown to

Re: [mailop] I Need someone from AOL and/or Yahoo to contact me

>>implement XOAUTH2 (which hopefully will already be supported by the client) Most MUAs don't support this except with a predefined list of providers. For example, Samsung Email only support XOAUTH2 for Gmail, Yahoo, Hotmail/Outlook, Exchange and Office365 servers. All other don't support it.

Re: [mailop] I Need someone from AOL and/or Yahoo to contact me

3-07-24 10:35, Sebastian Nielsen via mailop wrote: > Also on the topic on mail server hacking, I would suggest to add > IP-restriction on your mail accounts. > > Theres 2 ways to include IP-restrictions in Exim: > > The easiest one, is to simply lock out authentication

Re: [mailop] I Need someone from AOL and/or Yahoo to contact me

Also on the topic on mail server hacking, I would suggest to add IP-restriction on your mail accounts. Theres 2 ways to include IP-restrictions in Exim: The easiest one, is to simply lock out authentication for all unauthorized IPs (Or simply block in firewall so unauthorized IPs cannot

Re: [mailop] SPF +all considered harmful

>> Outbound MSA re-sends the >> Inbound spam filter re-sends the message >> Outbound compliance filter re-sends the message out to the world Those I consider internal processing of email, which don't really count as "forwarding" of a email. I consider a email forwarded, when its being

Re: [mailop] SPF +all considered harmful

>>them loathed the idea of the envelope from address being changed at one or more hops along the way. I think sender adress should be changed. The reason is, you didn't compose the email, you shouldn't use the sender's identity. When forwarding a email, you overtake the spam responsibility for

Re: [mailop] SPF +all considered harmful

I would say +all is always harmful. The difference between having +all and not having any at all (or ?all) is that you affirmately, by using +all, tell the system the email is genuine. If you somehow want to treat all emails as “unspecified” or “unknown”, ergo don’t want to reject, but you want to

Re: [mailop] Mimecast Adimin Probation Block - 74.203.49.59

>>See RFC 8058 on doing one-click unsubs in a way unlikely to be mistriggered. Its a good idea, but don't count on all MUAs implementing this function, so best here is to have both, if request arrives from the RFC 8058 header, treat it as secure enough to warrant one-click, but if it arrives

Re: [mailop] Mimecast Adimin Probation Block - 74.203.49.59

No, but a 2-step procedure is recommended. Click the link, then push a button to confirm. Some actors also require a checkbox, to really make sure link-following bots don't confirm. Or even a simple captcha. Don’t neccessarly need to use POST, but scanning systems scan the links to ensure no

Re: [mailop] Listed on Polspam.pl - how to delist?

Contacted spamhaus about delist and apparently my domain got errorously listed because being a robot flagged me for being in a "suspicious neighbourhood (IP rating)". They delisted me immediately and resetted my domain reputation (that are taken from IP reputation). It just seemed polspam and

Re: [mailop] Listed on Polspam.pl - how to delist?

to delist? Sebastian Nielsen via mailop skrev den 2023-06-26 10:39:> It seems I have got listed on polspam.pl for some reason. I cannot> find why, if there is some email that I sent that triggered something,> or if someone accidentially pressed "Spam" instead of "Delete&qu

[mailop] Listed on Polspam.pl - how to delist?

It seems I have got listed on polspam.pl for some reason. I cannot find why, if there is some email that I sent that triggered something, or if someone accidentially pressed "Spam" instead of "Delete" which happens regularly. Theres no contact details on their website, and they have disabled

Re: [mailop] SendGrid is deleting your mail

>> We update kernels, reload AV signatures, have databases go down, >> accidentally crash postfix during OS upgrades, typo config files, etc. Couldn't you make so if the inner servers are in trouble or go down or similar, then the perimeter server will buffer the email for you without a

Re: [mailop] SendGrid is deleting your mail

>> They were going to get a 4xx anyway. I changed the message to *help* >> SendGrid. Yes but if you can change the message for SendGrid only, you can accept the mail and let it through >> Where do I find out what the IP/domain is? Is it in my mail logs, Apparently you were able to send custom

Re: [mailop] SendGrid is deleting your mail

>>The RFC forbids doing that, and I argued against it The RFC and reality is two different things. If a client don't want to retry, I think they are free to choose to not retry. Why even send retry requests to SendGrid? Just accept the email, whats the problem? If your antivirus or mail

Re: [mailop] Transparency is key... Here is a perfect example.. M3AAWG is coming.. time to take a st

I don't agree with your stance. Hiding whois details doesn't mean you hiding your identity. Normally, this type of privacy is also used when you want to hide the actual person that is responsible for, lets say paying the domains. Because, you don't want people calling these phones, about spam,

Re: [mailop] Hotmail will start rejecting messages that fail DMARC

that fail DMARC It appears that Sebastian Nielsen via mailop said:>-=-=-=-=-=->-=-=-=-=-=->I think forwarders and mailing lists should start rewriting From: instead to a adress for which they are authorative,Oh, please, not the blame the victim argument again.See archives of this list

Re: [mailop] Hotmail will start rejecting messages that fail DMARC

I think forwarders and mailing lists should start rewriting From: instead to a adress for which they are authorative, or encapsulate the list message in a new rfc822 container, where the inner container is the email unmodified, and the outer container is From: replaced with the list or

Re: [mailop] Sendgrid abuse forwarding to Google - not one of your brightest ideas

the inbox. Originalmeddelande Från: Jaroslaw Rafa via mailop Datum: 2023-03-22 11:29 (GMT+01:00) Till: mailop@mailop.org Ämne: Re: [mailop] Sendgrid abuse forwarding to Google - not one of your brightest ideas Dnia 22.03.2023 o godz. 10:01:53 Sebastian Nielsen via mailop pisze:>

Re: [mailop] Sendgrid abuse forwarding to Google - not one of your brightest ideas

A good idea when you get this type of response, just include the full headersand not the actual body of message.A competent abuse department should be able to fish out a verbatim copy of the message being reported in their logging systems using the headers alone. Originalmeddelande

Re: [mailop] Compromised email account trends

Problem with OAuth2 is that many commercial mail clients only support it for a select number of big providers thus you have 2 choices, either implement geo-restriction, or have a 2FA auth portal where you authorize IPs to access your account. Originalmeddelande Från: Taavi

Re: [mailop] Compromised email account trends

Didn't get steve's mail for some reason (guess it was because i forgot to renew exim tls cert, but its renewed now), but replying to it here.Another good way to prevent account compromise in the first place, is:1: If your users solely are based in a few countries (employees for example), then

Re: [mailop] Branch: Fixing incorrect headers in emails

>>Users can always sort messages in receivedordertry doing that in Samsung >>Email or another OEM client like MS Outlook ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop

Re: [mailop] Branch: Fixing incorrect headers in emails

>>second guess sendersOf course, you should never "guess" anything. For >>example, dont correct spelling errors in subject lines.Im talking when a >>header is incorrect, invalid, or unparseable, or if header is unuseable for >>snother reason **AND** the fault is easily fixable.As I said, if

Re: [mailop] Branch: Fixing incorrect headers in emails

>>As long as these headers are not DKIM signed.Thats why you do DKIM-validation >>the very first thing you do. Then you can mess with the mail as your heart >>wish.If you have further servers down the line, create a header like >>X-DKIM-Origin: pass.Then have a routine which deletes all

Re: [mailop] [FEEDBACK REQUEST] Allowing Messages with Bcc to travel the internet.

For incoming mail, if you see only spam with bcc set in the clear, reject it.Maybe make exception for hosts that you know is problematic, and just strip the bcc header.For outgoing mail, strip the header instead of rejecting.(in the same way I strip the Date header off every outgoing and

Re: [mailop] [Admin] Changes to list behaviour, members spam filters etc

>>that trigger take over domain in from: header so its basicly not origin >>poster any more, but it pass dmarc, lol :) Yes it pass DMARC because the MIME From: domain is rewritten to mailop@mailop.org Having spurious signatures that don't validate fully, is OK (and some DKIM tools may report

Re: [mailop] [Admin] Changes to list behaviour, members spam filters etc

ll: mailop@mailop.org Ämne: Re: [mailop] [Admin] Changes to list behaviour, members spam filters etc On Mon 21/Nov/2022 16:22:28 +0100 Sebastian Nielsen via mailop wrote: > Very important that you keep the MIME From: and MAIL FROM: rewrite to > mailop@mailop.org if you are going to implement this

Re: [mailop] SPF (and other email security protocols) Survey

It DO make sense. What it means, is that the subject of the survey, is non human (is not about humans) and thus does not require any approval. Surveys that run a specific sensitive subject, must in some places, have a license or approval first. For example, these are non-human: "Do you run

Re: [mailop] [Admin] Changes to list behaviour, members spam filters etc

Very important that you keep the MIME From: and MAIL FROM: rewrite to mailop@mailop.org if you are going to implement this change, so you don't trip sender domain, antispoofing, TLD banlists, DKIM, SPF or DMARC filters. Also local permanent errors that indicates NS cannot be found, should IMHO

Re: [mailop] How do I break Gmail forwarding?

inbox though. Tara On Mon, Oct 24, 2022 at 9:23 AM Sebastian Nielsen via mailop mailto:mailop@mailop.org> > wrote: Does the MAIL FROM (Sender header) contain the gmail address? Does the MIME From contain the gmail address? Check the headers if the gmail address is SOM

Re: [mailop] How do I break Gmail forwarding?

Does the MAIL FROM (Sender header) contain the gmail address? Does the MIME From contain the gmail address? Check the headers if the gmail address is SOMEWHERE there. Then you could put a rule to block such mails. Från: Tara Natanson via mailop Skickat: den 24 oktober 2022 15:09

Re: [mailop] Tangent: Banks and imprint requirements in Germany

y receives mail? -Ursprungligt meddelande- Från: Slavko via mailop Skickat: den 23 oktober 2022 10:23 Till: 'Mailing List' Ämne: Re: [mailop] Tangent: Banks and imprint requirements in Germany Dňa 23. októbra 2022 2:40:42 UTC používateľ Sebastian Nielsen via mailop napísal: >

Re: [mailop] Tangent: Banks and imprint requirements in Germany

: [mailop] Tangent: Banks and imprint requirements in Germany Am 23.10.22 um 02:00 schrieb Sebastian Nielsen via mailop: When a service is provided totally for free, no strings attached, no requirements, nothing. Then its not a "service offered for remundiation" and thus, according to tha

Re: [mailop] Tangent: Banks and imprint requirements in Germany

oktober 2022 04:09 Till: mailop@mailop.org Ämne: Re: [mailop] Tangent: Banks and imprint requirements in Germany We're quite diverging from the topic ... Am 23.10.22 um 01:30 schrieb Sebastian Nielsen via mailop: a htaccess wont discharge you from being a "public service". Yes,

Re: [mailop] Tangent: Banks and imprint requirements in Germany

>> has to put up an imprint on their website as well and show a cookie banner >> before it can be seen No, theres no imprint requirement in Sweden if you do not operate a public service for remundiation (for pay). Then there is certain requirements by the consumer law if you provide paid

Re: [mailop] Tangent: Banks and imprint requirements in Germany

>>AFAIK, if _you_ get _any_ *benefit* from what you put on your website (via >>ads, affiliate links, whatever) Yes correct, everything that increases your "richness" or saves you money, counts as remuneration. Doesn’t matter if its money, if its affiliate links, if its donations, if its

Re: [mailop] Tangent: Banks and imprint requirements in Germany

The thing is that theres 2 things discussing here: There is "public service". According to EU and Swedish law, anything that responds on internet packets are a public service. This because HTTP is not the only protocol that exist on the internet. Different protocols ask for password in

Re: [mailop] Tangent: Banks and imprint requirements in Germany

aight off the EU law requirements. -Ursprungligt meddelande- Från: Kai 'wusel' Siering via mailop Skickat: den 23 oktober 2022 01:17 Till: mailop@mailop.org Ämne: Re: [mailop] Tangent: Banks and imprint requirements in Germany Am 22.10.22 um 23:55 schrieb Sebastian Nielsen via mailop: >

Re: [mailop] Tangent: Banks and imprint requirements in Germany

-Ursprungligt meddelande- Från: Kai 'wusel' Siering via mailop Skickat: den 23 oktober 2022 01:17 Till: mailop@mailop.org Ämne: Re: [mailop] Tangent: Banks and imprint requirements in Germany Am 22.10.22 um 23:55 schrieb Sebastian Nielsen via mailop: > Germany and Sweden do not. And

Re: [mailop] Tangent: Banks and imprint requirements in Germany

: den 23 oktober 2022 00:42 Till: mailop@mailop.org Ämne: Re: [mailop] Tangent: Banks and imprint requirements in Germany Moin, am 22.10.22 um 23:33 schrieb Jaroslaw Rafa via mailop: > Dnia 22.10.2022 o godz. 19:06:25 Sebastian Nielsen via mailop pisze: >> That’s why, running a PAID on

Re: [mailop] Tangent: Banks and imprint requirements in Germany

er outage Is a force majure. -Ursprungligt meddelande- Från: Jaroslaw Rafa via mailop Skickat: den 22 oktober 2022 23:41 Till: mailop@mailop.org Ämne: Re: [mailop] Tangent: Banks and imprint requirements in Germany Dnia 22.10.2022 o godz. 20:55:00 Sebastian Nielsen via mailop pisze:

Re: [mailop] Tangent: Banks and imprint requirements in Germany

. -Ursprungligt meddelande- Från: Jaroslaw Rafa via mailop Skickat: den 22 oktober 2022 23:34 Till: mailop@mailop.org Ämne: Re: [mailop] Tangent: Banks and imprint requirements in Germany Dnia 22.10.2022 o godz. 19:06:25 Sebastian Nielsen via mailop pisze: > > That’s why, running a PAID

Re: [mailop] Tangent: Banks and imprint requirements in Germany

imprint requirements in Germany Dňa 22. októbra 2022 17:06:25 UTC používateľ Sebastian Nielsen via mailop napísal: >If its free for absolutely no cost, then its "on your own risk". You can't >really expect anything if you grab something for free. >Then imprint is not required, th

Re: [mailop] Tangent: Banks and imprint requirements in Germany

Yeah, and for tax control purposes aswell. As long as you involve money into something, the government want to ensure its fair, so you don't scam people. Ergo, paid online services hold a minimum quality, online games doesn't involve cheating, products hold what they promise etc. Else it would

Re: [mailop] Tangent: Banks and imprint requirements in Germany

Its very clear from the document you provided, that it DOES require that the service in question does bear a cost. We have a similar law in Sweden when it comes to electronic communications, which only applies to services for-pay. Free services are not included, so if you provide free wifi, it

Re: [mailop] Microsoft 365 send spam via high-risk delivery pool (instead of block it)

>>What if the email was beng sent to an abuse team to complain that Simple: If (this.header('to') =~ m/.*>What if this is someone asking a trusted one whether the deal is real? >>..or their reply that it is not? if (Checkinbox(from, this.header('to')) == true) { Permit(); } Else { Block(); } Sub

Re: [mailop] So, Sendgrid / Zoom, planning on actually doing anything about webinar spams?

>>whereas press@ec.europa.eｕ would not. There have been cases where a role based email like that have been considered being personal details in case of only one person having access to the mailbox. This on the basis that there can be collected information (IP-adresses and such) from other

Re: [mailop] Barracuda DKIM checker reports invalid signature

One common issue is Canonicalization. Try setting your to relaxed/relaxed and it solves many issues. Many of these things "downconvert" the emails into 7BITMIME and also munge certain whitespace characters, which can b0rk the signatures. So try setting to relaxed/relaxed and see what happens.

Re: [mailop] outlook/hotmail (silently!) putting legit msgs into "Junk Email" folder

I suspect your webmail system is putting certain headers in the email, that Hotmail/Outlook detects, and Hotmail/Outlook have detected a issue with the particular webmail system, like a security issue that allows unauthorized users to send spam through the webmail system, causing

Re: [mailop] Any reason to NOT block the entire .cam domain? [signed]

Universität Berlin at www.tu.berlin. And, of course, you might miss this reply alltogether (sender from posel.email). Well your server your rules, of course. Best regards Johannes Von meinem iPhone gesendet > Am 27.05.2022 um 21:17 schrieb Sebastian Nielsen via mailop > : > > I

Re: [mailop] Any reason to NOT block the entire .cam domain?

I block a lot of these pieces of shit domains, including .cam: deny message = 5.7.1 Banned TLD in MAIL FROM sender_domains =

Re: [mailop] Interesting passage from the new EU Digital Services Act

It doesn't apply to phishing. Its very clear its about emergencies, ergo threats about violence, bombs and such. Phishing is definitely not a "threat to the life or safety of persons" as it only poses a threat to property, ergo money. -Ursprungligt meddelande- Från: Anne Mitchell via

Re: [mailop] Pretty convincing ICANN renewal notice making the rounds..

>>Seriously? Using Hotmail/Google is NOT FREE.. It is. They earn the money on ads, but the ad cost cannot swallow a fine. That would mean they would need some way to reimburse the fine from the end user, meaning you would need to have a credit rating as it would count as a loan agreement,

Re: [mailop] Pretty convincing ICANN renewal notice making the rounds..

Of course its important to check WHO is sending the email too, not just that its signed. The email is obviously not from ICANN. Of course it authenticates correctly as the sender it claims to be, as that’s the truth. Authentication – checking that something is true and not false. For

Re: [mailop] suggested max received headers/hop limit

Reason to have a hop limit is to prevent infinite loops where 2 email addresses or servers point on each other. So its not good to set a hop limit too high either, without any compensating controls, like having a high hop limit, but cease delivery if it for example stumbles upon 2 received

Re: [mailop] What the f**k, Google?

162.251.248.0/24 162.251.249.0/24 162.251.250.0/24 162.251.251.0/24 162.251.252.0/24 162.251.253.0/24 162.251.254.0/24

Re: [mailop] 2 questions about BCC and mailing lists

>>I would say a). Why? Then you end up with 3 copies of the email. Remember this: You have sender's server, which we can call ServerA. If recipient is yourn...@example.org and list is mailingl...@examplelist.org ServerA (sender's server) will now send the email to yourn...@example.org AND

Re: [mailop] Gmail does not validate DKIM for forwarded messages?

I feel this is the best option. Rewrite both MAIL FROM and MIME From:, and resign the message. This avoids any authentication errors, including SPF. Another method is to take the whole message (including its headers, which is a message/rfc822 object), and encapsulate it in a new

Re: [mailop] 2 questions about BCC and mailing lists

1: never, as the original email has already been sent to the recipient by the original server. EXCEPTION: If the message was submitted to the listserver by another means - for example webform/unix call, or via an authenticated session (where sender is either authenticated by username/password

Re: [mailop] [Admin note] re spam filters

into and meaning they don't get catched in the spam filter. -Ursprungligt meddelande- Från: Bill Cole via mailop Skickat: den 25 januari 2022 16:21 Till: Sebastian Nielsen via mailop Ämne: Re: [mailop] [Admin note] re spam filters On 2022-01-25 at 06:53:20 UTC-0500 (Tue, 25 Jan 2022 12:53:20

Re: [mailop] [Admin note] re spam filters

I don't know if my address generate any bounces, but I don't have any content based spam filters (except for some explicit content that is identified by exact match - should never trigger anything on this mailing list unless someone copies a spam email into the mailing list). Only thing I

Re: [mailop] Idea for new internet standard: DKIM-QR

The problem here is that the signer isn't shown prominently in MUA's. Here is where the QR code comes in. So yes, a phisher might own a own domain, lets say spammydomain.xyz, and get the mail legitimately signed as spammydomain.xyz and get DMARC/DKIM pass. That’s why I suggest this QR code

Re: [mailop] Idea for new internet standard: DKIM-QR

:22 Till: Sebastian Nielsen via mailop Ämne: Re: [mailop] Idea for new internet standard: DKIM-QR If the QR code is just another header added to the mail, you'll need support in every MUA to display this QR in a way that could be scanned easily. Adding this to multiple MUAs is much more unlikely

Re: [mailop] Idea for new internet standard: DKIM-QR

>>Note that to validate the message, the app needs access to not only the >>signed header fields, but also the body, that the value of bh= is based upon. Of course. That’s why I suggested that content validation should be ignored. Only headers should be validated. Since the content is "signed"

Re: [mailop] Idea for new internet standard: DKIM-QR

nks will have their QR in emails "DKIM-QR: Scan to verify its genuine" and even Paypal could use such a feature. -Ursprungligt meddelande- Från: John Levine via mailop Skickat: den 12 december 2021 00:04 Till: mailop@mailop.org Kopia: sebast...@sebbe.eu Ämne: Re: [mailop] Idea for ne

[mailop] Idea for new internet standard: DKIM-QR

Hi. Im new here, and have been a mail server operator for quite a bit of a time. I just got a new idea for a new internet standard - that builds upon DKIM - that should be named as DKIM-QR. And want to hear your toughts about the idea. The idea is as follows: An DKIM-compliant sender,