I'm trying to generate custom e-mail addresses that get forwarded to a catch-all. I'm wondering how postfix would need to be configured to handle these types of e-mails
我正在尝试生成自定义的电子邮件地址,这些地址可以转发给全能。我想知道如何配置postfix来处理这些类型的电子邮件
dropbox@123456.foobar.highrisehq.com
4 个解决方案
#1
2
I do believe that it is not totally a smtp server level thing. Like the mails where the ticket id is in the subject line and you have to keep that there, there would mostly be another application that would be checking TO address, doing a database lookup and then doing something useful.
我相信它不完全是一个smtp服务器级别的东西。就像票证ID在主题行中的邮件一样,你必须保留它,大多数情况下会有另一个应用程序检查TO地址,进行数据库查找然后做一些有用的事情。
I haven't signed up for highrise,but I imagine that the dropbox address, given in the sample as "dropbox@12345678.highrisehq.com",the 12345678 part would be a randomly generated but unique number (means that they will not be sequentially generated, like 0000001,0000002, ... but like 28902734, 1029383, ...) and connected to your account. This way if you mistype that part, the chances of it landing up in the wrong account are lowered, and mostly the mail would bounce back. All the mails sent to the dropbox address are added that members account, in that sense, the dropbox email address is not to be made public. The dropbox address would not be easy to remember, but it is not meant to be. This lends more credence to the theory that there is a separate application which processes the mails and files them in the correct account.
我还没有报名参加高层会议,但是我想,保管箱地址,在样本中给出为“dropbox@12345678.highrisehq.com”,12345678部分将是一个随机生成但唯一的数字(意味着它们不会是顺序生成,如0000001,0000002,...但像28902734,10239383,...)并连接到您的帐户。这样一来,如果你错误输入那个部分,那么它降级到错误账户的机会就会降低,而且大多数邮件都会反弹。发送到保管箱地址的所有邮件都添加了成员帐户,从这个意义上讲,保管箱电子邮件地址不会公开。保管箱地址不容易记住,但并不意味着。这为理论提供了更多的信任,即有一个单独的应用程序可以处理邮件并将文件记录在正确的帐户中。
#2
0
They're most likely piping a wildcard e-mail address into a script.
他们最有可能将通配符电子邮件地址发送到脚本中。
#3
0
A catch-all e-mail address? Wouldn't that be a total spam magnet?
一个包罗万象的电子邮件地址?这不是一个垃圾邮件总量吗?
#4
0
You can do all sorts of fancy stuff with Postfix. Notably 2.2 and up have a bit more power and better syntax when it comes to building queries. Here's an example of something I've used to determine if the email address, in this case user+pin@domain.com, meet the criteria in order to be allowed to hit the script.
你可以用Postfix做各种奇特的东西。值得注意的是,2.2和更高版本在构建查询时具有更强大的功能和更好的语法。以下是我用来确定电子邮件地址(在本例中为user+pin@domain.com)是否符合条件以允许命中脚本的示例。
mail01 # cat /etc/postfix/mysql_virtual_alias_maps.cf
mail01 #cat /etc/postfix/mysql_virtual_alias_maps.cf
user = email_api
password = email_api_pass
user = email_api password = email_api_pass
hosts = dbslave_vip
dbname = the_db
hosts = dbslave_vip dbname = the_db
query = SELECT 'local_user@localhost' FROM u_user WHERE login_name = substring_index( '%s ' , '+', 1 ) AND pin = substring_index(substring_index( '%s ' , '@', 1), '+', -1) limit 1;
query = SELECT'local_user @ localhost'FROM u_user WHERE login_name = substring_index('%s','+',1)AND pin = substring_index(substring_index('%s','@',1),'+', - 1)限制1;
#1
2
I do believe that it is not totally a smtp server level thing. Like the mails where the ticket id is in the subject line and you have to keep that there, there would mostly be another application that would be checking TO address, doing a database lookup and then doing something useful.
我相信它不完全是一个smtp服务器级别的东西。就像票证ID在主题行中的邮件一样,你必须保留它,大多数情况下会有另一个应用程序检查TO地址,进行数据库查找然后做一些有用的事情。
I haven't signed up for highrise,but I imagine that the dropbox address, given in the sample as "dropbox@12345678.highrisehq.com",the 12345678 part would be a randomly generated but unique number (means that they will not be sequentially generated, like 0000001,0000002, ... but like 28902734, 1029383, ...) and connected to your account. This way if you mistype that part, the chances of it landing up in the wrong account are lowered, and mostly the mail would bounce back. All the mails sent to the dropbox address are added that members account, in that sense, the dropbox email address is not to be made public. The dropbox address would not be easy to remember, but it is not meant to be. This lends more credence to the theory that there is a separate application which processes the mails and files them in the correct account.
我还没有报名参加高层会议,但是我想,保管箱地址,在样本中给出为“dropbox@12345678.highrisehq.com”,12345678部分将是一个随机生成但唯一的数字(意味着它们不会是顺序生成,如0000001,0000002,...但像28902734,10239383,...)并连接到您的帐户。这样一来,如果你错误输入那个部分,那么它降级到错误账户的机会就会降低,而且大多数邮件都会反弹。发送到保管箱地址的所有邮件都添加了成员帐户,从这个意义上讲,保管箱电子邮件地址不会公开。保管箱地址不容易记住,但并不意味着。这为理论提供了更多的信任,即有一个单独的应用程序可以处理邮件并将文件记录在正确的帐户中。
#2
0
They're most likely piping a wildcard e-mail address into a script.
他们最有可能将通配符电子邮件地址发送到脚本中。
#3
0
A catch-all e-mail address? Wouldn't that be a total spam magnet?
一个包罗万象的电子邮件地址?这不是一个垃圾邮件总量吗?
#4
0
You can do all sorts of fancy stuff with Postfix. Notably 2.2 and up have a bit more power and better syntax when it comes to building queries. Here's an example of something I've used to determine if the email address, in this case user+pin@domain.com, meet the criteria in order to be allowed to hit the script.
你可以用Postfix做各种奇特的东西。值得注意的是,2.2和更高版本在构建查询时具有更强大的功能和更好的语法。以下是我用来确定电子邮件地址(在本例中为user+pin@domain.com)是否符合条件以允许命中脚本的示例。
mail01 # cat /etc/postfix/mysql_virtual_alias_maps.cf
mail01 #cat /etc/postfix/mysql_virtual_alias_maps.cf
user = email_api
password = email_api_pass
user = email_api password = email_api_pass
hosts = dbslave_vip
dbname = the_db
hosts = dbslave_vip dbname = the_db
query = SELECT 'local_user@localhost' FROM u_user WHERE login_name = substring_index( '%s ' , '+', 1 ) AND pin = substring_index(substring_index( '%s ' , '@', 1), '+', -1) limit 1;
query = SELECT'local_user @ localhost'FROM u_user WHERE login_name = substring_index('%s','+',1)AND pin = substring_index(substring_index('%s','@',1),'+', - 1)限制1;