consumo de recursos con lista de correo

pereztroff · 22-mar-2007, 22:25

una de mis webs estan alojada con un proveedor ingles y me ha dicho que la lista de correo que uso en este caso phpmailer consume muchos recursos y que supero los emails establecidos por hora.

Me da una solución, pero como mi ingles no es fluido no entiendo bien que me dice, a ver si alguien me puede orientar por favor de que me dicen, gracias.

Cita:

We do allow the use of email mailing lists though there are some conditions in place as set out below. We recommend the use of a mailing list application called Dada Mail due to it's large amount of features, ease of use and server resource usage (eg ability to 'batch send'). Operating mailing lists using a basic home made script or a non mailing list application (eg forum application 'Email All' feature) are not recommended due to the lack of options and flexibility with these methods.

NO SPAM *
It goes without saying that our servers are not to be used to send spam email (unsolicited bulk email).

NO Safelists or Purchased lists *
We do not allow 'safe lists' or other similar schemes whereby advertisers trade email contacts. In addition to this, the vast majority of email address lists available for sale on the internet as 'legitimate opt-in lists of contacts who have agreed to be sent advertising emails' are fake and will lead to large numbers of spam reports so we do not allow the use of these purchased lists - all addresses on a mailing list must agree to be sent emails specifically with the website sending the emails.

MUST BE Double Opt-In *
An opt-in method of list subscription is where the subscriber asks to be put on the list by, for example, entering their email address in a website form to become subscribed.

We require that list administrators employ double opt-in methods whereby the subscriber has to authorise being added to the list after submitting their email address. This usually takes the form of an automated email being sent to the address submitted where a link needs to be clicked to confirm the subscription.

Not only does this get extra confirmation from the client, it also ensures that the email address is valid (avoiding problems with email bounces when sending to the list) and also that the email address is owned by the person subscribing (avoiding problems with people entering addresses not owned by them on website forms).

List administrators are also asked to keep evidence/logs of the date and method that subscribers agreed to be included in the mailing list.

MUST CONTAIN Unsubscribe Instructions *
All emails sent to the mailing list must contain clear instructions for unsubscription, ie not tiny text or otherwise hidden away within the email content . At a minimum, subscribers should be able to unsubscribe at any time by emailing to request this with unsubscription requests processed in a timely fashion.

We strongly recommend that list administrators implement an automated weblink unsubscription whereby all mailings contain a "click here to unsubscribe" link which will allow the user to be removed from the list in one click with no human intervention. This will also allow us to process unsubscriptions if any subscribers send in spam complaints and be more reliable as most do not feel comfortable replying to an email they consider as unwanted.

We do not force list administrators to use a weblink method of unsusbscription but should any list generate regular spam complaints we do reserve the right to insist on this method of unsubscription for future mailings on our server.

MUST BE Single Opt-Out *
We ask that those operating mailing lists allow unsubscriptions (opt-out's) with no email confirmation or other additional tasks required by those unsubscribing. If a subscriber clicks the unsubscribe link or request unsubscription their email address should then be removed from the database with no email confirmation or other tasks required.

NO Mailing List only hosting *
Mailing lists in use which send mailings primarily advertising/promoting a website not hosted with us are not permitted.

We offer the feature of being able to operate mailing lists as an addon service to our primary service of website hosting so if a website is hosted with a different web host we will not be able to permit the hosting of a mailing list for that website and we recommend that the same hosting company who hosts the website is also used to host the mailing list.

Reasons for email
We recommend that all mailings contain clear information detailing who the email is from and why the subscriber is being sent it (eg because the subscriber asked to be kept informed via the list).

Also, in order to help greatly if spam complaints do occur, we ask that the subscribers email address is included as text somewhere within the email so we know who the complaint is from and can be put in the email headers, within the content or embedded within the unsubscribe link (preferred method) or elsewhere in the email. This is because most blacklist notifications remove the senders email address which prevents us from knowing which email address needs to be removed from the database.

Apolo · 22-mar-2007, 22:32

Hola pereztroff,

Bienvenido a ComunidadHosting.

Básicamente te están recomendando el uso del software Dada Mail, el cual permite el envío por lotes (batch send), es decir, por ejemplo 500 mensajes por hora. Otros scripts especializados como phpList permiten hacer lo mismo.

Saludos,

pereztroff · 22-mar-2007, 22:45

Gracias Apolo por tu rapida respuesta.

Es que usaba phpmailer pero lleva casi una semana da mas que errores y eso que no es spamm ni nada raro, supongo que habran cambiado las politicas de empresa o algo asi.

Me han dico que phplist tiene bugs de seguridad, mejor dadamail?

Apolo · 22-mar-2007, 22:54

Cita:

Iniciado por pereztroff

Me han dico que phplist tiene bugs de seguridad, mejor dadamail?

No conozco Dada Mail.

Varios de nuestros clientes usan phpList y hasta el momento no han tenido problema alguno con asuntos de seguridad.

Saludos,