@travisdh1 said in Best practice MFP scanning to email for M365 shop?:

@dashrender said in Best practice MFP scanning to email for M365 shop?:

@travisdh1 said in Best practice MFP scanning to email for M365 shop?:

@pete-s said in Best practice MFP scanning to email for M365 shop?:

@dashrender said in Best practice MFP scanning to email for M365 shop?:

@gjacobse
what brand MFPs are those?

My Canon's do fine with 1.2 to MS.

Do you set up the MFP with credentials from a M365 user?

Yep, need a licensed account, and the lowest priced one doesn't work. I forget what it's called at the moment, but you need a license that includes the local apps.

Even if you go with option 1, not sure why the lowest account with an email account wouldn't work?

Because the lowest cost email account is online only. A local device can't login.

I don't understand - why can't a local device login? Sure it likely can't use modern auth - but normal SMTP logon should work (though I think MS is killing that)

Also, as I mentioned - i'm using a totally free account (a shared account - shared only with me :P) through option 2 in the link I provided.

@pete-s said in Email Send Error Research:

@dashrender said in Email Send Error Research:

@jaredbusch said in Email Send Error Research:

@wrcombs said in Email Send Error Research:

So would it likely to assume that Username and password are incorrect ?

If the computer receives email, then the username and password were likely correct. Outlook's account setup wizard will only ask for the information one time by default.

If this system has never been able to send email, what is likely incorrect is the email server configuration details.

If it once sent email, then mostlikely Outlook had a connection problem once and popped up the credentials box, then the user put in the wrong info.

This seems VERY likely at this point!

Probably entered the Windows password he uses to login.

Probably his personal email password from home.

@dbeato said in 550 5.0.350 Remote server returned an error:

@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:

@dbeato said in 550 5.0.350 Remote server returned an error:

@WLS-ITGuy said in 550 5.0.350 Remote server returned an error:

571 Delivery not authorized, message refused

That messages means a lot of things but yeah Whitelist on their Spam Filter end, Adding your IP to your SPF record, check if there is anything on the body of the message triggering the block on their end (i.e. URL or site link).

It is Office 365 with Exchange - I have created all the records that Microsoft wanted me to.

So, just to be clear, this is 100% not on my end, correct?

It shouldn't be on your end, the message is coming from the recipient's end server.

Right, which means that they received it.

@Emad-R said in Researching Mailing List Email Server Options:

So you dont want the SMTP server part, just the sending to many and if a user opt to be removed that will auto reflect ...

Either way. If we handle the SMTP that's fine. If we don't, that's fine.

@wrx7m said in Exchange 2016 - NDR:

@scottalanmiller said in Exchange 2016 - NDR:

@Natchos said in Exchange 2016 - NDR:

@JasGot Awesome, thanks for the input. I'll look into SPF.

SPF is considered a requirement these days. And DKIM is heavily recommended.

People are starting to come around. I have been using DKIM for a few years for all services sending email outside our org. With O365, SPF and DKIM are part of the setup.

Same with Zoho.

@sully93 said in Simple Password Compromise on MailGun:

@scottalanmiller, which service did you go with after dropping MailGun? We are looking at a relay service and have MailGun on our list. This is a bit concerning that they shut you down like that. We're also looking at Postmark and SendGrid.

We made the call to just move to Zoho and get email hosted. We've been super happy with Zoho.

@flaxking said in Outlook SMTP Non-Compliant Sender Address:

Hmm, I just got the same when testing using telnet

550 5.7.1 Non-Compliant sender address. Code : -4

Oh, good info! Thanks.

@Dashrender said in MailCow in Production Datacenter:

Question for Scott - the customer wanted self hosted email? why?

It's a commercial mail hosting business. Among other things.

@Osvaldo said in Email not showing in Outlook, but Have Been Delivered?:

yes, it is intermedia

If it is on Intermedia, check the Admin quarantine
https://kb.intermedia.net/article/36031
Also use Email tracking
https://kb.intermedia.net/article/38036

@dbeato said in Zimbra 8.8.12 Released:

@scottalanmiller said in Zimbra 8.8.12 Released:

Wow, They release Open Drive and it only works up to NextCloud 13? NextCloud 16 is in RC today. What the heck?

Yeah, that is weird. Behind the times.

My level of impressed keeps slipping.

https://tools.ietf.org/html/rfc5322#section-3.6.2

Originator Fields

The originator fields of a message consist of the from field, the
sender field (when applicable), and optionally the reply-to field.
The from field consists of the field name "From" and a comma-
separated list of one or more mailbox specifications. If the from
field contains more than one mailbox specification in the mailbox-
list, then the sender field, containing the field name "Sender" and a
single mailbox specification, MUST appear in the message. In either
case, an optional reply-to field MAY also be included, which contains
the field name "Reply-To" and a comma-separated list of one or more
addresses.

from = "From:" mailbox-list CRLF

sender = "Sender:" mailbox CRLF

reply-to = "Reply-To:" address-list CRLF

The originator fields indicate the mailbox(es) of the source of the
message. The "From:" field specifies the author(s) of the message,
that is, the mailbox(es) of the person(s) or system(s) responsible
for the writing of the message. The "Sender:" field specifies the
mailbox of the agent responsible for the actual transmission of the
message. For example, if a secretary were to send a message for
another person, the mailbox of the secretary would appear in the
"Sender:" field and the mailbox of the actual author would appear in
the "From:" field. If the originator of the message can be indicated by a single mailbox and the author and transmitter are identical, the "Sender:" field SHOULD NOT be used. Otherwise, both fields SHOULD appear.

Note: The transmitter information is always present. The absence
of the "Sender:" field is sometimes mistakenly taken to mean that
the agent responsible for transmission of the message has not been
specified. This absence merely means that the transmitter is
identical to the author and is therefore not redundantly placed
into the "Sender:" field.

The originator fields also provide the information required when
replying to a message. When the "Reply-To:" field is present, it
indicates the address(es) to which the author of the message suggests
that replies be sent. In the absence of the "Reply-To:" field,
replies SHOULD by default be sent to the mailbox(es) specified in the
"From:" field unless otherwise specified by the person composing the
reply.

In all cases, the "From:" field SHOULD NOT contain any mailbox that
does not belong to the author(s) of the message. See also section
3.6.3 for more information on forming the destination addresses for a
reply.

@dbeato said in Office 365 Moving Emails to Deleted Items:

@dafyre said in Office 365 Moving Emails to Deleted Items:

@dbeato said in Office 365 Moving Emails to Deleted Items:

@dafyre said in Office 365 Moving Emails to Deleted Items:

e got a strange one... I have a user here whose Emails go from whatever folder they are in to the Deleted Items folder after being read... Sometimes. Sometimes it doesn't happen for several minutes, and other times it happens right away.
The user hasn't been phished that we can tell. No bogus rules in Outlook forwarding things to the deleted items. Check both Web and Outlook 2016.
What am I not looking at that could be causing this?

They got hacked though
https://blogs.technet.microsoft.com/office365security/how-to-fix-a-compromised-hacked-microsoft-office-365-account/
https://docs.microsoft.com/en-us/office365/securitycompliance/responding-to-a-compromised-email-account

Sometimes the rule is a dot on the name....

I am assuming it's a hacked account, but we changed the password to a new one. I disconnected all of her sessions from Office 365.

Still happening. I see no rules with a dot in the name... or spaces or foreign characters. I see exactly the number of rules on my CLI as I do in Outlook and OWA.

Can you clear them all ? Take a screenshot of the settings and then remove them and see what changes. The rules run autonomously and is not someone running them.

That's what we've done now. All of the rules are disabled. End-user is turning them back on one at a time now.

@JaredBusch said in Resolved - Postfix on Fedora 29 - Why Can't I Send Mail?:

@wrx7m said in Resolved - Postfix on Fedora 29 - Why Can't I Send Mail?:

It applied to the instance (multiple servers)

FFS no. That is not what anything is.

It applied to the Account. Which contains multiple instances.
Instances that could be servers or desktops or WTF ever.

My apologies. I meant to put account.

@scottalanmiller said in Microsoft BCL or Bulk Complaint Level Values for Email:

Some sources call this an SCL or Spam Complaint Level.

Emails into O365 have both BCL and SCL.

Does the message trace in Exchange tell you anything? I know that when I had on-prem exchange and barracuda, I had weird issues where the attachment size restrictions being smaller/more restrictive on the Exchange server exhibited this behavior. The barracuda delivered, but Exchange rejected due to policy.

@flaxking said in Office 365 SMTP server not advertising StartTLS:

No idea, we don't manage the client's infrastructure

Then it was definitely the UTM, no question.