Re: [mailop] Debugging fwd issue meta.com to zoho.com (Help from user under meta.com needed)
On Sat, 2024-06-08 at 12:36 +0200, Alessandro Vesely via mailop wrote: > ... (unless bugs in email-security-scans are just decorative.) Which ones exactly? With best regards, Tobias -- Dr.-Ing. Tobias Fiebig T +31 616 80 98 99 M tob...@fiebig.nl ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] Debugging fwd issue meta.com to zoho.com (Help from user under meta.com needed)
On Sat 08/Jun/2024 13:28:30 +0200 Slavko via mailop wrote: Dňa 8. júna 2024 10:36:44 UTC používateľ Alessandro Vesely via mailop napísal: Yes, as it seems Tobias is going to file a bug against rspamd, I presume you are going to somehow fix it (unless bugs in email-security-scans are just decorative.) I have nothing to do with email-security-scans, and very little to do with rspamd (i only use it)... Thus no, i will not (be able to) fix anything about this ;-) Oops, I must have meant Vsevolod. Sorry, these Slavic names confused me... Best Ale -- ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] IPv6 only MX
the real server doesn't send directly, but send via a gateway such as mail.baby. Thanks. However, on the outbound, if the mx.myserver.com sends directly, you may run into issues there with servers that don't have a record on their MX - unless you proxy to a smarthost that can do IPv4. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] IPv6 only MX
Ah, you'd be using Cloudflare's email routing. If Cloudflare's MTA can deliver over IPv6, you should be ok, as only they would be delivering to the subdomain and everyone else would deliver to Cloudflare first. However, on the outbound, if the mx.myserver.com sends directly, you may run into issues there with servers that don't have a record on their MX - unless you proxy to a smarthost that can do IPv4. On Saturday, June 08, 2024 12:13 CEST, Jeff P via mailop wrote: Hello I was thinking to use cloudflare email routing for incoming messages. for example, domain.com points MX to mx.cloudflare.net And, sub.domain.com points MX to mx.myserver.com mx.myserver.com has ipv6 only. When u...@domain.com gets messages from internet, they are accepted by cloudflare. Then clouflare forward them to u...@sub.domain.com. So user read messages in the mailbox of u...@sub.domain.com. Surely they can send messages by the sender u...@domain.com. Thanks for all the kind answers. regards. > The interesting things is how is you priority set? > Is the IPv6 MX the highest? ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] Debugging fwd issue meta.com to zoho.com (Help from user under meta.com needed)
Dňa 8. júna 2024 10:36:44 UTC používateľ Alessandro Vesely via mailop napísal: >Yes, as it seems Tobias is going to file a bug against rspamd, I presume you >are going to somehow fix it (unless bugs in email-security-scans are just >decorative.) I have nothing to do with email-security-scans, and very little to do with rspamd (i only use it)... Thus no, i will not (be able to) fix anything about this ;-) regards -- Slavko https://www.slavino.sk/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] Debugging fwd issue meta.com to zoho.com (Help from user under meta.com needed)
On Fri 07/Jun/2024 17:03:00 +0200 Slavko via mailop wrote: Dňa 7. júna 2024 14:37:24 UTC používateľ Alessandro Vesely via mailop napísal: If I were Slavko I'd fix rspamd by adding bug reporting (if it's not already there) rather than removing 2047-decoding. Are you sure, that you did mean me? Yes, as it seems Tobias is going to file a bug against rspamd, I presume you are going to somehow fix it (unless bugs in email-security-scans are just decorative.) The fix I propose requires they to also consider DMARC reports, which would be cool. I was just curious about IDNA syntax in this case... Just got this: Authentication-Results: mx.google.com; dkim=pass header.i=@foà.it header.s=gamma header.b=Akp+6zYW; spf=pass (google.com: domain of postmaster@foà.it designates 94.198.96.74 as permitted sender) Best Ale -- ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] IPv6 only MX
Hello I was thinking to use cloudflare email routing for incoming messages. for example, domain.com points MX to mx.cloudflare.net And, sub.domain.com points MX to mx.myserver.com mx.myserver.com has ipv6 only. When u...@domain.com gets messages from internet, they are accepted by cloudflare. Then clouflare forward them to u...@sub.domain.com. So user read messages in the mailbox of u...@sub.domain.com. Surely they can send messages by the sender u...@domain.com. Thanks for all the kind answers. regards. The interesting things is how is you priority set? Is the IPv6 MX the highest? ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] IPv6 only MX
* Jeff P. via mailop: > Can cloudflare (or others) deliver messages correctly to this IPv6 MX? The longish answer is a resounding "maybe". An IPv6-only MX can be reached only by those third-party servers which support outbound IPv6 connections on their end. Even in 2024, that is by no means every server, not even for large organisations who could be expected to support IPv6. I have done contract work for nominally big players in the email scene who don't support IPv6 at all on their end, neither for inbound nor outbound network traffic. Short version: An IPv6-only MX may work for certain limited usecases, but will most likely not work in all scenarios. It comes down to external factors you cannot control. Personally, I would not attempt to run a production MX without having public-facing addresses for both IPv4 and IPv6. -Ralph ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
