Server Marking Mail an Hour Off

Thread: Server Marking Mail an Hour Off

Search this list only Search all lists
Server Marking Mail an Hour Off
United States	2007-07-06 19:17:28
We are in the central time zone and the time is properly set on the server. However, SurgeMail is marking mail an hour off (-0400 instead of -0500). This is on OS X 10.4.10. Any idea how to correct this? -- Chris Jett chrisjettfuel.net

Re: Server Marking Mail an Hour Off
United States	2007-07-06 19:28:00
Edit the timezones field. do a search in the gui for timezones. I have to change mine for PDT but not for PST. Then you have to stop and start surgemail. I'm on mac os x too. On Jul 6, 2007, at 5:17 PM, Christopher Jett wrote: > We are in the central time zone and the time is properly set on the > server. However, SurgeMail is marking mail an hour off (-0400 > instead of -0500). This is on OS X 10.4.10. Any idea how to > correct this? > -- > Chris Jett > chrisjettfuel.net >

Re: Server Marking Mail an Hour Off
United States	2007-07-07 15:03:56
The only thing I see when I search on timezone is g_timezone which has this beside it: 'Places in timezone part of date string, e.g. +1200 NZT. Please leave blank!' Is this what you're talking about? Then I just put CDT in there? -- Chris On Jul 6, 2007, at 7:28 PM, Jody McAlister wrote: > Edit the timezones field. do a search in the gui for timezones. I > have to change mine for PDT but not for PST. Then you have to stop > and start surgemail. > > I'm on mac os x too. > > On Jul 6, 2007, at 5:17 PM, Christopher Jett wrote: > >> We are in the central time zone and the time is properly set on >> the server. However, SurgeMail is marking mail an hour off (-0400 >> instead of -0500). This is on OS X 10.4.10. Any idea how to >> correct this? >> -- >> Chris Jett >> chrisjettfuel.net >> > >

Re: Server Marking Mail an Hour Off
United States	2007-07-07 19:52:32

Yes, follow their example and put the appropriate time statement in there. On Jul 7, 2007, at 1:03 PM, Christopher Jett wrote: The only thing I see when I search on timezone is g_timezone which has this beside it: 'Places in timezone part of date string, e.g. +1200 NZT. Please leave blank!' Is this what you're talking about? Then I just put CDT in there? -- Chris On Jul 6, 2007, at 7:28 PM, Jody McAlister wrote: Edit the timezones field. do a search in the gui for timezones. I have to change mine for PDT but not for PST. Then you have to stop and start surgemail. I'm on mac os x too. On Jul 6, 2007, at 5:17 PM, Christopher Jett wrote: We are in the central time zone and the time is properly set on the server. However, SurgeMail is marking mail an hour off (-0400 instead of -0500). This is on OS X 10.4.10. Any idea how to correct this? -- Chris Jett chrisjettfuel.net">chrisjettfuel.net Jody McAlister In-Site Communications (707)765-9993/(866)376-7076 infoiscweb.com">infoiscweb.com
Why did the spf fail on this?
United States	2007-07-07 21:23:36

66.60.188.99]) ;     by awasco.com (SurgeMail 3.8j) with ESMTP id 7575753-1801253 ;     for <norulesawasco.com>; Sun, 01 Jul 2007 09:47:52 -0700 X-Received: from 66-60-188-006.cpe.zetabroadband.com (HELO ronaldah1qbb56) (66.60.188.6) ; by 66-60-188-202.cpe.zetabroadband.com with SMTP; 1 Jul 2007 09:47:32 -0700 From: "Ron Fegley" <rwfegleyisp.com>; To: <norulesawasco.com> Subject: [Norules] [SUSPECTED SPAM] Date: Sun, 1 Jul 2007 09:47:21 -0700 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acd+u0cWxgFpxnziR5KE3WdHHW/z/w9QypTw X-Rcpt-To: <norulesawasco.com> X-SpamDetect: *****: 7.550000 From3consonants=0.3, SPF Fail=8.0**, Aspam=-0.8 The TXT entry for this service appears to be "v=spf1 ip4:66.60.188.0/22 a mx
Re: Why did the spf fail on this?
New Zealand	2007-07-08 21:13:37

I don't see any spf header in that message.  Is this from a mailing list? I'm wondering if this has gone through the server more than once and some headers have been stripped in the process.   ChrisP. orinwells wrote: smtp.awasco.com" type="cite">X-Received: from plesk.zetabroadband.com (unverified [66.60.188.99])       by awasco.com (SurgeMail 3.8j) with ESMTP id 7575753-1801253       for awasco.com"><norulesawasco.com>; Sun, 01 Jul 2007 09:47:52 -0700 X-Received: from 66-60-188-006.cpe.zetabroadband.com (HELO ronaldah1qbb56) (66.60.188.6) ; by 66-60-188-202.cpe.zetabroadband.com with SMTP; 1 Jul 2007 09:47:32 -0700 From: "Ron Fegley" isp.com"><rwfegleyisp.com>; To: awasco.com"><norulesawasco.com> Subject: [Norules] [SUSPECTED SPAM] Date: Sun, 1 Jul 2007 09:47:21 -0700 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acd+u0cWxgFpxnziR5KE3WdHHW/z/w9QypTw X-Rcpt-To: awasco.com"><norulesawasco.com> X-SpamDetect: *****: 7.550000 From3consonants=0.3, SPF Fail=8.0**, Aspam=-0.8 The TXT entry for this service appears to be "v=spf1 ip4:66.60.188.0/22 a mx
Re: Why did the spf fail on this?
United States	2007-07-08 21:43:07

Here are ALL the headers in the message: Received: from AWASCO-1 (unverified [127.0.0.1]) ;     by awasco.com (SurgeMail 3.8j) with ESMTP id 7575763-1801253 ;     for <orinwellswells.org>; Sun, 01 Jul 2007 09:48:00 -0700 Return-Path: <norules-bounceawasco.com> Received-SPF: fail (Last token (res=FAIL)) client-ip=66.60.188.99; envelope-from=<rwfegleyisp.com>;; x-ip-name=plesk.zetabroadband.com; X-Received: from plesk.zetabroadband.com (unverified [66.60.188.99]) ;      by awasco.com (SurgeMail 3.8j) with ESMTP id 7575753-1801253 ;     for <norulesawasco.com>; Sun, 01 Jul 2007 09:47:52 -0700 X-Return-Path: <rwfegleyisp.com>; X-Received: (qmail 15912 invoked from network); 1 Jul 2007 09:47:32 -0700 X-Received: from 66-60-188-006.cpe.zetabroadband.com (HELO ronaldah1qbb56) (66.60.188.6) ; by 66-60-188-202.cpe.zetabroadband.com with SMTP; 1 Jul 2007 09:47:32 -0700 From: "Ron Fegley" <rwfegleyisp.com>; To: <norulesawasco.com> References: <c12.15051298.33526a62aol.com>; Subject: [Norules] [SUSPECTED SPAM] Sicko Date: Sun, 1 Jul 2007 09:47:21 -0700 Message-ID: <000901c7bbff$80a43c10$6401a8c0ronaldah1qbb56> MIME-Version: 1.0 Content-Type: multipart/alternative; ;     boundary="----=_NextPart_000_000A_01C7BBC4.D447D510" X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <c12.15051298.33526a62aol.com>; Thread-Index: Acd+u0cWxgFpxnziR5KE3WdHHW/z/w9QypTw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Rcpt-To: <norulesawasco.com> X-SpamDetect: *****: 7.550000 From3consonants=0.3, SPF Fail=8.0, Aspam=-0.8 X-NotAscii: charset=us-ascii X-Avast: Message is clean X-IP-stats: Incoming Last 0, First 1, in=3, out=0, spam=0 ip=66.60.188.99 X-X-Originating-IP: 66.60.188.99 X-Mailing-List: norulesawasco.com List-ID: <norulesawasco.com> Precedence: bulk Reply-To: norulesawasco.com X-listMember: orinwellswells.org [norules-request] X-IsFriend: <norules-bounceawasco.com> X-Rcpt-To: <orinwellswells.org> X-Avast: Message is clean X-IP-stats: Incoming Last 0, First 389, in=50533, out=0, spam=0 ip=127.0.0.1 X-Originating-IP: 127.0.0.1 Status: U X-UIDL: 1183308480.2628_395404.awasco-1 ============================================ At 07:13 PM 7/8/2007, Support Surgemail CP wrote: I don't see any spf header in that message.  Is this from a mailing list? I'm wondering if this has gone through the server more than once and some headers have been stripped in the process.   ChrisP. orinwells wrote: X-Received: from plesk.zetabroadband.com (unverified [66.60.188.99]) ;     by awasco.com (SurgeMail 3.8j) with ESMTP id 7575753-1801253 ;     for norulesawasco.com"><norulesawasco.com>; Sun, 01 Jul 2007 09:47:52 -0700 X-Received: from 66-60-188-006.cpe.zetabroadband.com (HELO ronaldah1qbb56) (66.60.188.6) ; by 66-60-188-202.cpe.zetabroadband.com with SMTP; 1 Jul 2007 09:47:32 -0700 From: "Ron Fegley" rwfegleyisp.com"><rwfegleyisp.com>; To: norulesawasco.com"><norulesawasco.com> Subject: [Norules] [SUSPECTED SPAM] Date: Sun, 1 Jul 2007 09:47:21 -0700 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acd+u0cWxgFpxnziR5KE3WdHHW/z/w9QypTw X-Rcpt-To: norulesawasco.com"><norulesawasco.com> X-SpamDetect: ***: 7.550000 From3consonants=0.3, SPF Fail=8.0**, Aspam=-0.8 The TXT entry for this service appears to be "v=spf1 ip4:66.60.188.0/22 a mx
Re: Why did the spf fail on this?
New Zealand	2007-07-09 17:30:21

orinwells wrote: smtp.awasco.com" type="cite">Yes, this went through a mailing list. ; EVERY subscriber saw the suspected spam notation added to the message. Here are ALL the headers in the message: Ok, it's from isp.com">rwfegleyisp.com isp.com text =       "v=spf1 ip4:216.127.133.0/26 ip4:216.127.146.0/27 ip4:209.107.130.9/32 i p4:65.212.160.0/25 ip4:65.212.160.128/27 ip4:216.127.148.0/24 ip4:216.127.154.12 8/25 ip4:204.8.0.0/22 a:psmtp.com a:postini.com -all" I don't know where you got this rule from ? "v=spf1 ip4:66.60.188.0/22 a mx " ChrisP. smtp.awasco.com" type="cite"> Received: from AWASCO-1 (unverified [127.0.0.1])       by awasco.com (SurgeMail 3.8j) with ESMTP id 7575763-1801253       for wells.org"><orinwellswells.org>; Sun, 01 Jul 2007 09:48:00 -0700 Return-Path: awasco.com"><norules-bounceawasco.com> Received-SPF: fail (Last token (res=FAIL)) client-ip=66.60.188.99; envelope-from=isp.com"><rwfegleyisp.com>;; x-ip-name=plesk.zetabroadband.com; X-Received: from plesk.zetabroadband.com (unverified [66.60.188.99])       by awasco.com (SurgeMail 3.8j) with ESMTP id 7575753-1801253       for awasco.com"><norulesawasco.com>; Sun, 01 Jul 2007 09:47:52 -0700 X-Return-Path: isp.com"><rwfegleyisp.com>; X-Received: (qmail 15912 invoked from network); 1 Jul 2007 09:47:32 -0700 X-Received: from 66-60-188-006.cpe.zetabroadband.com (HELO ronaldah1qbb56) (66.60.188.6) ; by 66-60-188-202.cpe.zetabroadband.com with SMTP; 1 Jul 2007 09:47:32 -0700 From: "Ron Fegley" isp.com"><rwfegleyisp.com>; To: awasco.com"><norulesawasco.com> References: aol.com"><c12.15051298.33526a62aol.com>; Subject: [Norules] [SUSPECTED SPAM] Sicko Date: Sun, 1 Jul 2007 09:47:21 -0700 Message-ID: <000901c7bbff$80a43c10$6401a8c0ronaldah1qbb56> MIME-Version: 1.0 Content-Type: multipart/alternative;       boundary="----=_NextPart_000_000A_01C7BBC4.D447D510" X-Mailer: Microsoft Office Outlook 11 In-Reply-To: aol.com"><c12.15051298.33526a62aol.com>; Thread-Index: Acd+u0cWxgFpxnziR5KE3WdHHW/z/w9QypTw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Rcpt-To: awasco.com"><norulesawasco.com> X-SpamDetect: *****: 7.550000 From3consonants=0.3, SPF Fail=8.0, Aspam=-0.8 X-NotAscii: charset=us-ascii X-Avast: Message is clean X-IP-stats: Incoming Last 0, First 1, in=3, out=0, spam=0 ip=66.60.188.99 X-X-Originating-IP: 66.60.188.99 X-Mailing-List: awasco.com">norulesawasco.com List-ID: awasco.com"><norulesawasco.com> Precedence: bulk Reply-To: awasco.com">norulesawasco.com X-listMember: wells.org">orinwellswells.org [norules-request] X-IsFriend: awasco.com"><norules-bounceawasco.com> X-Rcpt-To: wells.org"><orinwellswells.org> X-Avast: Message is clean X-IP-stats: Incoming Last 0, First 389, in=50533, out=0, spam=0 ip=127.0.0.1 X-Originating-IP: 127.0.0.1 Status: U X-UIDL: 1183308480.2628_395404.awasco-1 ============================================ At 07:13 PM 7/8/2007, Support Surgemail CP wrote: I don't see any spf header in that message.  Is this from a mailing list? I'm wondering if this has gone through the server more than once and some headers have been stripped in the process.   ChrisP. orinwells wrote: X-Received: from plesk.zetabroadband.com (unverified [66.60.188.99])       by awasco.com (SurgeMail 3.8j) with ESMTP id 7575753-1801253       for awasco.com"><norulesawasco.com>; Sun, 01 Jul 2007 09:47:52 -0700 X-Received: from 66-60-188-006.cpe.zetabroadband.com (HELO ronaldah1qbb56) (66.60.188.6) ; by 66-60-188-202.cpe.zetabroadband.com with SMTP; 1 Jul 2007 09:47:32 -0700 From: "Ron Fegley" isp.com"><rwfegleyisp.com>; To: awasco.com"><norulesawasco.com> Subject: [Norules] [SUSPECTED SPAM] Date: Sun, 1 Jul 2007 09:47:21 -0700 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acd+u0cWxgFpxnziR5KE3WdHHW/z/w9QypTw X-Rcpt-To: awasco.com"><norulesawasco.com> X-SpamDetect: ***: 7.550000 From3consonants=0.3, SPF Fail=8.0**, Aspam=-0.8 The TXT entry for this service appears to be "v=spf1 ip4:66.60.188.0/22 a mx
Re: Why did the spf fail on this?
United States	2007-07-09 20:39:07

which reported "v=spf1 ip4:66.60.188.0/22 a mx [Unknown Var]all" That seemed "right" (kind of screwed up) because 1) I wasn't paying attention and the IP address being shown was 66.60.188.6 So I am thinking that isp.com is an affiliate of Zetabroadband but since the originating IP address is being checked by Surgemail is the workstation IP which is not covered in the isp.com TXT record, it failed. At 03:30 PM 7/9/2007, Support Surgemail CP wrote: orinwells wrote: Yes, this went through a mailing list. EVERY subscriber saw the suspected spam notation added to the message. Here are ALL the headers in the message: Ok, it's from rwfegleyisp.com">rwfegleyisp.com isp.com text = ;       "v=spf1 ip4:216.127.133.0/26 ip4:216.127.146.0/27 ip4:209.107.130.9/32 i p4:65.212.160.0/25 ip4:65.212.160.128/27 ip4:216.127.148.0/24 ip4:216.127.154.12 8/25 ip4:204.8.0.0/22 a:psmtp.com a:postini.com -all" I don't know where you got this rule from ?       ; "v=spf1 ip4:66.60.188.0/22 a mx "             ;  ChrisP. Received: from AWASCO-1 (unverified [127.0.0.1]) ;     by awasco.com (SurgeMail 3.8j) with ESMTP id 7575763-1801253 ;     for orinwellswells.org"><orinwellswells.org>; Sun, 01 Jul 2007 09:48:00 -0700 Return-Path: norules-bounceawasco.com"> <norules-bounceawasco.com> Received-SPF: fail (Last token (res=FAIL)) client-ip=66.60.188.99; envelope-from= rwfegleyisp.com"> <rwfegleyisp.com>;; x-ip-name=plesk.zetabroadband.com; X-Received: from plesk.zetabroadband.com (unverified [66.60.188.99]) ;      by awasco.com (SurgeMail 3.8j) with ESMTP id 7575753-1801253 ;     for norulesawasco.com"><norulesawasco.com>; Sun, 01 Jul 2007 09:47:52 -0700 X-Return-Path: rwfegleyisp.com"><rwfegleyisp.com>; X-Received: (qmail 15912 invoked from network); 1 Jul 2007 09:47:32 -0700 X-Received: from 66-60-188-006.cpe.zetabroadband.com (HELO ronaldah1qbb56) (66.60.188.6) ; by 66-60-188-202.cpe.zetabroadband.com with SMTP; 1 Jul 2007 09:47:32 -0700 From: "Ron Fegley" rwfegleyisp.com"><rwfegleyisp.com>; To: norulesawasco.com"><norulesawasco.com> References: c12.15051298.33526a62aol.com"> <c12.15051298.33526a62aol.com>; Subject: [Norules] [SUSPECTED SPAM] Sicko Date: Sun, 1 Jul 2007 09:47:21 -0700 Message-ID: <000901c7bbff$80a43c10$6401a8c0ronaldah1qbb56> MIME-Version: 1.0 Content-Type: multipart/alternative; ;     boundary="----=_NextPart_000_000A_01C7BBC4.D447D510" X-Mailer: Microsoft Office Outlook 11 In-Reply-To: c12.15051298.33526a62aol.com"> <c12.15051298.33526a62aol.com>; Thread-Index: Acd+u0cWxgFpxnziR5KE3WdHHW/z/w9QypTw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Rcpt-To: norulesawasco.com"><norulesawasco.com> X-SpamDetect: *****: 7.550000 From3consonants=0.3, SPF Fail=8.0, Aspam=-0.8 X-NotAscii: charset=us-ascii X-Avast: Message is clean X-IP-stats: Incoming Last 0, First 1, in=3, out=0, spam=0 ip=66.60.188.99 X-X-Originating-IP: 66.60.188.99 X-Mailing-List: norulesawasco.com">norulesawasco.com List-ID: norulesawasco.com"><norulesawasco.com> Precedence: bulk Reply-To: norulesawasco.com">norulesawasco.com X-listMember: orinwellswells.org">orinwellswells.org [norules-request] X-IsFriend: norules-bounceawasco.com"> <norules-bounceawasco.com> X-Rcpt-To: orinwellswells.org"><orinwellswells.org> X-Avast: Message is clean X-IP-stats: Incoming Last 0, First 389, in=50533, out=0, spam=0 ip=127.0.0.1 X-Originating-IP: 127.0.0.1 Status: U X-UIDL: 1183308480.2628_395404.awasco-1 ============================================ At 07:13 PM 7/8/2007, Support Surgemail CP wrote: I don't see any spf header in that message.  Is this from a mailing list? I'm wondering if this has gone through the server more than once and some headers have been stripped in the process.   ChrisP. orinwells wrote: X-Received: from plesk.zetabroadband.com (unverified [66.60.188.99]) ;     by awasco.com (SurgeMail 3.8j) with ESMTP id 7575753-1801253 ;     for norulesawasco.com"><norulesawasco.com>; Sun, 01 Jul 2007 09:47:52 -0700 X-Received: from 66-60-188-006.cpe.zetabroadband.com (HELO ronaldah1qbb56) (66.60.188.6) ; by 66-60-188-202.cpe.zetabroadband.com with SMTP; 1 Jul 2007 09:47:32 -0700 From: "Ron Fegley" rwfegleyisp.com"><rwfegleyisp.com>; To: norulesawasco.com"><norulesawasco.com> Subject: [Norules] [SUSPECTED SPAM] Date: Sun, 1 Jul 2007 09:47:21 -0700 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acd+u0cWxgFpxnziR5KE3WdHHW/z/w9QypTw X-Rcpt-To: norulesawasco.com"><norulesawasco.com> X-SpamDetect: ***: 7.550000 From3consonants=0.3, SPF Fail=8.0**, Aspam=-0.8 The TXT entry for this service appears to be "v=spf1 ip4:66.60.188.0/22 a mx

[1-9]

about | contact Other archives ( Real Estate discussion Medical topics )