Newsletter email block.


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Newsletter email block.
# 1  
Old 07-02-2014
Newsletter email block.

I currently built a website and tested the newsletter with like 20 emails from the same provider (videotron.ca) since its the only provider i'm targeting with the newsletter. The automated message from the newsletter contains a link that videotron.ca usually blocks after a small period of time (blocks the link only). Is there a way I can "mask" the link inside for each of the email sent but to redirect when clicked to the same address (https://<test>.ca/newsletter.php). The thing i wanna do is to send every time a different link inside their email but when they click to redirect them to my website.

Is there a way to do it? A script or something like that?

Thanks in advance,

Galford D. Weller

Last edited by galford; 07-02-2014 at 02:54 PM..
 
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Cybersecurity

Security Newsletter

Bruce Schneier has released a special edition of his monthly Crypto-Gram security newsletter. This issue discusses security & technology topics relating to the September 11th attack. It is not strictly Unix related, but I think it is well worth the read as it contains a lot of well-though out,... (0 Replies)
Discussion started by: PxT
0 Replies
Login or Register to Ask a Question
t_sndrel(3)						     Library Functions Manual						       t_sndrel(3)

NAME
t_sndrel() - initiate an orderly release SYNOPSIS
DESCRIPTION
The function is used in connection-oriented mode to initiate an orderly release at a transport endpoint specified by fd, which is a file descriptor previously returned by the function. After this orderly release is indicated, the transport user should not try to send more data through that transport endpoint. An attempt to send more data to a released transport endpoint may block continuously. However, the transport user may continue to receive data over the connection until an orderly release indication is received. This function is an optional service of the transport provider and is only supported if the transport provider returned service type on or Note HP OSI XTI does not support Fork Safety is not fork-safe. RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and is set to indicate the error. ERRORS
On failure, is set to one of the following: [TBADF] The specified identifier does not refer to a transport endpoint. [TFLOW] Asynchronous mode is indicated because was set, but the transport provider cannot accept a release because of flow-con- trol restrictions. [TLOOK] An asynchronous event has occurred on this transport endpoint and requires immediate attention. [TNOTSUPPORT] This function is not supported by the underlying transport provider. [TSYSERR] A system error has occurred during execution of this function. [TPROTO] (XTI only) This error indicates that a communication problem has been detected between XTI and the transport provider for which there is no other suitable XTI ( SEE ALSO
t_getinfo(3), t_open(3), t_rcvrel(3), thread_safety(5). STANDARDS CONFORMANCE
t_sndrel(3)