Hello all.
Stevan, you might be able to answer this one.
When using client/daemon mode, communication usually is done through
DLMTP right?
Happens that i was testing some stuff and i found out that if i use a
non email address in the --user part, the server refuses to process the
message.
--- snip ---
@400000004bc885010c7d7ca4 12725: [04/16/2010 16:40:39] process mode:
'--client --stdout --deliver=innocent,spam '
@400000004bc885010c7dea04 12725: [04/16/2010 16:40:39] SEND: 250 2.1.0 OK
@400000004bc88501114005f4 12725: [04/16/2010 16:40:39] SRECV: RCPT TO: <hm>
@400000004bc8850111400dc4
@400000004bc8850111409294 12725: [04/16/2010 16:40:39] SEND: 503 5.1.2
Invalid RCPT TO. Use RCPT TO: <recipient>
@400000004bc885011604aa54 12725: [04/16/2010 16:40:39] SRECV: QUIT
@400000004bc885011604b224
@400000004bc8850116052b3c 12725: [04/16/2010 16:40:39] SEND: 250 2.0.0 OK
--- snip ---
I've tracked it down to daemon.c
if (_ds_extract_address(username, cmdline, sizeof(username)) ||
username[0] == 0 || username[0] == '-' || username[0] == '@' ||
_ds_validate_address(username) == 0)
{
daemon_reply(TTX, LMTP_BAD_CMD, "5.1.2", ERR_LMTP_BAD_RCPT);
goto GETCMD;
}
and the only one that i can associate with a failure, while providing
--user hm, is _ds_validate_address()
In fact, in _ds_validate_address(), right in the middle we find
/* Next validate the domain part (local_p...@domain_part.tld) */
if (!*(domain = ++p)) return 0;
Please correct me if i'm wrong, but appears that in client/daemon mode,
at the moment, only email addresses are supported.
Regards,
Hugo Monteiro.
--
fct.unl.pt:~# cat .signature
Hugo Monteiro
Email : hugo.monte...@fct.unl.pt
Telefone : +351 212948300 Ext.15307
Web : http://hmonteiro.net
Divisão de Informática
Faculdade de Ciências e Tecnologia da
Universidade Nova de Lisboa
Quinta da Torre 2829-516 Caparica Portugal
Telefone: +351 212948596 Fax: +351 212948548
www.fct.unl.pt ap...@fct.unl.pt
fct.unl.pt:~# _
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Dspam-devel mailing list
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel
