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
Re: [mailop] reverse proxy for smtp client
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. -- Jeff Pang jeffp...@aol.com ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] reverse proxy for smtp client
Am 22.06.2024 um 15:45:36 Uhr schrieb Jeff Pang: > 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. Is that a latency or bandwidth issue? TCP is affected by high latency and will slow down. To make your solution work, place the MTA at a place where it is good reachable (low latency, high bandwidth) to your clients. Then the MTA will handle the slow connection. -- Gruß Marco ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] reverse proxy for smtp client
Am Sat, 22 Jun 2024 07:01:00 +0800 schrieb Jeff Pang via mailop : > do you know if there is a reverse proxy for submission? > for instance, my server is in the US, while some customers are in EU, > so I consider to deploy a reverse proxy in EU for speeding up their > access. Then you need a real MTA that accepts the message without connecting to the "real" server. After that it sends it to the server. sendmail can handle that with the smarthost option. Other MTAs can do that too. 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
Re: [mailop] reverse proxy for smtp client
According to Viktor Dukhovni via mailop : >In any case, modern MUAs deliver mail in the background, and TCP handles >high delay networks just fine, so most users don't feel any impact from >high RTTs to the submission service. It is your IMAP store and >especially any webmail servers that you might consider >replicating/colocating closer to your users. FWIW, I was at the ICANN meeting in central Africa a week ago, with ping times to my server in New York in the 300-400ms range. I think there was soms strange routing that sent the packets one way via Europe and the other way via South Africa and Brazil. Nonetheless, sending mail through a tunnel back to the US worked just fine. Perhaps it took an extra second or two for the "sending" indicator to turn off but who cares. IMAP access was perceptibly slower but even that remained quite usable since IMAP can pipeline commands and responses. R's, John ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] reverse proxy for smtp client
On Sat, Jun 22, 2024 at 07:01:00AM +0800, Jeff Pang via mailop wrote: > do you know if there is a reverse proxy for submission? None should be necessary. > For instance, my server is in the US, while some customers are in EU, > so I consider to deploy a reverse proxy in EU for speeding up their > access. A reverse proxy could just as easily slow things down. Submission isn't a content service that can be sped up via a CDN, if you don't replicate the authentication and access control service, let the users connect to the source of truth. Authentication/authorisation aside, submission servers can operate independently, with no shared state. In any case, modern MUAs deliver mail in the background, and TCP handles high delay networks just fine, so most users don't feel any impact from high RTTs to the submission service. It is your IMAP store and especially any webmail servers that you might consider replicating/colocating closer to your users. -- Viktor. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
