Once again.... a dilemma...
I was lead to the understanding incoming email could be then posted to a
sub using the sub:<intcode> in the alias.cfg. I have created a user called MTAINFO and signed up for a service that will send email TO: mtainfo@tequilamockingbirdonline.net. This service offers different information using different sending addresses but all with the same host.
In the alias.cfg I put the following line:
MTAINFO sub:1nyctinfo
When the email comes in addressed to mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:
1400 !SMTP lirr@alerts.mta.info (user #0) cannot post on NYCT/MTA Srv Information (Reason 690)
So I went a step further and added to alias.cfg:
lirr@alerts.mta.info sub:1nyctinfo
Same message.
Does each email address need to have a user #?
On 11-14-14 17:39, Digital Man wrote to Bill McGarrity <=-
Once again.... a dilemma...
I was lead to the understanding incoming email could be then posted to a
sub using the sub:<intcode> in the alias.cfg. I have created a user called MTAINFO and signed up for a service that will send email TO: mtainfo@tequilamockingbirdonline.net. This service offers different information using different sending addresses but all with the same host.
In the alias.cfg I put the following line:
MTAINFO sub:1nyctinfo
When the email comes in addressed to mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:
1400 !SMTP lirr@alerts.mta.info (user #0) cannot post on NYCT/MTA Srv Information (Reason 690)
So I went a step further and added to alias.cfg:
lirr@alerts.mta.info sub:1nyctinfo
Same message.
Does each email address need to have a user #?
No. Check the posting requirements you have set in SCFG for the
sub-board with the internal code "1nyctinfo". I suspect your posting requirements arenon-blank and therefore disallow an anonymous/unauthenticated SMTP agent from posting to the sub-board.
On 11-14-14 17:39, Digital Man wrote to Bill McGarrity <=-
Once again.... a dilemma...
I was lead to the understanding incoming email could be then posted to a sub using the sub:<intcode> in the alias.cfg. I have created a user
called MTAINFO and signed up for a service that will send email TO:
mtainfo@tequilamockingbirdonline.net. This service offers different information using different sending addresses but all with the same
host.
In the alias.cfg I put the following line:
MTAINFO sub:1nyctinfo
When the email comes in addressedto
mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:
1400 !SMTP lirr@alerts.mta.info (user #0) cannot post on NYCT/MTA Srv Information (Reason 690)
So I went a step furtherand added to alias.cfg:
lirr@alerts.mta.info sub:1nyctinfo
Same message.
Does each email address need to have a user #?
No. Check the posting requirements you have set in SCFG for the sub-board withthe internal code "1nyctinfo". I suspect your posting requirements are non-blank and therefore disallow an anonymous/unauthenticated SMTP agent from posting to the sub-board.
OK... what I found was the posting requirements was blank but the group access requirement was level 50. I created a new group and left everything blank and it works fine.
Thanks again DM...
On 11-15-14 20:02, Digital Man wrote to Bill McGarrity <=-
On 11-14-14 17:39, Digital Man wrote to Bill McGarrity <=-
Once again.... a dilemma...
I was lead to the understanding incoming email could be then posted to a sub using the sub:<intcode> in the alias.cfg. I have created a user called MTAINFO and signed up for a service that will send email TO: mtainfo@tequilamockingbirdonline.net. This service offers different information using different sending addresses but all with the same
host.
In the alias.cfg I put the following line:
MTAINFO sub:1nyctinfo
When the email comes in addressed to
mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:
1400 !SMTP lirr@alerts.mta.info (user #0) cannot post on NYCT/MTA Srv Information (Reason 690)
So I went a step further and added to alias.cfg:
lirr@alerts.mta.info sub:1nyctinfo
Same message.
Does each email address need to have a user #?
No. Check the posting requirements you have set in SCFG for the
sub-board with the internal code "1nyctinfo". I suspect your posting requirements are non-blank and therefore disallow an anonymous/unauthenticated SMTP agent fromposting to the sub-board.
OK... what I found was the posting requirements was blank but the group access requirement was level 50. I created a new group and left everything blank and it works fine.
Thanks again DM...
Sure. You could also use requirements like "LEVEL 50 OR USER=0" to
allow an authenticated user (e.g. SMTP agent) to have access.
On 11-14-14 17:39, Digital Man wrote to Bill McGarrity <=-
Once again.... a dilemma...
I was lead to the understanding incoming email could be then posted to a sub using the sub:<intcode> in the alias.cfg. I have created a user
called MTAINFO and signed up for a service that will send email TO:
mtainfo@tequilamockingbirdonline.net. This service offers different information using different sending addresses but all with the same
host.
In the alias.cfg I put the following line:
MTAINFO sub:1nyctinfo
When the email comes in addressedto
mtainfo@tequilamockingbirdonline.net say from lirr@alerts.mta.info I get an error stating:
1400 !SMTP lirr@alerts.mta.info (user#0) cannot post on NYCT/MTA Srv Information (Reason 690)
So I went a step furtherand added to alias.cfg:
lirr@alerts.mta.info sub:1nyctinfo
Same message.
Does each email address need to have a user #?
No. Check the posting requirements you have set in SCFG for the sub-board withthe internal code "1nyctinfo". I suspect your posting requirements are non-blank and therefore disallow an anonymous/unauthenticated SMTP agent from posting to the sub-board.
OK... what I found was the posting requirements was blank but the group access requirement was level 50. I created a new group and left everything blank and it works fine.
Thanks again DM...
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 96 |
Nodes: | 16 (0 / 16) |
Uptime: | 05:40:29 |
Calls: | 4,635 |
Calls today: | 8 |
Files: | 8,491 |
Messages: | 348,367 |
Posted today: | 1 |