Opened 2 years ago

Closed 2 years ago

#2721 closed task (fixed)

LDAP mails get greylisted

Reported by: strk Owned by: sac@…
Priority: normal Milestone: Unplanned
Component: SysAdmin Keywords:


Change History (16)

comment:1 by robe, 2 years ago

is it just the ldap mailings being greylisted. It's unclear to me from that page if our mail server is doing the greylisting of is doing it

comment:2 by strk, 2 years ago

I believe it's the *recipient* mail server greylisting mail sent from the ldap tools (possibly because they are not using authenticated SMTP)

comment:3 by robe, 2 years ago

strk why don't we seem to have this issue with the other servers or are we having the same issue with mail servers. I'm hosted on gmail and seem to have been getting emails fine.

comment:4 by strk, 2 years ago

Jayenashar just reported on IRC that he's getting a similar report from with a reference to this link:

comment:5 by robe, 2 years ago

I added a DMARC record with policy just monitor and will send to osgeo sysadmins. DKIM I think we need to make changes to mail server config too to put that in place so haven't done that yet.

comment:6 by robe, 2 years ago

okay the dmarc thing is getting a bit noisy and I'm not clear what the reports are telling me. I'm planning to switch the email to go to a different mail address so it doesn't annoy sysadmins. Right now I have it set to go to sysadmins+dmarc but that means all osgeo sysadmins are getting it. I'll set up a separate alias for it and send it to that so as to not annoy everyone.

At a glance all the dmarc notices are being generated from and claiming we are sending on behalf, but doesn't tell me which emails triggered. It just tells me the domains and many appear to be gmail and microsoft hosted.

comment:7 by robe, 2 years ago

I've added a new mail alias dmarc and have only me on that list. Others who want to get those notices can add themselves.

comment:8 by robe, 2 years ago

on a side note I think we are running postgrey to minimize on spam -- per

We should review those settings as part of this ticket.

comment:9 by robe, 2 years ago

Not sure it matters but I noticed that,, were in postfix config relay hosts lists. But not So I added it and restarted postfix on osgeo6. Did a quick test to mantra to make sure I didn't break anything.

comment:10 by jayenashar, 2 years ago

is there any update on this? many times i send the mantra to people but they don't receive it because they use gmail.

comment:11 by strk, 2 years ago

jayenashar how does your sending email to mantra seekers involve the OSGeo SMTP ? Are you sending mails with a Sender in the domain ?

comment:12 by robe, 2 years ago

No update yet sorry. Hoping to get back to this this weekend. Been tied up with setting up new server and dealing with download performance.

comment:13 by robe, 2 years ago

To strk's point. I understand that when you send to mantra@… that may be blocked since it goes thru osgeo to send to people. But it's unclear to me why when you are cc'ing or sending directly to a gmail address why that should be blocked.

FWIW I think I get all your emails when you send a mantra, and my domains are on gmail.

comment:14 by strk, 2 years ago

I understand that when you send to mantra@… that may be blocked since it goes thru osgeo to send to people.

But in his case he's sending directly to the mantra seeker, so they should get the mail UNLESS Google thinks the SMTP server he uses is not a legit one to send mail on his behalf. Is that correct ?

comment:15 by jayenashar, 2 years ago

ok maybe you are right. i'm just confused because i send the mantra, then another admin asks for more info, then the requester replies to the other admin, seemingly as if they didn't get my message. this is happening multiple times that's why i thought the requester isn't getting my email, but you are right. there is no reason they shouldn't get my email.

comment:16 by robe, 2 years ago

Resolution: fixed
Status: newclosed

closing this out as we've made a number of changes in osgeo6 mail and upgrading the server that should have addressed these issues.

Note: See TracTickets for help on using tickets.