News:

Bored?  Looking to kill some time?  Want to chat with other SMF users?  Join us in IRC chat or Discord

Main Menu

SMF Mailing List Mod

Started by pftq, June 24, 2011, 04:01:47 PM

Previous topic - Next topic

pftq

Made a fix so that email threads started by guests send notifications to the guest as well (think ticketing support system).

pasht

Hi ptfq,
Thank you for working on this mod, it is a fantastic piece of work.  I am trying to create a new post with an attachment by sending an email with an attachment; the post is created and populated with the subject and body, but the attachment does not get posted to the forum.  I know that the README states that attachments are not allowed for security reasons, but throughout this thread it is mentioned that attachments ARE allowed and are functioning.

Is posting new topics with attachments allowed?
Thank you!

pftq

Yes they are implemented. You have to enable it in Admin > Features > MailingList.

pasht

Hi,
When a new post is made via SMF with no body but an attachment, the attachment is placed into the body in what appears to be MIME format, and is not attached as an attachment.  Ideas? Thanks :)

pasht

I was using hMailServer on Windows initially, and getting this problem.  I made a new Debian server from scratch so I could use postfix, and ended up with the exact same output to the SMF forum. 
Here's the test.txt output:

DEBUGGER -> Initiating...2014-11-24, 06:53:06

DEBUGGER -> Loading SSI...

DEBUGGER -> Beginning email parse...
DEBUGGER -> Reading standard input (email piping)...

Header[from] = "Pasht" <[email protected]>
Header[to] = "Test Bed" <[email protected]>
Header[message-id] = <MAL.3c7b49ff-5b31-4f0c-9f68-bc9786c66bff@lucy>
Header[subject] = Message from Pasht (1430)
Header[content-type] = audio/wav; name=VoiceMessage.wav
Header[content-transfer-encoding] = Base64

Sending to Board: 2, with prefix ``
Non-Default Address Used.  Checking "Test Bed" <[email protected]>
Comparing `[email protected]` to `[email protected]`
Not `[email protected]`.
Comparing `[email protected]` to `[email protected]`
Not `[email protected]`.
Isolated Email From = [email protected], Name = &quot;Pasht&quot;
DEBUGGER -> Non-Member: &quot;Pasht&quot;

DEBUGGER -> Message Boundary: 
DEBUGGER -> Attachments Boundary:

DEBUGGER -> Message Body:

UklGRoJQAABXQVZFZm10IBIAAAAHAAEAQB8AAEAfAAABAAgAAABmYWN0BAAAAFBQAABkYXRhUFAA
AP9+/////f////79/v///v3//v7//v7+/f///v39/v///f3+/////f3////9/f7//n3+/P/+///9
/X58fP/+/nx8f/z8fXh6/Pl8cm/37Xpvbvbs/3Rt+u/8e2/99fh/cP77+v9yfv3+/3Z8//9/en19
/395/358/nz//nx9//3/f3z//f//fP7/ff59ffx9fH57/n17/Ht9+nx+/Xz+/Xz+/Hn8+nT2/XHu
eHjtb/7xbvL7cfN4e/N3fPh6/f16ff3/fv5+fvr/evz9fvl9f/p9//1+//5///5///9//398fv98
//58fv/9fH76eX78d/z9d/h+fPl9f/p8ff58/P96/v99/n18/v//fH7/fP17fPx6//98/f9+f35/
fv7///9+/n9+/nz9/nr7f3r7fnv6fnr///9+/318+nt+/Xv8e/78fPv9f/z+/f7//P/+/P//fX76
e//7e//8fP79ff3+f/1///7//n79f3z+f3/9f3/8fX39fHz9fnz9/3r+fnz/fX99fX9+////fv7+
fv39/f1+//5+//59//18//58/f99/H9+/n7+fv/9ff/9ff9+fH5+f37/fH39en37en78eX/9e/1/
*SNIP*
fX5+fn5+fn59fn59fn59fn5+fn5+fn5+fn5+fX5+fn5+fX1+fn59fn59fn59fn5+fX7/fn5+fn5+
fn5+fn59fn59/359fn5+fn5+fX5+fn1+fn1+fn5+fn5+fn5+fX5+fn5+fX1+fn5+fn5+fn59fn59
fn59fn59fX5+fX5+fn5+/35+/35+fn5+fn59fv9+fn5+fX7/fn5+fn5+fn5+fn59fn59fn5+fn5+
fX5+fn7/fn5+fn5+fn18fn59fv9+fn5+fn5+fn5+fn1+fn5+fn5+fn5+fn59fH5+fX5+fn1+fn5+
/35+fn5+fn5+fn59fX5+fn5+fn5+fXx+fn5+fn5+fv9+fn5+fX7/fX5+fX5+fn5+fn1+fn1+fn59
fv9+fn5+fn7/fn1+fn1+fn1+fn59fv9+fn5+fX5+fX5+fn5+fX1+fn5+fn59fv9+fn59fn5+fX7/
fn5+fn1+fn59fn19fn59fn59fX5+fX5+fn5+fn5+/35+fn59fn59//9+fn5+fX7/fn7/fn19fn19
fn59fn5+fn59fn59fX5+fn5+fn5+fn1+/35+fn5+fv9+fn59fX5+fX5+fn1+fn1+fn5+fn5+fn5+
fn5+fn7/fn5+fn5+fn5+fn59fn5+fn59fX5+fX5+fn5+fn5+fn1+/35+fn18fn59fn5+fn5+fX5+
fn5+fn5+fn5+fn59fn59fn5+fn5+fn5+fn1+fn1+////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////8=




DEBUGGER -> CONTENT-TYPE NOT MULTIPART, USING HEADER: audio/wav; name=VoiceMessage.wav
CONTENT-TYPE PLAINTEXT and CHARSET



DEBUGGER -> Checking that line break exists between headers and content.



DEBUGGER -> HEADERS PULLED OUT FOR CURRENT MESSAGE FORMAT:



DEBUGGER -> SELECTING EMAIL FORMAT: PLAINTEXT


UklGRoJQAABXQVZFZm10IBIAAAAHAAEAQB8AAEAfAAABAAgAAABmYWN0BAAAAFBQAABkYXRhUFAA
AP9+/////f////79/v///v3//v7//v7+/f///v39/v///f3+/////f3////9/f7//n3+/P/+///9
/X58fP/+/nx8f/z8fXh6/Pl8cm/37Xpvbvbs/3Rt+u/8e2/99fh/cP77+v9yfv3+/3Z8//9/en19
/395/358/nz//nx9//3/f3z//f//fP7/ff59ffx9fH57/n17/Ht9+nx+/Xz+/Xz+/Hn8+nT2/XHu
*SNIP*
fn5+fn1+fn59fn19fn59fn59fX5+fX5+fn5+fn5+/35+fn59fn59//9+fn5+fX7/fn7/fn19fn19
fn59fn5+fn59fn59fX5+fn5+fn5+fn1+/35+fn5+fv9+fn59fX5+fX5+fn1+fn1+fn5+fn5+fn5+
fn5+fn7/fn5+fn5+fn5+fn59fn5+fn59fX5+fX5+fn5+fn5+fn1+/35+fn18fn59fn5+fn5+fX5+
fn5+fn5+fn5+fn59fn59fn5+fn5+fn5+fn1+fn1+////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////8=




DEBUGGER -> ENCODING DETECTED IN HEADER: Base64



DEBUGGER -> DECODING EMAIL: Base64


UklGRoJQAABXQVZFZm10IBIAAAAHAAEAQB8AAEAfAAABAAgAAABmYWN0BAAAAFBQAABkYXRhUFAA
AP9+/////f////79/v///v3//v7//v7+/f///v39/v///f3+/////f3////9/f7//n3+/P/+///9
/X58fP/+/nx8f/z8fXh6/Pl8cm/37Xpvbvbs/3Rt+u/8e2/99fh/cP77+v9yfv3+/3Z8//9/en19
/395/358/nz//nx9//3/f3z//f//fP7/ff59ffx9fH57/n17/Ht9+nx+/Xz+/Xz+/Hn8+nT2/XHu
*SNIP*
fn5+fn1+fn59fn19fn59fn59fX5+fX5+fn5+fn5+/35+fn59fn59//9+fn5+fX7/fn7/fn19fn19
fn59fn5+fn59fn59fX5+fn5+fn5+fn1+/35+fn5+fv9+fn59fX5+fX5+fn1+fn1+fn5+fn5+fn5+
fn5+fn7/fn5+fn5+fn5+fn59fn5+fn59fX5+fX5+fn5+fn5+fn1+/35+fn18fn59fn5+fn5+fX5+
fn5+fn5+fn5+fn59fn59fn5+fn5+fn5+fn1+fn1+////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////8=




DEBUGGER -> Converted to post: PLAINTEXT

UklGRoJQAABXQVZFZm10IBIAAAAHAAEAQB8AAEAfAAABAAgAAABmYWN0BAAAAFBQAABkYXRhUFAA
AP9+/////f////79/v///v3//v7//v7+/f///v39/v///f3+/////f3////9/f7//n3+/P/+///9
/X58fP/+/nx8f/z8fXh6/Pl8cm/37Xpvbvbs/3Rt+u/8e2/99fh/cP77+v9yfv3+/3Z8//9/en19
/395/358/nz//nx9//3/f3z//f//fP7/ff59ffx9fH57/n17/Ht9+nx+/Xz+/Xz+/Hn8+nT2/XHu
eHjtb/7xbvL7cfN4e/N3fPh6/f16ff3/fv5+fvr/evz9fvl9f/p9//1+//5///5///9//398fv98
//58fv/9fH76eX78d/z9d/h+fPl9f/p8ff58/P96/v99/n18/v//fH7/fP17fPx6//98/f9+f35/
*SNIP*
fn59fn59fX5+fX5+fn5+/35+/35+fn5+fn59fv9+fn5+fX7/fn5+fn5+fn5+fn59fn59fn5+fn5+
fX5+fn7/fn5+fn5+fn18fn59fv9+fn5+fn5+fn5+fn1+fn5+fn5+fn5+fn59fH5+fX5+fn1+fn5+
/35+fn5+fn5+fn59fX5+fn5+fn5+fXx+fn5+fn5+fv9+fn5+fX7/fX5+fX5+fn5+fn1+fn1+fn59
fv9+fn5+fn7/fn1+fn1+fn1+fn59fv9+fn5+fX5+fX5+fn5+fX1+fn5+fn59fv9+fn59fn5+fX7/
fn5+fn1+fn59fn19fn59fn59fX5+fX5+fn5+fn5+/35+fn59fn59//9+fn5+fX7/fn7/fn19fn19
fn59fn5+fn59fn59fX5+fn5+fn5+fn1+/35+fn5+fv9+fn59fX5+fX5+fn1+fn1+fn5+fn5+fn5+
fn5+fn7/fn5+fn5+fn5+fn59fn5+fn59fX5+fX5+fn5+fn5+fn1+/35+fn18fn59fn5+fn5+fX5+
fn5+fn5+fn5+fn59fn59fn5+fn5+fn5+fn1+fn1+////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
//////////////////////////////////////////////////////8=

DEBUGGER -> Passed user permissions check. Posting... Message from Pasht (1430)

DEBUGGER -> Posted.  Checking format...

DEBUGGER -> POST IS OK!


I also tried having the message sent to another email address where a client was set up with a rule to forward the email to the SMF MLM piped address in the hopes that the client would re-assemble the message in such a way that the body and attachment were more distinct.  That resulted in the post being "This is a multi-part message in MIME format" with no attachment.  I'm guessing I don't have postfix set up quite right in that instance.

Miker1029

#85
Hey all,

   It's telling me that this hasn't been posted in for 120 days (or more), But to be honest I can't find the right place to post this....

OK, SO, HERE's the Question, I've Installed this MOD, and It's working, I Have Piping setup through my server, But I want the reply to the E-Mails to go to "[email protected]", am I understanding correctly the I need to Change my "[email protected]" e-mail in Server Settings??

If Not, It's not posting to the Froum from E-Mail reply..

If So, Is there a way around this (other then using that 3rd party link) as I use that E-mail for ALL my Forum Notifs....

Any help appreciated...

Mike

EDIT:

Ya this doesn't make sense how can I change my Server Setting e-mail Address to the Piped E-Mail Address?!?!?  That means ALL my Mail is going to get piped to the email

This is what I get when I try to reply via [email protected]

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  pipe to |/home/mike***/public_html/emailpost.php

pftq

Your server email needs to be what you want people to reply to.  This is the same email you set up piping for.  If you get an error when replying, check that your host lets you run scripts like this and what settings you might need.  For example, my host requires I reference the PHP install at the top of the script with the line "#!/usr/bin/php -q"

You can check here for a test board on how it should work (it's pretty much like Googlegroups):
http://www.pftq.com/forums/index.php?board=59.0

Miker1029

Ok I kind of got it working, Doing some trouble shooting now...

But to be Clear (And I've been getting double posts and thinking this may be why)

my Server Settings E-Mail where I get New User Sign ups and All that can stay the same "[email protected]"

And I can set up the PIPE on Cpanel (which is done) to "[email protected]"

And yes my Server (surprisingly the more stuff I do) lets me do all this...

I've just switched my Server E-mail Back to "[email protected]" and am going back in to test...

And Ya I went there and was gonna post some questions (after I did some searching) on What the Settings In the MOD DO...

Will CHeck back in a let ya know...

Thanks for the reply

Mike

Miker1029

ok here seems to be the issue at the moment, I have my E-mail setup through my hosts SMTP Server, as I said "[email protected]" in server settings, for Forum Admin Stuff, Logically....

SO, Basically my problem is, (for testing the mod and trying to get it to work) I had changed Server Email to [email protected], and the PIPE set to the same address, Which Worked (Think it was double posting, ill get to that when this is/can-be fixed)..

NOW I changed Server Mail BACK to [email protected], for my Admin Mails, and left the PIPE the same, That didn't work,  So I added THE pipe for the mod to [email protected], and sent myself a test email through the forum, it worked, but the pipe bounced (of course)....

What I'd like to try and Accomplish, is have the PIPE set to something like "[email protected]", and have the Server Email for Admin Stuff to "[email protected]"

Is there a way to do this, and if so can you explain it?!?!?

If Not, How do you suggest I set it up, so I can have my Admin Emails, and forum post/reply e-mails seperate?!?!?

I noticed on your Test Board that you have "Send emails to [email protected]" as your E-mail PIPE, and I'm sure you don't have your Admin Server Setting email going there......

So what Am I missing here?????   i know it's gotta be something....

Thanks,

Mike

Miker1029

#89
Hey,

Just an Update on the Above issue, The Problem was the hash bang, My Host will automatically FIX it if it's wrong and in doing so the -q is not sent to the PHP, When the Hashbang was fixed in the script everything worked fine...

Mike

Jeff_B

Hey folks - sorry for dredging this thread up but I'm having an issue with the mod.

I just installed a fresh copy of SMF 2.0.11 and installed this mod.

I followed the direction and I keep getting the following message when I try to REPLY to an existing thread. I can post new threads without an error.

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 6
File: /home/rchel320/public_html/wpgfpvclub/Sources/Subs-Post.php
Line: 1598

I've restored that file several times now and redid the changes carefully and keep coming up with the same issue.

The only other things I've installed were a few themes but I've reverted to the default curve theme and still getting the same message.

Here's some other information that may help:

Apache Version   2.2.31
PHP Version   5.5.29
MySQL Version   5.5.47-cll

Any ideas?


Jeff_B

Disregard. I have fixed the issue ... apparently you have to click every single option and save for the mod, the unclick the ones you don't want and save again.

SMiFFER

I have downloaded the mod and installed it.

But is there really no documentation or step-by-step-instructions on how to configure this nice tool?
Quote of the day: A troll is an obstinate bloke who only hungers for your attention. If you feed him, he will puke all over you!

viking9

1. Will this mod work with SMF v2.018?

2. The latest version of the "SMF Mailing List Mod" is supposedly v2.012. However, when I download it, it is v2.03.

Kindred

1- probably. But you should upgrade to 2.0.19 first

2-  2.03 was updated in August of 2020 and is the last update. Where did you get the 2.012 number?
Слaва
Украинi

Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

"Loki is not evil, although he is certainly not a force for good. Loki is... complicated."

viking9

Quote from: Kindred on February 13, 2024, 08:47:28 PM1- probably. But you should upgrade to 2.0.19 first

2-  2.03 was updated in August of 2020 and is the last update. Where did you get the 2.012 number?
1. Why upgrade to 2.0.19?

2. Here https://custom.simplemachines.org/index.php?mod=2843 (it shows latest is 2.012)

Kindred

1- because  2.0.18 does not support modern php versions and there are security patches.
Honestly,  you SHOULD br planning to upgrade to 2.1.4, since 2.0.x is almost eol.

2- ah... I'd say the author updated the version incorrectly there 2.03 is the latest mentioned
Слaва
Украинi

Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

"Loki is not evil, although he is certainly not a force for good. Loki is... complicated."

Advertisement: