Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use custom marker to denote end of email #23

Open
r-a-y opened this issue Nov 8, 2012 · 0 comments
Open

Use custom marker to denote end of email #23

r-a-y opened this issue Nov 8, 2012 · 0 comments
Labels
Enhancement

Comments

@r-a-y
Copy link
Owner

r-a-y commented Nov 8, 2012

Jetpack recently added this feature to their Post By Email module; RBE should implement something like this as well, but be a bit more liberal.

From Jetpack's documentation:

If your email system attaches a signature that does not match any of these patterns then you can manually tell Post by Email to stop including text by adding the special [end] shortcode on its own line with a blank line above it.
@r-a-y r-a-y mentioned this issue Nov 26, 2012
Open
@yorkiedale yorkiedale mentioned this issue Dec 24, 2012
Closed
r-a-y added a commit that referenced this issue Apr 20, 2017
@r-a-y
Fix inaccurate PHPMailer 'Date' timestamp when auto-connect is on and…
bc03b3e 
… when using IMAP mode.

BuddyPress uses a static version of PHPMailer:
https://buddypress.trac.wordpress.org/browser/tags/2.8.2/src/bp-core/classes/class-bp-phpmailer.php?marks=28,39,47#L27

When RBE is using IMAP mode with auto-connect turned on, BP's PHPMailer
would never change the 'Date' header from when it was first initialized.

This meant that subsequent emails would all use the older timestamp, which
is wrong!

This commit remedies this by always setting the 'Date' field when IMAP mode
and auto-connect is on.

See #23.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@r-a-y