Here’s a thought:

 

We saw that some messages got dropped by Exchange and/or Microsoft On-Line Protection for Exchange (EOP/FOPE/Office365) when they contained an identical Message-ID header. A very difficult problem to diagnose. I manage our employee distribution lists and would normally BCC a copy to myself prior to moderation. The released message never came to me because LISTSERV preserved the original Message-ID. I now BCC a different address prior to message moderation.

 

matthew black

california state university, long beach

 

 

-----Original Message-----
From: LISTSERV Site Administrators' Forum [mailto:[log in to unmask]] On Behalf Of Reed Farnsworth
Sent: Monday, November 17, 2014 10:21 AM
To: [log in to unmask]
Subject: Re: User can't post to list

 

No error messages.

 

We're wondering if sending to multiple lists and other non-list email addresses may be why we aren't getting error messages. It may be that it's getting through to the non-LISTSERV email addresses, so no error message is thrown.

 

Reed

 

---

REED J. FARNSWORTH | Knowledge Base Analyst | SirsiDynix

P: 800.288.8020 ext. 5483 | F: 801.223.5202 | [log in to unmask]

www.sirsidynix.com 

Join the conversation: Like us on Facebook! Follow us on Twitter!

 

 

 

-----Original Message-----

From: LISTSERV Site Administrators' Forum [mailto:[log in to unmask]] On Behalf Of F J Kelley

Sent: Saturday, November 15, 2014 9:51 AM

To: [log in to unmask]

Subject: Re: User can't post to list

 

Is there any error message at all? (ask your user to check the Junkmail folder; Outlook might be filtering).

 

If there is not, see if your Exchange mail admins can trace the message to your listserver.

 

While everything sounds like settings, the missing error message might be the key. 

best,

 

________________________________________

From: LISTSERV Site Administrators' Forum <[log in to unmask]> on behalf of Ben Parker <[log in to unmask]>

Sent: Saturday, November 15, 2014 11:21 AM

To: [log in to unmask]

Subject: Re: User can't post to list

 

On Fri, 14 Nov 2014 20:38:14 +0000, Reed Farnsworth <[log in to unmask]> wrote:

 

>My image didn't come through on the previous email, so I'm attaching it as a pdf.

 

LSTSRV-L does not allow attachments.  You can always copy/paste the text results of the command:  Query listname FOR [log in to unmask]  into your email to show us the current settings of the user in question.

 

As to the user, the first thing I would try is to inspect their subscription settings.  If they are not subscribed, the answer is obvious.  If they are subscribed, are they set to NOPOST or REVIEW?  If none of those are obvious blocks, I would next try the command:  SERVE [log in to unmask]

 

If they have been served off the behavior would be as you describe.  Anyone (except the user in question) may issue this command.  If they are served off, this will restore service.  At worst, you'll get a mild error saying they aren't served off.

 

After this point, you need to examine the LISTSERV log files.  Since that is a pain, I try other things first.  Check list-level and site-level CONTENT_FILTER.  Set her to REVIEW (moderated) status and have her post. If her msg doesn't go into the moderation queue, then it may not be getting to LISTSERV at all.  External spam filter?

 

Can she post via the WWW interface?  (bypassing email)

 

############################

 

To unsubscribe from the LSTSRV-L list:

write to: mailto:[log in to unmask]

or click the following link:

http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

 

############################

 

To unsubscribe from the LSTSRV-L list:

write to: mailto:[log in to unmask]

or click the following link:

http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1

 

############################

 

To unsubscribe from the LSTSRV-L list:

write to: mailto:[log in to unmask]

or click the following link:

http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1



To unsubscribe from the LSTSRV-L list, click the following link:
http://peach.ease.lsoft.com/scripts/wa-PEACH.exe?SUBED1=LSTSRV-L&A=1