Re: [mailop] Yahoo/AOL Blocking
won't lili here help you? Anybody from Yahoo/AOL able to assist with what's causing the IP address - 67.222.148.107 - to be blocked? -- Jeff Pang jeffp...@aol.com ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] [E] Yahoo/AOL Blocking
On Mon, Jun 24, 2024 at 6:43 PM Scott Mutter via mailop wrote: > Anybody from Yahoo/AOL able to assist with what's causing the IP address - > 67.222.148.107 - to be blocked? > I assume you have already reached out to the official Yahoo postmaster support team via the link conveniently provided in the SMTP response? ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] slow submission, was reverse proxy for smtp client
According to Marco Moock via mailop : >Am 24.06.2024 um 12:03:49 Uhr schrieb Alessandro Vesely via mailop: > >> IME, large sending times are often caused by IMAP. Most clients >> operate by first sending the message and then saving it in the Sent >> IMAP folder. Just changing that method to Bcc: halves the time >> required. > >Why should using Bcc: change that the client saves the message in >Draft/Sent via IMAP? The MUA submits one copy of the message with a second RCPT TO that gets delivered to the Sent folder, rather than one copy submitted and one by IMAP append/ For large messages I suppose it's noticable. A sufficiently clever MTA could do the submit and IMAP append at the same time but I doubt that happens very often. -- Regards, John Levine, jo...@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] Yahoo/AOL Blocking
Certainly seems to be - the error is quite clear. You might want to check the usual? Hacked script originating or proxying spam (sometimes not even through your mta), forwarding users onto yahoo and spam that misses your inbound filtering is being forwarded on? It’d save these periodic emails to the list that are all “is provider x here and can they assist with a block” --srs From: mailop on behalf of Scott Mutter via mailop Sent: Tuesday, June 25, 2024 7:08:09 AM To: mailop@mailop.org Subject: [mailop] Yahoo/AOL Blocking Anybody from Yahoo/AOL able to assist with what's causing the IP address - 67.222.148.107 - to be blocked? All messages from 67.222.148.107 will be permanently deferred; Retrying will NOT succeed. See https://postmaster.yahooinc.com/error-codes Messages have DKIM and DMARC IP is not listed in Spamhaus (or any other RBL) Does not seem to be message specific, seems to be IP related. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
[mailop] Yahoo/AOL Blocking
Anybody from Yahoo/AOL able to assist with what's causing the IP address - 67.222.148.107 - to be blocked? All messages from 67.222.148.107 will be permanently deferred; Retrying will NOT succeed. See https://postmaster.yahooinc.com/error-codes Messages have DKIM and DMARC IP is not listed in Spamhaus (or any other RBL) Does not seem to be message specific, seems to be IP related. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
mailop@mailop.org
On 2024-06-24 22:06, Benny Pedersen via mailop wrote: Umut Alemdar via mailop skrev den 2024-06-24 15:40: Since the beginning of June, we have been experiencing delivery issues with AT&T. Despite our attempts to resolve this by contacting support, we have not received any feedback or resolution. Could anyone from AT&T contact me off list, please? please no ads here, turn off html Some MUAs like roundcube I am using, have the feature to turn off HTML view. That might be helpful. :) ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
mailop@mailop.org
Marco Moock via mailop skrev den 2024-06-24 16:46: Am 24.06.2024 um 16:06:32 Uhr schrieb Benny Pedersen via mailop: that sayed We can’t connect to the server at list.mailop.org. Works for me. Please use traceroute to find out if that is a problem at your side. it was my slow unifi router dns issue :) all ok now ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
mailop@mailop.org
Am 24.06.2024 um 16:06:32 Uhr schrieb Benny Pedersen via mailop: > that sayed We can’t connect to the server at list.mailop.org. Works for me. Please use traceroute to find out if that is a problem at your side. -- Gruß Marco ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
mailop@mailop.org
Umut Alemdar via mailop skrev den 2024-06-24 15:40: Since the beginning of June, we have been experiencing delivery issues with AT&T. Despite our attempts to resolve this by contacting support, we have not received any feedback or resolution. Could anyone from AT&T contact me off list, please? please no ads here, turn off html that sayed We can’t connect to the server at list.mailop.org. mailarchive is not working ? try read maillist archive if you have it somewhere, had seen multi mails about AT&T ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
mailop@mailop.org
Since the beginning of June, we have been experiencing delivery issues with AT&T. Despite our attempts to resolve this by contacting support, we have not received any feedback or resolution. Could anyone from AT&T contact me off list, please? Thank you. -- ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] reverse proxy for smtp client
On 2024/06/24 12:16, Marco Moock via mailop wrote: > Am 24.06.2024 um 12:03:49 Uhr schrieb Alessandro Vesely via mailop: > > > IME, large sending times are often caused by IMAP. Most clients > > operate by first sending the message and then saving it in the Sent > > IMAP folder. Just changing that method to Bcc: halves the time > > required. > > Why should using Bcc: change that the client saves the message in > Draft/Sent via IMAP? You only need to send the message to save once not twice (though that can also be avoided by RFC 4468 "BURL" if supported), and SMTP sending is often queued and done in the background in mail clients, whereas IMAP operations are often done immediately. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] reverse proxy for smtp client
On Mon 24/Jun/2024 12:16:32 +0200 Marco Moock via mailop wrote: Am 24.06.2024 um 12:03:49 Uhr schrieb Alessandro Vesely via mailop: IME, large sending times are often caused by IMAP. Most clients operate by first sending the message and then saving it in the Sent IMAP folder. Just changing that method to Bcc: halves the time required. Why should using Bcc: change that the client saves the message in Draft/Sent via IMAP? I meant if the client is able to send to Bcc: /instead/ of saving the message via IMAP. Otherwise it can be done on the server, but you need to synchronize start adding Bcc: with the user telling the client not to save any more (and vice versa). I automatically prepare a -sent (or +sent) alias to the Sent folder of every new user. Some can setup their clients to use it. Draft saving usually is not a worry, as the client does it while-U-type, and thus you don't have to wait for it. HTH Ale -- ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] reverse proxy for smtp client
Am 24.06.2024 um 12:03:49 Uhr schrieb Alessandro Vesely via mailop: > IME, large sending times are often caused by IMAP. Most clients > operate by first sending the message and then saving it in the Sent > IMAP folder. Just changing that method to Bcc: halves the time > required. Why should using Bcc: change that the client saves the message in Draft/Sent via IMAP? -- Gruß Marco Send unsolicited bulk mail to 1719223429mu...@cartoonies.org ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] reverse proxy for smtp client
IME, large sending times are often caused by IMAP. Most clients operate by first sending the message and then saving it in the Sent IMAP folder. Just changing that method to Bcc: halves the time required. Best Ale On Sat 22/Jun/2024 09:45:36 +0200 Jeff Pang wrote: Hello that's b/c the attachment can be sent as 100MB between users. some users said they are hard sending large mail, so I am asking the question. Thanks. Although, I am interested in how much the latency affects the submission and how much that impacts your users. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
