At 03:45 PM 4/1/05 -0800, $Bill Luebkert wrote:
>That would involve a big hash that converts everyone's pseudoname with the
>real thing. Could be a hassle. Switching the To and CC seems easier and
>the reply-to header might be even easier (provided it works - we'd have to
>test some of the OOFs a
I'm all for putting the sender's address in the From header and the list
address in the Reply-To header. That's how it works on most every list
I'm on, and it works great.
Regards,
Lyle Kopnicky
___
Perl-Win32-Users mailing list
Perl-Win32-Users@lists
Chris Wagner wrote:
> At 12:02 PM 4/1/05 -0800, Jan Dubois wrote:
>
The best way to do this is to substitute the sender's email address
with that of the list but keep the sender's name. Like "Bob
>>
>>Nope, that doesn't fly. It makes it very hard to reply to the original
>>sender because
jeff griffiths wrote:
> Chris Wagner wrote:
>
>>At 10:47 AM 4/1/05 -0800, jeff griffiths wrote:
>>
>>
>>>The one thing we *could* do to mitigate this is to have list emails look
>>>like they come *from* the list, not the poster. Currently none of our
>>>lists work this way, and I believe this is
- Original Message -
From: "Chris Wagner" <[EMAIL PROTECTED]>
To: "perl-win32-users"
Sent: Saturday, April 02, 2005 12:10 AM
Subject: Re: [OT] Spam to list
> It could be that they got spammed sometime by somebody on ur network and
now
> they flag everything coming from +/- 3 miles of
At 12:02 PM 4/1/05 -0800, Jan Dubois wrote:
>>> The best way to do this is to substitute the sender's email address
>>> with that of the list but keep the sender's name. Like "Bob
>Nope, that doesn't fly. It makes it very hard to reply to the original
>sender because their address is lost now.
No
On Fri, 01 Apr 2005, jeff griffiths wrote:
> Chris Wagner wrote:
>> At 10:47 AM 4/1/05 -0800, jeff griffiths wrote:
>>
>>> The one thing we *could* do to mitigate this is to have list emails
>>> look like they come *from* the list, not the poster. Currently none
>>> of our lists work this way, and
Chris Wagner wrote:
At 10:47 AM 4/1/05 -0800, jeff griffiths wrote:
The one thing we *could* do to mitigate this is to have list emails look
like they come *from* the list, not the poster. Currently none of our
lists work this way, and I believe this is for a collection of technical
/ philosophical
At 10:47 AM 4/1/05 -0800, jeff griffiths wrote:
>The one thing we *could* do to mitigate this is to have list emails look
>like they come *from* the list, not the poster. Currently none of our
>lists work this way, and I believe this is for a collection of technical
>/ philosophical / religious rea
jeff griffiths wrote:
> I agree the OOF replies are annoying, but it is something we can't
> control within the limitations of the current mailing list settings. We
> can trap OOF stuff from users sent to the LIST, but the OOF also replies
> to the poster.
>
> The one thing we *could* do to mitig
$Bill Luebkert wrote:
Sisyphus wrote:
Hi, Whenever I reply to this list I receive a message from
[EMAIL PROTECTED] with the following subject:
Symantec Mail Security detected that you sent a message containing
prohibited content that is considered spam - please call email
recipient.
...
Obvious
Thank you Rob,
Some of the vars got lost in translation when I pasted...
You are right about me checking for the return incorrectly, I have made the
change as you have suggested and it's working.
ps, I will start using warnings and strict.
Regards,
Ben
-Original Message-
From: Sisyphu
>From what I can tell, Win32::API is geared towards executing functions
in DLLs. The DLL I need to interact with contains a few classes which I
need to instantiate, then I need to access some methods to alter some
attributes, then I need to access some other methods to actually do
something.
The
It could be that they got spammed sometime by somebody on ur network and now
they flag everything coming from +/- 3 miles of u.
--
REMEMBER THE WORLD TRADE CENTER ---=< WTC 911 >=--
"...ne cede males"
0100
___
Perl-Win32-Users mailing l
- Original Message -
From: "$Bill Luebkert" <[EMAIL PROTECTED]>
>
> PS: I don't get the rejections you speak of, but I do get tons of OOF
replies.
>
The message I sent with Net::SMTP to this list still triggered the spam
notification from [EMAIL PROTECTED] .
I went to the selkirkinc we
From: "Bullock, Howard A." <[EMAIL PROTECTED]>
> I apologize for the previous post that was sent prematurely.
>
> After reading the IniHash.pm I found that I could pass The ReadINI
> method a scalar reference. So my solution is:
>
> use Encode;
> open(FH, "<:encoding(UTF-16)", $file);
>
Title: restraining grep
Spencer_Lists wrote, on Fri 4/1/2005 02:34
: I have a few programs that accept user input as a series of
integer: values pairs separated by a delimiters between the pairs and
the: elements of the pairs. I previously made an array out of the first:
halves of the pai
Spencer_Lists wrote:
> Greetings perl-win32-users,
>
> I have a few programs that accept user input as a series of integer
> values pairs separated by a delimiters between the pairs and the
> elements of the pairs. I previously made an array out of the first
> halves of the pairs and also a hash
18 matches
Mail list logo
