sending the same msg back to the person who sent it

PaulW

posted Oct 16 '10 at 10:55 am

[quote user="gears"]i d abit of codeing, if its not to hard i could write one up, know where i might get a thing todo this with?[/quote]

If you are going to write a daemon to sort out every problem with mail clients that connect to your mail server, I think you've started an impossible task. Far better to correct this mis-configured client to do what is wanted.

<P>[quote user="gears"]i d abit of codeing, if its not to hard i could write one up, know where i might get a thing todo this with?[/quote]</P> <P>If you are going to write a daemon to sort out every problem with mail clients that connect to your mail server, I think you've started an impossible task.&nbsp; Far better to correct this mis-configured client to do what is wanted.</P>

gears

posted Oct 14 '10 at 3:02 pm

Ok so when someone sends a msg to like me, the server sends it to me and back to them-selfs, is there a config or something to stop this? or a way to make it so they cant send msgs to them-selfs? because this is really annoying

Ok so when someone sends a msg to like me, the server sends it to me and back to&nbsp;them-selfs, is there a config or&nbsp;something&nbsp;to stop this? or a way to make it so they cant send msgs to&nbsp;them-selfs? because this is really&nbsp;annoying&nbsp;

Rolf Lindby

posted Oct 14 '10 at 7:38 pm

Start by figuring out why a copy of the message is sent back to the original sender (like filtering rule, forwarding, autoreply, policy, daemon, cc or bcc to local user). Check log files and complete message headers for clues.

/Rolf

<p>Start by figuring out why a copy of the message is sent back to the original sender (like filtering rule, forwarding, autoreply, policy, daemon, cc or bcc to local user). Check log files and complete message headers for clues.</p><p>/Rolf </p>

gears

posted Oct 14 '10 at 9:43 pm

I tried, it just seems to come with both addresses marked for sending which is really weird, I even used different software hoping it was that but the server still sent a msg to the same person sending it

I tried, it just seems to come with both addresses marked for sending which is really weird, I even used&nbsp;different&nbsp;software&nbsp;hoping&nbsp;it was that but the server still sent a msg to the same person sending it

Rolf Lindby

posted Oct 14 '10 at 10:09 pm

Turn on session logging in MercuryS to see exactly what the client sends to Mercury. In this case it's the RCPT TO lines that you should keep an eye on. Remember to switch session logging off once you have logs for one message.

Next have a look at the core log file and find the entries for this message there.

If it still isn't obvious what happens you can post log excerpts here, and maybe we can figure it out.

/Rolf

<p>Turn on session logging in MercuryS to see exactly what the client sends to Mercury. In this case it's the RCPT TO lines that you should keep an eye on. Remember to switch session logging off once you have logs for one message.</p><p>Next have a look at the core log file and find the entries for this message there.</p><p>If it still isn't obvious what happens you can post log excerpts here, and maybe we can figure it out.</p><p>/Rolf&nbsp;</p>

gears

posted Oct 14 '10 at 10:25 pm

Connection from 192.168.1.57, Thu Oct 14 04:38:10 2010<lf>

04:38:11.593: << 220 siteofpurity.gotdns.com ESMTP server ready.<cr><lf>

04:38:11.609: >> EHLO siteofpurity.gotdns.com<cr><lf>

04:38:11.640: << 250-siteofpurity.gotdns.com Hello siteofpurity.gotdns.com; ESMTPs are:<cr><lf>250-TIME<cr><lf>

04:38:11.656: << 250-SIZE 0<cr><lf>

04:38:11.671: << 250 HELP<cr><lf>

04:38:11.687: >> MAIL FROM:<mary.campbell@siteofpurity.gotdns.com><cr><lf>

04:38:11.796: << 250 Sender OK - send RCPTs.<cr><lf>

04:38:11.812: >> RCPT TO:<mary.campbell@siteofpurity.gotdns.com><cr><lf>

04:38:11.828: << 250 Recipient OK - send RCPT or DATA.<cr><lf>

04:38:11.843: >> RCPT TO:<gears@siteofpurity.gotdns.com><cr><lf>

04:38:11.859: << 250 Recipient OK - send RCPT or DATA.<cr><lf>

04:38:11.875: >> DATA<cr><lf>

04:38:11.875: << 354 OK, send data, end with CRLF.CRLF<cr><lf>

04:38:11.890: >> MIME-Version: 1.0<cr><lf>

04:38:11.906: >> X-Mailer: AfterLogic WebMail Pro PHP<cr><lf>

04:38:11.921: >> X-Originating-IP: x.x.x.x<cr><lf>

04:38:11.937: >> X-Priority: 3 (Normal)<cr><lf>

________________________________________________

its only supposed to send to gears, yet it sends it to herself to

<div>Connection from 192.168.1.57, Thu Oct 14 04:38:10 2010&lt;lf&gt;</div><div>04:38:11.593: &lt;&lt; 220 siteofpurity.gotdns.com ESMTP server ready.&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.609: &gt;&gt; EHLO siteofpurity.gotdns.com&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.640: &lt;&lt; 250-siteofpurity.gotdns.com Hello siteofpurity.gotdns.com; ESMTPs are:&lt;cr&gt;&lt;lf&gt;250-TIME&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.656: &lt;&lt; 250-SIZE 0&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.671: &lt;&lt; 250 HELP&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.687: &gt;&gt; MAIL FROM:&lt;mary.campbell@siteofpurity.gotdns.com&gt;&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.796: &lt;&lt; 250 Sender OK - send RCPTs.&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.812: &gt;&gt; RCPT TO:&lt;mary.campbell@siteofpurity.gotdns.com&gt;&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.828: &lt;&lt; 250 Recipient OK - send RCPT or DATA.&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.843: &gt;&gt; RCPT TO:&lt;gears@siteofpurity.gotdns.com&gt;&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.859: &lt;&lt; 250 Recipient OK - send RCPT or DATA.&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.875: &gt;&gt; DATA&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.875: &lt;&lt; 354 OK, send data, end with CRLF.CRLF&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.890: &gt;&gt; MIME-Version: 1.0&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.906: &gt;&gt; X-Mailer: AfterLogic WebMail Pro PHP&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.921: &gt;&gt; X-Originating-IP: x.x.x.x&lt;cr&gt;&lt;lf&gt;</div><div>04:38:11.937: &gt;&gt; X-Priority: 3 (Normal)&lt;cr&gt;&lt;lf&gt;</div><div>________________________________________________</div><div>its only supposed to send to gears, yet it sends it to herself to&nbsp;</div>

Rolf Lindby

posted Oct 15 '10 at 12:23 am

The client explicitly requested that the message should be sent to both addresses, so it's not something that happens in Mercury.

/Rolf

<p>The client explicitly requested that the message should be sent to both addresses, so it's not something that happens in Mercury.&nbsp;</p><p>/Rolf&nbsp;</p>

gears

posted Oct 15 '10 at 1:15 am

is there a way to set a filter to not send a msg to ones self?

dilberts_left_nut

posted Oct 15 '10 at 3:58 am

[quote]If header "T" contains "mary.campbell@siteofpurity.gotdns.com" Delete ""[/quote]

Although, I suspect that's not what you really want ...

You should fix the client, rather than trying to mask the problem at the server level.

<p>[quote]If header "T" contains "mary.campbell@siteofpurity.gotdns.com" Delete ""[/quote]</p><p>Although, I suspect that's not what you really want ...</p><p>You should fix the client, rather than trying to mask the problem at the server level. </p>

Rolf Lindby

posted Oct 15 '10 at 4:07 am

Filtering rules can only match headers against a known pattern, there are no variables containing sender or recipient. A policy with a tailor-made program to scan message headers could perhaps do it if the recipient is clearly identifiable from message headers. The best (but at the same time the most complicated) way would be to write a daemon to do it. Daemons have access to both envelope information and the complete message, and can decide how to proceed with handling the message.

/Rolf

<p>Filtering rules can only match headers against a known pattern, there are no variables containing sender or recipient. A policy with a tailor-made program to scan message headers could perhaps do it if the recipient is clearly identifiable from message headers. The best (but&nbsp;at the same time&nbsp;the most complicated) way would be to write a daemon to do it. Daemons have access to both envelope information and the complete message, and can decide how to proceed with handling the message.</p><p>/Rolf&nbsp;</p>

gears

posted Oct 15 '10 at 9:52 pm

i d abit of codeing, if its not to hard i could write one up, know where i might get a thing todo this with?

Rolf Lindby

posted Oct 15 '10 at 10:22 pm

The daemon developer kit is here:

http://community.pmail.com/files/folders/mercur/entry10073.aspx

Then you will need Microsoft Visual C++ (or Borland C++) as well.

/Rolf

<p>The daemon developer kit is here:</p><p>http://community.pmail.com/files/folders/mercur/entry10073.aspx</p><p>Then you will need Microsoft Visual C++ (or Borland C++) as well.</p><p>/Rolf </p>

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history