* Victor Duchovni victor.ducho...@morganstanley.com:
- Remove non-working addresses promptly from your lists.
This step alon considerably improves reputation AND delivery time.
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus
True but there got to be some easy way to export that list, otherwise
I'll have to delete the dead mails from our database manually from time
to time. Any ideas how I can get everything work fluently? I mean, for
example, every several days I get all dead mail addresses from postfix
by maybe a
Thanks for the suggestions. Some comments below.
Regards,
Yaoxing
2010/12/24 9:17, Victor Duchovni Wrote:
On Fri, Dec 24, 2010 at 09:11:19AM +0800, ? wrote:
- Make sure your lists really contain users who want to receive the
newsletter, not just users whose email address you
Yaoxing:
True but there got to be some easy way to export that list, otherwise
I'll have to delete the dead mails from our database manually from time
to time. Any ideas how I can get everything work fluently? I mean, for
example, every several days I get all dead mail addresses from
So I must scan the log for the list, isn't it? It works of course but is
there any more specific way to do that? because scanning spends a lot of
time, and you don't know where you stopped last time (or not easy to
find out). especially our front end platform is based on .NET which does
not
Wietse Venema:
Yaoxing:
True but there got to be some easy way to export that list, otherwise
I'll have to delete the dead mails from our database manually from time
to time. Any ideas how I can get everything work fluently? I mean, for
example, every several days I get all dead mail
I neglected to mention the exchange server, source outbound server,
is on internal edge of the dmz.
On Fri, Dec 24, 2010 at 12:02 AM, Stan Hoeppner s...@hardwarefreak.com wrote:
Roman Gelfand put forth on 12/23/2010 10:01 PM:
I am now looking to use the postfix mail gateway, smart host,
to
On Fri, Dec 24, 2010 at 11:38:19PM +0800, Yaoxing wrote:
So I must scan the log for the list, isn't it? It works of course but is
there any more specific way to do that? because scanning spends a lot of
time, and you don't know where you stopped last time (or not easy to find
out).
Roman Gelfand put forth on 12/24/2010 10:45 AM:
I neglected to mention the exchange server, source outbound server,
is on internal edge of the dmz.
Bah, you did mention the Exchange server and I just missed it. The 587
is more geared toward MUAs like Outlook and TBird. If you just want to
On Fri, Dec 24, 2010 at 03:20:11PM -0600, Stan Hoeppner wrote:
I neglected to mention the exchange server, source outbound server,
is on internal edge of the dmz.
Bah, you did mention the Exchange server and I just missed it. The 587
is more geared toward MUAs like Outlook and TBird.
Yaoxing put forth on 12/24/2010 9:20 AM:
The list comes from our clients' subscriptions. However, we didn't
verify the ownership of the emails before which maybe lead to invalid
email addresses. This is what we can improve in future.
You should have already had a process in place for list
We do have a web portal for users to s*bscribe or uns*bscribe
themselves. And each newsletter contains such a link in case users want
to uns*bscribe.
We already have a very big list which is filled with users who purchased
and s*bscribed in our web site. So there's no need to buy that from a
3rd
12 matches
Mail list logo
