Charles Marcus wrote:
> I'm confused... above you say that they don't allow relaying from
> outside their network 'no matter what'... then you say you need their
> relay service while outside their IP block...
>
The ISP and the third-party relayer are two different companies. I need
the rela
On 3/17/2008, Frank Griffin ([EMAIL PROTECTED]) wrote:
> They don't seem to want the risk of basic SMTP auth being cracked or
> sniffed, so they just refuse to relay for anything outside their IP
> block, period, no matter what.
> Since I don't want to have to reconfigure may laptop every time I
Charles Marcus wrote:
> Most ISPs in the US simply allow relaying on their IP blocks...
>
> But, they don't absolutely need to support *secure* smtp auth - basic
> smtp auth would be much better than using and easily forged 'From:'
> header...
>
> I'd find another ISP/3rd party relay service...
>
On 3/17/2008, Frank Griffin ([EMAIL PROTECTED]) wrote:
> It's their billing model. Most ISPs refuse to support secure SMTP
> because of the perceived cost of encryption. The relayer does, but
> charges you twice as much for using TLS (actually, mails/bytes are
> billed against your account limit
Charles Marcus wrote:
> On 3/17/2008, Frank Griffin ([EMAIL PROTECTED]) wrote:
>
>> My test machines all use a third-party relay server which requires
>> "From:" to be one of a fixed set of pre-registered values. I handle
>> this by using Postfix's "generic" file to rewrite the sender on
>> o
On 3/17/2008, Frank Griffin ([EMAIL PROTECTED]) wrote:
> My test machines all use a third-party relay server which requires
> "From:" to be one of a fixed set of pre-registered values. I handle
> this by using Postfix's "generic" file to rewrite the sender on
> outbound messages to the 'frank.gr
Mark Sapiro wrote:
>> But here's the thing: the only occurrence of
>> "[EMAIL PROTECTED]" on the fresh system is a .forward file in
>> /root, /var/spool/postfix, and /home/ftg. The test message is sent from
>> the 'ftg' ID whose home directory is /home/ftg.
>>
>> Do you guys follow or look at .for
Mark Sapiro writes:
> It appears non-standard in at least a few obvious ways, and I have no
> way to know in what others. You might find answers using Mandriva
> support resources
Mandrake always prided itself on the excellence of its user and admin
interfaces, and did not hesitate to change f
Frank Griffin wrote:
>
>Mark Sapiro wrote:
>>
>> If you want to see what's behind that, you can do
>>
>> bin/dumpdb lists/webdata/config.pck
>>
>> and look at the actual values of the three attributes
>> first_strip_reply_to, reply_goes_to_list and reply_to_address.
>>
>>
>For the webdata list
Mark Sapiro wrote:
>
> It appears non-standard in at least a few obvious ways, and I have no
> way to know in what others. You might find answers using Mandriva
> support resources
>
>
I did before posting here, but found no bug reports there or on Google
which resembled this in any way.
There'
Mark Sapiro wrote:
> Frank Griffin wrote:
>
>>>
>>>
>> It wasn't the addition of [EMAIL PROTECTED] in the reply-to that made
>> me curious (I can see that this list does that as well), but the fact
>> that the second entry has the correct description but the wrong
>> address. Referenc
Frank Griffin wrote:
>
>Mark Sapiro wrote:
>>
>> Why is it the To: address of the post?
>>
>
>You've got me. I'm assuming that all this stems from some anomaly in
>the upgrade that was done of the files copied from the old system.
It is clear to me that whatever Mailman this is, it is not the
Frank Griffin wrote:
>>
>It wasn't the addition of [EMAIL PROTECTED] in the reply-to that made
>me curious (I can see that this list does that as well), but the fact
>that the second entry has the correct description but the wrong
>address. Referencing my later post, it seems to be getting the
Mark Sapiro wrote:
> Frank Griffin wrote:
>
>
>> Addenda: I set up a new list on the same host with [EMAIL PROTECTED]
>> as the owner and as a subscriber, and sent a post from
>> [EMAIL PROTECTED] to the list.
>>
>> When [EMAIL PROTECTED] received the copy of the post, the headers were:
>>
>> F
Mark Sapiro wrote:
> I'm not sure what's happening in total, but the '[EMAIL PROTECTED]' is
> your own Reply-To: from the incoming post. The default is to add any
> additional reply-to address to that. If you want it removed, you need
> to set first_strip_reply_to to Yes.
>
> As far as the rest of
Frank Griffin wrote:
>Addenda: I set up a new list on the same host with [EMAIL PROTECTED]
>as the owner and as a subscriber, and sent a post from
>[EMAIL PROTECTED] to the list.
>
>When [EMAIL PROTECTED] received the copy of the post, the headers were:
>
>From: Frank Griffin <[EMAIL PROTECTED]>
Frank Griffin wrote:
>
>Thanks for the reply. I've recently gotten back to this and wanted to
>post my results.
>
>In addition to the steps you posted, I needed to run "withlist -a -l -r
>fix_url".
>
>However, I have one anomaly that still needs resolution:
>
>All of the lists I moved had the opti
Frank Griffin wrote:
>
> In this case, the list owner is [EMAIL PROTECTED] and the
> poster is [EMAIL PROTECTED] . It seems to me that this ought to be
> WebData Project Discussion <[EMAIL PROTECTED]> .
>
> Did I miss a step ? What can I do to correct this ?
Addenda: I set up a new list on the sam
Mark Sapiro wrote:
> Frank Griffin wrote:
>> According to the UPGRADE document, file formats have changed as have
>> actual files (some new, some gone). What triggers the 2.1 version to do
>> the necessary conversions ? Is it just finding files of the old version
>> and recognizing them as such ?
>
Frank Griffin wrote:
>
>According to the UPGRADE document, file formats have changed as have
>actual files (some new, some gone). What triggers the 2.1 version to do
>the necessary conversions ? Is it just finding files of the old version
>and recognizing them as such ?
Yes, as far as the old c
Hi all,
I need to migrate lists from an *old* Slackware system running MM 2.0
(0x20f0) to a new system where MM is installed via RPM (2.1.9).
I've read the posts linked to by the FAQ, and the basic procedure is to
copy the data, lists, and archives directories and run withlist
fix_url. But I
21 matches
Mail list logo
