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 at
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 usi
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 th
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 th
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.
--
_
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?
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
m
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 dn
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.
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 Sp
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 t
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:
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
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
14 matches
Mail list logo
