Sending large email from office365

%3CLINGO-SUB%20id%3D%22lingo-sub-663736%22%20slang%3D%22en-US%22%3ESending%20large%20email%20from%20office365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-663736%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20unable%20to%20migrate%20one%20mailbox%20to%20office365%20which%20is%20used%20for%20sending%20bulk%20email%20during%20add%20campaign%20time%20for%20clients.%20Office365%20a%20mailbox%20from%20sending%20more%20than%202000%20email%20in%20an%20hour.%20However%2C%20I%20am%20thinking%20about%20creating%20five%20numbered%20suffix%20mailboxes%20beginning%20with%20same%20mailbox%20and%20distributing%20campaign%20emails%20by%20sending%201800%20per%20mailbox.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20current%20on%20prem%20campaign%20mailbox%20has%20following%20characteristics%20-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EEvery%20campaign%20email%20that%20goes%20out%20has%20a%20duplicate%20that%20also%20goes%20to%20roi%40lab.com%20(for%20liability).%3C%2FP%3E%3CP%3EIt%20varies%2C%20but%20generally%20about%208%2C000%20emails%20per%20hour%20get%20sent%20to%20roi%40lab.com%20during%20a%20campaign%20run.%20Last%20run%20on%20moth%2Fyear%20was%20about%2047%2C000%20emails%20(ran%20from%205%3A27pm%20to%201%3A05am).%3C%2FP%3E%3CP%3EWe're%20using%20Postfix%20on%20linux%20server%20to%20route%20mail%20from%20SQL%20server%20to%20skpost%20(for%20recipient%20send%20out)%20and%20locally%20to%20exchange%20(the%20duplicate%20explained%20earlier).%20It's%20possible%20to%20throttle%20the%20send%20rate%20%2C%20but%20we%20also%20need%20the%20send%20out%20to%20finish%20before%20business%20hours%20the%20next%20day.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-663736%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665188%22%20slang%3D%22en-US%22%3ERe%3A%20Sending%20large%20email%20from%20office365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665188%22%20slang%3D%22en-US%22%3E%3CP%3ESending%20bulk%20messages%20via%20O365%20is%20a%20bad%20idea%20and%20can%20get%20the%20mailbox%20or%20sending%20IP%20blocked.%20Use%20a%20third-party%20service%20that%20specializes%20in%20bulk%20sending%20instead%2C%20every%20major%20player%20in%20the%20field%20is%20recognized%20by%20O365%20and%20should%20have%20no%20trouble%20delivering%20(legitimate)%20bulk%20messages.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

I am unable to migrate one mailbox to office365 which is used for sending bulk email during add campaign time for clients. Office365 a mailbox from sending more than 2000 email in an hour. However, I am thinking about creating five numbered suffix mailboxes beginning with same mailbox and distributing campaign emails by sending 1800 per mailbox. 

 

My current on prem campaign mailbox has following characteristics -

 


Every campaign email that goes out has a duplicate that also goes to roi@lab.com (for liability).

It varies, but generally about 8,000 emails per hour get sent to roi@lab.com during a campaign run. Last run on moth/year was about 47,000 emails (ran from 5:27pm to 1:05am).

We're using Postfix on linux server to route mail from SQL server to skpost (for recipient send out) and locally to exchange (the duplicate explained earlier). It's possible to throttle the send rate , but we also need the send out to finish before business hours the next day.

1 Reply
Highlighted

Sending bulk messages via O365 is a bad idea and can get the mailbox or sending IP blocked. Use a third-party service that specializes in bulk sending instead, every major player in the field is recognized by O365 and should have no trouble delivering (legitimate) bulk messages.