canonite

Debug Output

Connect to Mail Host
Postie connection: sockets
Postie protocol: pop3-ssl
Postie server: pop.gmail.com
Postie port: 995
pConnection: mailbox: INBOX
Connecting via Socket
Socket: tls://pop.gmail.com:995
Socket error: 0 - 
Socket: POP3
socket read (1) :+OK Gpop ready for requests from 115.42.251.102 e11-v6mb162546760ywl
Socket: attempting a secure connection
socket write: STLS
socket read (1) :-ERR not supported e11-v6mb162546760ywl
socket write: USER **********@gmail.com
socket read (1) :+OK send PASS
socket write: (login) LOGIN/APOP/PASS
socket read (1) :+OK Welcome.
socket write: STAT
socket read (1) :+OK 394 3346843
pop count: +OK 394 3346843
Successful POP3-SSL connection on port 995
# of waiting messages: 394
socket write: QUIT
socket read (1) :+OK Farewell.
Test complete

problem is i have 3 mails in inbox and 400+ in Sent mails .. like you mentioned.. POP doesn’t recognise folders… so i am not too sure where it’s picking up the emails from

pop-ssl… can’t connect on port 110..

it went thru my sent mails, triggering 337 ‘unauthorised post’ notices, and 2 successful ones

this code helps to filter out strings in the post title and deletes the post if it matches the filter string.

function deny_auto_reply($post) {
	$title = $post['post_title'];
	$deleteID = $post['ID'];
	$filter_string = "Automatic reply";
	if (stristr($title,$filter_string) != true) {
		//output content if there is no text "automatic reply" (case insensitive) in title
		DebugEcho("DBPostTitle: No auto reply in title");
		return $post;
	} else {
		//output to debug screen
		DebugEcho("DBPostTitle: Auto reply in title");
		DebugEcho("DBPostDelete: Deleting postID $deleteID");
		wp_delete_post($deleteID);
		return null;
	}
}

the position of the add_filter seems to play a part in the running of the script.. as i have included a post_restrict_category function:

add_filter('postie_post_before', 'post_restrict_category');
add_filter('postie_post_before', 'deny_auto_reply');

the above works fine… the auto reply is caught and deleted (does not appear in trash at all)

add_filter('postie_post_before', 'deny_auto_reply');
add_filter('postie_post_before', 'post_restrict_category');

this one triggers a “PostToDB Error: Content, title, and excerpt are empty.”, with the resulting empty tmptitle post being left in the trash.

• This reply was modified 8 years, 1 month ago by canonite.

thanks Wayne,

tmptitle still seems to be created and trashed even with the return null added..

but overall it does solve my problem of having an author’s away message being posted by mistake..

was looking at postie_post_pre, but it ended up removing the whole subject line and creating a ‘live from the field’ default title..

add_filter('postie_post_pre', 'deny_auto_reply');

function deny_auto_reply($email) {
	$subject = $email['headers']['subject'];
	if (stristr($subject,"automatic reply") == false) {
		DebugEcho("DBecho : No Auto Reply");
		DebugDump($subject);
		DebugEcho("DBechoEnd");
		return $email;
	} else {
		DebugEcho("DBecho: Auto reply found");
		DebugDump($subject);
		DebugEcho("DBechoEnd");
		return null;
	}
}

thanks Wayne,
this seems to have worked…
/wp-content/filterPostie.php

<?php 
function deny_auto_reply($post) {
	$title = $post['post_title'];
	if (stristr($title,"Automatic reply") != true) {
		//output content if there is no text "automatic reply" (case insensitive) in title
		DebugEcho("DBPostTitle: No auto reply in title");
		return $post;
	} else {
		//output to debug screen
		DebugEcho("DBPostTitle: Auto reply in title");
	}
}

add_filter('postie_post_before', 'deny_auto_reply');
?>

Debug output:

post_email: Before postie_post_before filter
DBPostTitle: No auto reply in title

and so on..