Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

RjOllos
Hello,

I have attempted to configure my issue tracking site to BCC the Nabble mailing list each time a notification is sent.  This way, I can aggregate the notifications and have them sent to all users once each day.

I'd like to include the ml-node*@n3.nabble.com in the BCC list, however my testing shows that the message is not accepted when the address is in the BCC list.  The message is accepted when the address is in the CC list.

Is it possible to configure the mailing list to accept messages to ml-node*@n3.nabble.com when the address is in the BCC list?

Thank you.
- Ryan
Reply | Threaded
Open this post in threaded view
|

Re: Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

Hugo <Nabble>
Hi Ryan, the problem is that Nabble can't find the "ml-node*@n3.nabble.com" address in the email that arrives in our inbox. This address is important because it has the ID of the forum where the message must be archived. You can make a test and see that the Bcc address is not listed in the email headers and this is an issue. All subscription emails go to the same inbox, so we need this information to archive them correctly.
Reply | Threaded
Open this post in threaded view
|

Re: Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

RjOllos
Thank you for the follow-up.  It sounds like my only option is to use the Nabble email address in the CC field.  I would rather hide the Nabble email address in the outgoing email from my issue tracking system, but its not that big of a deal.
Reply | Threaded
Open this post in threaded view
|

Re: Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

Hugo <Nabble>
Another option is to create a standard mailing list (e.g., google groups, yahoo groups, etc.) and archive this mailing list on Nabble. Then you can send the email to the mailing list using the Bcc field. It would be better to configure this mailing list so that only your system can post to it. You can also set the Nabble archive to read-only.
Reply | Threaded
Open this post in threaded view
|

Re: Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

RjOllos
It seems I am still having an issue.  The message headers looks like:

From: PSI Trac Admin [tracadmin@mydomain.com]
Sent: Tuesday, 01 December, 2009 22:47
Cc: ml-node+*@n3.nabble.com; Ryan J Ollos; Bhavani

I double checked that I have the correct ml-node+*@n3.nabble.com address for tracadmin@mydomain.com.

Using my personal account ryano@mydomain.com and CC'ing the associated ml-node+*@n3.nabble.com address, I have been able to post to the forum via email.

However, the messages from my issue tracking system that CC the ml-node+*@n3.nabble.com email address associated with tracadmin@mydomain.com do not end up on the Nabble archive.  If I also CC myself (as I did for the message header listed above), I receive the messages in my personal inbox, but they don't end up on the Nabble archive.

Any suggestions?

Thank you for your time.
Reply | Threaded
Open this post in threaded view
|

Re: Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

Hugo <Nabble>
I found your message in our logs. It contains these headers:
Precedence: bulk
Auto-Submitted: auto-generated
Is it possible to remove these two lines? They basically mean that this message is auto generated and Nabble doesn't archive them because they are useless in 99.9% of the cases (like automated vacation/out of office replies). Please let me know if you have control over these headers.
Reply | Threaded
Open this post in threaded view
|

Re: Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

PSI Trac Admin
Hi Hugo,

Thank you for the reply.  I'm checking with my hosting provider to see if we can change the header in sent mail.  I will let you know as soon as I hear back.
Reply | Threaded
Open this post in threaded view
|

Re: Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

RjOllos
In reply to this post by Hugo <Nabble>
Hugo <Nabble> wrote
I found your message in our logs. It contains these headers:
Precedence: bulk
Auto-Submitted: auto-generated
Is it possible to remove these two lines? They basically mean that this message is auto generated and Nabble doesn't archive them because they are useless in 99.9% of the cases (like automated vacation/out of office replies). Please let me know if you have control over these headers.
I'm still waiting to hear from my hosting provider whether this change can be made.  If not, do we have any other alternatives?  A nice, but probably development intensive option, would be to have a safe-senders list for a mail archive forum.
Reply | Threaded
Open this post in threaded view
|

Re: Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

Hugo <Nabble>
Another option is described here:

http://n2.nabble.com/Messages-not-accepted-when-ml-node-n3-nabble-com-is-in-the-BCC-list-tp4096092p4096882.html

This should be simple to do. After creating the mailing list elsewhere (e.g., googlegroups, etc.), you should go to our homepage and click on "Archive Your Mailing List".
Reply | Threaded
Open this post in threaded view
|

Re: Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

RjOllos
I started receiving notification emails from my forum today without making any changes myself. Note sure if it was a change on the Nabble side or the server sending the messages.
Reply | Threaded
Open this post in threaded view
|

Re: Messages not accepted when ml-node*@n3.nabble.com is in the BCC list

Hugo <Nabble>
Your messages should work now if you keep them in the CC field. We have changed our code and now it should accept them.